[cisco-voip] FXO calls disconnect when answered

[Scott Coner (US)]

Low voltage doesn't necessarily have to be caused by an inline device (surge protector).....   Might be worth a look

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Kris Seraphine
Sent: Fri 8/25/2006 3:16 PM
To: cisco-voip
Subject: Re: [cisco-voip] FXO calls disconnect when answered


that's a good thought.  

Unfortunately I don't think it applies to this case.  I'm coming right off the block.  Unless the telco is doing something outside the building. 


On 8/25/06, Scott Coner (US) <scott.coner at us.didata.com> wrote: 

	I had a similar problem with a customer and it turned out to be low voltage on the POTS line.  In my case the low voltage situation was being caused by an inline surge protector on the POTS line.  

	 

	Scott

	 

	
________________________________


	From: cisco-voip-bounces at puck.nether.net [mailto: cisco-voip-bounces at puck.nether.net <mailto:cisco-voip-bounces at puck.nether.net> ] On Behalf Of Kris Seraphine
	Sent: Friday, August 25, 2006 2:27 PM
	To: cisco-voip
	Subject: [cisco-voip] FXO calls disconnect when answered

	 

	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 

	

________________________________

	


	
	Disclaimer:
	
	This e-mail communication and any attachments may contain
	confidential and privileged information and is for use by the
	designated addressee(s) named above only. If you are not the
	intended addressee, you are hereby notified that you have received
	this communication in error and that any use or reproduction of
	this email or its contents is strictly prohibited and may be
	unlawful. If you have received this communication in error, please
	notify us immediately by replying to this message and deleting it
	from your computer. Thank you.
	




-- 
kris seraphine 



-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060825/a29839ec/attachment-0001.html