DID's in 2.3 or 2.4 Trixbox

have you tried setting the DID on the extensions page (click the extension and DID is towards the top)??

I have tried everything possible.
this is a PRI from XO comm. it is a 16 channel flex product
i have set just the 1st 6 lines to hunt on the IAD. still doesnt work... it goes to the main IVR
what do need to see?

Did you give consideration to the previous post with the same subject text as this one? It seems to me your best bet. Try deleting the "catch everything" incoming route at the top of the list. If that helps, and you need to have a "catch everyting else" route, then try adding it back in at the bottom of the incoming route list. If deleting it helps and adding it back at the end breaks things again, then maybe there is a bug in FreePBX.

This section says:
Zap Channel DIDs allow you to assign a DID to specific Zap Channels. You can supply the same DID to multiple channels. This would be a common scenario if you have multiple POTS lines that are on a hunt group from your provider. You MUST assign the channel's context to from-zaptel for these settings to have effect. It will be a line that looks like:

context = from-zaptel

in your zapata.conf configuration effecting the specified channel(s). Once you have assigned DIDs you can use standard Inbound Routes with the specified DIDs to route your calls.

So, what should my zapata.conf look like then? Here is what I have:

;
; 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=900
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-auto.conf

group=1

;Include AMP configs
#include zapata_additional.conf

thanks for the help!
T

Thanks for the info Joe,
However, it didn't work before. That is the catch. When you call a DID number it goes right for the 1st open line in the hunt! When trixbox sees this, it comes in on the 1645 line even though 1327 was dialed! With that, it goes right to the IVR and NOT the targeted ext!
Is there any logs you would like to see? This is wearing on me big time and my client is wondering why it doesn't work. aaaahhh!! Thanks for you help!
Tom

I was certain I unsubscribed to the old but it still here... anyway.... very sorry for the confusion. my bad!! I deserve a cyber slap!

I completely removed the ZAP Channel DID thing. Calls are now starting to route they way they should. BUT!!! here is what happened... when i upgraded the trixbox it DID INDEED create ZAPChanl1 thru 6!! I did not create those, so, I renamed them and set them accordingly. But now it does make since for use with POTS. I was thinking it was a 'catch all' thing. So far it seems to be routing as planed! YEAH!
Thanks for the advise and help!
Tom

also, could you tell me what to do here on the forum to remove threads? That way I don't do this again! thank you!
Tom