Manage Dahdi Channels in Elastix

Ashraf.jabali

Joined
Nov 15, 2009
Messages
22
Likes
0
Points
0
#1
Hi All,

I would like to know if any one can help me with maneging the dahdi channels for control the inbound and outbound calls

Also i have one question please.

I installed elastix on my server with openvox A1200P 12 FXO port but all the ports or channel in the same group which is G0

How can i make it as 3 group each group have 4 channels please if any one have answer for me i will thanks for you.

Please find below my conf:

1- chan_dahdi.conf.template
;# Flash Operator Panel will parse this file for dahdi trunk buttons
;# AMPLABEL will be used for the display labels on the buttons

;# %c Dahdi Channel number
;# %n Line number
;# %N Line number, but restart counter
;# Example:
;# ;AMPLABEL:Channel %c - Button %n

;# For Dahdi/* buttons use the following
;# (where x=number of buttons to dislpay)
;# ;AMPWILDCARDLABEL(x):MyLabel


[channels]
language=en

; include dahdi extensions defined in FreePBX
#include chan_dahdi_additional.conf

; XTDM20B Port #1,2 plugged into PSTN
;AMPLABEL:Channel %c - Button %n
context=from-pstn
signalling=fxs_ks
faxdetect=incoming
usecallerid=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
group=0
channel=1-2
********************************************************************

2- chan_dahdi.conf

[trunkgroups]

[channels]
context=from-pstn
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
callerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=5.0
txgain=5.0
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=3

immediate=no

#include dahdi-channels.conf
#include chan_dahdi_additional.conf

*************************************************************************************


3- dahdi-channels.conf


; Autogenerated by /usr/sbin/dahdi_genconf on Tue Nov 3 12:52:07 2009 -- do not hand edit
; 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: OPVXA1200/12 "OpenVox A1200P/A800P Board 13" (MASTER)
;;; line="1 OPVXA1200/12/0 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

;;; line="2 OPVXA1200/12/1 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=default

;;; line="3 OPVXA1200/12/2 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=default

;;; line="4 OPVXA1200/12/3 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
callerid=
group=
context=default

;;; line="5 OPVXA1200/12/4 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 5
callerid=
group=
context=default

;;; line="6 OPVXA1200/12/5 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 6
callerid=
group=
context=default

;;; line="7 OPVXA1200/12/6 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 7
callerid=
group=
context=default

;;; line="8 OPVXA1200/12/7 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 8
callerid=
group=
context=default

;;; line="9 OPVXA1200/12/8 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 9
callerid=
group=
context=default

;;; line="10 OPVXA1200/12/9 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 10
callerid=
group=
context=default

;;; line="11 OPVXA1200/12/10 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 11
callerid=
group=
context=default

;;; line="12 OPVXA1200/12/11 FXSKS (EC: OSLEC)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 12
callerid=
group=
context=default
 

omid.mohajerani

Joined
Jul 10, 2009
Messages
18
Likes
0
Points
0
#2
easily change the group option for your channels

for example:


signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=default


signalling=fxs_ks
callerid=asreceived
group=1
context=from-pstn
channel => 3
callerid=
group=
context=default

signalling=fxs_ks
callerid=asreceived
group=1
context=from-pstn
channel => 4
callerid=
group=
context=default
 

Ashraf.jabali

Joined
Nov 15, 2009
Messages
22
Likes
0
Points
0
#3
Hi I tried to do that its not working as still its showing in the outbound tap zap/g0, its not showing any additional group


Is there another way to handle and manage the channel i need to do this scenario

i have 12 ports FXO that mean i have 12 channel, i need to make 4 channels for fax and 4 channels for call center the other 4 channels for office auto attendance


Thank you in advance
 

omid.mohajerani

Joined
Jul 10, 2009
Messages
18
Likes
0
Points
0
#4
Ashraf.jabali said:
Hi I tried to do that its not working as still its showing in the outbound tap zap/g0, its not showing any additional group


Is there another way to handle and manage the channel i need to do this scenario

i have 12 ports FXO that mean i have 12 channel, i need to make 4 channels for fax and 4 channels for call center the other 4 channels for office auto attendance


Thank you in advance
Yes . it will not appear automatically . you should make it . after you change it , make a ZAP trunk and fill the "Zap Identifier (trunk name)" to g1 or g2 etc.
Now you can use different inbound/inbound route for your channels.
Goodluck
 

Ashraf.jabali

Joined
Nov 15, 2009
Messages
22
Likes
0
Points
0
#5
yes you are right but this way work only if you want to manage the outbound calls


i need some thing to manage the inbound calls as i show you in the example
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#6
RTFM (Elastix Without Tears) then change context from-pstn to from-zaptel (you use dahdi)
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,565
Latest member
omarmenichetti
Top