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

Weird FXO problem

Hi guys,

Here is a weird thing.. I have a 2911 with : (C2900-UNIVERSALK9-M), Version 15.1(4)M4,  and 3 VIC2-4FXO cards.

From time to time a line will go into a weird state and I am not able to send calls through that port.. I do a shut, no shut, router reload and nothing happens... the only solution is to unplug the RJ-11 cable and life is good again...

I ran a test on the port that does not work:

test voice port 0/0/0 si-reg-read 29 1

OAK_VGW1#

Jul 30 22:25:13.145:

Values read from SiLabs Codec connected to DSP 0, channel 0:

--------------------------------------------------------------

Register 29 = 0xCE

A port that works:

OAK_VGW1#test voice port 0/0/1 si-reg-read 29 1

OAK_VGW1#

Jul 30 22:25:36.053:

Values read from SiLabs Codec connected to DSP 0, channel 1:

--------------------------------------------------------------

Register 29 = 0x34

The call will not busy out.. it will go through and you can see the port going off-hook but nothing happens:

A debug from a vpm signal does not tell me much:

ul 30 22:01:59.809: htsp_timer_stop3 htsp_setup_req

Jul 30 22:01:59.813: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_setup

Jul 30 22:01:59.813: [0/0/0] set signal state = 0xC timestamp = 0

Jul 30 22:01:59.813: dsp_set_sig_state: [0/0/0] packet_len=12 channel_id=128 packet_id=39 state=0xC timestamp=0x0

Jul 30 22:01:59.813: TGRM: reg_invoke_tgrm_call_update(0, 0, 0, 65535, 1, TGRM_CALL_BUSY, TGRM_CALL_VOICE, TGRM_DIRECTION_OUT)

Jul 30 22:01:59.813: htsp_timer - 1300 msec

Jul 30 22:02:00.089: htsp_process_event: [0/0/0, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_0110]fxols_disc_clear

Jul 30 22:02:00.089: htsp_timer_stop2

OAK_VGW1(config-voiceport)#

Jul 30 22:02:00.089: htsp_timer - 1300 msec

OAK_VGW1(config-voiceport)#

Jul 30 22:02:01.389: htsp_process_event: [0/0/0, FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER]fxols_wait_dial_timer  htsp_dial

Jul 30 22:02:01.389: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

OAK_VGW1(config-voiceport)#

Jul 30 22:02:03.613: htsp_process_event: [0/0/0, FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE]fxols_wait_dial_done htsp_progress

Jul 30 22:02:03.613: htsp_timer - 350 msec

Jul 30 22:02:03.613: htsp_call_bridged invoked

Jul 30 22:02:03.721: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

Jul 30 22:02:03.721: flex_dsprm_forking_mixing_support:

Jul 30 22:02:03.721: mars_flex_dsprm_current_codec_comp:DSP:0 FLEX Complexity Codec

Jul 30 22:02:03.721: htsp_process_event: [0/0/0, FXOLS_WAIT_CUT_THRU, E_HTSP_VOICE_CUT_THROUGH]fxols_handle_cut_thru

Jul 30 22:02:03.721: htsp_timer_stop

Port config is simple and it works fine except when the port goes down:

!

voice-port 0/0/0

trunk-group POTS 1

no battery-reversal

cable-detect

connection plar 8805

busyout forced

caller-id enable

!

voice-port 0/0/1

trunk-group POTS 1

connection plar 8805

caller-id enable

!

Port 0/0/0 is the one that does not work right now and I have it "busy out" so that the calls use other ports since the environment is in production.

I have tryied battery reversal, disconnect parameters... nothing!

The provider delivers the PSTN lines using and Adtran and they say that everything is good.

Any ideas?

Thanks!


2 REPLIES

Weird FXO problem

If you do a "show voice call summ", what is the status of the port?

If the port is an FXO, I don't think it's a problem with the port, however we have to proof it.

Have you tried moving the cables? Meaning, if the affected line is connected on port 0/0/0, move it for example to 0/0/1, and if the issue affects 0/0/1, it's definitively an issue with the line, otherwise an RMA will be needed, since there's not much you can do with an FXO

HTH

--
Jorge Armijo

Please remember to rate helpful responses and identify helpful or correct answers.

-- Jorge Armijo Please remember to rate helpful responses and identify helpful or correct answers.

Weird FXO problem

Hi,

The port goes off-hook as it should but... dead air! I did try moving the cables and the problem would not really move with the line, it is kind of random. The only way to solve it disconnecting the cable and connecting it again.

I am pretty sure is the Provider's Adtran but I can't porve it.

Is there any way I can test the current, or Voltage, of the line when it's in this weird state ?

Joan

182
Views
5
Helpful
2
Replies
CreatePlease to create content