Askozia Forums
February 09, 2012, 06:00:25 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Digium TDM40XX  (Read 2412 times)
stuntshell
Newbie
*

Karma: 0
Posts: 5


View Profile
« on: February 21, 2010, 09:38:09 pm »

Does anyone have one of these cards working?
I'm getting this error, but the config is correct:
Code:
Feb 21 19:00:29 asterisk[1190]: WARNING[1195]: chan_dahdi.c:8146 in handle_init_event: Unable to play dialtone on channel 2, do you have defaultzone and loadzone defined?
Feb 21 19:00:29 asterisk[1190]: VERBOSE[1236]: -- Starting simple switch on 'DAHDI/2-1'
Feb 21 19:00:34 asterisk[1190]: VERBOSE[1236]: -- Hungup 'DAHDI/2-1'
This happens when I take the phone off-hook. None of my lines FXS and FXO work.
Regular SIP and IAX phones and trunks work fine, including the conference room.

Thanks,
Logged
Michael
Askozia Staff
Hero Member
*

Karma: 50
Posts: 1020


View Profile
« Reply #1 on: February 22, 2010, 07:12:30 am »

I have this issue with some not-yet-stable custom drivers for the COMpact 3000 hardware. I have not been able to track it down.

What version are you using?
Logged
Michael
Askozia Staff
Hero Member
*

Karma: 50
Posts: 1020


View Profile
« Reply #2 on: February 22, 2010, 03:11:08 pm »

My problem seems to have been related to some unused channels in the system. By removing an unused ISDN module, everything now works.

What cards are present in your system? How are they (or are they at all) being used?
Logged
stuntshell
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #3 on: February 23, 2010, 12:08:46 pm »

My problem seems to have been related to some unused channels in the system. By removing an unused ISDN module, everything now works.
How can I remove this module?
Quote
What cards are present in your system? How are they (or are they at all) being used?
It's a Digium TDM400P with 02 FXO modules and 01 FXS module.

Code:
/root # cat /etc/dahdi/system.conf
# Hardware Info
# analog fxo channel 1 (Port 1) is on card Wildcard TDM400P REV I
# analog fxs channel 2 (Port 2) is on card Wildcard TDM400P REV I
# analog fxo channel 3 (Port 3) is on card Wildcard TDM400P REV I
# analog non channel 4 (Port 4) is on card Wildcard TDM400P REV I

# Dynamic Spans

# Spans

# Channels
fxsks=1
fxoks=2
fxsks=3
fxsks=4 <= Empty
Logged
Michael
Askozia Staff
Hero Member
*

Karma: 50
Posts: 1020


View Profile
« Reply #4 on: February 23, 2010, 03:04:30 pm »

Could you post the output of executing: /usr/sbin/dahdi_scan

If that module is not present, Askozia should not generate configuration for it....or more intelligently ignore it.
Logged
stuntshell
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #5 on: February 23, 2010, 04:17:34 pm »

Code:
/root # /usr/sbin/dahdi_scan
[1]
active=yes
alarms=OK
description=Wildcard TDM400P REV I Board 5
name=WCTDM/4
manufacturer=Digium
devicetype=Wildcard TDM400P REV I
location=PCI Bus 01 Slot 14
basechan=1
totchans=4
irq=10
type=analog
port=1,FXO
port=2,FXS
port=3,FXO
port=4,none
/root #
Logged
giovanni.v
Hero Member
*****

Karma: 51
Posts: 666


View Profile
« Reply #6 on: February 23, 2010, 05:42:31 pm »

I replicated something similar to this behaviour using an Openvox A400P with an FXO module and two FXS modules, one place intentionally left empty. Askozia generated 4 ports in /etc/dahdi/system.conf and asterisk refused to load tonezones  so nothing works.

Auto generated /etc/dahdi/system.conf:
# Hardware Info
# analog fxo channel 1 (Port 1) is on card Wildcard TDM400P REV E/F
# analog fxs channel 2 (Port 2) is on card Wildcard TDM400P REV E/F
# analog fxs channel 3 (Port 3) is on card Wildcard TDM400P REV E/F
# analog non channel 4 (Port 4) is on card Wildcard TDM400P REV E/F

# Dynamic Spans

# Spans

# Channels
fxsks=1
fxoks=2
fxoks=3
fxsks=4

# Tone Zones
loadzone=us
defaultzone=us

# Echo Cancellers
echocanceller=mg2,1
echocanceller=mg2,2
echocanceller=mg2,3
echocanceller=mg2,4


Deleting the unwanted port from the gui (Telephony Ports->Analog) now all dahdi hardware works but... only until system reboots.

The only valid workaround is to override the auto generated dahdi configuration.
@stuntshell... press esc in the askozia gui, click on the files tab, select etc/dahdi/system.conf, choose override then remove the lines referring to the latest module both in the channel and echo cancellers. Save and reboot.

However there are a couple of additional bugs in the fxo config but I won't to speak about until can understand the exact behaviour.
« Last Edit: February 23, 2010, 05:45:57 pm by giovanni.v » Logged
stuntshell
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #7 on: February 23, 2010, 06:52:31 pm »

Quote
@stuntshell... press esc in the askozia gui, click on the files tab, select etc/dahdi/system.conf, choose override then remove the lines referring to the latest module both in the channel and echo cancellers. Save and reboot.
It works!
I haven't tested the FXO ports but will do in a few.

Thanks,
Logged
giovanni.v
Hero Member
*****

Karma: 51
Posts: 666


View Profile
« Reply #8 on: February 23, 2010, 08:11:06 pm »

If that module is not present, Askozia should not generate configuration for it....or more intelligently ignore it.

I fixed the code for analog ports detection, now ignore the latest module testing on the same configuration as before. I will test again tomorrow leaving an "hole" in the card middle to see what happens.
Logged
stuntshell
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #9 on: February 24, 2010, 12:26:28 am »

Just an FYI,
FXO ports working fine Wink

Thanks,
Logged
giovanni.v
Hero Member
*****

Karma: 51
Posts: 666


View Profile
« Reply #10 on: February 24, 2010, 07:53:29 am »

Done some other tests on mixed modules configuration, seems ok.

Fix committed https://wush.net/trac/askozia/changeset/1388.
Logged
Michael
Askozia Staff
Hero Member
*

Karma: 50
Posts: 1020


View Profile
« Reply #11 on: February 24, 2010, 09:27:14 am »

Great find and fix, Giovanni. Thanks for testing and getting that in!

This tonezone loading problem came up testing some other hardware last week and I had never seen it before. Another DAHDI mystery solved.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.169 seconds with 20 queries.