-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-registration doesn't work, it registers only once. #1071
Comments
Any updates? |
The same issue exists in SIP.js v0.13.5, and it is currently suspected that this may be due to unexpected behavior of timers (registrationTimer and registrationExpiredTimer). Relevant code: https://github.com/onsip/SIP.js/blob/0.13.5/src/RegisterContext.ts#L296 Is it possible for you to provide an API for custom timer functions? For example, APIs like Related links: |
First time the registration occurs and it is successful. After 5 mins, it re-registers and goes to "Unregistered, Bye" state. After that nothing happens.
browser console log:
sip-0.20.0.min.js:2 Tue Mar 05 2024 17:44:07 GMT+0530 (India Standard Time) | sip.Registerer | An attempt was made to send a REGISTER request while a prior one was still in progress. RFC 3261 requires UAs MUST NOT send a new registration until they have received a final response from the registrar for the previous one or the previous REGISTER request has timed out. Note that if the transport disconnects, you still must wait for the prior request to time out before sending a new REGISTER request or alternatively dispose of the current Registerer and create a new Registerer.
sip-0.20.0.min.js:2 Uncaught (in promise) Error: REGISTER request already in progress, waiting for final response
at he.register (sip-0.20.0.min.js:2:110877)
at sip-0.20.0.min.js:2:116504
sip-0.20.0.min.js:2 Tue Mar 05 2024 17:44:09 GMT+0530 (India Standard Time) | sip.Registerer | Registration expired
The text was updated successfully, but these errors were encountered: