03-11-2014 12:41 PM
Hi Community.
I have three numbers that I requested to have forwarded to another number via the Telco. Two of them work fine, one does not. The two that are working fine are linked to Extension Mobility Profiles. The problematic number is pointing to a Call Tree in unity. When I dial the DID for the call tree 571.XXX.XXXX I get to the call tree successfully. When I dial 703.XXX.XXXX which is pointed to 571.XXX.XXXX I get another unity Greeting. Below I am including the activity I see on the gateway when I dial 703.XXX.XXXX. Please note there are two seperate gateways.
To me this seems like a Telco problem. I just want to make sure I am not missing anything form the Call Manager side.
GW2
Progress Ind i = 0x8188 - In-band info or appropriate now available
Mar 11 19:35:12 UTC: ISDN Se0/1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x916E
Mar 11 19:35:12 UTC: ISDN Se0/1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x116E
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x1039
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Display i = 'Sharrard, Emily'
Calling Party Number i = 0x0081, '571.MyExtension'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '1703Number that is being Forwarded'
Plan:Unknown, Type:Unknown
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x9039
Channel ID i = 0xA98397
Exclusive, Channel 23
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x9039
Progress Ind i = 0x8088 - In-band info or appropriate now available
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x9039
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x1039
GW1
Mar 11 19:34:59 UTC: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x0634
Mar 11 19:34:59 UTC: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8634
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x1C3E
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A10F02010E06072A8648CE1500040A0100
Protocol Profile = Networking Extensions
0xA10F02010E06072A8648CE1500040A0100
Component = Invoke component
Invoke Id = 14
Operation = InformationFollowing (calling_name)
Name information in subsequent FACILITY message
Calling Party Number i = 0x0080, '571MyExtension'
Plan:Unknown, Type:Unknown
Called Party Number i = 0xA1, '571Extension to Which the call is being forwarded'
Plan:ISDN, Type:National
Redirecting Number i = '!', 0x008F, '703Number that is forwarded to the number above'
Plan:ISDN, Type:National
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x1C3E
Facility i = 0x9F8B0100A11702010F020100800F4245434854454C2020202020202020
Protocol Profile = Networking Extensions
0xA11702010F020100800F4245434854454C2020202020202020
Component = Invoke component
Invoke Id = 15
Operation = CallingName
Name Presentation Allowed Extended
Name = BECHTEL
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x9C3E
Channel ID i = 0xA98381
Exclusive, Channel 1
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x9C3E
Progress Ind i = 0x8088 - In-band info or appropriate now available
Mar 11 19:35:18 UTC: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x9C3E
Display i = 'VoiceMail Srv 1'
03-15-2014 03:10 AM
Yes certainly this is a Telco issue , you need to talk with them.
There is one more solution to it by using translation on voice gateway. Convert called number 703.xxxxxx to DID of the call tree 571.XXX.XXXX before sending to CUCM.
Thanks
Manish
03-18-2014 10:07 AM
HI Manish,
Thank you for your input. We were able to get it resolved. It was a combination of Telco and Call Routing on our part. Because this particular line was routing to a call tree in Cisco Unity Connection, that was part of the issue. To resolve it we added a "Forwarded Routing Rule" in unity under 'Call Routing'.
I hope this answer can help others,
Emily
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