ZAP Channel DID issue

Guys,
my chan_dahdhi.conf is…

;
; DAHDI telephony
;
; 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=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include setup-pstn configs
#include dahdi-channels.conf

group=1

;Include PBXconfig configs
#include chan_dahdi_additional.conf

======================

dadhi_channels is…

; Autogenerated by /usr/sbin/dahdi_genconf on Tue Nov 30 15:38:13 2010
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: WCTDM/4 “Wildcard TDM400P REV I Board 5” (MASTER)
;;; line="1 WCTDM/4/0 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=from-zaptel
;;context=default

;;; line="2 WCTDM/4/1 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=from-zaptel

;;; line="3 WCTDM/4/2 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=from-zaptel

;;; line="4 WCTDM/4/3 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
callerid=
group=
context=from-zaptel

Now I am using TB2.8.0 CE. I have a Digium TDM400 FXO card with 4 ports. I wish to use the Channel 1 for outgoing trunk and Ch 2 for incoming route (or vice versa). It is kind of binding the in/out calls to a specific channels (ports of the card). If i use anyDID/anyCID, it works… but that is not binding with a port… any ideas?? I made a zap channel DID with FXO2 and a it is not working… (but outbound is working with binding zap channel 1, i tested, if i switch the cable to port 2,3,4 it cant make out calls… but i wish to tie the incoming with ch1 and outgoing with ch2.) Here is the CLI…

– Starting simple switch on ‘DAHDI/1-1’
– Starting simple switch on ‘DAHDI/2-1’
– Executing [[email protected]:1] NoOp(“DAHDI/1-1”, “No DID or CID Match”) in new stack
– Executing [[email protected]:2] Answer(“DAHDI/1-1”, “”) in new stack
– Executing [[email protected]:3] Wait(“DAHDI/1-1”, “2”) in new stack
– Executing [[email protected]:1] NoOp(“DAHDI/2-1”, “No DID or CID Match”) in new stack
– Executing [[email protected]:2] Answer(“DAHDI/2-1”, “”) in new stack
– Executing [[email protected]:3] Wait(“DAHDI/2-1”, “2”) in new stack
– Executing [[email protected]:4] Playback(“DAHDI/1-1”, “ss-noservice”) in new stack
– Executing [[email protected]:4] Playback(“DAHDI/2-1”, “ss-noservice”) in new stack
– Playing ‘ss-noservice.gsm’ (language ‘en’)
– Playing ‘ss-noservice.gsm’ (language ‘en’)
– Executing [[email protected]:5] SayAlpha(“DAHDI/1-1”, “”) in new stack
– Executing [[email protected]:6] Hangup(“DAHDI/1-1”, “”) in new stack
== Spawn extension (from-pstn, s, 6) exited non-zero on ‘DAHDI/1-1’
– Executing [[email protected]:1] Hangup(“DAHDI/1-1”, “”) in new stack
== Spawn extension (from-pstn, h, 1) exited non-zero on ‘DAHDI/1-1’
– Hungup ‘DAHDI/1-1’
– Executing [[email protected]:5] SayAlpha(“DAHDI/2-1”, “”) in new stack
– Executing [[email protected]:6] Hangup(“DAHDI/2-1”, “”) in new stack
== Spawn extension (from-pstn, s, 6) exited non-zero on ‘DAHDI/2-1’
– Executing [[email protected]:1] Hangup(“DAHDI/2-1”, “”) in new stack
== Spawn extension (from-pstn, h, 1) exited non-zero on ‘DAHDI/2-1’
– Hungup ‘DAHDI/2-1’

help me guys please…

Mishu~

First of all this is not trixbox support. trixbox forked FreePBX then abandoned the project. The trixbox you are using is based on FreePBX 2.6 and Asterisk 1.6, both end of life packages.

Have you taken a look at the latest FreePBX distro? You no longer have to install FreePBX by hand. The Distro install the latest Asterisk and FreePBX for you.

To answer your question on the Zap DID, you put whatever pseudo DID you assigned in the Zap DID setup page in the DID field on the inbound route.

set overlapdial=yes in dahdi channel additional file.