[Serusers] Cancel'ing filure_route
klaus.mailinglists at pernau.at
Wed Aug 31 12:41:06 CEST 2005
Dmitry Isakbayev wrote:
> Hi Klaus,
> Thank you for pointing me to the discussion thread. Checking for code
> "487" does not help in my case. When t_relay times out, the lowest
> status is 408.
If 408 happens (timeout), then usually you will send to voicemail.
If 487 happens (cancelled by user), then usually you will do nothing.
Thus, checking for 487 is mostly fine, except the situations when a
phone is busy in an forked scenario.
> The new 't_was_cancelled' sounds really useful. I hope it takes care of
> all cases. I will test it out.
> When do you suppose the new "t_was_cancelled" function will become
> available in ser?
Just port it ;-)
> ----- Original Message ----- From: "Klaus Darilion"
> <klaus.mailinglists at pernau.at>
> To: "Dmitry Isakbayev" <isakdim at gmail.com>
> Cc: <serusers at lists.iptel.org>
> Sent: Tuesday, August 30, 2005 4:30 AM
> Subject: Re: [Serusers] Cancel'ing filure_route
>> Dmitry Isakbayev wrote:
>>> I need help understanding how to handle "CANCEL" messages. Here is
>>> the case -
>>> 1 Proxy rebuilds URI, sets 'failure_route', and executes 't_relay'
>>> 2 't_realy' times out and the proxy executes 'failure_route' after
>>> the fr_timer hits
>>> If the OUI cancels the call between steps 1 and 2, the proxy still
>>> executes the 'failure_route' after the fr_timer hits.
>>> Can I cancel any "t_on_failure" logic after receiving a CANCEL message?
>> Hi Dimitry!
>> Take a look at the openser mailinglist, were this issue was recently
>> With ser you can use if(t_check_status("487")), with openser you could
>> use the new function if(t_was_cancelled()).
>>> Or, while in in the 'failre_rout' block, can I figure out that there
>>> was a CANCEL message?
>>> Thank You,
>>> Serusers mailing list
>>> serusers at lists.iptel.org
More information about the sr-users