FXO Incoming Call not being routed to the destination

[Ralph John Tampilic]

Hi All,

Blessed day!

May I ask for you assistance, regarding the issue on FXO incoming calls not routed to end device only ringing (outgoing calls were working fine). It was working before we've migrated to new CUCM v.11. The VG was configured before as H323 then changed to MGCP. 

Here what I have done troubleshooting so far:

- I have checked already that the Attendant DN partition was already included to the CSS of FXO port.

- tried to default the config of fxo.

- tried to change the protocol from Loopstart to Groundstart (the incoming/outgoing calls not working so I have revert it to Loopstart).

- when I have tried removing the "connection plar opx" or changing it to "connection plar" the incoming call ring once then goes fast busy. I don't know why it was affecting the calls even the VG was already acting as MGCP.

Hopefully you can help me on this.

Regards,

Ralph

[Ralph John Tampilic]

This is what i have found:

Sep 1 04:34:25.345: htsp_process_event: [1/1/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
Sep 1 04:34:25.345: htsp_timer - 125 msec
Sep 1 04:34:25.473: htsp_process_event: [1/1/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
Sep 1 04:34:25.473: htsp_timer - 10000 msec
Sep 1 04:34:26.453: htsp_process_event: [1/1/1, FXOLS_RINGING, E_DSP_SIG_0100]
Sep 1 04:34:26.453: fxols_ringing_not
Sep 1 04:34:26.453: htsp_timer_stop
Sep 1 04:34:26.453: htsp_timer_stop3 htsp_setup_ind
Sep 1 04:34:26.453: [1/1/1] get_local_station_id calling num= calling name= calling time=09/01 12:34 orig called=
Sep 1 04:34:26.453: htsp_process_event: [1/1/1, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
Sep 1 04:34:26.453: fxols_wait_setup_ack:
Sep 1 04:34:26.453: htsp_timer - 6000 msec
Sep 1 04:34:26.453: htsp_process_event: [1/1/1, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc
Sep 1 04:34:26.457: htsp_pre_connect_disconnect, cdb = 100DAB0 cause = 26

Sep 1 04:34:26.457: htsp_process_event: [1/1/1, FXOLS_PROCEEDING, E_HTSP_PRE_CONN_DISC]
Sep 1 04:34:28.457: htsp_process_event: [1/1/1, FXOLS_OFFHOOK, E_HTSP_RELEASE_REQ]fxols_offhook_release
Sep 1 04:34:28.457: htsp_timer_stop
Sep 1 04:34:28.457: htsp_timer_stop2
Sep 1 04:34:28.457: htsp_timer_stop3
Sep 1 04:34:28.457: [1/1/1] set signal state = 0x4 timestamp = 0
Sep 1 04:34:28.457: htsp_timer - 1000 msec
Sep 1 04:34:29.457: htsp_process_event: [1/1/1, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout
Sep 1 04:34:29.457: htsp_process_event: [1/1/1, FXOLS_ONHOOK, E_DSP_SIG_0100]
Sep 1 04:34:30.393: htsp_process_event: [1/1/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

[Elliot Dierksen]

It does look like the MGCP port is registered. It looks like either a problem reaching the attendant DN, or possibly some sort of media/codec problem when connecting to the attendant DN. Can you set a phone to have the same device pool and CSS as the gateway and can you reach the attendant DN you have configured? If so, you will have to look at CCM traces, CDR info, or possibly a 'debug voip ccapi inout' in the MGCP gateway. That debug command will generate a lot of output.