Hi,
I have installed the below versions freshly and tried to make SIP to FXS calls. Asterisk is establishing a call leg in the SIP Side but not initiating a call leg towards the FXS line. I didn’t see any traces like “Dahdi/49 ringing” on the asterisk console and as i said anolog phone (FXS line 49) is not ringing.
Asterisk 1.6.1-rc1
DAHDI Version: 2.1.0.4
I am able to hear dial tone for anolog Phone connected to the FXS Lines 49 & 50.
SIP to SIP calls are working fine.
And my configuration of the dahdi files are mentioned as below:
System.conf -
fxoks=49
fxoks=50
fxsks=51
loadzone = us
defaultzone=us
chan_dahdi.conf
[trunkgroups]
; define any trunk groups
[channels]
; hardware channels
; default
usecallerid=yes
hidecallerid=no
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
;echotraining=yes
immediate=no
; define channels
context=phones ; Uses the [internal] context in extensions.conf
signalling=fxo_ks ; Uses FXO signaling for an FXS channel
channel => 49,50 ; Telephones attached to ports 49 and 50
context=incoming ; Incoming calls go to [incoming] context in extensions.conf
signalling=fxs_ks ; Uses FXS signaling for an FXO channel
channel => 51 ; PSTN line attached to port 51
extensions.conf
[default]
include => incoming
[incoming]
exten => 567,1,Answer()
exten => 567,2,Dial(Dahdi/49)
exten => 567,3,Hangup()
exten => 123,1,Answer()
exten => 123,2,Dial(Dahdi/50,10)
exten => 123,3,Hangup()
dahdi_cfg -vv
DAHDI Tools Version - 2.1.0.2
DAHDI Version: 2.1.0.4
Echo Canceller(s):
Configuration
Channel map:
Channel 49: FXO Kewlstart (Default) (Slaves: 49)
Channel 50: FXO Kewlstart (Default) (Slaves: 50)
Channel 51: FXS Kewlstart (Default) (Slaves: 51)
3 channels to configure.
dahdi_hardware
pci:0000:02:01.0 wct4xxp+ d161:0205 Wildcard TE205P (4th Gen)
pci:0000:02:02.0 wctdm24xxp+ d161:8005 Wildcard TDM410P
*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
49 incoming default In Service
50 incoming default In Service
51 incoming default In Service
Could anybody please help me in resolving this configuration issue…