What causes 32 seconds disconnection?
A 32-second disconnection issue is caused by a broken ACK.
- The SIP server will be sending 200ok Messages to confirm a call has been answered and is expecting an ACK message for its 200ok which will acknowledge that the UA is ready to accept the call.
- The ACK messages are not send beyond the first hop as the SIP server did not accept its format.
Instead, the SIP server continues to send 200ok messages until it receives a correctly build ACK message.
The ACK message is broken. - After 32 seconds, the SIP server will give up and will send a BYE message that terminates the call.
If you have another (brand) device, please try if that has the same issue.
If you can't get it solved on your side, do get in touch with us and we can try and help you solve this.
Last updated: 01/01/2024
© Voyced
All information provided is copyrighted and purely informative in nature. It is maintained by Voyced with the greatest of care using reliable sources only.
Given the fast evolution of the telecom sector, Voyced does not offer any guarantee about the accuracy and completeness of the information offered.
We explicitly do not give anyone permission to use this information in any other way than to inform themselves about what (legal) requirements there may be and they need to comply with when registering Services and/or DIDs with Voyced.
