|Summary:||ASTERISK-19369: SIP timeout to peer causes hangup, call does not continue to next priority.|
|Reporter:||Ross Beer (rossbeer)||Labels:|
|Date Opened:||2012-02-15 10:38:43.000-0600||Date Closed:||2012-10-19 11:03:49|
|Description:||When dialling a peer that has a long registration period and the peer goes off-line, after a short wait the call is hung up.|
As this is a dial attempt, the call should continue to the next priority with the DIALSTATUS variable set, not just end the call.
|Comments:||By: Matt Jordan (mjordan) 2012-10-03 16:01:58.796-0500|
I apologize; I know this issue was filed quite awhile ago and put on the queue. Can you provide your sip.conf and a snippet of dialplan that reproduces this? Even better would be a DEBUG log with sip set debug on.
I think the part that I'm confused about is the order of operations here. Does the peer itself fail to register and the registration expire? Or does the peer unregister itself by sending a REGISTER request with an expiry of 0? In either case, does that happen before or during the dial?
By: Matt Jordan (mjordan) 2012-10-19 11:03:36.771-0500
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines
By: Ross Beer (rossbeer) 2013-03-09 13:16:23.732-0600
If a registered peer goes offline where the registration period is set to 3600, the call does not failover to the next priority. However it does after the registration period expires.
For example a device may register and then either the internet connection goes offline or the power fails. If either of these cases occur and a 'Dial' is attempted to the device the call will hangup after a timeout instead of going to the the next priority.