<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Steve,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Try to uncomment "<span style="font-family:Arial,Helvetica,sans-serif">dchan=24" and remove "</span><span style="font-family:Arial,Helvetica,sans-serif">hardhdlc=24" in the /etc/dahdi/system.conf</span></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><br></div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Leonid </div></div><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 13, 2018 at 8:01 PM <<a href="mailto:asterisk-users-request@lists.digium.com">asterisk-users-request@lists.digium.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send asterisk-users mailing list submissions to<br>
<a href="mailto:asterisk-users@lists.digium.com" target="_blank">asterisk-users@lists.digium.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, 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><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:asterisk-users-request@lists.digium.com" target="_blank">asterisk-users-request@lists.digium.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:asterisk-users-owner@lists.digium.com" target="_blank">asterisk-users-owner@lists.digium.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of asterisk-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Xorcom PRI (Jeff LaCoursiere)<br>
2. Detect missed call in extensions? (Sebastian Nielsen)<br>
3. Re: Xorcom PRI (Steve Totaro)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 12 Nov 2018 13:42:54 -0600<br>
From: Jeff LaCoursiere <<a href="mailto:jeff@stratustalk.com" target="_blank">jeff@stratustalk.com</a>><br>
To: <a href="mailto:asterisk-users@lists.digium.com" target="_blank">asterisk-users@lists.digium.com</a><br>
Subject: [asterisk-users] Xorcom PRI<br>
Message-ID: <<a href="mailto:14920cf8-2c8d-0d40-f2b7-cf207ad25dee@stratustalk.com" target="_blank">14920cf8-2c8d-0d40-f2b7-cf207ad25dee@stratustalk.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
<br>
I've been struggling for a few weeks now with the local telco trying to <br>
bring up a trunk that has been down for a year (hurricanes in the <br>
caribbean). Box is a Dell R710, 16G RAM, Ubuntu 14.04.5 LTS, Dahdi <br>
2.10.2-rc1, asterisk 13.23.1. Xorcom Astribank w/ one T1/E1/PRI module, <br>
plugged into a USB 2.0 port on the Dell. All of this was working <br>
*before* the storms last year with the same hardware/versions.<br>
<br>
Dahdi sees the astribank and loads firmware without issue:<br>
<br>
root@astbeach:~# dmesg | grep -i dahdi<br>
[661368.877090] dahdi: Version: 2.10.2-rc1<br>
[661368.880450] dahdi: Telephony Interface Registered on major 196<br>
[661368.963988] dahdi_transcode: Loaded.<br>
[661368.982746] INFO-xpp: FEATURE: with sync_tick() from DAHDI<br>
[661369.233471] INFO-xpd_pri: FEATURE: WITHOUT DAHDI_AUDIO_NOTIFY<br>
[661370.256053] dahdi_devices astribanks:xbus-00: local span 1 is<br>
already assigned span 1<br>
[661370.270028] dahdi_echocan_mg2: Registered echo canceler 'MG2'<br>
<br>
root@astbeach:~# lsusb<br>
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub<br>
Bus 001 Device 002: ID e4e4:1162 Xorcom Ltd. Astribank 2 series<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<br>
The dahdi drivers are loaded, and the T1 layer has no alarms... telco <br>
also reports the line itself is "UP":<br>
<br>
root@astbeach:~# service dahdi status<br>
### Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1" (MASTER) <br>
ESF/B8ZS ClockSource<br>
1 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
2 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
3 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
4 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
5 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
6 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
7 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
8 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
9 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
10 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
11 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
12 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
13 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
14 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
15 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
16 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
17 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
18 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
19 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
20 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
21 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
22 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
23 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
24 T1 Hardware-assisted HDLC (In use)<br>
<br>
asterisk chan_dahdi shows the T1 up with no alarms:<br>
<br>
astbeach*CLI> dahdi show status<br>
Description Alarms IRQ bpviol CRC Fra <br>
Codi Options LBO<br>
Xorcom XPD [usb:X1067719].1: T1 OK 0 0 0 ESF <br>
B8ZS 0 db (CSU)/0-133 feet (DSX-1)<br>
<br>
but the PRI is down:<br>
<br>
astbeach*CLI> pri show spans<br>
PRI span 1/0: Down, Active<br>
<br>
I'm not really sure where to take it from here, and the telco has even <br>
less of a clue. They brought out some gear that they hooked up to our <br>
cabling for the T1 and pretty quickly established a PRI, then placed and <br>
received test calls over it. At that point they washed their hands of <br>
it, and logged as a "CPE issue"!<br>
<br>
Could it be that the storms damaged the Xorcom unit in such a way that <br>
the T1 can be up without alarms but the PRI signaling is broken? Seems <br>
unlikely.<br>
<br>
I have included a few relevant config files below. Note that the <br>
cabling wasn't in place when we ran dahdi_genconf, which is why it shows <br>
red alarm. There is no red alarm now.<br>
<br>
/etc/dahdi/system.conf:<br>
<br>
# Autogenerated by /usr/sbin/dahdi_genconf on Fri Oct 12 11:34:27 2018<br>
# If you edit this file and execute /usr/sbin/dahdi_genconf again,<br>
# your manual changes will be LOST.<br>
# Dahdi Configuration File<br>
#<br>
# This file is parsed by the Dahdi Configurator, dahdi_cfg<br>
#<br>
# Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1" (MASTER) RED<br>
span=1,1,0,esf,b8zs<br>
# termtype: te<br>
bchan=1-23<br>
#dchan=24<br>
echocanceller=mg2,1-23<br>
hardhdlc=24<br>
<br>
# Global data<br>
<br>
loadzone = us<br>
defaultzone = us<br>
<br>
----------------------------------------------------------------------<br>
<br>
root@astbeach:/etc/dahdi# egrep -v '^#' xpp.conf<br>
pri_protocol T1<br>
<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>
<br>
Thanks for any debugging advice!<br>
<br>
Cheers,<br>
<br>
j<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/7b4d8eeb/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/7b4d8eeb/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 12 Nov 2018 22:39:28 +0100<br>
From: "Sebastian Nielsen" <<a href="mailto:sebastian@sebbe.eu" target="_blank">sebastian@sebbe.eu</a>><br>
To: <<a href="mailto:asterisk-users@lists.digium.com" target="_blank">asterisk-users@lists.digium.com</a>><br>
Subject: [asterisk-users] Detect missed call in extensions?<br>
Message-ID: <001c01d47ad0$3152c040$93f840c0$@<a href="http://sebbe.eu" rel="noreferrer" target="_blank">sebbe.eu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
How I do to detect missed calls?<br>
<br>
<br>
<br>
After Dial() has been executed, theres 3 ways a call could end up in:<br>
<br>
<br>
<br>
1: The callee answers, and a communication is going on. Then one party hangs<br>
up, and thus execution goes to the h extension.<br>
<br>
2: The callee newer answers or there was some error, the Dial() fails, and<br>
execution continues on next line in extensions.<br>
<br>
3: The caller hangs up before callee have answered, and execution goes to<br>
the h extension.<br>
<br>
<br>
<br>
Now to the problem. I want to detect if callee did answer or not (in<br>
separate 1 and 3) so I could determite if a missed call should be logged to<br>
a missedcall.txt log file. (call should be logged in 3 case, but not in 1<br>
case)<br>
<br>
2 is easy to detect, as these always are failed (non-answered) calls.<br>
<br>
<br>
<br>
Best regards, Sebastian Nielsen<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/4450e232/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/4450e232/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/pkcs7-signature<br>
Size: 5261 bytes<br>
Desc: S/MIME Cryptographic Signature<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/4450e232/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/4450e232/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 12 Nov 2018 21:22:06 -0500<br>
From: Steve Totaro <<a href="mailto:stotaro@totarotechnologies.com" target="_blank">stotaro@totarotechnologies.com</a>><br>
To: Asterisk Users Mailing List - Non-Commercial Discussion<br>
<<a href="mailto:asterisk-users@lists.digium.com" target="_blank">asterisk-users@lists.digium.com</a>><br>
Subject: Re: [asterisk-users] Xorcom PRI<br>
Message-ID:<br>
<CAGA-L+UTRV-zVgB-KPzuxvSUoAzj1NnT-TGxZCbnHLFyjO3p=<a href="mailto:w@mail.gmail.com" target="_blank">w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Turn on PRI debugging and double check your cable.<br>
<br>
On Mon, Nov 12, 2018 at 3:24 PM Jeff LaCoursiere <<a href="mailto:jeff@stratustalk.com" target="_blank">jeff@stratustalk.com</a>><br>
wrote:<br>
<br>
><br>
> I've been struggling for a few weeks now with the local telco trying to<br>
> bring up a trunk that has been down for a year (hurricanes in the<br>
> caribbean). Box is a Dell R710, 16G RAM, Ubuntu 14.04.5 LTS, Dahdi<br>
> 2.10.2-rc1, asterisk 13.23.1. Xorcom Astribank w/ one T1/E1/PRI module,<br>
> plugged into a USB 2.0 port on the Dell. All of this was working *before*<br>
> the storms last year with the same hardware/versions.<br>
><br>
> Dahdi sees the astribank and loads firmware without issue:<br>
><br>
> root@astbeach:~# dmesg | grep -i dahdi<br>
> [661368.877090] dahdi: Version: 2.10.2-rc1<br>
> [661368.880450] dahdi: Telephony Interface Registered on major 196<br>
> [661368.963988] dahdi_transcode: Loaded.<br>
> [661368.982746] INFO-xpp: FEATURE: with sync_tick() from DAHDI<br>
> [661369.233471] INFO-xpd_pri: FEATURE: WITHOUT DAHDI_AUDIO_NOTIFY<br>
> [661370.256053] dahdi_devices astribanks:xbus-00: local span 1 is already<br>
> assigned span 1<br>
> [661370.270028] dahdi_echocan_mg2: Registered echo canceler 'MG2'<br>
> root@astbeach:~# lsusb<br>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
> Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub<br>
> Bus 001 Device 002: ID e4e4:1162 Xorcom Ltd. Astribank 2 series<br>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
><br>
> The dahdi drivers are loaded, and the T1 layer has no alarms... telco also<br>
> reports the line itself is "UP":<br>
><br>
> root@astbeach:~# service dahdi status<br>
> ### Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1" (MASTER)<br>
> ESF/B8ZS ClockSource<br>
> 1 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 2 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 3 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 4 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 5 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 6 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 7 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 8 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 9 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 10 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 11 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 12 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 13 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 14 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 15 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 16 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 17 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 18 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 19 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 20 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 21 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 22 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 23 T1 Clear (In use) (EC: MG2 - INACTIVE)<br>
> 24 T1 Hardware-assisted HDLC (In use)<br>
><br>
> asterisk chan_dahdi shows the T1 up with no alarms:<br>
><br>
> astbeach*CLI> dahdi show status<br>
> Description Alarms IRQ bpviol CRC Fra<br>
> Codi Options LBO<br>
> Xorcom XPD [usb:X1067719].1: T1 OK 0 0 0 ESF<br>
> B8ZS 0 db (CSU)/0-133 feet (DSX-1)<br>
><br>
> but the PRI is down:<br>
><br>
> astbeach*CLI> pri show spans<br>
> PRI span 1/0: Down, Active<br>
><br>
> I'm not really sure where to take it from here, and the telco has even<br>
> less of a clue. They brought out some gear that they hooked up to our<br>
> cabling for the T1 and pretty quickly established a PRI, then placed and<br>
> received test calls over it. At that point they washed their hands of it,<br>
> and logged as a "CPE issue"!<br>
><br>
> Could it be that the storms damaged the Xorcom unit in such a way that the<br>
> T1 can be up without alarms but the PRI signaling is broken? Seems<br>
> unlikely.<br>
><br>
> I have included a few relevant config files below. Note that the cabling<br>
> wasn't in place when we ran dahdi_genconf, which is why it shows red<br>
> alarm. There is no red alarm now.<br>
><br>
> /etc/dahdi/system.conf:<br>
> # Autogenerated by /usr/sbin/dahdi_genconf on Fri Oct 12 11:34:27 2018<br>
> # If you edit this file and execute /usr/sbin/dahdi_genconf again,<br>
> # your manual changes will be LOST.<br>
> # Dahdi Configuration File<br>
> #<br>
> # This file is parsed by the Dahdi Configurator, dahdi_cfg<br>
> #<br>
> # Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1" (MASTER) RED<br>
> span=1,1,0,esf,b8zs<br>
> # termtype: te<br>
> bchan=1-23<br>
> #dchan=24<br>
> echocanceller=mg2,1-23<br>
> hardhdlc=24<br>
><br>
> # Global data<br>
><br>
> loadzone = us<br>
> defaultzone = us<br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> root@astbeach:/etc/dahdi# egrep -v '^#' xpp.conf<br>
> pri_protocol T1<br>
><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>
><br>
> Thanks for any debugging advice!<br>
><br>
> Cheers,<br>
><br>
> j<br>
> --<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:<br>
> <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:<br>
> <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><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/d8969ba9/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.digium.com/pipermail/asterisk-users/attachments/20181112/d8969ba9/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<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>
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><br>
<br>
------------------------------<br>
<br>
End of asterisk-users Digest, Vol 171, Issue 7<br>
**********************************************<br>
</blockquote></div></div>