[OpenSIPS-Users] 408 timeout
volga629 at networklab.ca
volga629 at networklab.ca
Tue May 2 06:38:36 EDT 2017
Hello Everyone,
Thank you for help.
On Mon, 1 May, 2017 at 5:49 AM, Bogdan-Andrei Iancu
<bogdan at opensips.org> wrote:
> Hi,
>
> The failure route is correct and you have to arm it before sending
> out the request via the request route (before the t_relay()) with
> t_on_failure("MANAGE_FAILURE")
>
> Regards,
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> OpenSIPS Summit May 2017 Amsterdam
> http://www.opensips.org/events/Summit-2017Amsterdam.html
> On 05/01/2017 04:22 AM, volga629 at networklab.ca wrote:
>> Hello Bogdan,
>> I created fail route
>>
>> failure_route[MANAGE_FAILURE] {
>> if (t_check_status("408")) {
>> append_branch();
>> route(DISPATCH);
>> }
>>
>> if (t_was_cancelled()) {
>> exit;
>> }
>> }
>>
>> How I can detect that timer expire ? On which stage in reply need
>> apply fail route.
>>
>> volga629
>>
>> On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu
>> <bogdan at opensips.org> wrote:
>>> Hi,
>>>
>>> OpenSIPS is generating the CANCEL due to the timeout (no answer to
>>> the call) - see:
>>>
>>> http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout
>>>
>>> If you want to get a redirect to a VM, you need to use the failure
>>> route in order to catch the 408 reply and create a new branch to
>>> the VM server.
>>>
>>> Regards,
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developer
>>> http://www.opensips-solutions.com
>>>
>>> OpenSIPS Summit May 2017 Amsterdam
>>> http://www.opensips.org/events/Summit-2017Amsterdam.html
>>> On 04/29/2017 06:28 AM, volga629 at networklab.ca wrote:
>>>> Hello Alex,
>>>> So what it is
>>>>
>>>> 2017/04/28 22:12:45.455111 server_public_ip:5082 ->
>>>> client_public_ip:47293
>>>> SIP/2.0 180 Ringing
>>>> Via: SIP/2.0/TCP
>>>> 192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
>>>> Record-Route:
>>>> <sip:10.18.130.27;r2=on;lr;ftag=f30d187f;did=acf.146ecb6>
>>>> Record-Route:
>>>> <sip:server_public_ip:5082;transport=tcp;r2=on;lr;ftag=f30d187f;did=acf.146ecb6>
>>>> From: "volga629" <sip:4310 at sip.company.tld>;tag=f30d187f
>>>> To: <sip:4300 at sip.company.tld>;tag=ZH2mc6gFgS9Fg
>>>> Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
>>>> CSeq: 2 INVITE
>>>> Contact: <sip:4300 at 10.18.130.26:5160;transport=udp>
>>>> User-Agent: B2BUA01
>>>> Accept: application/sdp
>>>> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE,
>>>> REGISTER, NOTIFY, PUBLISH, SUBSCRIBE
>>>> Supported: timer, path, replaces
>>>> Allow-Events: talk, hold, conference, presence, as-feature-event,
>>>> dialog, line-seize, call-info, sla, include-session-description,
>>>> presence.winfo, message-summary, refer
>>>> Content-Length: 0
>>>>
>>>> OPENSIPS send to PBX
>>>>
>>>> 2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
>>>> CANCEL sip:4300 at sip.company.tld SIP/2.0
>>>> Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
>>>> From: "volga629"<sip:4310 at sip.company.tld>;tag=f30d187f
>>>> Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
>>>> To: <sip:4300 at sip.company.tld>
>>>> CSeq: 2 CANCEL
>>>> Max-Forwards: 70
>>>> Reason: SIP;cause=480;text="NO_ANSWER"
>>>> User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
>>>> Content-Length: 0
>>>>
>>>>
>>>>
>>>> 2017/04/28 22:13:14.639605 server_public_ip:5082 ->
>>>> client_public_ip:47293
>>>> SIP/2.0 408 Request Timeout
>>>> Via: SIP/2.0/TCP
>>>> 192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
>>>> To:
>>>> <sip:4300 at sip.company.tld>;tag=c88f800b416e86b8a763b24c260500d8-3c4f
>>>> From: "volga629"<sip:4310 at sip.company.tld>;tag=f30d187f
>>>> Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
>>>> CSeq: 2 INVITE
>>>> Server: OpenSIPS (2.4.0-dev (x86_64/linux))
>>>> Content-Length: 0
>>>>
>>>>
>>>> On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov
>>>> <abalashov at evaristesys.com> wrote:
>>>>> OpenSIPS didn't hang up anything.
>>>>>
>>>>> On April 28, 2017 10:30:08 PM EDT, volga629 at networklab.ca wrote:
>>>>>> Hello Everyone,
>>>>>> Why opensips hang up session with 408 on
>>>>>> SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
>>>>>> voicemail.
>>>>>> What way possible fix it.
>>>>>>
>>>>>> Please see attached trace.
>>>>>>
>>>>>> volga629
>>>>>
>>>>>
>>>>> -- Alex
>>>>>
>>>>> --
>>>>> Principal, Evariste Systems LLC (www.evaristesys.com)
>>>>>
>>>>> Sent from my Google Nexus.
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170502/e56e2e25/attachment.html>
More information about the Users
mailing list