Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Equinox calls failing with "+" plus sign 1

Status
Not open for further replies.

chippowell9

Technical User
Aug 18, 2005
176
US
Using Equinox on either iPhone or Android, any call with a "+" plus sign in front of it fails, such as when a phone contact is selected that is in E.164 format. It looks like 011 is added in the plus's place, like it wants to be an international call. In Equinox, the advanced setting "Apply dialing rules to '+' numbers" defaults to on, but toggling it off causes the call to fail in a different way. All other iterations of dialing work fine: 1+NPA+NXX, NPA+NXX, and even NXX is rigged to append 1NPA for intra-NPA dialing. All my other Equinox dialing rules work fine as well.

I've included my traces below. Anyone have an idea where to fix this? (Note: identifying numbers have been modified for privacy. We're pretending we're trying to dial (987) 654-3210 from extension 1234)

*** Failed call to +19876543210 with "Apply dialing rules to '+' numbers" toggled ON ***

09:40:48.488 |--INVITE-->| | | (1) T:901119876543210 F:1234 U:901119876543210

09:40:48.489 |<--Trying--| | | (1) 100 Trying

09:40:48.492 | |--INVITE-->| | (1) T:901119876543210 F:1234 U:901119876543210 P:imsorig

09:40:48.493 | |<--Trying--| | (1) 100 Trying

09:40:48.496 | |<--PUBLISH-| | (2) sips:1234@mydomain.net

09:40:48.497 | |<--Forbidd-| | (1) 403 Forbidden (Denial 1343)

09:40:48.497 | |--200 OK-->| | (2) 200 OK (PUBLISH)

09:40:48.498 |<--NOTIFY--| | | (3) <sip:1234@mydomain.net> Ev:dialog

09:40:48.498 | |----ACK--->| | (1) sip:901119876543210@mydomain.net

09:40:48.499 | |<--PUBLISH-| | (4) sips:1234@mydomain.net

09:40:48.499 |<--Forbidd-| | | (1) 403 Forbidden (Denial 1343)

09:40:48.500 |----ACK--->| | | (1) sip:901119876543210@mydomain.net

09:40:48.500 | |--200 OK-->| | (4) 200 OK (PUBLISH)

09:40:48.500 |<--NOTIFY--| | | (3) <sip:1234@mydomain.net> Ev:dialog

09:40:48.540 |--200 OK-->| | | (3) 200 OK (NOTIFY)

09:40:48.548 |--200 OK-->| | | (3) 200 OK (NOTIFY)



*** Failed call to +19876543210 with "Apply dialing rules to '+' numbers" toggled OFF ***

14:56:41.773 |--INVITE-->| | | (2) T:+19876543210 F:1234 U:+19876543210

14:56:41.774 |<--Trying--| | | (2) 100 Trying

14:56:41.777 | |--INVITE-->| | (2) T:+19876543210 F:1234 U:+19876543210 P:imsorig

14:56:41.778 | |<--Trying--| | (2) 100 Trying

14:56:41.780 | |<--PUBLISH-| | (3) sips:1234@mydomain.net

14:56:41.782 | |--200 OK-->| | (3) 200 OK (PUBLISH)

14:56:41.782 |<--NOTIFY--| | | (4) <sip:1234@mydomain.net> Ev:dialog

14:56:41.783 | |<--INVITE--| | (6) T:+19876543210 F:1234 U:+19876543210 P:eek:rigdone

14:56:41.782 |<--NOTIFY--| | | (5) <sip:1234@mydomain.net> Ev:dialog

14:56:41.783 | |--Trying-->| | (6) 100 Trying

14:56:41.784 | |--Not Fou->| | (6) 404 Not Found (No route available)

14:56:41.789 |--200 OK-->| | | (4) 200 OK (NOTIFY)

14:56:41.823 | |<----ACK---| | (6) sip:+19876543210@mydomain.net

14:56:41.824 | |<--Not Fou-| | (2) 404 Not Found

14:56:41.825 | |<--PUBLISH-| | (7) sips:1234@mydomain.net

14:56:41.829 | |----ACK--->| | (2) sip:+19876543210@mydomain.net

14:56:41.830 |<--Not Fou-| | | (2) 404 Not Found

14:56:41.831 |----ACK--->| | | (2) sip:+19876543210@mydomain.net

14:56:41.831 |<--NOTIFY--| | | (4) <sip:1234@mydomain.net> Ev:dialog

14:56:41.831 |<--NOTIFY--| | | (5) <sip:1234@mydomain.net> Ev:dialog

14:56:41.831 | |--200 OK-->| | (7) 200 OK (PUBLISH)

14:56:41.839 |--200 OK-->| | | (4) 200 OK (NOTIFY)
 
I thought there was something in CM sig groups or SM adaptations to drop the +. Obviously CM doesn't like it.

Calltype analysis tables in CM might let you take 9-011-1-NPA-NXX-XXXX and delete 4 (9011) and send to ARS
 
In the traces above: are these messages from list trace or traceSM? Either way, do you have ARS conversions and adaptation rules in place to strip out the plus? If you're getting to SM and your SBC is configured to route E.164 already, you may want to add a dial pattern to route matching patterns beginning with "+" to your SBC.
 
Kyle555 is correct that there is something in sig groups. You can prepend a + to outgoing (or turn of prepending), and you can remove, or not remove, the + on incoming.

But my opinion is the better place to handle the + is in SM's adaptations where you have the ability to manipulate digits and routing to a very high degree.
 
traceSM, @PBXNewbie4Now. Thank you for all the good suggestions everyone.
 
To update, the fix was pretty simple. I removed "011" as "Number to dial for international calls" from the Equinox dialing rules. I think the "+" pushed the number of digits over 10/NPA, so it was being read as an international call and the 011 was being automatically inserted. I don't need an automatic 011 insertion, so blanking out that field solved the problem.
 
I would suggest changing the adaptation from SM to CM to strip the plus in at least the destination.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top