Ubuntu + Asterisk + FreePBX + Digium B410P + Telstra BRI = ?

Forums › VoIP › Ubuntu + Asterisk + FreePBX + Digium B410P + Telstra BRI = ?

magu

Professional yak shaver
1599 posts

Uber Geek
+1 received by user: 7

Trusted

BitSignal

Lifetime subscriber

#53865 14-Dec-2009 22:49

Howdy guys!

I've been helping a friend set up a replacement IP-PBX system to SwyxWare, but got a bit stuck with setting up the ISDN lines into Asterisk.

I've got Asterisk 1.6 running with DAHDI drivers for the Digium card and they show up in Asterisk correctly. I'm using switchtype=euroisdn and signalling=bri_cpe, but for some reason the calls don't show up in Asterisk at all.

I know the lines work because when using default switchtype= and signalling= values Asterisk will ring the configured extensions, but in this case the call drops after a few seconds and there's no ringing on the caller's side. I believe this has something to do with the signalling=, but ain't quite sure.

Anyone ever configured Telstra's ISDNs on a Digium card?

"Roads? Where we're going, we don't need roads." - Doc Emmet Brown

rphenix

990 posts

Ultimate Geek
+1 received by user: 127

ID Verified

Lifetime subscriber

#282674 15-Dec-2009 13:13

What version of DAHDI do you have? Support for B410P was only recently added to DAHDI (in the past year) prior to that mISDN was used. What modules do you have loaded (B410p uses the wcb4xxp dahdi module).

Other things to check make sure mISDN is not running. And perhaps you could try mISDN instead of DAHDI?

What is the contents of your system.conf from /etc/dadhi ? (perhaps upload it to pastebin.com

magu

Professional yak shaver
1599 posts

Uber Geek
+1 received by user: 7

Trusted

BitSignal

Lifetime subscriber

#282679 15-Dec-2009 13:28

Latest (stable) versions of all parts (Asterisk, FreePBX, DAHDI) compiled from source on Saturday. DAHDI loads up the wcb4xxp module correctly (although Ubuntu kernel was loading hfcmulti before, causing a conflict -- I blacklisted it) and mISDN is not installed at all.

I'll see if I can source the system.conf from that system. It was generated from dahdi_genconf.

"Roads? Where we're going, we don't need roads." - Doc Emmet Brown

rphenix

990 posts

Ultimate Geek
+1 received by user: 127

ID Verified

Lifetime subscriber

#282722 15-Dec-2009 14:48

There isn't much you need uncommented in the system.conf here is a good sample:
http://svnview.digium.com/svn/dahdi/tools/tags/2.1.0-rc3/system.conf.sample
important bits of system.conf:

loadzone = nz
defaultzone = nz

#span=<span num>,<timing source>,<line build out (LBO)>,<framing>,<coding>[,yellow]
#span 1
span=1,1,3,ccs,ami
bchan=1-2
dchan=3

#span 2
span=2,1,3,ccs,ami
bchan=4-5
dchan=6

#span3
span=3,1,3,ccs,ami
bchan=7-8
dchan=9

#span4
span=4,1,3,ccs,ami
bchan=10-11
dchan=12

#if that doesnt work try
#span=<span#>,1,0,ccs,ami

magu

Professional yak shaver
1599 posts

Uber Geek
+1 received by user: 7

Trusted

BitSignal

Lifetime subscriber

#283161 16-Dec-2009 17:51

/etc/dahdi/system.conf contents below:

# Autogenerated by /usr/sbin/dahdi_genconf on Sun Dec 13 18:13:38 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS RED
span=1,1,0,ccs,ami
# termtype: te
bchan=1-2
hardhdlc=3
echocanceller=mg2,1-2

# Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS
span=2,2,0,ccs,ami
# termtype: te
bchan=4-5
hardhdlc=6
echocanceller=mg2,4-5

# Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS
span=3,3,0,ccs,ami
# termtype: te
bchan=7-8
hardhdlc=9
echocanceller=mg2,7-8

# Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS
span=4,4,0,ccs,ami
# termtype: te
bchan=10-11
hardhdlc=12
echocanceller=mg2,10-11

# Global data

loadzone = nz
defaultzone = nz

"Roads? Where we're going, we don't need roads." - Doc Emmet Brown

magu

Professional yak shaver
1599 posts

Uber Geek
+1 received by user: 7

Trusted

BitSignal

Lifetime subscriber

#284177 20-Dec-2009 13:13

Finally got it going. Telstra's ISDN service uses bri_cpe for signalling, and I was trying bri_cpe_ptmp.

That sample file really helped a lot!

Remind me to buy you a beer in the next Geekzone Pizza!

"Roads? Where we're going, we don't need roads." - Doc Emmet Brown