SOLVED Simonics outbound from a Cisco Phone

[lrosenman]

when I set everything up, inbound works great, but outbound appears to be dropping the Area Code:

Audio is at 15954
Adding codec ulaw to SDP
Adding codec alaw to SDP
Adding codec gsm to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (NAT) to 104.236.102.59:5060:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.200.91:5060;branch=z9hG4bK5abb8e41;rport
Max-Forwards: 70
From: "Larry Rosenman" <sip:[email protected]>;tag=as6a9f4ab9
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: [email protected]:5060
CSeq: 103 INVITE
User-Agent: FPBX-12.0.74(13.6.0)
Authorization: Digest username="GV12146429640x2", realm="GVGW", algorithm=MD5, u ri="sip:[email protected]", nonce="6ed7e084c0316f616062fb740f839b4e.145 3084935", response="02efaf2113cde6879beac0b40c4ef14a"
Date: Mon, 18 Jan 2016 02:42:14 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 532


I had dialed 2146422187
HELP

 

[tbrummell]

Check your Outbound route, looks like you are stripping digits in there.

 

[lrosenman]

I didn't see anything there that was obvious. I'll get a screenshot when I'm back at home....

 

[tbrummell]

Specifically check to see if you have "214" in the Prefix section, and a "1" in the Prepend section. That's what it looks like the manipulation is doing, removing 214 and adding a 1. This could also be manipulated in the Trunk programming as well, so check there too.

 

[lrosenman]

214 does NOT appear ANYWHERE in either the trunk or outbound route

This is fairly generic IPBX

 

[tbrummell]

Weird. OK, then a capture of the INVITE sent from the IP Phone to the pbx would be helpful. Maybe the Cisco dialplan is messing up the invite?

 

[lrosenman]

AFAIK the Cisco dialplan is the standard US/NA one, but I'll attach that and capture the invite tonight.

Thanks for the consideration

 

[lrosenman]

Ok, it was me being stupid and not understanding the prefix field. Once I changed the outbound route to be
1(prepend), blank prefix, and NXXNXXXXXX it works perfectly.

I'll get this figured out one of these years.

Thanks for the clue-by-four upside the head

 

[tbrummell]

Yeah, the terminology used in the dialplan can be confusing. Basically, the prefix field is used as the "Dial X to get an outside line" digit. If you want to match certain area codes to a route you need to do it in the "Match Pattern" field.

 

[lrosenman]

Thanks!