cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1395
Views
0
Helpful
3
Replies

Outbound Caller ID issue using CUCM 8.6,MGCP gateway & PRI lines

gyanendra88
Level 1
Level 1

Hi,

We have two DID range from our service provider: 02825911XX & 02829212XX

02825911XX maps to extension 11XX

02829212XX maps to extension 12XX.

We have 2 E1 lines 60 Channels.

Current setup:

CUCM (8.6.2) <----MGCP----> Gateway (2921) <======2 E1=====> Carrier/ Teleco.

Issue:

When calling from 11XX we are getting correct caller id 02825911XX.

But when calling from 12XX we are getting caller ID 02825911XX instead of 02829212XX.

eg: when calling from 1206 far end caller id shows 0282591106 instead of 0282921206.

There is no issue in incoming calls on both the ranges.

 

The external mask are correctly configured under the DN.

 

The debug ISDN q931 shows the correct caller id till the gateway:

 ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x016A
    Sending Complete
    Bearer Capability i = 0x8090A3
        Standard = CCITT
        Transfer Capability = Speech  
        Transfer Mode = Circuit
        Transfer Rate = 64 kbit/s
    Channel ID i = 0xA98396
        Exclusive, Channel 22
    Display i = 'test'
    Calling Party Number i = 0x0081, '0282921206'
        Plan:Unknown, Type:Unknown
    Called Party Number i = 0x80, '82353587'
        Plan:Unknown, Type:Unknown

Attaching ccapi inout & isdn q931 debug. & Gateway config.

 

1 Accepted Solution

Accepted Solutions

Amarjeet Saini
Level 1
Level 1

Hello Gyanendra,

 

 

I have checked the debug and gateway configuration. 

 

These debug are taken from gateway. The gateway shows TX- Setup. Once we have sent  setup information to Telco, I don't think we can change the calling ID information. This means that we are sending correct calling party number information to Telco(0282921206). 

May be Telco is changing the calling party number on their own? Have you checked with Telco as yet? If no, ask them what's the calling party number they are getting. You can do a live test and trace same call with Telco engineer.

 

The trace log details:

 

Sep 10 00:49:25.410: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x016A 
Sending Complete 
Bearer Capability i = 0x8090A3 
Standard = CCITT 
Transfer Capability = Speech  
Transfer Mode = Circuit 
Transfer Rate = 64 kbit/s 
Channel ID i = 0xA98396 
Exclusive, Channel 22 
Display i = 'Ludvik Aunedi' 
Calling Party Number i = 0x0081, '0282921206' 
Plan:Unknown, Type:Unknown 
Called Party Number i = 0x80, '82353587' 
Plan:Unknown, Type:Unknown
Sep 10 00:49:26.222: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x816A 
Channel ID i = 0xA98396 
Exclusive, Channel 22
Sep 10 00:49:26.222: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x816A
Sep 10 00:49:26.258: //6444/9E3008C18C96/CCAPI/ccCallModifyExtended:
   Nominator=0x2B305B60, Params=0x2B304D78, Call Id=6444
Sep 10 00:49:26.258: //6445/9E3008C18C96/CCAPI/ccCallModify:
   Nominator=0x18E30, Params=0x2B304F80, Call Id=6445
Sep 10 00:49:26.258: //6444/9E3008C18C96/CCAPI/cc_api_call_modify_done:
   Result=0, Interface=0x2AF52C6C, Call Id=6444
Sep 10 00:49:26.262: //6445/9E3008C18C96/CCAPI/cc_api_call_modify_done:
   Result=0, Interface=0x2AD55F80, Call Id=6445
Sep 10 00:49:29.406: //6444/9E3008C18C96/CCAPI/cc_handle_inter_digit_timer:
   Generate inter-digit timeout CC_EV_CALL_DIGIT_END event
Sep 10 00:49:35.262: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8  callref = 0x816A
Sep 10 00:49:35.266: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x016A
 
Also, can you do another test call and attach:
debug mgcp packet along with debug isdn q931  and CCAPI inout
 
 
Regards,
Amarjeet
 

View solution in original post

3 Replies 3

Amarjeet Saini
Level 1
Level 1

Hello Gyanendra,

 

 

I have checked the debug and gateway configuration. 

 

These debug are taken from gateway. The gateway shows TX- Setup. Once we have sent  setup information to Telco, I don't think we can change the calling ID information. This means that we are sending correct calling party number information to Telco(0282921206). 

May be Telco is changing the calling party number on their own? Have you checked with Telco as yet? If no, ask them what's the calling party number they are getting. You can do a live test and trace same call with Telco engineer.

 

The trace log details:

 

Sep 10 00:49:25.410: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x016A 
Sending Complete 
Bearer Capability i = 0x8090A3 
Standard = CCITT 
Transfer Capability = Speech  
Transfer Mode = Circuit 
Transfer Rate = 64 kbit/s 
Channel ID i = 0xA98396 
Exclusive, Channel 22 
Display i = 'Ludvik Aunedi' 
Calling Party Number i = 0x0081, '0282921206' 
Plan:Unknown, Type:Unknown 
Called Party Number i = 0x80, '82353587' 
Plan:Unknown, Type:Unknown
Sep 10 00:49:26.222: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x816A 
Channel ID i = 0xA98396 
Exclusive, Channel 22
Sep 10 00:49:26.222: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x816A
Sep 10 00:49:26.258: //6444/9E3008C18C96/CCAPI/ccCallModifyExtended:
   Nominator=0x2B305B60, Params=0x2B304D78, Call Id=6444
Sep 10 00:49:26.258: //6445/9E3008C18C96/CCAPI/ccCallModify:
   Nominator=0x18E30, Params=0x2B304F80, Call Id=6445
Sep 10 00:49:26.258: //6444/9E3008C18C96/CCAPI/cc_api_call_modify_done:
   Result=0, Interface=0x2AF52C6C, Call Id=6444
Sep 10 00:49:26.262: //6445/9E3008C18C96/CCAPI/cc_api_call_modify_done:
   Result=0, Interface=0x2AD55F80, Call Id=6445
Sep 10 00:49:29.406: //6444/9E3008C18C96/CCAPI/cc_handle_inter_digit_timer:
   Generate inter-digit timeout CC_EV_CALL_DIGIT_END event
Sep 10 00:49:35.262: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8  callref = 0x816A
Sep 10 00:49:35.266: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x016A
 
Also, can you do another test call and attach:
debug mgcp packet along with debug isdn q931  and CCAPI inout
 
 
Regards,
Amarjeet
 

Thank you guys the issue was with carrier/teleco end. They hadn't actually enable the 2nd range form line perspective &  had NATL configed for 2 digits. We are now going to ask them to change it to NATL 6 Digits.

Vivek Batra
VIP Alumni
VIP Alumni

You have very limited choice other than to contact your service provider. Beside you can collect the debug from other line where correct ANI is being sent and see the Plan/Type. 

Try changing Type to subscriber/national etc and see if it makes any difference.