Do you run on an online server or on your local machine? My test app runs on my laptop and it runs for days, overnights etc.
I will check with the owner of the SDK to see if he knows any solutions but I am sure that it’s related to the environment, not the SDK itself.
Meanwhile, can you implement a call function and test an outbound call to see if it’s successful when the inbound call fails.
We run the server online, the sever did not stopped for that time, I double checked that.
My test app runs on my laptop and it runs for days, overnights etc
And it still answers the call every time without restarts? Because in our case it just stops acepting the answers after some time. Maybe it’s only when the is no calls for some time.
I will check with the owner of the SDK to see if he knows any solutions but I am sure that it’s related to the environment, not the SDK itself.
Thanks, I am waiting for the answer.
Meanwhile, can you implement a call function and test an outbound call to see if it’s successful when the inbound call fails.
Could you please clarify what do you mean here?
Thanks.
Yes, I could receive and accept inbound call after days of running continuously.
Are you register `softphone` just once when app starts and you do not restart your sever? Right?
Turn on debug mode: https://github.com/ringcentral/ringcentral-softphone-ts/blob/main/demos/inbound-call.ts#L12
Make sure that you can see SIP messages.
By default, the client will send register message every 3 minutes: https://github.com/ringcentral/ringcentral-softphone-ts/blob/main/src/softphone.ts#L81
I don’t know what is wrong until you capture the SIP messages.
Turn on debug mode: https://github.com/ringcentral/ringcentral-softphone-ts/blob/main/demos/inbound-call.ts#L12
Make sure that you can see SIP messages.
By default, the client will send register message every 3 minutes: https://github.com/ringcentral/ringcentral-softphone-ts/blob/main/src/softphone.ts#L81
I don’t know what is wrong until you capture the SIP messages.
Thanks, I will check this out.
Thanks, we can see all debug logs.
It seems like this is the separate issue and it happens only when we configured redirect from main line to this user with softphone. I created a separate topic about this issue.