All
Rafael Rodríguez Do newer DAHDI versions include the drivers for old or outdated cards?
Let me elaborate:
Say there is an old or outdated, digium-compliant PCI-E card (lspci on CLI throws me Digium Comm) that should be working with a given dahdi version. If I installed the current (ie, most recent release) available DAHDI, should I be able to use the card just the same? Or must I stick to the old version?
If I must stick with the old version, could there be problems using recent Asterisk releases with an old dahdi? Is there a way to downgrade my current dahdi?
Best Answer chosen by Rafael RodríguezDenis (Sangoma) DAHDI still contains the drivers for old or updated cards, therefore you should be able to use it. This being said, please note that our Eng efforts to maintain the driver stop when the card reaches End of Life. This means that an old driver has an small chance to create problems.
As regards of downgrade, you can downgrade the version of DAHDI, but you will required to recompile Asterisk, this option is not recommended as you may not be ale to install old version of DAHDI on new operating systems
As regards of downgrade, you can downgrade the version of DAHDI, but you will required to recompile Asterisk, this option is not recommended as you may not be ale to install old version of DAHDI on new operating systems
Roxanne Tran What does "no interfaces" mean for your line of analog modular cards?
Does it mean they are not configured as either FXS or FX0?
Best Answer chosen by Roxanne TranBrian (Digium) OK, I understand the question better now. Thank you for clarifying. The no interfaces means that specific model of card does not ship with any modules. That link is referencing to a TDM410 (4 port analog card) and you can purchase the base card with different combinations of modules. The ones that say "no interfaces", simply means that card does not ship with any interfaces such as FXO and FXS modules.
Best Answer chosen by Denis (Sangoma) Denis (Sangoma) Mark,
The question that you posed is a little more complex than it seems.
The Asterisk's core does not interact directly with the Digium interfaces cards. As matter of fact, the core only communicates with the channels drives that reports the state of each available channels.
As an example:
If you have Asterisk setup with TE122 (24 channels) and TDM844 (8 channels). Asterisk will know that it has up to 32 available channels in chan_dahdi, but it won't know the hardware configuration on each of cards.
Within the chan_dahdi module - The channel driver that manages the communication between the Asterisk's core and DAHDI - there is a CLI command that you could use to query the status of each card.
dahdi show status
Example:
*CLI> dahdi show status
Description ....
T2XXP (PCI) Card 0 Span 1 ...
T2XXP (PCI) Card 0 Span 2 ...
Wildcard TDM410P ...
Keep in mind that this command reports all the cards detected by DAHDI regardless if their channels are configured in asterisk.
If you want to know the hardware configuration of the cards, we suggest to look for DAHDI output in dmesg. DAHDI will report all the modules that were detected during the cards initialization and you could look this information by running the following command:
dmesg | grep -i "wct" | grep -i "vpm"
Example:
[root@server ~]# dmesg | grep -i "wct" | grep -i "vpm"
wct4xxp 0000:03:08.0: VPM450: Not Present
wctdm24xxp 0000:04:02.0: Booting VPMADT032
wctdm24xxp 0000:04:02.0: VPM present and operational (Firmware version 125)
- WCT4XXP is the driver for the dual and quad span cards. "VPMxxx: Not Present" means that none of our digital cards have a hardware echo cancellation module
- WCTDM24XXP is the driver for our analog cards, " Booting VPMADT032" and "VPM present and operational" means that a Hardware echo cancelation was found and it's firmware was successfully loaded.
Keep in mind that the reported message about the hardware echo cancellation module could be different depending on card or module.
Please let me know if you have more questions.
The question that you posed is a little more complex than it seems.
The Asterisk's core does not interact directly with the Digium interfaces cards. As matter of fact, the core only communicates with the channels drives that reports the state of each available channels.
As an example:
If you have Asterisk setup with TE122 (24 channels) and TDM844 (8 channels). Asterisk will know that it has up to 32 available channels in chan_dahdi, but it won't know the hardware configuration on each of cards.
Within the chan_dahdi module - The channel driver that manages the communication between the Asterisk's core and DAHDI - there is a CLI command that you could use to query the status of each card.
dahdi show status
Example:
*CLI> dahdi show status
Description ....
T2XXP (PCI) Card 0 Span 1 ...
T2XXP (PCI) Card 0 Span 2 ...
Wildcard TDM410P ...
Keep in mind that this command reports all the cards detected by DAHDI regardless if their channels are configured in asterisk.
If you want to know the hardware configuration of the cards, we suggest to look for DAHDI output in dmesg. DAHDI will report all the modules that were detected during the cards initialization and you could look this information by running the following command:
dmesg | grep -i "wct" | grep -i "vpm"
Example:
[root@server ~]# dmesg | grep -i "wct" | grep -i "vpm"
wct4xxp 0000:03:08.0: VPM450: Not Present
wctdm24xxp 0000:04:02.0: Booting VPMADT032
wctdm24xxp 0000:04:02.0: VPM present and operational (Firmware version 125)
- WCT4XXP is the driver for the dual and quad span cards. "VPMxxx: Not Present" means that none of our digital cards have a hardware echo cancellation module
- WCTDM24XXP is the driver for our analog cards, " Booting VPMADT032" and "VPM present and operational" means that a Hardware echo cancelation was found and it's firmware was successfully loaded.
Keep in mind that the reported message about the hardware echo cancellation module could be different depending on card or module.
Please let me know if you have more questions.
Best Answer chosen by Denis (Sangoma) Denis (Sangoma) Mac,
According to Zaptel Sample configuration, you should be able to set PCM encoding by using the following command
alaw=1-4
# Overiding PCM encoding
# ~~~~~~~~~~~~~~~~~~~~~~
# Usually the channel driver sets the encoding of the PCM for the
# channel (mulaw / alaw. That is: g711u or g711a). However there are
# some cases where you would like to override that. 'mulaw' and 'alaw'
# set different such encoding. Use them for channels you have already
# defined with e.g. 'bchan' or 'fxoks'.
#mulaw=1-4
#alaw=1-4
For more information about how to configure Zaptel please read:
http://svn.digium.com/svn/zaptel/branches/1.4/zaptel.conf.sample
Additionally, I would like to mention that Zaptel has been discontinued and has been replaced by DAHDI (the Digium Asterisk Hardware Device Interface). See the following announcements:
http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/
To use DAHDI, you must use Asterisk 1.4.22 or later, or Asterisk 1.6.0 or later:
According to Zaptel Sample configuration, you should be able to set PCM encoding by using the following command
alaw=1-4
# Overiding PCM encoding
# ~~~~~~~~~~~~~~~~~~~~~~
# Usually the channel driver sets the encoding of the PCM for the
# channel (mulaw / alaw. That is: g711u or g711a). However there are
# some cases where you would like to override that. 'mulaw' and 'alaw'
# set different such encoding. Use them for channels you have already
# defined with e.g. 'bchan' or 'fxoks'.
#mulaw=1-4
#alaw=1-4
For more information about how to configure Zaptel please read:
http://svn.digium.com/svn/zaptel/branches/1.4/zaptel.conf.sample
Additionally, I would like to mention that Zaptel has been discontinued and has been replaced by DAHDI (the Digium Asterisk Hardware Device Interface). See the following announcements:
http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/
To use DAHDI, you must use Asterisk 1.4.22 or later, or Asterisk 1.6.0 or later:
Oleg Tsurikov Unable to create channel of type 'DAHDI' (cause 17 - User busy)
unable to create channel of type DAHDI (cause 17 user busy)
I installed Asterisk 1.8 on Linux Gentoo 6.4 with DAHDI version 2.6.2. I installed a TDM800P card with two red fxo modules.
My chan_dahdi.conf file looks like this:
[channels]
usecallerid = no
hidecallerid = no
callwaiting = yes
threewaycalling = yes
transfer = yes
echocancel = yes
echocancelwhenbridged = yes
rxgain = 0.0
txgain = 0.0
group = 1
signalling=fxs_ks
context = from-pstn
channel = 1-8
My system.conf looks like this:
loadzone = us
defaultzone = us
fxsks = 1-8
echocanceller = mg2,1-8
When I load the card with wctdm24xxp and dahdi_cfg -vv I got following output:
DAHDI Version: 2.6.1
Echo Canceller(s): HWEC, MG2
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04)
Channel 05: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 05)
Channel 06: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 06)
Channel 07: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 07)
Channel 08: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 08)
8 channels to configure.
Setting echocan for channel 1 to mg2
Setting echocan for channel 2 to mg2
Setting echocan for channel 3 to mg2
Setting echocan for channel 4 to mg2
Setting echocan for channel 5 to mg2
Setting echocan for channel 6 to mg2
Setting echocan for channel 7 to mg2
Setting echocan for channel 8 to mg2
I made a simple dailplan. My extensions.conf looks like this:
[from-pstn]
exten => s,1,Answer
exten => s,n,Wait(2)
exten => s,n,Dial(SIP/1403,10,m)
exten => s,n,Wait(2)
exten => s,n,Hangup
[Incoming]
exten => 6000,1,Dial(DAHDI/1/ww1451,20,rt)
exten => 6001,1,Dial(DAHDI/2/ww1451)
exten => 6002,1,Dial(DAHDI/4/ww1451,20,rt)
exten => 6003,1,Dial(DAHDI/5,20,rt)
I attached to telephone line to my asterisk server. When I call now from SIP/1403 - I got following output on the CLI: Unable to create channel of type "DAHDI" (cause 17 User busy).
Executing [6000@internal:1] Dial("SIP/1401-00000002", "DAHDI/1/ww1451,20,rt") in new stack
[Mar 19 10:01:28] WARNING[2628]: app_dial.c:2341 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 17 - User busy)
== Everyone is busy/congested at this time (1:1/0/0)
-- Auto fallthrough, channel 'SIP/1401-00000002' status is 'BUSY'
== Using SIP RTP CoS mark 5
-- Executing [6001@internal:1] Dial("SIP/1401-00000003", "DAHDI/2/ww1451") in new stack
[Mar 19 10:01:32] WARNING[2629]: app_dial.c:2341 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 17 - User busy)
== Everyone is busy/congested at this time (1:1/0/0)
-- Auto fallthrough, channel 'SIP/1401-00000003' status is 'BUSY'
Also, Asterisk doesn’t react at all at incoming outside phone calls.
What caused this error and how can I fix this?
How can I check a line status at any channel of my TDM800P card?
I installed Asterisk 1.8 on Linux Gentoo 6.4 with DAHDI version 2.6.2. I installed a TDM800P card with two red fxo modules.
My chan_dahdi.conf file looks like this:
[channels]
usecallerid = no
hidecallerid = no
callwaiting = yes
threewaycalling = yes
transfer = yes
echocancel = yes
echocancelwhenbridged = yes
rxgain = 0.0
txgain = 0.0
group = 1
signalling=fxs_ks
context = from-pstn
channel = 1-8
My system.conf looks like this:
loadzone = us
defaultzone = us
fxsks = 1-8
echocanceller = mg2,1-8
When I load the card with wctdm24xxp and dahdi_cfg -vv I got following output:
DAHDI Version: 2.6.1
Echo Canceller(s): HWEC, MG2
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04)
Channel 05: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 05)
Channel 06: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 06)
Channel 07: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 07)
Channel 08: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 08)
8 channels to configure.
Setting echocan for channel 1 to mg2
Setting echocan for channel 2 to mg2
Setting echocan for channel 3 to mg2
Setting echocan for channel 4 to mg2
Setting echocan for channel 5 to mg2
Setting echocan for channel 6 to mg2
Setting echocan for channel 7 to mg2
Setting echocan for channel 8 to mg2
I made a simple dailplan. My extensions.conf looks like this:
[from-pstn]
exten => s,1,Answer
exten => s,n,Wait(2)
exten => s,n,Dial(SIP/1403,10,m)
exten => s,n,Wait(2)
exten => s,n,Hangup
[Incoming]
exten => 6000,1,Dial(DAHDI/1/ww1451,20,rt)
exten => 6001,1,Dial(DAHDI/2/ww1451)
exten => 6002,1,Dial(DAHDI/4/ww1451,20,rt)
exten => 6003,1,Dial(DAHDI/5,20,rt)
I attached to telephone line to my asterisk server. When I call now from SIP/1403 - I got following output on the CLI: Unable to create channel of type "DAHDI" (cause 17 User busy).
Executing [6000@internal:1] Dial("SIP/1401-00000002", "DAHDI/1/ww1451,20,rt") in new stack
[Mar 19 10:01:28] WARNING[2628]: app_dial.c:2341 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 17 - User busy)
== Everyone is busy/congested at this time (1:1/0/0)
-- Auto fallthrough, channel 'SIP/1401-00000002' status is 'BUSY'
== Using SIP RTP CoS mark 5
-- Executing [6001@internal:1] Dial("SIP/1401-00000003", "DAHDI/2/ww1451") in new stack
[Mar 19 10:01:32] WARNING[2629]: app_dial.c:2341 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 17 - User busy)
== Everyone is busy/congested at this time (1:1/0/0)
-- Auto fallthrough, channel 'SIP/1401-00000003' status is 'BUSY'
Also, Asterisk doesn’t react at all at incoming outside phone calls.
What caused this error and how can I fix this?
How can I check a line status at any channel of my TDM800P card?
Best Answer chosen by Denis (Sangoma) Daniel (Sangoma) Oleg:
I see that you're hard-coding the channels that you wish for the extensions to be using. I would suggest that you set up logical groups for your PSTN configuration and allow Asterisk to auto-select an open line with which to dial to. Instructions on doing that can be found within the chan_dahdi.conf file that was provided upon Asterisk installation. If any problems persist, please contact Technical Support at +1 (256) 428-6000 or toll-free in the US at +1 (877) 344-4861.
If you want to check the status of any channel at any time, simply execute the command "core show channels" in the Asterisk CLI.
I see that you're hard-coding the channels that you wish for the extensions to be using. I would suggest that you set up logical groups for your PSTN configuration and allow Asterisk to auto-select an open line with which to dial to. Instructions on doing that can be found within the chan_dahdi.conf file that was provided upon Asterisk installation. If any problems persist, please contact Technical Support at +1 (256) 428-6000 or toll-free in the US at +1 (877) 344-4861.
If you want to check the status of any channel at any time, simply execute the command "core show channels" in the Asterisk CLI.
Best Answer chosen by Dan StruthersDenis (Sangoma) Dan,
If's my understanding that Asterisk/DAHDI is unable to restart an specifct port on a Digium card.
But, if the Channel lock that you mentioned on your previous comments means that there is zombie call (an active call, but there is no one using it) you could use the following CLI command in order to terminate the call (thus restarting the line).
*CLI> channel request hangup <Channel-ID>
If's my understanding that Asterisk/DAHDI is unable to restart an specifct port on a Digium card.
But, if the Channel lock that you mentioned on your previous comments means that there is zombie call (an active call, but there is no one using it) you could use the following CLI command in order to terminate the call (thus restarting the line).
*CLI> channel request hangup <Channel-ID>
Sadaf Farman DAHDI_SPANCONFIG failed on span 1
Hi,
I am using Digium card for PRIs,
When I run dahdi_cfg I got this message "DAHDI_SPANCONFIG failed on span 1: No such device or address (6)"
Kindly guide. Many thanks
I am using Digium card for PRIs,
When I run dahdi_cfg I got this message "DAHDI_SPANCONFIG failed on span 1: No such device or address (6)"
Kindly guide. Many thanks
Best Answer chosen by Sadaf FarmanSadaf FarmanIssue is resolved by upgrading dahdi version. Thanks for ur support.
Best Answer chosen by Brian (Digium) Brian (Digium) Sand,
Digium does not have any products that interfaces with cellular networks. We suggest to look on the internet for WCDMA/GSM 2 SIP.
For gateways, Digium has a G200 or G100 gateways.
Digium does not have any products that interfaces with cellular networks. We suggest to look on the internet for WCDMA/GSM 2 SIP.
For gateways, Digium has a G200 or G100 gateways.
# asterisk -rx "module show like timer"
If you see that res_timing_timerfd.so is in use and is running, then you're good.