Flowroute PoP issues

I just got off the phone with FlowRoute support. With the new POPs my outbound calls worked fine, but DIDs failed (after retirement of the Nevada POP) with a 401 back to FW. After much fiddling and some friendly but not too knowledgeable support people at FW we found the problem. Their documentation for setting up the new POPs assumes you have no other need for CHAN_SIP. CHAN_SIP and CHAN_PJSIP can not share the same port (5060). SO…if you still have CHAN_SIP enabled inbound you need to configure an alternate port for CHAN_PJSIP. You’d need to change the listen port in the trunk setting, you’d have to open up the AWS Security Group setting to allow the alternate port (e.g. 5160), AND you have to alter the Route FW sends the calls to by appending the port (e.g. sip.myserver.com:5160). Assuming you have everything else right in your configuration you should start getting calls from FW again.