Random Incoming Calls Drop After 1 Ring

Unanswered Question
Apr 25th, 2008

Occasionally, incoming calls will ring once and drop. Debug is attached.

These lines stuck out

*Apr 25 09:30:05.906 EDT: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_DSP_SIG_0110]fxols_rvs_battery

*Apr 25 09:36:06.362 EDT: htsp_process_event: [0/1/0, FXOLS_ONHOOK, E_DSP_SIG_0110]

*Apr 25 09:36:06.362 EDT: fxols_line_reversal_clid_wait. On_hook line reversal detected possibily due to crossed cable

My concerns revolve around the battery reversal and the crossed cable entries.

Here is my config, pretty simple:

voice-port 0/1/0

timing hookflash-out 500

connection plar 82380

caller-id alerting ring 2

dial-peer voice 1 pots

incoming called-number .

port 0/1/0

dial-peer voice 300 voip

preference 3

destination-pattern 82380

progress_ind setup enable 3

voice-class h323 1

session target ipv4:10.224.0.10

dtmf-relay h245-signal

codec g711ulaw

ip qos dscp cs3 signaling

no vad

All 4 ports are configured identically.

I am using a 2821 and Call Manager. I have verified I do not have the DSP bug.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
cybrsage Fri, 04/25/2008 - 07:08

As a note, I found this in a subsequent debug capture:

*Apr 25 10:44:45.366 EDT: htsp_process_event: [0/1/2, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc

*Apr 25 10:44:45.366 EDT: htsp_timer - 120000 msec

*Apr 25 10:44:45.366 EDT: flex_dsprm_close_cleanup

*Apr 25 10:44:45.366 EDT: //-1/313233343930/DSM:(0/1/2):-1/dsmp_dsmapi_reserve_resource_cb: .

*Apr 25 10:44:45.366 EDT: [0/1/2] htsp_dsm_close_donehtsp_alert_notify

*Apr 25 10:44:45.446 EDT: htsp_process_event: [0/1/2, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Apr 25 10:44:45.446 EDT: htsp_process_event: [0/1/2, FXOLS_PROCEEDING, E_DSP_SIG_0110]fxols_rvs_battery

*Apr 25 10:44:45.446 EDT: htsp_timer_stop2

*Apr 25 10:44:45.638 EDT: htsp_process_event: [0/1/2, FXOLS_PROCEED_RVS_BT, E_DSP_SIG_0110]

*Apr 25 10:44:45.638 EDT: [0/1/2, FXOLS_PROCEED_RVS_BT, E_DSP_SIG_0110] -> ERROR: INVALID INPUT

*Apr 25 10:44:47.774 EDT: htsp_process_event: [0/1/2, FXOLS_PROCEED_RVS_BT, E_HTSP_EVENT_TIMER3]

*Apr 25 10:44:47.774 EDT: [0/1/2, FXOLS_PROCEED_RVS_BT, E_HTSP_EVENT_TIMER3] -> ERROR: INVALID INPUT

*Apr 25 10:44:56.538 EDT: htsp_call_bridged invoked

cybrsage Fri, 04/25/2008 - 07:15

Thought I would add one more debug. This one shows the following interesting info:

*Apr 25 10:40:09.282 EDT: htsp_timer - 1300 msec

*Apr 25 10:40:09.670 EDT: htsp_process_event: [0/1/2, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_power_denial_proc

*Apr 25 10:40:09.670 EDT: htsp_timer2 - 1000 msec

*Apr 25 10:40:09.670 EDT: htsp_timer_stop

*Apr 25 10:40:09.870 EDT: htsp_process_event: [0/1/2, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_0110]fxols_disc_clear

*Apr 25 10:40:09.874 EDT: htsp_timer_stop2

cybrsage Mon, 05/12/2008 - 05:31

So that anyone else who has this issue will know the solution, I have found it and repaired it.

There was an open pair in the third POTS line. Since the lines ring in order from 1 to 3 (last line), the error did not appear until all three lines were in use. The open pair caused the issue.

Actions

This Discussion