QUESTION Stripping E.164 + upon outbound route failure

[simplydrew]

A new outbound provider that I'm using requires that numbers be sent to them as E.164 with the plus symbol to be passed. Not a big deal on changing my current outbound route strategy. However, one thing that is a concern is that, if they become unavailable/down, my secondary provider preference in that outbound route will then no longer operate - because my secondary and tertiary providers do not expect E.164.

I'm trying to determine how, upon Asterisk receiving a 503 or something similar that would trigger it to go to the next route in the list, how I'd instruct FreePBX to remove the + if having to route the call out of the secondary or tertiary provider.

I've tried messing around with "Optional Destination on Congestion" and selecting a trunk, but that doesn't have a logical flow to egress the call (absence of another outbound route). Should I just setup another outbound route with the same dial plan (minus the +) and move it underneath whatever my first outbound route is?

 

[dicko]

You should do that digit manipulation on your individual trunks not your outbound routes, you should probably "normalize" your incoming CallerID's to strip the initial +1 if there and replace + with 011 if the next digit is not 1 otherwise, as most landlines in NANP land don't have that key and it will confuse directories and callbacks from your phones. Then arrange for 10 or 11 digit (or both for ubiquity) dialing as appropriate for your locale.

 

[simplydrew]

You should do that digit manipulation on your individual trunks not your outbound routes, you should probably "normalize" your incoming CallerID's to strip the initial +1 if there and replace + with 011 if the next digit is not 1 otherwise, as most landlines in NANP land don't have that key and it will confuse directories and callbacks from your phones. Then arrange for 10 or 11 digit (or both for ubiquity) dialing as appropriate for your locale.

Thanks - will take a further look at the trunks and give that a shot. Looking through the wizard for dial manipulations on my outbound trunk, that makes a little more sense now. Would my outbound routes just be changed to not prefix'ing anything, and just setup my prefixes at the trunk level? Just wondering what needs to be switched and where.

Good point on the inbound CID. I am receiving + on inbound CID, which is probably an issue that I haven't experienced yet on redials from call logs, etc. I'm imaging so far that if I change the context to "from-pstn-e164-us" that should resolve it for the inbound side.

 

[dicko]

[from-pstn-e164-us] is a good place to start to understand NANP dialing , just do the reverse on outbound trunks if necessary.