Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Incoming call rings and then disconnects

I just replaced an FXO card in a 2911 router since it was having multiple issues.  Now one last issue I'm facing is that when I call the last number in the hunt sequence it rings once and disconnects.  I was running "debug vpm all" and it seems like as compared to the working line this one doesn't establishes the call all the way.  Below are the logs any ideas?

WORKING LOG:

Jan 20 12:56:35.064: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

Jan 20 12:56:35.064: TGRM: reg_invoke_tgrm_call_update(0, 0, 0, 65535, 1, TGRM_CALL_PENDING, TGRM_CALL_VOICE, TGRM_DIRECTION_IN)

Jan 20 12:56:35.064: htsp_timer - 125 msec

Jan 20 12:56:35.192: htsp_process_event: [0/0/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

Jan 20 12:56:35.192: htsp_timer - 10000 msec

Jan 20 12:56:36.440: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]

Jan 20 12:56:36.440: fxols_ringing_not

Jan 20 12:56:36.440: htsp_timer_stop

Jan 20 12:56:36.440: htsp_timer_stop3 htsp_setup_ind

Jan 20 12:56:36.444: [0/0/0] get_local_station_id calling num= calling name= calling time=01/20 12:56  orig called=

Jan 20 12:56:36.444: TGRM: reg_invoke_tgrm_accept_call(1, TGRM_CALL_VOICE, TGRM_DIRECTION_IN, 0, 0, 0, 65535)

Jan 20 12:56:36.444: TGRM: Calling vtsp_tsp_call_setup_ind().

Jan 20 12:56:36.448: htsp_validate_cap****

Jan 20 12:56:36.448: dsp_digit_collect_off: [0/0/0] packet_len=8 channel_id=128 packet_id=36htsp_connect: no_offhook 0 call_connected 0

Jan 20 12:56:36.448: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

Jan 20 12:56:36.448: fxols_wait_setup_ack:

Jan 20 12:56:36.448: [0/0/0] set signal state = 0xC timestamp = 0

Jan 20 12:56:36.448: dsp_set_sig_state: [0/0/0] packet_len=12 channel_id=128 packet_id=39 state=0xC timestamp=0x0fxols_check_auto_call

Jan 20 12:56:36.452: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect

Jan 20 12:56:36.452: htsp_timer_stop

Jan 20 12:56:36.488: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice

Jan 20 12:56:36.492: htsp_call_bridged invoked

Jan 20 12:56:36.496: flex_dsprm_forking_mixing_support:

Jan 20 12:56:36.496: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

Jan 20 12:56:36.496:  DSPWARE Version >= 3.0, actual is 4.2

Jan 20 12:56:36.496: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

Jan 20 12:56:36.496: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

Jan 20 12:56:36.500: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice

Jan 20 12:56:36.724: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_DSP_SIG_0110]fxols_rvs_battery

Jan 20 12:56:36.724: htsp_timer_stop2

NON WORKING:

Jan 20 12:50:40.253: htsp_process_event: [0/0/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

Jan 20 12:50:40.253: TGRM: reg_invoke_tgrm_call_update(0, 0, 1, 65535, 1, TGRM_CALL_PENDING, TGRM_CALL_VOICE, TGRM_DIRECTION_IN)

Jan 20 12:50:40.253: htsp_timer - 125 msec

Jan 20 12:50:40.381: htsp_process_event: [0/0/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

Jan 20 12:50:40.381: htsp_timer - 10000 msec

Jan 20 12:50:41.633: htsp_process_event: [0/0/1, FXOLS_RINGING, E_DSP_SIG_0100]

Jan 20 12:50:41.633: fxols_ringing_not

Jan 20 12:50:41.633: htsp_timer_stop

Jan 20 12:50:41.633: htsp_timer_stop3 htsp_setup_ind

Jan 20 12:50:41.633: [0/0/1] get_local_station_id calling num= calling name= calling time=01/20 12:50  orig called=

Jan 20 12:50:41.633: TGRM: reg_invoke_tgrm_accept_call(1, TGRM_CALL_VOICE, TGRM_DIRECTION_IN, 0, 0, 1, 65535)

Jan 20 12:50:41.633: TGRM: Calling vtsp_tsp_call_setup_ind().

Jan 20 12:50:41.641: dsp_digit_collect_on: [0/0/1] packet_len=20 channel_id=129 packet_id=35 min_inter_delay=240 max_inter_delay=9760 mim_make_time=10 max_make_time=100 min_brake_time=10 max_brake_time=100

Jan 20 12:50:41.641: htsp_process_event: [0/0/1, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

Jan 20 12:50:41.641: fxols_wait_setup_ack:

Jan 20 12:50:41.641: [0/0/1] set signal state = 0xC timestamp = 0

Jan 20 12:50:41.641: dsp_set_sig_state: [0/0/1] packet_len=12 channel_id=129 packet_id=39 state=0xC timestamp=0x0fxols_check_auto_call

Jan 20 12:50:41.917: htsp_process_event: [0/0/1, FXOLS_PROCEEDING, E_DSP_SIG_0110]fxols_rvs_battery

Jan 20 12:50:41.917: htsp_timer_stop2

7 REPLIES
Bronze

Incoming call rings and then disconnects

Hi Mohammad,

Router is receiving a battery reversal signal from service provider when phone is ringing.

Jan 20 12:50:41.917: htsp_process_event: [0/0/1, FXOLS_PROCEEDING, E_DSP_SIG_0110]fxols_rvs_battery

By default FXO port will disconnect the call if battery reversal is detected. To disable battery reversal detection configure below mentioned command under FXO port

voice-port

no battery-reversal

shut

no shut

Kindly check after making above changes.

Regards,

Mohit Singh

Incoming call rings and then disconnects

Thank you for the reply, I tried it but it is still dowing the same thing happening.  Going to create a ticket with telco.     

Re: Incoming call rings and then disconnects

Why would the FXO port still see the battery reversal?  Here is some more information:

"show voice trace"

NON WORKING

0/0/1 State Transitions: timestamp (state, event) -> (state, event) ...

69446.732 (FXOLS_RINGING, E_DSP_SIG_0100) ->

69446.736 (FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK) ->

69447.012 (FXOLS_PROCEEDING, E_DSP_SIG_0110) ->

69467.620 (FXOLS_PROCEED_RVS_BT, E_DSP_SIG_1100) ->

69467.972 (FXOLS_PROCEEDING, E_HTSP_EVENT_TIMER2) ->

69467.972 (FXOLS_PROCEEDING, E_HTSP_RELEASE_REQ) ->

69468.568 (FXOLS_GUARD_OUT, E_DSP_SIG_0110) ->

69468.972 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->

69468.972 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->

WORKING

0/0/0 State Transitions: timestamp (state, event) -> (state, event) ...

69383.764 (FXOLS_RINGING, E_DSP_SIG_0100) ->

69383.768 (FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK) ->

69383.772 (FXOLS_PROCEEDING, E_HTSP_CONNECT) ->

69383.812 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

69383.820 (FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH) ->

69384.044 (FXOLS_CONNECT, E_DSP_SIG_0110) ->

69406.776 (FXOLS_CONNECT, E_DSP_SIG_1100) ->

69407.128 (FXOLS_CONNECT, E_HTSP_EVENT_TIMER2) ->

69407.192 (FXOLS_REMOTE_RELEASE, E_HTSP_RELEASE_REQ) ->

69407.720 (FXOLS_GUARD_OUT, E_DSP_SIG_0110) ->

69409.192 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->

69409.192 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->

Bronze

Incoming call rings and then disconnects

collect below debugs and share for a test call.

debug vpm signal

debug voip vtsp session

debug voip vtsp default

debug voip ccapi inout

Also share voice port configuration

Regards,

Mohit Singh

Re: Incoming call rings and then disconnects

Thank you for the reply.  Weirdest thing I moved it from fxo0/0/1 to 0/0/3 and now everything is working.  I'm wondering if the 0/0/1 was defective in the new card as well. 

Bronze

Incoming call rings and then disconnects

You had to disable battery reversal or without it new port is working?

Regards,

Mohit Singh

Re: Incoming call rings and then disconnects

I tried disabling the battery reversal on 0/0/1 (the original port) but no use.  On the new port it is working without it.

757
Views
0
Helpful
7
Replies
CreatePlease login to create content