Hi,
I've been running with TB 2.2ish for prob a couple of years now without any issues and thought it might be time for an upgrade. I downloaded and installed 2.8rc but ran into problems with Dahdi/zap config thing.
Initially it seemed to ignore my card altogether so I read around here and ran setup-pstn which seemed to pick up the card. I had already configured a zap trunk, extension and outbound routes based on my previous config. My handset (previously on ZAP/1-1) came alive and seems to work fine, dials internal codes and my IAX trunk as normal.
But dialout via zap (previously 4-1) yields the wonderful 'all circuits are busy' response :( Looking at the CLi console when attempting to dial in to zap shows absolutely nothing, just ignoring that port.
I have one FXO port and FXS port on the card.
Here is the Dahdi config:-
; Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXOKS (SWEC: MG2)"
signalling=fxo_ks
callerid="Channel 1"
mailbox=4001
group=5
context=from-internal
channel => 1
callerid=
mailbox=
group=
context=default
;;; line="4 WCTDM/4/3 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
callerid=
group=
context=default
Can anyone please point me in the right direction? I've tried using the channel numbers:-
4
4-1
1! should be fxs and does appear to be
Zap/4-1
ZAP/4
Dahdi/4-1
Dahdi/4
Both the last two options appear to drop back to Dahdi when submitted.
Any help gratefully received I'm at a bit of a loss here, would rather fix it than have to downgrade to a release with zaptel as zap is clearly going to dissapear soon...
Thanks....Jason.
Member Since:
2006-06-09