Zaptel Channel Not Recognising DID

Asterisk Asterisk Support
1

Hi,

I’m running PBX in a Flash, Asterisk v1.4.21.2, FreePBX 2.7.0.2

I have an FXO card installed in my system, which I’m using for faxing. The card is working, and I can send faxes, but receiving is eing a bit of a pain.

I’m trying to setup the inbound route so different Zaptel DIDs go to different destinations, but for some reason, the DIDs are not being recognised.

I have the Zap Channel DIDs setup, so for example, ‘Zap Channel 1’ has DID ‘0123456789’, then under inbound routes I have ‘Inbound Zap 1’ DID Number ‘0123456789’ with the destination set to ‘Fax (Hylafax)’. But, when I try to fax to this number, it fails, I’ve even tried calling with a normal voice call, and I get the error, saying something like ‘this number is not in use’. However, if I remove the DID Number, so it’s just blank, then fax, it works, the fax is received successfully, and if I call it, I get the squeaky fax noises.

It seems like the DID that is being assigned to the Zap channel under ‘Zap Channel DIDs’ is not being recognised by the inbound route.

Zapata.conf has the following:

[trunkgroups]
;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

[channels]
language=en
context=from-zaptel
signalling=fxs_ls
rxwink=300
;usedistinctiveringdetection=yes
channel=1
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=nochannel=1

Does anyone have any suggestions as to how to get inbound routes to recognise the Zap DIDs?

Thanks

Ben

2

I’ve the same problem.
In this week I’ve updated my TB from 2.6 to 2.8.0.8 and, now, I can receive call only if in inbound route I set any DID /any CID.
See my post on trixbox.org :
http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/inbound-route-and-did-number-trixbox-2804Have you found any solution for the issue?
Thanks in advance.
M4Biz

3

Howdy,

The routing of calls based on DID is not supported across analog trunk (FXO) ports.

Cheers.

4

Sorry malcomd,
but I use succesfully this feature on all my TB system (using Sangoma A200) only on this, particular, TB server, that I’ve upgraded from 2.6 to the latest 2.8.0.4 and that has a TDM400 with one FXO onboard, I’ve experienced this issue.
At the same time, on the same machine with TB 2.6 I can use inbound DID without any problem.

5

Howdy,

In your post on the Trixbox forum you reference that you’re not setting any CID number. CID is something that can be routed upon; DID is not for FXO - for other technologies like E1 or T1, yes.

Cheers.

6

Issue fixed!
I’ve resolved the issue:

  1. edit dahdi-channels.conf and change context=from-pstn in context=from-zaptel (you can view the change by show dahdi channel in CLI)
  2. Go to Zap Channel DIDs an Add a channel with your DID (see on wich channel your FXO module is installed, on my TB is Channel 4)
  3. add an Inbound Route with the same DID you has defined in Zap Channels
    All works fine!
    I hope this post can be helpful to others that has the same problem.
    M4Biz