[Spce-user] Question about fallback SIP codes.

Jaime jaime at tnagroup.cl
Thu Sep 7 09:23:21 EDT 2017


For my version: mr4.5.4 I used the steps indicated by Andrew in https://www.sipwise.org/doc/mr4.5.4/spce/ar01s10.html#_tt2_and_customtt_tt2_files <https://www.sipwise.org/doc/mr4.5.4/spce/ar01s10.html#_tt2_and_customtt_tt2_files>

a) create a copy: cp proxy.cfg.tt2 proxy.cfg.customtt.tt2 in /etc/ngcp-config/templates/etc/kamailio/proxy/

b) added the 403 sip code to the line 6089:
# cd /etc/ngcp-config/templates/etc/kamailio/proxy/
# diff proxy.cfg.tt2 proxy.cfg.customtt.tt2 
< 	if(!t_check_status("408|500|503"))
> 	if(!t_check_status("403|408|500|503")) 

c) applied the change with:  ngcpcfg apply 'Adding fallback on 403 sip code. Jaime'

and now the route fallback works correctly for the 403 sip code.

Thank you all (and especially Andrew) for the tips.

> El 04-08-2017, a las 1:35 p.m., Jaime <jaime at tnagroup.cl> escribió:
> Hi Andrew, Thanks for the info,
> also can you please tell us the documentation about howto use  customtt ?
> Regards
> Jaime
>> El 04-08-2017, a las 5:18 a.m., Andrew Pogrebennyk <apogrebennyk at sipwise.com> escribió:
>> Hi,
>> it is possible to define your own codes in config.yml under option
>> kamailio.proxy.filter_failover_response starting from release mr5.2.1.
>> For older releases you can use a customtt.
>> Andrew
>> On 08/04/2017 01:34 AM, Jaime wrote:
>>> Hi All,
>>> I’m testing Sipwise, ver. mr4.5.4, it works fine but I’m curious if
>>> SipWise can incorporate an additional code to make Fallback in the
>>> choice of routes (peering groups).
>>> As say’s in the manual: "If a peering server replies with SIP
>>> codes |408|, |500| or |503|, or if a peering server doesn’t respond at
>>> all, the next peering server in the current peering group is tried as a
>>> fallback."
>>> The query is whether you can incorporate an additional SIP code to
>>> perform fallback, for example Sip code 403.
>>> Thanks for your help.
>>> Jaime

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20170907/12852510/attachment.html>

More information about the Spce-user mailing list