Solved: Issues with incoming calls CUCM 8.5 - Page 2

divine007 · ‎06-03-2015

Outgoing calls works perfectly

but incoming don't work, can someone advice

here are the #debug mgcp events

3900series#
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(208):[lvl=0]MGCP sys msg: (EXTERNAL_EVENT)
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_sys_ev(69):[lvl=0]xlate sys msg: (EXTERNAL_EVENT, 264873C)
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(217):[lvl=0]sys msg values: (INVALID MGCP EVENT, 0, , 0, CALL_IDLE)
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_handle_cmapp_event(441):[lvl=0]process
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_cmapp_send_keepalive(286):[lvl=0]send NTFY KeepAlive
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/send_mgcp_empty_notify_msg(3675):[lvl=1]endpt *, complete_endpt *@3900series
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_get_ne_info(2768):[lvl=1]Used endpoint NE 192.168.0.3
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_enq_retx_msg(911):[lvl=0]trans_id 402909875,ntfy_ent 192.168.0.3
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_root_get_profile(1905):[lvl=0]Entered
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/MGCP_NEDB_get_next_addr(1211):[lvl=1]
NOTIFY ENTITY = 192.168.0.3
next->192.168.0.3
<END>
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_add_trans_id_rec(1167):[lvl=1]Add trans id (402909875, 18189B38) record
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 0, duration 500
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 15, duration 20000
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/send_mgcp_empty_notify_msg(3738):[lvl=2]NTFY Packet sent successfully - *
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 192.168.0.3, total=1462, succ=1461, failed=0
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3507):[lvl=0] : <NEW MGCP MSG From CA>
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6876):[lvl=0]Entered
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 192.168.0.3, total=1462, succ=1462, failed=0
*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6948):[lvl=1]Removing msg : NTFY 402909875 *@3900series MGCP 0.1
X: 0
O:

*Jun 3 10:41:20.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_socket(3618):[lvl=0]Entered
3900series#
3900series#
3900series#
3900series#
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(208):[lvl=0]MGCP sys msg: (EXTERNAL_EVENT)
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_sys_ev(69):[lvl=0]xlate sys msg: (EXTERNAL_EVENT, 2648750)
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(217):[lvl=0]sys msg values: (INVALID MGCP EVENT, 0, , 0, CALL_IDLE)
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_handle_cmapp_event(441):[lvl=0]process
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_cmapp_send_keepalive(286):[lvl=0]send NTFY KeepAlive
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/send_mgcp_empty_notify_msg(3675):[lvl=1]endpt *, complete_endpt *@3900series
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_get_ne_info(2768):[lvl=1]Used endpoint NE 192.168.0.3
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_enq_retx_msg(911):[lvl=0]trans_id 402909876,ntfy_ent 192.168.0.3
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_root_get_profile(1905):[lvl=0]Entered
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/MGCP_NEDB_get_next_addr(1211):[lvl=1]
NOTIFY ENTITY = 192.168.0.3
next->192.168.0.3
<END>
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_add_trans_id_rec(1167):[lvl=1]Add trans id (402909876, 18189B38) record
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 0, duration 500
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 15, duration 20000
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/send_mgcp_empty_notify_msg(3738):[lvl=2]NTFY Packet sent successfully - *
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 192.168.0.3, total=1463, succ=1462, failed=0
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3507):[lvl=0] : <NEW MGCP MSG From CA>
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6876):[lvl=0]Entered
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 192.168.0.3, total=1463, succ=1463, failed=0
*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6948):[lvl=1]Removing msg : NTFY 402909876 *@3900series MGCP 0.1
X: 0
O:

*Jun 3 10:41:35.443: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_socket(3618):[lvl=0]Entered

Nadeem Ahmed · ‎06-04-2015

Hello Neba,

You can't directly to SP and asking for that until you figure out its your service provider who is not sending CLID.

Is calls coming on PRI ? if yes can you take debug isdn q931 to verify we are receiving it or not, if yes does it get process or is it the CUCM stripping it off . as i see you have some collecting the logs

just collect the logs this way

1) no logging console

2) no logging monitor

# logging buffer 3000000

enabled the debugs, make a test a call and also check on the MGCP GW on CUCM.

Br,

Nadeem

Br, Nadeem Please rate all useful post.

yahsiel2004 · ‎06-05-2015

What are your internal extension lengths, i.e. XXXX or XXXXXXXXX? Like Manish stated, you have to set the "significant digits" to the correct length. Unless you have a translation pattern that is converting the number, into an internal number.

HTH

Yosh

HTH Regards, Yosh