[asterisk-bugs] [DAHDI-linux 0015311]: [patch] Call to a FXS DAHDI channel with Panasonic KX-TG4000 connected drops in 8 seconds randomly

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jun 16 17:55:20 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15311 
====================================================================== 
Reported By:                vmikhelson
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15311
Category:                   dahdi (the module)
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2009-06-11 00:49 CDT
Last Modified:              2009-06-16 17:55 CDT
====================================================================== 
Summary:                    [patch] Call to a FXS DAHDI channel with Panasonic
KX-TG4000 connected drops in 8 seconds randomly
Description: 
More often than not a call placed to a DAHDI channel with Panasonic
KX-TG4000 connected would drop on its own in exactly 8 seconds after being
answered. Before being disconnected two (2) clicks are being heard in
succession. The second click kills the connection.
====================================================================== 

---------------------------------------------------------------------- 
 (0106525) vmikhelson (reporter) - 2009-06-16 17:55
 https://issues.asterisk.org/view.php?id=15311#c106525 
---------------------------------------------------------------------- 
Alec,

Thank you for clarifications. I bet [^] has something to do with
hyper-links.

You may want to change "cd dahdi-linux" to "cd dahdi-linux/2.1.0.4" in
your instructions otherwise 'patch' command has trouble accessing
sub-directories.

Now regarding the 'reversepolarity' issue. As I understand, it is a known
issue and polarity in TDM400p FXS lines is normally reversed unless the
'reversepolarity=1' parameter is passed to wctdm at startup. Is my
understanding correct? This is what I observe with my hardware.

I also confirm that the first call is needed after reboot to reset the
polarity back to normal. Return to normal only occurs if
'reversepolarity=1' parameter is passed to wctdm at startup, otherwise the
polarity stays reverted all the time.

Should I keep the 'boostringer=1'?

Thank you,
Vladimir 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-16 17:55 vmikhelson     Note Added: 0106525                          
======================================================================




More information about the asterisk-bugs mailing list