[cisco-voip] FXO calls disconnect when answered

[Wes Sisk]

Kris,

 From a reputable colleague in TAC:
In this case "normal battery" just refers to power denial from
the CO.  The DSP has detected an on-hook condition which has
persisted beyond the minimum qualification time and has decided
that this is more than just a transient.

If the customer has an IOS in the 12.4 range get him to set a
higher value for "timing sup-disconnect" under the voice-port.
This will increase the qualification time for on-hook.

CSCea51194 Most analog FXO ports cannot detect short disconnect signals
[Peng Mok]

/Wes

On Aug 25, 2006, at 2:27 PM, Kris Seraphine wrote:

Hi

I've been struggling with this issue for over a month and both I and  
TAC seem to be stumped.

I have a customer with a small office that we are trying to migrate  
to a centralized CCM cluster.  They have a 1760V with 4 analog lines  
that we want to connect to an FXO card. When we connect the lines to  
the router for testing I get the following behavior.

PSTN caller calls into the system.
The IP phone user hears the phone ring and answers the call.
The IP phone user sees the call disconnect After a second or two, the  
call begins to ring again on the IP phone If the IP phone user  
answers the call again, the call disconnects and the process repeats  
The PSTN caller hears ringback the whole time.

The problem seems to be that the router is interpreting a disconnect  
coming from the telco.

Trace snippet:-
008192: .Jul 31 08:36:28.484: htsp_process_event: [2/0,
FXOLS_PROCEEDING,
E_HTSP_CONNECT]fxols_offhook_connect
008193: .Jul 31 08:36:28.488: [2/0] set signal state = 0xC timestamp = 0
008194: .Jul 31 08:36:28.488: htsp_timer_stop
008195: .Jul 31 08:36:28.488: htsp_process_event: [2/0, FXOLS_CONNECT,

E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
008196: .Jul 31 08:36:28.716: htsp_process_event: [2/0, FXOLS_CONNECT,

E_DSP_SIG_0100]fxols_normal_battery
008197: .Jul 31 08:36:28.744: htsp_process_event: [2/0, FXOLS_CONNECT,

E_DSP_SIG_1100]fxols_offhook_disc

I've talked to the CO guy but he's been little help.  I did have them  
run a ground start trunk for testing but it exibits the same behavior.

I've tried every combination of battery-reversal supervisory  
disconnect etc... that I can think of but I cannot seem to solve this  
problem.

TAC does not think its hardware related but I'm going to send a  
replacement router out just in case.

I'm hoping someone might have some suggestions for me.

Thanks in advanced.

Kris Seraphine
CCIE No. 15163, MCSE
Kris.Seraphine at cliftoncpa.com




-- 
kris seraphine
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060825/445588e8/attachment.html