[Home]

Summary:DAHTOOL-00043: TE110P won't use (or doesn't indicate use of external clock
Reporter:Mark Jones (mark0978)Labels:
Date Opened:2010-03-08 09:23:42.000-0600Date Closed:2012-04-04 12:59:44
Priority:MajorRegression?No
Status:Closed/CompleteComponents:General
Versions:2.2.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:dahdi_tool shows the card correctly configured and operational, except the sync source seems to always be Internally Clocked.  System is functioning without cracks or pops, not sure if the problem is in the tool, or in the way dahdi_cfg is setting up the card, I'm not even sure how to tell.

system.conf
# Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" (MASTER) B8ZS/ESF
span=1,1,0,esf,b8zs
# termtype: te
e&m=1-4
unused=5-24

dahdi-channels.conf
; Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" (MASTER) B8ZS/ESF
group=0,11
context=from-pstn
rxgain=2.0
txgain=3.0
signalling = em_w
channel => 1-4
context = default
group = 63
usercallerid=yes


****** STEPS TO REPRODUCE ******

See above config
Comments:By: Mark Jones (mark0978) 2010-03-08 09:44:01.000-0600

Looks like this bug has been outstanding for a year now (maybe unreported)

http://www.asteriskguru.com/archives/image-vp343887.html
By: Mark Jones (mark0978) 2010-03-08 09:46:32.000-0600

More notes:  I'm suggesting this didn't fix the issue.

2009-05-14 14:49 +0000 [r6621]  Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Set the syncsrc in the
+  span appropriately. Before this commit, dahdi_tool would report
+  "Internally clocked" for boards supported by the wcte12xp driver
+  both when receiving timing from the span and providing it to the
+  span. Now it reports "Internally clocked" if providing timeing to
+  the span, and the card if receiving timeing from the span.
+  DAHDI-65.
By: Mark Jones (mark0978) 2010-03-08 09:54:50.000-0600

Looks like it is a known, longstanding bug all the way back to zttool in 2005

https://issues.asterisk.org/view.php?id=4186

Time someone fixed this thing.  I wasted hours trying to figure out why it wasn't working, and this is at 4:30 in the morning when I'm doing it!
By: Grigoriy Puzankin (boroda) 2010-11-02 12:28:42

Dahdi 2.2.1 shows correct timing source. But all recent versions 2.3-2.4 show "internally clocked". I have TE205P card.
By: Shaun Ruffell (sruffell) 2011-09-11 00:51:21.309-0500

I don't know if anyone cares about this still but, [r6621|http://svnview.digium.com/svn/dahdi?view=revision&revision=6621] was only for the wcte12xp driver and not the wct1xxp driver which support the TE110P card that this issue was opened up against.

With regards to the comment that "Internally Clocked" is displayed for the TE220 cards, I'm not seeing that.


Here is when span 1 is up and is the clock source:

{noformat}
# dahdi_scan | grep -e "^\[1\|2\]" -e "^syncsrc"
[1]
syncsrc=1
[2]
syncsrc=1
{noformat}

and when both spans are in alarm:

{noformat}
# dahdi_scan | grep -e "^\[1\|2\]" -e "^syncsrc"
[1]
syncsrc=0
[2]
syncsrc=0
{noformat}

Which would result in "Internally clocked" displayed in dahdi_tool since syncsrc = 0. This is as I would expect. So I believe the behavior in 2.3+ for wcte12xp and wct4xxp based cards is correct.

Since I don't have easy access to any of the TE110P cards would anyone still be interested in testing a patch for the wct1xxp driver?
By: Shaun Ruffell (sruffell) 2012-04-04 12:59:44.042-0500

I'm suspending this issue. If anyone has an interest in testing a patch for the TE110, please feel free to comment / reopen.