keywords:pbx ip pbx voip gateway gsm gateway

× Questions about A400/800/1200 Analog Interface Card

FIX: A400P with SuSE 11.1 asterisk 1.6.1 and Dahdi 2.2.1 without any tones.

9 years 10 months ago #4600 by pemer
Hi there,

on the System is following installed:

SuSE 2.6.27.39-0.2-default #1 SMP 2009-11-23 12:57:38 +0100 x86_64 x86_64 x86_64 GNU/Linux
asterisk 1.6.1.13
dahdi-linux = 2.2.1
dahdi-tools = 2.2.1

following hardware:
Intel Atom 330 Board
A400P with one FXS Green card.

if i am start the dahdi channel driver, the connected analog telefon are under power. so far so good.
Than i start asterisk and in the asterisk-dahdi module says following:

== Registered application 'DAHDISendKeypadFacility'
== Parsing '/etc/asterisk/chan_dahdi.conf': == Found
== Parsing '/etc/asterisk/users.conf': == Found
-- Registered channel 1, FXO Kewlstart signalling
-- Registered channel 1, FXO Kewlstart signalling
-- Automatically generated pseudo channel
[Jan 30 23:51:04] WARNING[5103]: chan_dahdi.c:15084 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23.
[Jan 30 23:51:04] WARNING[5103]: chan_dahdi.c:15084 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31.
[Jan 30 23:51:04] WARNING[5103]: chan_dahdi.c:15084 process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35.
[Jan 30 23:51:04] WARNING[5103]: chan_dahdi.c:15084 process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39.
[Jan 30 23:51:04] WARNING[5103]: chan_dahdi.c:15084 process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47.
== Registered channel type 'DAHDI' (DAHDI Telephony Driver w/PRI w/SS7)
== Manager registered action DAHDITransfer
== Manager registered action DAHDIHangup
== Manager registered action DAHDIDialOffhook
* == Manager registered action DAHDIDNDon
== Manager registered action DAHDIDNDoff
== Manager registered action DAHDIShowChannels
== Manager registered action DAHDIRestart
Loaded chan_dahdi.so => (DAHDI Telephony w/PRI & SS7)

asterisk command: "dahdi show status":
DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFI 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
Wildcard TDM400P REV E/F Board 5 OK 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)

asterisk comamnd:
pseudo default default In Service
1 analog de default In Service

so far, so good.
But if i am abolish from the analog telefon the hearer, i hear nothing.
If i am try to dial out or something else on the analog telefone, nothing happend.
If i am try to dial the analog telefone with a SIP Client following happend in asterisk:

*CLI> == Using SIP RTP CoS mark 5
-- Executing [123@analog:1] Dial("SIP/telefon-00000001", "dahdi/g1/123456") in new stack
[Jan 30 23:59:19] WARNING[8025]: chan_dahdi.c:2501 dahdi_call: cidspill already exists??
-- Called g1/123456

The line is ringing, but you can not hear anything!
The line respand about the get-off the line.
Nothing happening in asterisk at this status if i am hangup the line with the analog telephone.
If i am hangup the line with the SIP client following happening in asterisk:

*CLI> -- Hungup 'DAHDI/1-1'
== Spawn extension (analog, 123, 1) exited non-zero on 'SIP/telefon-00000001'

Now i have the situation that the card didn't respond anymore in asterisk and the analog telephone is dead, without power?
If i take now the same call from the sip client to the analog telephone follwing happening in asterisk:

*CLI> == Using SIP RTP CoS mark 5
-- Executing [123@analog:1] Dial("SIP/telefon-00000002", "dahdi/g1/123456") in new stack
[Jan 31 00:10:34] WARNING[8061]: chan_dahdi.c:2539 dahdi_call: Unable to ring phone: Device or resource busy
-- Couldn't call g1/123456
-- Hungup 'DAHDI/1-1'
== Everyone is busy/congested at this time (0:0/0/0)
-- Auto fallthrough, channel 'SIP/telefon-00000002' status is 'CHANUNAVAIL'


I think this is a signalling problem, but i tried any kind of signalling out. With no result.
Did you know this problem ? and can you help me?
Work this card with dahdi 2.2.1 properly ?

with this ducumentaion had i am configured the system:
http://www.henkelm.de/computer/asterisk/tdm400p.html

thx in advance for a answear.

best regards

Patrick

i] Last edited by pemer at 2010-2-8 17:09 [/i
Attachments:
9 years 10 months ago #4607 by Joe.Yung
Hello Patrick,
Please add my MSN account: This email address is being protected from spambots. You need JavaScript enabled to view it. or Gtalk: This email address is being protected from spambots. You need JavaScript enabled to view it..
Let's chat there for more details.

9 years 10 months ago #4611 by james.zhu
yes, the A400P works with elastix-XX, trixbox-xxxxxx, zaptel and dahdi without any problem.
unless the hardware failed, it should be an very stable product.

9 years 10 months ago #4630 by pemer
Hi there,

first of all, i would like to thank Joe, Thank you!

If got a working status with this Card, with Dahdi-Linux 2.2.0.2 and 2.2.1 on a SuSE 11.1 System an a Elastix 1.6.X with diffenerent systems.

The primary fault was the PCI Riser card. On this RISER Card you can make a manuelle setup of adressing the pci bus sub system.
If have been change this settings manuelly and the card worked!

this is the link of the RISER card:
http://www.mini-tft.de/xtc-neu/product_info.php?info=p28680_Jetway-JPCI-RISER2A-PB--PCI-2x-Riser-Karte--mit-Ju.html

the jumper setting (hice to know):
Jumper adress: 1-2
setting with 24 adress

with Jumper set 2 (int)
Jumber int: 7-8
setting with int_d

please show at the RISER card, to follow my sentence.

my mainboard with Atom 330 cpu:
Intel D945GCLF2D

The secound problem was the signalling.
To get the right signalling, please read the source file "drivers/dahdi/fxo_modes.h" in the sources of dahdi-linux.

If you have been found your right signalling, my was "GERMANY", the word in the configuration like this:

"/etc/modprobe.d/dahdi"
options wctdm opermode=GERMANY

now your module know the right signalling.
After this you need to inform asterisk about your signalling:

/etc/asterisk/indications.conf
[general]
country=de

/etc/asterisk/chan_dahdi.conf
tonezone=29 ; -> stand for GERMANY -> please see your number with the command "dmesg | less"

Now, if you are doing right, have you got the right signalling or the base for busy tone detection dtmf and many more.

In Germany there is so many ways in the analog cable with RJ11 to connect a Analog device.

So wat information that you need, if you are useing or create a analog cable:

Pin Number 3 and 4 from the analog card you must connect to the 2 and 5 on the analog device.
As shown in the table:
A400P Card -> Analog Device
1 -> Not Connected
2 -> Not Connected
3 -> Pin 5 on the RJ11 connector on the other side
4 -> Pin 2 on the RJ11 connector on the other side
5 -> Not Connected
6 -> Not Connected

best regards

Patrick

i] Last edited by pemer at 2010-2-8 17:23 [/i
Time to create page: 0.030 seconds
Powered by Kunena Forum