07-09-2010 01:26 PM - edited 03-15-2019 11:38 PM
We have a problem where when we call from our desk phones (CUCM) to 3G wireless phones, the wireless phone will receive caller ID as “unknown number”. We contacted our telco/PRI provider to check the digit that we are sending and it was ok.
Then we contacted AT&T and made some tests and found out that the “unknown number” is only happening to 3G wireless user and it is only for local number (7-digit dialing)
AT&T said that “The Calling Party Number parameter as it is sent in from the office number is not set according to standards. The Numbering Plan is Unknown and should be ISDN/Telephony. In addition, the Screening Indicator is Reserved - User Provided,Not Screened and it should be Network Provided or "User-Provided - Screened and Passed”
Questions:
Is this some configuration in our system or with telco/PRI provider?
Thanks,
sienz
07-09-2010 02:18 PM
You can set that under your PRI/H323 config and also using calling/called party transformation patterns.
Telcos can also override and change it, but you need to start by sending it correctly from CUCM
HTH
java
If this helps, please rate
www.cisco.com/go/pdihelpdesk
07-09-2010 02:25 PM
Thanks Java,
Any documentation on making changing on our gateway?
I just did debug q931 and here is the result if anyone can help: (Thanks)
Jul 9 21:28:04.070: ISDN Se0/0/0:23 Q931: TX -> PROGRESS pd = 8 callref = 0xF865
Cause i = 0x8181 - Unallocated/unassigned number
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Jul 9 21:28:06.798: ISDN Se0/0/0:23 EVENT: process_pri_call: call id 0xB725, number 2688622, Guid 0082A73AAE3E, speed 0, call type VOICE, redial No, CSM call No, pdata Yes
*Jul 9 21:28:06.798: ISDN Se0/0/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 13
*Jul 9 21:28:06.798: ISDN Se0/0/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 13
*Jul 9 21:28:06.802: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Called num 2688622
*Jul 9 21:28:06.802: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x376E
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98393
Exclusive, Channel 19
Calling Party Number i = 0x0081, '7028582580'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '2688622'
Plan:Unknown, Type:Unknown
*Jul 9 21:28:07.054: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xB76E
Channel ID i = 0xA98393
Exclusive, Channel 19
*Jul 9 21:28:07.054: ISDN Se0/0/0:23 EVENT: process_rxstate: ces/callid 1/0xB725 calltype 2 CALL_PROCEEDING
*Jul 9 21:28:08.798: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0xB76E
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Jul 9 21:28:08.798: ISDN Se0/0/0:23 EVENT: process_rxstate: ces/callid 1/0xB725 calltype 2 CALL_PROGRESS
*Jul 9 21:28:08.830: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x7865
Cause i = 0x8090 - Normal call clearing
*Jul 9 21:28:08.830: ISDN Se0/0/0:23 EVENT: process_rxstate: ces/callid 1/0x4797 calltype 2 CALL_DISC
*Jul 9 21:28:08.830: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0xF865
*Jul 9 21:28:08.854: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x7865
*Jul 9 21:28:08.854: ISDN Se0/0/0:23 EVENT: process_rxstate: ces/callid 1/0x4797 calltype 2 CALL_CLEARED
07-09-2010 06:19 PM
07-10-2010 09:58 AM
Its a telco issue show this to them
Calling Party Number i = 0x0081, '7028582580'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '2688622'
Plan:Unknown, Type:Unknown
if we send the calling party number no amount of config will fix this issue since we already send the calling number
07-10-2010 12:09 PM
It's entirely possible that even sending calling party number the provider doesn't accept it if you are not sending the type. Please confirm from your provdier what type they would like to see.
HTH
07-10-2010 04:33 PM
Thanks all for the input, especially Javalenc.
The Calling party Number that we are sending is correct according to our telco provider but AT&T (as the receiver) said that Screening Indicator and the Numbering Plan is not acceptable to their 3G network. AT&T also confirm that they receive a good phone number but the Screening Indicator and the Numbering Plan is not acceptable.
I will try changing it on Monday based on Javalence Document.
07-10-2010 04:52 PM
They may insist that you set plan/type to their spec, but the Screening Indicator is already correctly set to "user-provided, verified and passed". Note also the Presentation Indicator is correctly set.
http://www.acacia-net.com/wwwcla/protocol/q931_ie.htm#ie_field_screening_indicator_cgpn
07-10-2010 05:53 PM
Thank you for checking it and for the link p.bevilacqua.
I will verify it again on Monday.
I guess, it may come down to "The Numbering Plan is Unknown and should be ISDN/Telephony"
Also if the screening indicator is already correctly set, the telco may override it so I will need to check to our telco provider what they are sending.
Thanks again
sienz
07-10-2010 06:08 PM
You will see that is easily solved.
What I do in similar cases, is to fix it from home during the weekend, then show up late at the office on Monday explaining how the issues took most of the day talking to telcos.
07-14-2010 09:34 AM
07-14-2010 07:23 PM
Cery good, please remember to rate useful posts clicking on the stars below.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide