[Spce-user] Failure route for PSTN call - 403 forbidden

[Matthias Hohl]

Oh i think i found the solution in an earlier posting:

Is there a reason why 403 is not a default failover trigger?

 

 

> 403 Does not trigger a failover by default.

> By default the codes triggering a failover are 408, 500, 503:

> 

> from /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2

> 

> route[ROUTE_FILTER_FAILOVER]

> ..

> ..

> xlog("L_INFO", "Filter reply code - S=$rs SS='$rr' M=$rm R=$ru F=$fu T=$tu
IP=$avp(s:ip):$avp(s:port)($si:$sp) UAIP=$si UA='$ua' ID=$ci \n");

> if(!t_check_status("408|500|503"))

> {

>                 xlog("L_NOTICE", "No failover routing needed for this
response code - S=$rs SS='$rr' M=$rm R=$ru F=$fu T=$tu

> IP=$avp(s:ip):$avp(s:port)($si:$sp) UAIP=$si UA='$ua' ID=$ci \n");

> 

> 

> 

> If you want to trigger a failover with 403, you should add 403 (or other

> codes) in that list, for instance:

> 

> if(!t_check_status("403|408|488|500|502|503|504|604"))

> 

> remeber to create a proxy.cfg.customtt.tt2 file and apply your changes.

 

 

Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
Matthias Hohl
Gesendet: Montag, 23. Mai 2016 11:49
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] Failure route for PSTN call - 403 forbidden

 

Hello,

 

Today I did some test with another upstream carrier and found out that they
don't accept 43 810 numbers.

I checked the log files and see that they rejected the call with "403 -
forbidden". 

After that I see that there is a "Failure route for PSTN call" log entry and
then there is also a "No failover routing needed for this response code".

 

But there should be a failover routing to another peering (my other peering
accept 43 810 numbers), if a call fails because of 403 forbidden.

How can I enable this failover routing? 

 

Thanks.

 

May 23 11:36:02 spce (local7.notice) proxy[3627]: NOTICE: <script>: Request
leaving server, D-URI='sip:127.0.0.1:5080' -
R=sip:30#4381010018633 at 94.xxx.xxx.xxx:5060;transport=udp
ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at
<mailto:ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at>
UA='Telematica PBX v1.7 R6'

May 23 11:36:02 spce (local7.notice) proxy[3621]: NOTICE: <script>:
NAT-Reply - S=100 - Connecting M=INVITE IP=176.123.55.22:5060
(127.0.0.1:5080) ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at
<mailto:ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at>  UA='<null>'

May 23 11:36:03 spce (local7.notice) proxy[3636]: NOTICE: <script>:
NAT-Reply - S=403 - Forbidden M=INVITE IP=176.123.55.22:5060
(127.0.0.1:5080) ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at
<mailto:ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at>
UA='FreeSWITCH-mod_sofia/1.5.6b+git~20131014T235757Z~850c154bd4'

May 23 11:36:03 spce (local7.notice) proxy[3636]: NOTICE: <script>: Failure
route for PSTN call - R=sip:4381010018633 at 94.xxx.xxx.xxx:5060;transport=udp
ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at
<mailto:ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at>
UA='Telematica PBX v1.7 R6'

May 23 11:36:03 spce (local7.notice) proxy[3636]: NOTICE: <script>: No
failover routing needed for this response code -
R=sip:4381010018633 at 94.xxx.xxx.xxx:5060;transport=udp
ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at
<mailto:ID=3a5b114019b8dbeb0282bfe03bdffcc8 at sip.telematica.at>
UA='Telematica PBX v1.7 R6'

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160523/e9b658f8/attachment-0001.html>