<div dir="ltr">Turn on PRI debugging and double check your cable.<br><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 12, 2018 at 3:24 PM Jeff LaCoursiere <<a href="mailto:jeff@stratustalk.com">jeff@stratustalk.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>I've been struggling for a few weeks now with the local telco
trying to bring up a trunk that has been down for a year
(hurricanes in the caribbean). Box is a Dell R710, 16G RAM,
Ubuntu 14.04.5 LTS, Dahdi 2.10.2-rc1, asterisk 13.23.1. Xorcom
Astribank w/ one T1/E1/PRI module, plugged into a USB 2.0 port on
the Dell. All of this was working *before* the storms last year
with the same hardware/versions.</p>
<p>Dahdi sees the astribank and loads firmware without issue:</p>
<blockquote>
<p><tt>root@astbeach:~# dmesg | grep -i dahdi</tt><tt><br>
</tt><tt>[661368.877090] dahdi: Version: 2.10.2-rc1</tt><tt><br>
</tt><tt>[661368.880450] dahdi: Telephony Interface Registered
on major 196</tt><tt><br>
</tt><tt>[661368.963988] dahdi_transcode: Loaded.</tt><tt><br>
</tt><tt>[661368.982746] INFO-xpp: FEATURE: with sync_tick()
from DAHDI</tt><tt><br>
</tt><tt>[661369.233471] INFO-xpd_pri: FEATURE: WITHOUT
DAHDI_AUDIO_NOTIFY</tt><tt><br>
</tt><tt>[661370.256053] dahdi_devices astribanks:xbus-00: local
span 1 is already assigned span 1</tt><tt><br>
</tt><tt>[661370.270028] dahdi_echocan_mg2: Registered echo
canceler 'MG2'</tt><tt><br>
</tt></p>
<tt>root@astbeach:~# lsusb</tt><tt><br>
</tt><tt>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub</tt><tt><br>
</tt><tt>Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1
root hub</tt><tt><br>
</tt><tt>Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1
root hub</tt><tt><br>
</tt><tt>Bus 001 Device 003: ID 0424:2514 Standard Microsystems
Corp. USB 2.0 Hub</tt><tt><br>
</tt><tt>Bus 001 Device 002: ID e4e4:1162 Xorcom Ltd. Astribank 2
series</tt><tt><br>
</tt><tt>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub</tt><tt><br>
</tt><tt>Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1
root hub</tt><tt><br>
</tt><tt>Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1
root hub</tt><br>
</blockquote>
<p>The dahdi drivers are loaded, and the T1 layer has no alarms...
telco also reports the line itself is "UP":</p>
<p><tt>root@astbeach:~# service dahdi status</tt><br>
<tt>### Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1"
(MASTER) ESF/B8ZS ClockSource </tt><br>
<tt> 1 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 2 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 3 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 4 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 5 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 6 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 7 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 8 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 9 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 10 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 11 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 12 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 13 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 14 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 15 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 16 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 17 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 18 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 19 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 20 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 21 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 22 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 23 T1 Clear (In use) (EC: MG2 - INACTIVE) </tt><br>
<tt> 24 T1 Hardware-assisted HDLC (In use) </tt><br>
</p>
<p>asterisk chan_dahdi shows the T1 up with no alarms:</p>
<p><tt>astbeach*CLI> dahdi show status</tt><tt><br>
</tt><tt>Description Alarms IRQ
bpviol CRC Fra Codi Options LBO</tt><tt><br>
</tt><tt>Xorcom XPD [usb:X1067719].1: T1 OK 0
0 0 ESF B8ZS 0 db (CSU)/0-133 feet (DSX-1)</tt><br>
</p>
<p>but the PRI is down:</p>
<p><tt>astbeach*CLI> pri show spans</tt><tt><br>
</tt><tt>PRI span 1/0: Down, Active</tt><br>
</p>
<p>I'm not really sure where to take it from here, and the telco has
even less of a clue. They brought out some gear that they hooked
up to our cabling for the T1 and pretty quickly established a PRI,
then placed and received test calls over it. At that point they
washed their hands of it, and logged as a "CPE issue"!</p>
<p>Could it be that the storms damaged the Xorcom unit in such a way
that the T1 can be up without alarms but the PRI signaling is
broken? Seems unlikely.</p>
<p>I have included a few relevant config files below. Note that the
cabling wasn't in place when we ran dahdi_genconf, which is why it
shows red alarm. There is no red alarm now.</p>
<blockquote>
<p><tt>/etc/dahdi/system.conf:</tt></p>
<tt># Autogenerated by /usr/sbin/dahdi_genconf on Fri Oct 12
11:34:27 2018</tt><tt><br>
</tt><tt># If you edit this file and execute
/usr/sbin/dahdi_genconf again,</tt><tt><br>
</tt><tt># your manual changes will be LOST.</tt><tt><br>
</tt><tt># Dahdi Configuration File</tt><tt><br>
</tt><tt>#</tt><tt><br>
</tt><tt># This file is parsed by the Dahdi Configurator,
dahdi_cfg</tt><tt><br>
</tt><tt>#</tt><tt><br>
</tt><tt># Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1:
T1" (MASTER) RED </tt><tt><br>
</tt><tt>span=1,1,0,esf,b8zs</tt><tt><br>
</tt><tt># termtype: te</tt><tt><br>
</tt><tt>bchan=1-23</tt><tt><br>
</tt><tt>#dchan=24</tt><tt><br>
</tt><tt>echocanceller=mg2,1-23</tt><tt><br>
</tt><tt>hardhdlc=24</tt><tt><br>
</tt><tt><br>
</tt><tt># Global data</tt><tt><br>
</tt><tt><br>
</tt><tt>loadzone = us</tt><tt><br>
</tt><tt>defaultzone = us</tt><tt><br>
<br>
----------------------------------------------------------------------<br>
<br>
root@astbeach:/etc/dahdi# egrep -v '^#' xpp.conf<br>
pri_protocol T1<br>
</tt><tt><tt><br>
----------------------------------------------------------------------<br>
<br>
root@astbeach:/etc/asterisk# egrep -v '^;' chan_dahdi.conf<br>
<br>
[trunkgroups]<br>
<br>
[channels]<br>
<br>
switchtype = national<br>
context=from-pstn<br>
signalling = pri_cpe<br>
callwaiting=yes<br>
usecallingpres=yes<br>
callwaitingcallerid=yes<br>
threewaycalling=no<br>
transfer=no<br>
canpark=no<br>
cancallforward=no<br>
callreturn=no<br>
echocancel=yes<br>
echocancelwhenbridged=yes<br>
group=0<br>
callgroup=1<br>
pickupgroup=1<br>
channel => 1-23<br>
</tt></tt><br>
</blockquote>
<p>Thanks for any debugging advice!</p>
<p>Cheers,</p>
<p>j<br>
</p>
</div>
-- <br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" rel="noreferrer" target="_blank">http://www.api-digital.com</a> --<br>
<br>
Astricon is coming up October 9-11! Signup is available at: <a href="https://www.asterisk.org/community/astricon-user-conference" rel="noreferrer" target="_blank">https://www.asterisk.org/community/astricon-user-conference</a><br>
<br>
Check out the new Asterisk community forum at: <a href="https://community.asterisk.org/" rel="noreferrer" target="_blank">https://community.asterisk.org/</a><br>
<br>
New to Asterisk? Start here:<br>
<a href="https://wiki.asterisk.org/wiki/display/AST/Getting+Started" rel="noreferrer" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Getting+Started</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" rel="noreferrer" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a></blockquote></div></div>