Outbound route failover

Status
Not open for further replies.
Feb 1, 2017
28
1
3
107
Have an outbound route [and this is the sole outbound route] programmed thusly:
upload_2017-2-8_21-50-14.png

Gamma_MSX17 is the active peer and Gamma_MSX9 is the standby. Gamma_MSX17 has ping enabled and the idea is that MSX17 will be used all the time, and MSX9 only gets used if MSX17 has failed.

What I can see in the logs is that occasionally calls are placed to MSX9 after being tried on MSX17:

Code:
MSX_17-leg 2017-02-08 16:01:22.576445 [DEBUG] sofia.c:7041 Channel sofia/external Active/01388528362 entering state [terminated][404]                                          
MSX_17-leg 2017-02-08 16:01:22.576445 [NOTICE] sofia.c:8212 Hangup sofia/external Active/01388528362 [CS_EXCHANGE_MEDIA] [UNALLOCATED_NUMBER]                                  
MSX_17-leg 2017-02-08 16:01:22.576445 [DEBUG] switch_ivr_bridge.c:679 sofia/external Active/01388528362 ending bridge by request from read function                            
MSX_17-leg 2017-02-08 16:01:22.576445 [DEBUG] switch_ivr_bridge.c:752 BRIDGE THREAD DONE [sofia/external Active/01388528362]
Then it's tried on MSX9:
Code:
MSX_9-leg 2017-02-08 16:01:38.476446 [DEBUG] sofia.c:7041 Channel sofia/external Standby/01388528362 entering state [terminated][404]
MSX_9-leg 2017-02-08 16:01:38.476446 [NOTICE] sofia.c:8212 Hangup sofia/external Standby/01388528362 [CS_EXCHANGE_MEDIA] [UNALLOCATED_NUMBER]
MSX_9-leg 2017-02-08 16:01:38.476446 [DEBUG] switch_ivr_bridge.c:679 sofia/external Standby/01388528362 ending bridge by request from read function
MSX_9-leg 2017-02-08 16:01:38.476446 [DEBUG] switch_ivr_bridge.c:752 BRIDGE THREAD DONE [sofia/external Standby/01388528362]

and that's the end of the call.

So my expectation here was that if I get a 404 then that would be the end of the call, but it appears in this instance that the second choice is tried even though the number is reported not to exist [the irony here (or maybe it's not an irony and I've misunderstood the meaning of a SIP 404) is that 01388528362 is actually a valid number].

Full bin of the relevant logs:
https://pastebin.freeswitch.org/view/ee47fe18
I have replaced UUID with labels for the call legs to make it readabler.
 
Last edited:

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,045
565
113
Is this causing a problem? Or if you mean it is a valid number then you would need to speak with the carrier and ask why 404.

Also, is this UK? I would expect carrier to want e164, ie 441388528362 but I could be wrong.
 
Feb 1, 2017
28
1
3
107
No, it's not causing a problem, yet, but the the carrier's intention is that we only use the two SBCs in an active/standby fashion. It's more a case of technical fussiness on my part.

Yes it's the UK. The carrier [Gamma Telecom] lets you choose what format to send calls in.

I will ask them why they give us a 404.
 
Feb 1, 2017
28
1
3
107
They tell me that they send us a 404 because that's what they got from their next hop. Their techs tested it and find that when it works, it works, but when it doesn't work, it always goes from 180 to 404 after exactly 15 seconds so they suspect something misconfigured on the destination phone system.
 
Status
Not open for further replies.