FXO and MGCP gateway

Unanswered Question
Aug 9th, 2009
User Badges:

Hi There,


I've configured a cisco 2801 with a VIC2-2FXO card as an MGCP gateway on our CUCM 7.0. Connecting a single PSTN line on to the FXO port.

The gateway registers ok in call manager so as the route list does. The gateway is assigned correctly in the route group and in turn this in the route list and route patterns. I've made sure the partition assigned to the route patterns is assigned properly to the CSS of the gateway and the phone device I'm using for testing.


I am not able to make any outbound calls neither i can receive any calls. This is the debug out put of "debug vpm signal" in the router (gateway), only when i ring the inbound number, i get nothing when making calls.


*Aug 10 07:12:57.262: htsp_process_event: [0/3/1, FXOGS_ONHOOK, E_DSP_SIG_0100]fxogs_onhook_tip_ground

*Aug 10 07:12:57.262: htsp_timer - 7000 msec

*Aug 10 07:12:57.950: htsp_process_event: [0/3/1, FXOGS_TIP_GROUND, E_DSP_SIG_0100]

*Aug 10 07:12:57.950: fxogs_stop_disc_timer

*Aug 10 07:12:57.950: htsp_timer_stop2

*Aug 10 07:12:58.350: htsp_process_event: [0/3/1, FXOGS_TIP_GROUND, E_DSP_SIG_1100]fxogs_ringing_disc

*Aug 10 07:12:58.350: htsp_timer_stop

*Aug 10 07:12:58.350: htsp_timer_stop2

*Aug 10 07:12:58.350: htsp_timer_stop3

*Aug 10 07:12:59.978: htsp_process_event: [0/3/1, FXOGS_ONHOOK, E_DSP_SIG_0100]fxogs_onhook_tip_ground

*Aug 10 07:12:59.978: htsp_timer - 7000 msec

*Aug 10 07:13:01.078: htsp_process_event: [0/3/1, FXOGS_TIP_GROUND, E_DSP_SIG_0100]

*Aug 10 07:13:01.078: fxogs_stop_disc_timer

*Aug 10 07:13:01.078: htsp_timer_stop2

*Aug 10 07:13:01.482: htsp_process_event: [0/3/1, FXOGS_TIP_GROUND, E_DSP_SIG_1100]fxogs_ringing_disc

*Aug 10 07:13:01.482: htsp_timer_stop

*Aug 10 07:13:01.482: htsp_timer_stop2

*Aug 10 07:13:01.482: htsp_timer_stop3


Can any one please give us a hand interpreting or solving this?


Cheers,


Esteban





  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Nicholas Matthews Mon, 08/10/2009 - 03:59
User Badges:
  • Red, 2250 points or more

Hi Esteban,


You're likely using the wrong type of signaling. It is not likely that your connection is ground start.


Change this to loop start and this will probably work.


You can change it in CUCM (and should), but can test with:


voice-port 0/3/1

signal loop

shut

no shut



-nick

egua5261 Mon, 08/10/2009 - 16:26
User Badges:

Hi Nick,


I've changed signalling to loopstart in voice-port 0/3/1 as your recommendation as well as in call manager. But unfortunately it still does not work. This is the debug output i now get for inbound calls,


*Aug 11 10:09:26.094 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

*Aug 11 10:09:26.794 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

*Aug 11 10:09:28.830 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

*Aug 11 10:09:29.922 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

*Aug 11 10:09:31.826 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

*Aug 11 10:09:32.918 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0100]


It seems to me that it is the right output. The thing is that I configured the gateway with an Attendant DN that is configured to forward a call to an external mobile number. I tested calling external numbers directly from another device that is registered in call manager but it does not work and no output comes under the debug vpm signal when making outbound calls. So it seems the problem to be with outbound calls. Anything else i should be looking at?


Cheers,


Esteban



egua5261 Thu, 08/13/2009 - 00:01
User Badges:

Hi There,


I have not been able to sort this out. I dont understand what is going on. I now see the following output under the "debug vpm signal" but the device phone that I have configured to the Attendant DN under the gateway config still does not ring...


*Aug 13 17:53:19.500 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

*Aug 13 17:53:19.500 AEDT: htsp_timer - 125 msec

*Aug 13 17:53:19.628 AEDT: htsp_process_event: [0/3/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

*Aug 13 17:53:19.628 AEDT: htsp_timer - 10000 msec

*Aug 13 17:53:20.188 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:22.216 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:23.316 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:25.216 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:26.316 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:28.212 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:29.316 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]

*Aug 13 17:53:29.628 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_HTSP_EVENT_TIMER]fxols_ringing_disc

*Aug 13 17:53:29.628 AEDT: htsp_timer_stop3

*Aug 13 17:53:29.628 AEDT: htsp_timer_stop

*Aug 13 17:53:31.232 AEDT: htsp_process_event: [0/3/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

*Aug 13 17:53:31.232 AEDT: htsp_timer - 125 msec

*Aug 13 17:53:31.360 AEDT: htsp_process_event: [0/3/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

*Aug 13 17:53:31.360 AEDT: htsp_timer - 10000 msec

*Aug 13 17:53:32.320 AEDT: htsp_process_event: [0/3/1, FXOLS_RINGING, E_DSP_SIG_0000]



Can anyone help?


Regards,


Esteban

Actions

This Discussion