I have to set up a new PBX with ISDN30 for outgoing lines. I’ve only set up one system so far and it used a normal ZAP PSTN card. What type of card do I need for ISDN30 and how does it differ from setting up (and workig with) a ZAP PSTN card? (by the way I used PBX in a Flash incase that’s relivant)
Thanks.
Update: I found the type of card, I think a Sangoma A101DX PCI Express Pri ISDN Card will work, but anyway, will this be different fomr configuring a ZAP PSTN card? 9and what kind of trunk does it go under? ( Zap, IAX2, SIP, ENUM, DUNDi, Custom)
Yes a Sangoma A101 DX is just what you need. You will need to install wanrouter, which will automatically configure zapata.conf for you and ask for all of the necessary bits for your ISDN30. ie number of spans etc, and depending on whether you have any other cards installed, will determine which Zap group you specify as the trunk to use in Freepbx. If it’s the first card thenm you should still be able to use Zap/g0 as the trunk. You can download the latest stable release from Sangoma. Look at the README’s in the software for install instructions.
Be careful, and don’t use Asterisk 1.4.22 at the moment, as that wants to install Dahdi by default, and there is still issues with Dahdi channels, and Zap. I’ve stuck with 1.4.21.2 at the moment, until things sort themselves out with the changes in Zaptel over to Dahdi.
If you need configs etc get back to me. I’ve been setting up the same card for an ISDN10 which only uses 10 channels instead of 30, but the config is very similar.
Well I have Asterisk 1.4.21.2 so that’s good. By the way, yes this is the only card.
This is what PBX In A Flash / genzaptelconf had set up by default for my /etc/asterisk/zapata.conf
[code];
; Zapata telephony interface
;
; Configuration file
[trunkgroups]
[channels]
language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no
;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no
;Include genzaptelconf configs
#include zapata-channels.conf
;Include AMP configs
#include zapata_additional.conf[/code]
/etc/asterisk/zapata-channels.conf:
[code]; Autogenerated by /usr/local/sbin/genzaptelconf – do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;
; Span 1: ZTDUMMY/1 “ZTDUMMY/1 (source: RTC) 1” (MASTER) [/code]
/etc/asterisk/zapata_additional.conf
;--------------------------------------------------------------------------------;
; Do NOT edit this file as it is auto-generated by FreePBX. All modifications to ;
; this file must be done via the web gui. There are alternative files to make ;
; custom modifications, details at: http://freepbx.org/configuration_files ;
;--------------------------------------------------------------------------------;
;
In FreePBX under Basic > Trunks there’s one entry: Trunk ZAP/g0
Is there an idiot’s guide to what to do to install and run wanrouter? I’m downloading it now, well it says wanpipe, is thta the same thing or somehting else, I think I’ll read the instructions if i can find them.
I think it might have managed to install it now, it says running wanrouter hwprobe shows that it’s working, here’s the output:
[code]root@pbx:/usr/src/wanpipe-3.2.7.1 $ wanrouter hwprobe
| Wanpipe Hardware Probe Info |
|---|
1 . AFT-A101-SH : SLOT=4 : BUS=5 : IRQ=10 : CPU=A : PORT=1 : HWEC=32 : V=34
Card Cnt: S508=0 S514X=0 S518=0 A101-2=1 A104=0 A300=0 A200=0 A108=0 A05
6=0[/code]
Okay I found the setup script: /usr/sbin/wancfg_zaptel
It’s asking me questions I don’t understand, media type i think is E1, Select Clock Normal/Master, I don’t know what that means, Select signalling type: PRI CPE, PRI NET, E & M, E & M Wink, FXS - Loop Start, FXS - Ground Start, FXS - Kewl Start, FX0 - Loop Start, FX0 - Ground Start, FX0 - Kewl Start, don’t know what thta means. switchtype, use all channels? select diaplan?
I’m going to keep looking on the sangoma wiki but i think i need the idiot’s guide.
This is what you should need in your zapata.conf. Remembering though I have set this up for an Australian Telstra provided Onramp 30 with 10 channels enabled.
;autogenerated by /usr/local/sbin/config-zaptel do not hand edit
;Zaptel Channels Configurations (zapata.conf)
;
;For detailed zapata options, view /etc/asterisk/zapata.conf.orig
[trunkgroups]
[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
pridialplan=unknown
prilocaldialplan=unknown
nationalprefix=0
internationalprefix=0011
overlapdial=yes
priindication=outofband
;Sangoma A101 port 1 [slot:4 bus:13 span:1]
switchtype=euroisdn
context=from-pstn
group=0
signalling=pri_cpe
channel =>1-10
The group=0 option is what you see in FreePBX trunks ie Zap/g0. the g0 means what zaptel group your trunk applies to.
Note the switchtype, and signalling. Also use the pridialpland, and prilocaldialplan options, as I could not make outbound calls without them.
You need to select PRI CPE, type E1, clock Normal as the clock comes from the telco, and the channels option depends on how many lines you have. You can see above that I only have 10 enabled on our ISDN 30. Your PRI d channel will be number 16.
Dial plan option should by default show from-pstn. This is the dialplan context you want calls coming in from outside being directed to.
Hope that helps.
You can see if it’s running and connected correctly by typing pri show spans at the CLI.
Thi is what I get when I type pri show span 1 (pri show spans shows just the one span). Note that the ISDN isn’t plugged into the card yet because I can’t do that till I get it on the customer’s site. Does this look okay?
pbx*CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, In Alarm, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3
Considering it’s not plugged in it looks OK in the status area.
Our system is live, and I’m waiting on changing over from our old system, so our PRI isn’t plugged in either 
elastix*CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, In Alarm, Down, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: -1
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3
I set up the system on the ISN and it’s not working. The ISDN was receiving calls but nto making them for a while now i’ts doing neither. Here’s the debug output on the span, it looks to me as if it’s continually resetting but I don’t know:
[code]pbx*CLI> pri debug span 1
Enabled debugging on span 1
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
– Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:733 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
– Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:733 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
– Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:733 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
– Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:733 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
Protocol Discriminator: Q.931 (8) len=13
Call Ref: len= 2 (reference 0/0x0) (Originator)
Message type: RESTART (70)
[18 03 a9 83 84]
Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan
: 0
ChanSel: As indicated in following octets
Ext: 1 Coding: 0 Number Specified Channel Type: 3
Ext: 1 Channel: 4 ]
[79 01 80]
Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated Channel (
Protocol Discriminator: Q.931 (8) len=13
Call Ref: len= 2 (reference 0/0x0) (Originator)
Message type: RESTART (70)
[18 03 a9 83 85]
Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan
: 0
ChanSel: As indicated in following octets
Ext: 1 Coding: 0 Number Specified Channel Type: 3
Ext: 1 Channel: 5 ]
[79 01 80]
Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated Channel (