We use Sprint as a switched long distance provider. Sprint is configured to prompt for a long distance access code when certain numbers dial long distance, and not prompt for others.
Until I migrated from MGCP to H323, this worked fine. Post migration, all numbers are getting prompted for long distance access codes. This is problematic for certain numbers (fax machines) that are getting prompted to enter a long distance code.
Sprint: Call traces say that when the call comes in, they are seeing the BTN (Billing telephone number) instead of the DID (calling party number) that I should be passing along.
XO (Telco provider): They say that everything should work. I've made sure that my PRI settings match what they were previously (ISDN switch type = NI2, etc).
When I view ISDN q931 debugs, I see the calling party number as it should be.
Here is a test call with q931 debugging enabled (I intentionally replaced area codes with X):
Jun 7 08:32:19: ISDN Se2/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 13
Jun 7 08:32:19: ISDN Se2/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num XXX9463091
Jun 7 08:32:19: ISDN Se2/0:23 Q931: Sending SETUP callref = 0x0B30 callID = 0x8E85 switch = primary-ni interface = User
The only time your provider will replace the calling number with the billing number is when your calling number is not in the allocated DDI range. If you are 100% certain that the calling number is in your ddi block range then take this up with XO. XO switch is the one passing the CLI to Sprint.
The fact that they said it should work doesnt mean it will or is working. I will hold their neck tight until they figure out or tell you why they are modifying the CLI
Please rate useful posts
"I am complete in God, God completes me"
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...