Hi,

I am trying to do a fresh installation of Elastix 2.2.0 and use and Openvox A400P card with 2FXO and 2 FXS. I have read the Elastix without tears and tried to search online but haven't been able to successfully install/ configure the card.

Please help me and tell me what am i doing wrong here. How do i configure this card properly to get it working.


========================================================================================
I have installed the card as suggested. Connected the molex power supply.

The card is being detected in the Hardware Detection:
1 FXO Detected by Asterisk (Pink)
2 FXO Detected by Asterisk (Pink)
3 FXS Detected by Asterisk (Green)
4 FXS Detected by Asterisk (Green)

But when i check the dahdi_channels.conf it shows the FXS first and then FXO channels. When i reverse the positions of FXO and FXS on the phisical card, the channels file changes again. The hardware detector detects it fine though.

Does this cause any issue?



========================================================================================
Output from dmesg

Freshmaker version: 71
Freshmaker passed register test
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Installed -- AUTO FXO (FCC mode)
Module 2: Installed -- AUTO FXS/DPO
Module 3: Installed -- AUTO FXS/DPO
Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
rxt1: no version for "dahdi_hdlc_putbuf" found: kernel tainted.
dahdi: Registered tone zone 0 (United States / North America)


The "show channels" command comes up with an error message
Connected to Asterisk 1.8.7.0 currently running on localhost (pid = 4667)
Verbosity is at least 3
localhost*CLI> show channels
No such command 'show channels' (type 'core show help show channels' for other possible commands)

chan_dahdi.conf file
[trunkgroups]

[channels]
;context=from-pstn
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
useincommingcalleridonzaptransfer=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
language=au ;(default is us)
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.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


dahdi_channels.conf file
; Autogenerated by /usr/sbin/dahdi_genconf on Mon Feb 6 20:54:10 2012
; 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 E/F Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
callerid=
group=
context=default

;;; line="2 WCTDM/4/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 2
callerid=
group=
context=default

;;; line="3 WCTDM/4/2 FXOKS"
signalling=fxo_ks
callerid="Channel 3" <4003>
mailbox=4003
group=5
context=from-internal
channel => 3
callerid=
mailbox=
group=
context=default

;;; line="4 WCTDM/4/3 FXOKS"
signalling=fxo_ks
callerid="Channel 4" <4004>
mailbox=4004
group=5
context=from-internal
channel => 4
callerid=
mailbox=
group=
context=default

newboy,

We have a winner!!! (sorry me being tired and weary)

I say we have a winner as I haven't seen this question in years and its a good question....BTW, great detail in your post, made it easy to answer & worthy of a good response.

Your system is correctly configured.....your ports are being detected correctly, however in dahdi-channels.conf, it shows the signalling required

To quote a passage from Asterisk: The Definitive Guide,

A Foreign eXchange (FX) port is named by what it connects to, not by what it does. So, for example, a Foreign eXchange Office (FXO) port is actually a station: it connects to the central office. A Foreign eXchange Station (FXS) port is actually a port that provides the services of a central office (in other words, you would plug an analog set into an FXS port).

It is for this reason that the signaling settings in the Asterisk config files seem backwards: FXO ports use FXS signaling; FXS ports use FXO signaling. When you understand that the name of the physical port type is based on what it connects to, the signaling names in Asterisk make a bit more sense: if an FXO port connects to the central office, it needs to be able to behave as a station, and therefore needs FXS signaling.

probably explains it better than I could....

So your configuration is correct, but I suspect that your interest in that configuration file goes past just believing it to be incorrect. (unless you are a very thorough person)

Are you having problems with getting calls in and out??

Regards

Bob

Good answer Bob, I'm investigating the same topic
I have a similar connection with a Openvox A400P in chan_dahdi.conf and channels, in elastix 2.2.0, I create trunk and outbound routes, but even I can call from inside to any local number outside PBX, I can't receive calls... If anyone call me to a FXO port, just receive a message from busy of telecom server and on the console does not appear the call input

That's are my files,and I`m having problems with getting calls:
CLI>

CLI>dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-pstn default In Service
2 from-zaptel default In Service

chan_dahdi.conf
[channels]
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=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=6.0
txgain=6.7
callgroup=1
pickupgroup=1
relaxdtmf=yes

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

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

dahdi-channels.conf
; 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"
signalling=fxs_ks
callerid=asreceived
group=1
context=from-pstn
channel => 1
callerid=
group=
context=default
;;; line="2 WCTDM/4/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=1
context=from-zaptel
channel => 2
callerid=
group=
context=default

and Dmesg
Found a Wildcard TDM: Wildcard TDM400P REV I (2 modules)
dahdi: Registered tone zone 0 (United States / North America)
dahdi_echocan_oslec: Registered echo canceler 'OSLEC'
dahdi: Idled echo canceller because of CED rx detected on channel 2
dahdi: Idled echo canceller because of CED rx detected on channel 2
dahdi: Idled echo canceller because of CED rx detected on channel 2
dahdi: Idled echo canceller because of CED rx detected on channel 2

If you can help me with this item. I would be very grateful... With the previous version of elastix 1.6, I have not had this problem.

Hi all,
To install a A400P on elastix should be very easy and you almost have to do nothing changed on the configuration files. Only thing you need to do is to setup a inbound rule and outbound rule for A400P through the Web Panel. If you are still in trouble, you can send me email, I will check for you!
Good luck!

Thanks for your response and bob.

I had actually not tried the incoming and outgoing because i read somewhere that connecting the main phoneline to the wrong port can cause some damage the card.

I just wanted to be sure and do it right.

I have tried the incoming and outgoing and it is working.

Thanks for the suggestions and help.

Newboy,

Great to hear it is working and respect where you are coming from....

Last thing you want to do is throw away a card because you blew it up...

Glad to be of help....

Regards

Bob

I have a problem with this card
I have the same configuration
Port 3-4 are the 2 plugged in PSTN lines
The lines are in Spain, so the /etc/dahdi/system.conf "zones" is "es"

Whenever I make a call, i hear ringing, but its a phantom call, it doesn't actually calls...
What could be the problem?

dmesg output says at the end

ACPI: PCI Interrupt 0000:0a:00.0[A] -> GSI 16 (level, low) -> IRQ 177
wctdm24xxp 0000:0a:00.0: Port 1: Installed -- AUTO FXO (FCC mode)
wctdm24xxp 0000:0a:00.0: Port 2: Installed -- AUTO FXO (FCC mode)
wctdm24xxp 0000:0a:00.0: Port 3: Installed -- AUTO FXS/DPO
wctdm24xxp 0000:0a:00.0: Port 4: Installed -- AUTO FXS/DPO
wctdm24xxp 0000:0a:00.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 4 analog channels)
dahdi: Registered tone zone 0 (United States / North America)
dahdi_echocan_oslec: Registered echo canceler 'OSLEC'
dahdi: Registered tone zone 6 (Spain)


I don't know why the tone zone is shown twice, and one with each zone... like I said, system.conf has "es" ... do I have to set it somewhere else¿?