Flowroute E164 Handling
Posted: Thu Dec 03, 2015 6:26 pm
I'm moving to flowroute due because Allworx returns a bad ip for the public ip address and flowroute can fix this in their messaging where bandwidth.com cannot. To be clear, the problem here is how Allworx is handling the public ip address setting. If you hard set it, failing over will not work to another ip. If you leave it blank, Allworx passes along local ip data. If they allowed a failover ip or FQDN or had an ip test, my entire problem I've had with allworx since ~2009 would disappear....
I've run into a weird problem. With flowroute, they preprend a userid which is a big part of why they can deal with incorrect ip messaging from our Allworx 6x (thank goodness someone is dealing with Allworx's failure). However, when I put in the userid properly or prefix the dialing with it, the Allworx adds an additional 1 at before the userid. This goes away if I turn off E164 dialing. This additional 1 breaks the user id because... well they just randomly added another digit. Any ideas?
I've run into a weird problem. With flowroute, they preprend a userid which is a big part of why they can deal with incorrect ip messaging from our Allworx 6x (thank goodness someone is dealing with Allworx's failure). However, when I put in the userid properly or prefix the dialing with it, the Allworx adds an additional 1 at before the userid. This goes away if I turn off E164 dialing. This additional 1 breaks the user id because... well they just randomly added another digit. Any ideas?