Re: [OpenSIPS-Users] SIP Status 486 goes to onreply instead of failure route
Hi Mike, All replied do get first in onreply_route (provisional, success or failure). After that, only the negative replies trigger the failure route. See : http://www.opensips.org/Resources/DocsCoreRoutes16 Regards, Bogdan Mike O'Connor wrote: > Hi All > > Is there any way that I could have broken or changed something which > would cause a sip busy (486) to go to onreply route instead of failure > route ? > > Thanks > Mike > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] SIP Status 486 goes to onreply instead of failure route
On 10/01/10 9:07 PM, Mike O'Connor wrote: > Hi All > > Is there any way that I could have broken or changed something which > would cause a sip busy (486) to go to onreply route instead of failure > route ? > > Thanks > Mike > > > Ok that is strange: This call was ok it processed the busy with in 1 second Jan 10 21:11:39 ser1 /usr/sbin/opensips[15100]: ONBRANCH: sip:500...@203.xx.xx.67:63968;rinstance=5e4bd7cb6192241e Jan 10 21:11:40 ser1 /usr/sbin/opensips[15103]: ONREPLY: 100 Jan 10 21:11:40 ser1 /usr/sbin/opensips[15101]: ONREPLY: 100 Jan 10 21:11:41 ser1 /usr/sbin/opensips[15102]: ONREPLY: 180 Jan 10 21:11:42 ser1 /usr/sbin/opensips[15100]: ONREPLY: 486 Jan 10 21:11:42 ser1 /usr/sbin/opensips[15100]: ACC: call missed: timestamp=1263120102;method=INVITE;from_tag=700d9c07;to_tag=5dac880f;call_id=OGVhNWJiODM0MWZhNTg1MTIwYjhkNzAzMWI3YWU2MTE.;code=486;reason=Busy Here Jan 10 21:11:42 ser1 /usr/sbin/opensips[15100]: FAILURE_ROUTE: sip:500...@203.xx.xx.67:63968;rinstance=5e4bd7cb6192241e Where as this took over 30 seconds. Jan 10 21:10:57 ser1 /usr/sbin/opensips[14756]: DEFAULTHANDLER: sip:500...@203.xx.xx.67:63968;rinstance=5e4bd7cb6192241e Jan 10 21:10:58 ser1 /usr/sbin/opensips[14754]: ONREPLY: 100 Jan 10 21:10:58 ser1 /usr/sbin/opensips[14757]: ONREPLY: 100 Jan 10 21:10:59 ser1 /usr/sbin/opensips[14755]: ONREPLY: 180 Jan 10 21:11:35 ser1 /usr/sbin/opensips[14756]: ONREPLY: 486 Jan 10 21:11:35 ser1 /usr/sbin/opensips[14756]: ACC: call missed: timestamp=1263120061;method=INVITE;from_tag=34d2750e;to_tag=95401734;call_id=NmU3M2UwYmYwNGYwMGVkNDlmNDYzZThjNDUwNzQyN2Q.;code=486;reason=Busy Here Jan 10 21:11:01 ser1 /usr/sbin/opensips[14756]: FAILURE_ROUTE: sip:500...@203.xx.xx.67:63968;rinstance=5e4bd7cb6192241e The 486 must have been going via onreply and I did not reliased this, the extra delay I was seeing must have been some sort of load issue. So unless i can find a reason please forget about this question. Thanks All Mike ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] SIP Status 486 goes to onreply instead of failure route
Hi All Is there any way that I could have broken or changed something which would cause a sip busy (486) to go to onreply route instead of failure route ? Thanks Mike ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
