Long-Running subscription issues C# SDK

I have a winform app that will run either minimized or in the system tray. Part of its job is to display incoming caller info. I am using the C# SDK to successfully authenticate, create the subscription and then receive notification information. The problems start when I just leave the program running and no new events are coming in simulating the use case where someone leaves the program running overnight (or an extended lunch). We start to see first chance web socket exceptions, null exceptions and eventually a code break will happen and a final error will indicate that objects have been optimized away. These errors are coming from the SDK code and don't bubble up through any try/catch code so that I could handle the error.

The application is dead simple at this point. It connects, authorizes, creates a subscription and listens via callbacks. Is there a method I need to call on a timer to keep the objects alive?

Quick update. I downloaded the code from github and compiled locally. Used those in the project instead of getting the SDK from Nuget. Isolated the issue to the PubnubCore ClientNetworkStatus.cs file. Looks like the error is being thrown from the ParseCheckSocketConnectException<T> method. Looks like it believes that the Internet/socket connection was lost. Still looks like an object was caught up by garbage collection but I can't tell which one.

Got it. Just sent an email over with all of the details. I'll be happy to share the exact code that we are using to test the functionality if the instructions for recreating don't make sense in the support ticket.

Got past the gateway timeout issue with pubnub's help enabling/forcing
ssl when creating the subscription. We also found that a couple of
objects in the SDK were being disposed (picked up by garbage collection)
after long periods of inactivity. Fixed that as well. Now working on
figuring out why the Subscribe method in the SDK is throwing an error
when a disconnect message is fired (again after a long period of time
goes by simulating a user being logged in overnight).

We are continuing to test but are running into small issues at this point related to error handling for devices that rely on wireless connections or where wired connections are not as reliable. We will post the errors and where they are occurring once we nail it down.

I'll post an issue in github shortly to help correct a timeout issue when behind a proxy that is outside our control for configuration.

Saw the issues in Github for the RingCentral C# SDK, thanks for doing that Chris. Anytime there are issues with the SDK, looking in the Github issue tracker and reporting new issues if one doesn't already exist is usually a good first step towards getting it resolved.

We're working on prioritizing these issues, but any help is always welcomed, especially since the C# SDK is open source.

We have a couple of community members who need to resolve these bugs to continue moving forward, if we could get some help from the community to assign one or two of these issues and resolve with a pull request, it would help everyone. We will continue getting these prioritized, in the meantime you can use the Github issue tracker to watch or contribute. :)

Sounds like a different issue. Make sure to include "?detailedTelephonyState" at the end of the event subscription URL to get the right information. Second, if you don't have the soft phone running and logged into your test account, you will not receive presence events via the sdk.

Please use the RingCentral C# SDK which includes the PubNub C# SDK as a dependency. There should be no need to use the PubNub C# SDK directly. The RingCentral C# SDK will manage connections with PubNub and also automatically decrypt messages for you. I posted some working code in that thread using the RingCentral C# SDK which will receive and print presence events.

In the meantime, the RingCentral C# SDK is open source, and we welcome contributions from our community. Please see the Github Issue tracker for reported issues and follow the contribution documentation to become an active contributor this open source project.https://github.com/ringcentral/ringcentral-csharp/issues

Testing with the simplified code shared above. Looks like the original issues are fixed. Ran for many hours and did not see a disconnect. A new issue seems to be we are not getting subscription messages when the presence is supposed to change to "Ringing". The softphone is still configured to connect to the sandbox account and is prompting correctly for inbound calls. When watching the code execution we are getting nothing on the notification side from the subscription. Tested this out on the original code, and the simplified example shared above. No dice.