John Paul Kendall
asked on
Cisco Call Manager MGCP Outbound Caller ID showing "restricted" on HD enabled Mobile phones only
Hello,
Can anyone point me in the right direction? There are a few google hits for this problem, so it seems like a known issue.
///////Summary: On outbound calls, we are sending out caller ID, and it is showing as "restricted" on HD enabled mobile phones only. Older mobile phones and land lines display our caller ID correctly. The telco PSTN providers have all pointed to our call manager as not providing the correct 1TU-T E.164 standard. This is occurring on all 5 MGCP gateway PRI's across multiple local PSTN providers.
///////System Parameters
We have 2 call managers in our HA cluster, 1 publisher, 1 subscriber.
Cisco Unified CM Administration
System version: 10.0.1.12900-2
VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, disk 1: 80Gbytes, 4096Mbytes RAM, Partitions aligned
///////Troubleshooting Steps
Here is the support forum posting of the same issue, I have performed the changes advised in this posting with no success:
https://supportforums.cisco.com/discussion/12746556/debug-caller-id
1) Under Service Parameters - Clusterwide Parameters - Calling Party Number Screening Indicator
Set this value to Callmanager Provides Calling Number (No success)
2) I have performed the changed to Call routing information - Outbound calls, tested with Calling Party IE type as both "national/ISDN", Calling Numbering plan "ISDN". No success.
Here are our test call DNs appearing in the debug isdnq931:
May 4 11:44:02: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x013F
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, 'XXXXXXXXXX'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, 'XXXXXXXXXX'
Plan:Unknown, Type:Unknown
May 4 11:44:02: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x813F
Channel ID i = 0xA98397
Exclusive, Channel 23
Can anyone point me in the right direction? There are a few google hits for this problem, so it seems like a known issue.
///////Summary: On outbound calls, we are sending out caller ID, and it is showing as "restricted" on HD enabled mobile phones only. Older mobile phones and land lines display our caller ID correctly. The telco PSTN providers have all pointed to our call manager as not providing the correct 1TU-T E.164 standard. This is occurring on all 5 MGCP gateway PRI's across multiple local PSTN providers.
///////System Parameters
We have 2 call managers in our HA cluster, 1 publisher, 1 subscriber.
Cisco Unified CM Administration
System version: 10.0.1.12900-2
VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, disk 1: 80Gbytes, 4096Mbytes RAM, Partitions aligned
///////Troubleshooting Steps
Here is the support forum posting of the same issue, I have performed the changes advised in this posting with no success:
https://supportforums.cisco.com/discussion/12746556/debug-caller-id
1) Under Service Parameters - Clusterwide Parameters - Calling Party Number Screening Indicator
Set this value to Callmanager Provides Calling Number (No success)
2) I have performed the changed to Call routing information - Outbound calls, tested with Calling Party IE type as both "national/ISDN", Calling Numbering plan "ISDN". No success.
Here are our test call DNs appearing in the debug isdnq931:
May 4 11:44:02: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x013F
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, 'XXXXXXXXXX'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, 'XXXXXXXXXX'
Plan:Unknown, Type:Unknown
May 4 11:44:02: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x813F
Channel ID i = 0xA98397
Exclusive, Channel 23
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.