Trixbox Replacement - Overcoming Span problem on ISDN 30

Chrism2
Posts: 90
Member Since:
2007-08-15

Once of our clients had a Trixbox system put in two months ago, but the build used was buggy and the list of issues with the install was massive. Some the issues simply couldn't be addressed without a full rebuild of the server.

Like most companies, they are reliant on their telephone system being operational during office hours, so rebuilding the installed server was not an option. We were also getting some complaints about echo on calls.

We took the decision to start from scratch using the same HP Blade server specification but replacing the existing Digium Wilcard with a Sangoma A101D with echo cancellation. Despite issues discussed later, this turned out to be an excellent decision.

I might also add that four weeks ago, I was a total novice on Trixbox and my experience with Linux was negligable. I'm happy to say that after a three day training course, some time designing a new build and patience devising a proper dial plan, it's all paid off. But not without some seriously commendable intervention by Sangoma.

The systems worked perfectly in our offices' test ISDN 30 box. But on connecing our newly configured system to the BT ISDN 30 PRI NTE 2e box at the clients' side, we were getting no calls in or out. Asterisk was reporting "Channel 1 down" and I was getting nowhere. I suppose being UK based worked to our advantage in that the people at Sangoma were able to look at our system out of business hours using an SSH session. From their final report, I can see that the problem was neither common nor easy to fix. However, they spend several "nights" (days to them!) going through this system until coming up with the fix. I might add that it looks like the fix involves a driver change; one of their software developers talking to me directly about the problems.

Last night at 11pm I called Sangoma for an update - where I was given the good news a fix had been found. I took a leap of faith this morning and left the site connected to the new server. There has been not one complaint. Not one dropped call, no echo and simlies all 'round. Needless to say, my boss is ecstatic. He even gave me the afternoon off. :-)

I have serveral more new builds to put in place soon. Props to the team at Sangoma for their support and help with this:- one thing for sure, I'll be sticking with them on my projects.



stujava
Posts: 5
Member Since:
2007-07-08
A101D UK ISDN30

Hi maybe you would help me, with my install, i have a Sangoma A101D and an ISDN30 with 8 channels from BT. my inbound calls are working great and with the quality you would expect from BT. problem is when i dial out i get all circuits are busy. is there extra setup that i have missed. i see a lot about dialplans but i havent changed anything can you tell me how you got your's working
stuart



Chrism2
Posts: 90
Member Since:
2007-08-15
Did you solve your problem?

Did you solve your issue? Still need help?



Cadfael
Posts: 5
Member Since:
2008-05-13
same problem here

I have exactly the same problem here. Trixbox with Sangoma card, BT ISDN30 with 10 channels enabled. Incoming calls ok but "all circuits busy" on outgoing.

How did you fix yours?

Cadfael



Chrism2
Posts: 90
Member Since:
2007-08-15
Couple of things to check

Couple of things to check spring to mind:

1) in zapata.conf do you have pridialplan=unknown?

2) in FreePbx, under Trunks, for your ZAP/g0 trunk, make sure that maximum channels is blank, not 0. Got us a couple of times.

If you still have bother, post your zapata.conf for starters.

Hope this might help.



Cadfael
Posts: 5
Member Since:
2008-05-13
Max channels was blank. I

Max channels was blank. I had dial plan set to local. Have now changed it. Unfortunately this server suffers a kernel panic every time zaptel is restarted, and most times when rebooted, so can't be rebooted remotely.

zapata.conf is now as follows

;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

pridialplan=unknown

[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

;Sangoma A101 port 1 [slot:2 bus:3 span:1]

switchtype=euroisdn

context=from-pstn

signalling=pri_cpe

channel =>1-10

--------------------------

zaptel.conf follows

# Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not hand edit
# Zaptel Channels Configurations (zaptel.conf)
#
loadzone=uk
defaultzone=uk

#Sangoma A101 port 1 [slot:2 bus:3 span:1]
span=1,0,0,ccs,hdb3,crc4
bchan=1-10
hardhdlc=16



Chrism2
Posts: 90
Member Since:
2007-08-15
There's a problem with

There's a problem with zaptel, especially if it's going into panic when you restart it.

Is that the zapata.conf generated after a Standard install. Which version of Trixbox are you using?

Our (working) zapata.conf is laid out differently:

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-pstn
signalling=pri_cpe
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

pridialplan=unknown
nationalprefix=0
internationalprefix=00

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

group=1

;Include AMP configs
#include zapata_additional.conf

# Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not hand edit
# Zaptel Channels Configurations (zaptel.conf)
#
loadzone=us
defaultzone=us

#Sangoma A101 port 1 [slot:2 bus:2 span:1]
span=1,0,0,ccs,hdb3,crc4
bchan=1-15,17-31
hardhdlc=16

Let me know how you're getting on.



Cadfael
Posts: 5
Member Since:
2008-05-13
thanks for that' I'll try

thanks for that' I'll try some of those settings at the next boot.
in zapata-channels.conf what do you have? is there anything in zapata-additional.conf?
Could you post these files, as ours just uses the one file, and I want to be sure I haven't missed anything.

Cadfael



Chrism2
Posts: 90
Member Since:
2007-08-15
Zapata information

From zapata-auto.conf (zapata-channels has the same information in it)

; Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- 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
;
callerid=asreceived

;Sangoma A101 port 1 [slot:2 bus:2 span:1]
switchtype=euroisdn
context=from-zaptel
group=0
signalling=pri_cpe
channel =>1-15,17-31

There is nothing is zapata-addtional



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.