Did 5.5.3 break the iPhone App?

[mcleone8087]

We upgraded to version 5.5.3 and now the iPhone app cannot call the cell phone. I see this in the error logs - SIP call failed when dialing 91xxxxxxxxxx using PAETEC . Check the status of the provider on the System Status page.

I can call the number directly and when using cascade and ring all rules just not using the app.

Any one else run into this?

-Mike

[sterlingmarking]

I'd do a sip packet capture on the server and see what the sip error is. It may be sending the wrong digits through the api (either sending the 9 or dropping it when the provider needs it).

Use wireshark to open the pcap file, then click telephony -> voip calls in the menu to find the call that's failing.

[hiltonmw]

I just tested our system with my iPhone APP and it works as expected.

I dialed a number using the Switchvox iPhone App and used "call using Switchvox". Worked like a charm. We're using a PRI, though.

[kmeshane]

I have a client having the same exact issue on 5.5.3 and the provider is PaeTec. Same exact issue. Worked prior to upgrade, now it does not....

From packet capture it appears it's not following caller ID rules, so at least in this case we're sending a 4 digit extension, which PaeTec is rejecting due to not matching an "assigned" DID.

We have pure SIP/VoIP integration with PaeTec, no session border controller or PRI handoff. Just pure SIP

Waiting on Digium Support ticket to investigate further.

[sterlingmarking]

I have a similar issue logged with support, except opposite. We were using call forwarding to cell phones, and before 5.5.2 the calls would come to the cell phone as the extension number that dialed, now they come through as our pilot number set in the provider. they appear to have changed the way caller id is maintained in the system.