How to determine the digits received from carrier

[ahren]

I am getting ready for my carrier to install a new PRI and they are asking how many digits we receive 4, 7, or 10. I think it's 7 and the installers suspect it's 7, but I don't know how to verify.

I've gone through all of the settings in 3CX and our Patton SmartNode, but I don't really know what I'm looking for. Can anyone point me in the right direction? There's got to be some test I can do or logs I can look at that will tell me how many digits we are receiving from the carrier.

 

[craigreilly]

Make a test call and see what is in the Call Log on 3cx. This should show what is coming in.

 

[JasonNadeau]

Are you replacing this PRI from another ?? If so just look at your existing inbound rules, the number of digits in your rule is the digits you're currently receiving ...

 

[ahren]

Unfortunately when I look at the logs this is all the info it's giving me:

16-May-2017 12:38:52.550 NAT/ALG check:L:151.2[Extn:1250] RESPONSE 200 on 'INVITE' - some of SIP/SDP headers contain inconsistent information or modified by intermediate hop
SIP contact header is not equal to the SIP packet source(IPort):
Contact address:192.168.106.136:5060
Received from :192.168.106.136:49156​

I have verbose logging on, but I don't see any actual phone numbers in the Activity Log. Is there some place else I should be checking?

When I run a Call Report it shows the 10 digit number and Caller ID name in the Caller ID column.

When I look at the Inbound Rules it shows all of my DIDs as 7-digit numbers in the DID/DDI number/mask field. Is that what I'm looking for?

 

[craigreilly]

if the 7 in inbound routes is working - then its 7.

But you should see something like this in the logs:
05/16/2017 11:16:22 AM - [CM500002]: Call(C:318): Info on incoming INVITE from Line:10002<<480fromxxx: Invite-IN Recv Req INVITE from 216.115.69.144:5060 tid=488a.cc5f48fff26a6c8fe908abee57a0f841.0 [email protected]: INVITE sip:look_here@70.my_IP:5060 SIP/2.0 Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK488a.cc5f48fff26a6c8fe908abee57a0f841.0 Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bK488a.51bc7e961dc92e9ac363a6274690027b.1 Via: SIP/2.0/UDP 216.115.69.132;branch=z9hG4bK488a.c7cf6e5a4c8346f0368adfabc033e9bc.0 Via: SIP/2.0/UDP 74.120.93.198:5060;branch=z9hG4bK04Bf7414c6ff08f229a Max-Forwards: 66 Record-Route: <sip:216.115.69.144;lr> Record-Route: <sip:216.115.69.132;lr> Contact: <sip:[email protected]:5060> To: <sip:+look_here@fl.gg> From: <sip:[email protected];isup-oli=61>;tag=gK046bd22d Call-ID: [email protected] CSeq: 342819 INVITE Session-Expires: 1800 Min-SE: 90 Content-Type: application/sdp P-Asserted-Identity: <sip:[email protected]> P-Charge-Info: tel:6023207626 Content-Length: 222

 

[ahren]

Ok thanks a bunch! I think the reason it wasn't showing up in the logs properly is because of that line about the "SIP headers contain inconsistent information or modified by intermediate hop" because that's right where that information should be when I compare your logs to mine.