Hi!
I have setup a Trixbox and while I am able to receive calls from within the trixbox and to receive calls from outside (PSTN & GSM). I am unable to make any calls to the outside. For clarification I have attached my zaptel and zapata files here below. I appreciate all help that I can get on this issue.
ZAPTEL.CONF:
since you are using trixbox (but you don’t say which version) they have a script that you should run to configure zaptel properly.
In 1.2 it was called genzaptelconf, once that was done you needed to reboot the box so that it loaded the configured drivers and things started to work. I don’t know if they changed the name of it going forward in newer versions but have you run that script yet and rebooted?
a good manual to take a look at is trixbox without tears 2. You’ll find it on the web in many locations and it walks you through the whole process.
I checked the manual, haven’t been able to figure out anything yet from it. Did run the genzaptelconf though, didn’t make any difference.
Since you asked for the version I checked it out and it is trixbox CE current release is 2.6.1.13. I have updated everything on the server with the newest packages.
Well to start you are missing two lines to start in your zaptel.conf file the parameters you are missing are: loadzone = and defaultzone = . They default to us if they are missing and based on your config you are not in the US so that can cause problems.
At the linux command line type ztcfg -vv
This should give you a output with all the channels listed, if not the drivers are not loading the configuration correctly. Asterisk only see’s what the privers say is is available and FreePBX only see’s what asterisk says it see’s.
I always get the prompt “Your call cannot be completed as dialed, please check the number and dial again” or “all circuits are busy now, please try your call again later”
Yes, it sounds like you have an outbound routing problem. Make sure your trunk is listed as the top sequence in the outbound route. Also, I’ve never used a pri, but asterisk may be sending the digits too quickly (this happens often with zap hardware). Try adding a wait command (w) before the trunk’s dial rules- for example: w+XXXXXXX
Still no solution on my end. I am battling with the problem. I can’t figure out what’s wrong with the setup.
There is one zap trunk setup with the id ZAP/g1, dial rule pretty straight forward just XXXXXXX (seven digits) and caller id hidden (have also tried various numbers).
The outbound route has the same dial pattern as the trunk (XXXXXXX) trunk sequence ZAP/g1
I just don’t see what the problem is and any help would be greatly appreciated.
I figured out what the problem was. I had incorrect zaptel configuration. As can be seen on my first post I had the span configured with crc4 when it shouldn’t be setup with crc4. (span=1,1,0,ccs,hdb3,crc4). That and the need to use a custom trunk setup enabling DAHDI instead of Zap solved the issue at hand. By using “DAHDI/g1/$OUTNUM” as the custom dialout string. I hope this helps someone out there.