Posted: Wed May 20, 2009 9:12 am Post subject: [asterisk-users] Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all!
Days ago I bought a OpenVox A400P card with a port FXS and another FXO
that I am testing with my Asterisk installation in my house. I'm using
Asterisk 1.4.24.1 with DAHDI Linux 2.1.0.4 and DAHDI Tools 2.1.0.2 on
Debian GNU/Linux Lenny.
I was reading "The future of telephony" and this [1] document looking
for information about how to configure both types of channels.
Hardware is recognized without problems by operating system and DAHDI:
I load the modules wctdm and dahdi. But when I execute in Asterisk CLI
"dahdi show channels", I get the following error message:
No such command 'dahdi show channels' (type 'help dahdi show' for other
possible commands)
I suppose that beyond not to have added in /etc/asterisk/extensions.conf
something like:
exten => s,1,Wait(1) ; Wait a second, just for fun
exten => s,n,Answer ; Answer the line
exten => s,n,Dial(dahdi/2) ; zap has been changed to dahdi
exten => s,n,Hangup
exten => 1,1,Dial(dahdi/2|60|m(default)) ; zap has been changed to dahdi
exten => 1,2,hangup
the command would have to exist. Which can be the problem?
Posted: Wed May 20, 2009 12:05 pm Post subject: [asterisk-users] Channels configuration with DAHDI
On Wed, May 20, 2009 at 07:03:15AM -0300, Daniel Bareiro wrote:
Quote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all!
Days ago I bought a OpenVox A400P card with a port FXS and another FXO
that I am testing with my Asterisk installation in my house. I'm using
Asterisk 1.4.24.1 with DAHDI Linux 2.1.0.4 and DAHDI Tools 2.1.0.2 on
Debian GNU/Linux Lenny.
I was reading "The future of telephony" and this [1] document looking
for information about how to configure both types of channels.
Hardware is recognized without problems by operating system and DAHDI:
Hint: you don't need to set 'signalling' for analog channels. Or just
set it explicitly to "auto". This is for Asterisk >= 1.6.0 . Simply
reduces the complication a bit...
On Wed, May 20, 2009 at 07:03:15AM -0300, Daniel Bareiro wrote:
Quote:
Hint: you don't need to set 'signalling' for analog channels. Or just
set it explicitly to "auto". This is for Asterisk >= 1.6.0 . Simply
reduces the complication a bit...
Thanks for the tip. I will remember it for when I use Asterisk 1.6 :-)
Quote:
> I load the modules wctdm and dahdi. But when I execute in Asterisk
> CLI "dahdi show channels", I get the following error message:
>
>
> No such command 'dahdi show channels' (type 'help dahdi show' for
> other possible commands)
# asterisk -r
Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
for details.
This is free software, with components licensed under the GNU General
Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
19777)
Verbosity is at least 7
alderamin*CLI>
alderamin*CLI> module unload chan_dadhi.so
alderamin*CLI> module load chan_dadhi.so
[May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
Error loading module 'chan_dadhi.so':
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
No such file or directory
[May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
'chan_dadhi.so' could not be loaded.
alderamin*CLI>
Mmmm... it would seem to be a bug:
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
No such file or directory
> On Wed, May 20, 2009 at 07:03:15AM -0300, Daniel Bareiro wrote:
> Hint: you don't need to set 'signalling' for analog channels. Or just
> set it explicitly to "auto". This is for Asterisk >= 1.6.0 . Simply
> reduces the complication a bit...
Thanks for the tip. I will remember it for when I use Asterisk 1.6 :-)
>> I load the modules wctdm and dahdi. But when I execute in Asterisk
>> CLI "dahdi show channels", I get the following error message:
>>
>>
>> No such command 'dahdi show channels' (type 'help dahdi show' for
>> other possible commands)
> Try running:
>
> asterisk -r
>
> and in that prompt:
>
> module unload chan_dadhi.so
> module load chan_dadhi.so
>
> and tell us the output you got.
# asterisk -r
Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
for details.
This is free software, with components licensed under the GNU General
Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
19777)
Verbosity is at least 7
alderamin*CLI>
alderamin*CLI> module unload chan_dadhi.so
alderamin*CLI> module load chan_dadhi.so
[May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
Error loading module 'chan_dadhi.so':
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
No such file or directory
[May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
'chan_dadhi.so' could not be loaded.
alderamin*CLI>
Mmmm... it would seem to be a bug:
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
No such file or directory
Sounds like DAHDI was installed/compiled *after* Asterisk was compiled.
Recompile Asterisk again and make sure
/usr/lib/asterisk/modules/chan_dahdi.so is created when you make install.
-Dave
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>> I load the modules wctdm and dahdi. But when I execute in Asterisk
>>> CLI "dahdi show channels", I get the following error message:
>>>
>>>
>>> No such command 'dahdi show channels' (type 'help dahdi show' for
>>> other possible commands)
Quote:
>> Try running:
>>
>> asterisk -r
>>
>> and in that prompt:
>>
>> module unload chan_dadhi.so
>> module load chan_dadhi.so
>>
>> and tell us the output you got.
Quote:
> # asterisk -r
> Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
> Created by Mark Spencer <markster@digium.com>
> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
> for details.
> This is free software, with components licensed under the GNU General
> Public
> License version 2 and other licenses; you are welcome to redistribute it
> under
> certain conditions. Type 'core show license' for details.
> =========================================================================
> Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
> 19777)
> Verbosity is at least 7
> alderamin*CLI>
> alderamin*CLI> module unload chan_dadhi.so
> alderamin*CLI> module load chan_dadhi.so
> [May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
> Error loading module 'chan_dadhi.so':
> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
> No such file or directory
> [May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
> 'chan_dadhi.so' could not be loaded.
> alderamin*CLI>
>
>
> Mmmm... it would seem to be a bug:
>
> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
> No such file or directory
Quote:
Sounds like DAHDI was installed/compiled *after* Asterisk was
compiled. Recompile Asterisk again and make sure
/usr/lib/asterisk/modules/chan_dahdi.so is created when you make
install.
Mmmm... but I believe that it had done already in that order. In fact, I
reviewed the existence of the module and it was in the directory. For that
reasonI said that perhaps it was bug by the following thing:
[May 20 20:49:07] WARNING[23599]: loader.c:359 load_dynamic_module:
Error loading module 'chan_dadhi.so':
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
^^^^^^^^^^^^^
No such file or directory
[May 20 20:49:07] WARNING[23599]: loader.c:653 load_resource: Module
'chan_dadhi.so' could not be loaded.
Apparently Asterisk is looking for the module using an incorrect name.
Whatever happens, I compile Asterisk again but I got the same error
message.
>>>> I load the modules wctdm and dahdi. But when I execute in Asterisk
>>>> CLI "dahdi show channels", I get the following error message:
>>>>
>>>>
>>>> No such command 'dahdi show channels' (type 'help dahdi show' for
>>>> other possible commands)
Quote:
>>> Try running:
>>>
>>> asterisk -r
>>>
>>> and in that prompt:
>>>
>>> module unload chan_dadhi.so
>>> module load chan_dadhi.so
>>>
>>> and tell us the output you got.
Quote:
>> # asterisk -r
>> Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
>> Created by Mark Spencer <markster@digium.com>
>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
>> for details.
>> This is free software, with components licensed under the GNU General
>> Public
>> License version 2 and other licenses; you are welcome to redistribute it
>> under
>> certain conditions. Type 'core show license' for details.
>> =========================================================================
>> Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
>> 19777)
>> Verbosity is at least 7
>> alderamin*CLI>
>> alderamin*CLI> module unload chan_dadhi.so
>> alderamin*CLI> module load chan_dadhi.so
>> [May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
>> Error loading module 'chan_dadhi.so':
>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>> No such file or directory
>> [May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
>> 'chan_dadhi.so' could not be loaded.
>> alderamin*CLI>
>>
>>
>> Mmmm... it would seem to be a bug:
>>
>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>> No such file or directory
Quote:
> Sounds like DAHDI was installed/compiled *after* Asterisk was
> compiled. Recompile Asterisk again and make sure
> /usr/lib/asterisk/modules/chan_dahdi.so is created when you make
> install.
Quote:
Mmmm... but I believe that it had done already in that order. In fact, I
reviewed the existence of the module and it was in the directory. For that
reasonI said that perhaps it was bug by the following thing:
[May 20 20:49:07] WARNING[23599]: loader.c:359 load_dynamic_module:
Error loading module 'chan_dadhi.so':
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
^^^^^^^^^^^^^
No such file or directory
[May 20 20:49:07] WARNING[23599]: loader.c:653 load_resource: Module
'chan_dadhi.so' could not be loaded.
Apparently Asterisk is looking for the module using an incorrect name.
Whatever happens, I compile Asterisk again but I got the same error
message.
Now that I see the error with a little more of thoroughness, it seems
that when doing a copy/paste in the CLI, the name of the module was
incorrect and for that reason I got that error message :-). Now get a
different error:
alderamin*CLI> module unload chan_dahdi.so
alderamin*CLI> module load chan_dahdi.so
[May 21 06:15:34] WARNING[25314]: chan_dahdi.c:1233 dahdi_open: Unable
to specify channel 2: No such device or address
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:7662 mkintf: Unable to open
channel 2: No such device or address
here = 0, tmp->channel = 2, channel = 2
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:11270 build_channels:
Unable to register channel '2'
Can this be due to something incorrect in the configurations that I
mentioned in a previous post? Whatever happens, could that be the cause
by which the command 'dahdi show status' is not found?
Posted: Thu May 21, 2009 8:59 am Post subject: [asterisk-users] Channels configuration with DAHDI
On Thu, May 21, 2009 at 06:38:27AM -0300, Daniel Bareiro wrote:
Quote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El miércoles 20 de mayo del 2009 a las 21:19:18 -0300,
Daniel Bareiro escribió:
>>>>> I load the modules wctdm and dahdi. But when I execute in Asterisk
>>>>> CLI "dahdi show channels", I get the following error message:
>>>>>
>>>>>
>>>>> No such command 'dahdi show channels' (type 'help dahdi show' for
>>>>> other possible commands)
>>>> Try running:
>>>>
>>>> asterisk -r
>>>>
>>>> and in that prompt:
>>>>
>>>> module unload chan_dadhi.so
>>>> module load chan_dadhi.so
>>>>
>>>> and tell us the output you got.
>>> # asterisk -r
>>> Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
>>> Created by Mark Spencer <markster@digium.com>
>>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
>>> for details.
>>> This is free software, with components licensed under the GNU General
>>> Public
>>> License version 2 and other licenses; you are welcome to redistribute it
>>> under
>>> certain conditions. Type 'core show license' for details.
>>> =========================================================================
>>> Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
>>> 19777)
>>> Verbosity is at least 7
>>> alderamin*CLI>
>>> alderamin*CLI> module unload chan_dadhi.so
>>> alderamin*CLI> module load chan_dadhi.so
>>> [May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
>>> Error loading module 'chan_dadhi.so':
>>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>>> No such file or directory
>>> [May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
>>> 'chan_dadhi.so' could not be loaded.
>>> alderamin*CLI>
>>>
>>>
>>> Mmmm... it would seem to be a bug:
>>>
>>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>>> No such file or directory
>> Sounds like DAHDI was installed/compiled *after* Asterisk was
>> compiled. Recompile Asterisk again and make sure
>> /usr/lib/asterisk/modules/chan_dahdi.so is created when you make
>> install.
> Mmmm... but I believe that it had done already in that order. In fact, I
> reviewed the existence of the module and it was in the directory. For that
> reasonI said that perhaps it was bug by the following thing:
>
> [May 20 20:49:07] WARNING[23599]: loader.c:359 load_dynamic_module:
> Error loading module 'chan_dadhi.so':
> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
> ^^^^^^^^^^^^^
> No such file or directory
> [May 20 20:49:07] WARNING[23599]: loader.c:653 load_resource: Module
> 'chan_dadhi.so' could not be loaded.
>
> Apparently Asterisk is looking for the module using an incorrect name.
> Whatever happens, I compile Asterisk again but I got the same error
> message.
Now that I see the error with a little more of thoroughness, it seems
that when doing a copy/paste in the CLI, the name of the module was
incorrect and for that reason I got that error message :-). Now get a
different error:
alderamin*CLI> module unload chan_dahdi.so
alderamin*CLI> module load chan_dahdi.so
[May 21 06:15:34] WARNING[25314]: chan_dahdi.c:1233 dahdi_open: Unable
to specify channel 2: No such device or address
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:7662 mkintf: Unable to open
channel 2: No such device or address
here = 0, tmp->channel = 2, channel = 2
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:11270 build_channels:
Unable to register channel '2'
In your configuration channel 2 is the first one, so this could be just
about anything related to accessing dahdi / zaptel .
Posted: Thu May 21, 2009 12:39 pm Post subject: [asterisk-users] Channels configuration with DAHDI
What are you getting if you do a dahdi_cfg -vv?
-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Daniel Bareiro
Sent: Thursday, May 21, 2009 4:38 AM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El miércoles 20 de mayo del 2009 a las 21:19:18 -0300,
Daniel Bareiro escribió:
Quote:
>>>> I load the modules wctdm and dahdi. But when I execute in Asterisk
>>>> CLI "dahdi show channels", I get the following error message:
>>>>
>>>>
>>>> No such command 'dahdi show channels' (type 'help dahdi show' for
>>>> other possible commands)
Quote:
>>> Try running:
>>>
>>> asterisk -r
>>>
>>> and in that prompt:
>>>
>>> module unload chan_dadhi.so
>>> module load chan_dadhi.so
>>>
>>> and tell us the output you got.
Quote:
>> # asterisk -r
>> Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
>> Created by Mark Spencer <markster@digium.com>
>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty'
>> for details.
>> This is free software, with components licensed under the GNU General
>> Public
>> License version 2 and other licenses; you are welcome to redistribute it
>> under
>> certain conditions. Type 'core show license' for details.
>>
=========================================================================
Quote:
>> Connected to Asterisk 1.4.24.1 currently running on alderamin (pid =
>> 19777)
>> Verbosity is at least 7
>> alderamin*CLI>
>> alderamin*CLI> module unload chan_dadhi.so
>> alderamin*CLI> module load chan_dadhi.so
>> [May 20 17:52:19] WARNING[10345]: loader.c:359 load_dynamic_module:
>> Error loading module 'chan_dadhi.so':
>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>> No such file or directory
>> [May 20 17:52:19] WARNING[10345]: loader.c:653 load_resource: Module
>> 'chan_dadhi.so' could not be loaded.
>> alderamin*CLI>
>>
>>
>> Mmmm... it would seem to be a bug:
>>
>> /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
>> No such file or directory
Quote:
> Sounds like DAHDI was installed/compiled *after* Asterisk was
> compiled. Recompile Asterisk again and make sure
> /usr/lib/asterisk/modules/chan_dahdi.so is created when you make
> install.
Quote:
Mmmm... but I believe that it had done already in that order. In fact, I
reviewed the existence of the module and it was in the directory. For that
reasonI said that perhaps it was bug by the following thing:
[May 20 20:49:07] WARNING[23599]: loader.c:359 load_dynamic_module:
Error loading module 'chan_dadhi.so':
/usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
^^^^^^^^^^^^^
No such file or directory
[May 20 20:49:07] WARNING[23599]: loader.c:653 load_resource: Module
'chan_dadhi.so' could not be loaded.
Apparently Asterisk is looking for the module using an incorrect name.
Whatever happens, I compile Asterisk again but I got the same error
message.
Now that I see the error with a little more of thoroughness, it seems
that when doing a copy/paste in the CLI, the name of the module was
incorrect and for that reason I got that error message :-). Now get a
different error:
alderamin*CLI> module unload chan_dahdi.so
alderamin*CLI> module load chan_dahdi.so
[May 21 06:15:34] WARNING[25314]: chan_dahdi.c:1233 dahdi_open: Unable
to specify channel 2: No such device or address
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:7662 mkintf: Unable to open
channel 2: No such device or address
here = 0, tmp->channel = 2, channel = 2
[May 21 06:15:34] ERROR[25314]: chan_dahdi.c:11270 build_channels:
Unable to register channel '2'
Can this be due to something incorrect in the configurations that I
mentioned in a previous post? Whatever happens, could that be the cause
by which the command 'dahdi show status' is not found?
Posted: Sun May 24, 2009 7:02 pm Post subject: [asterisk-users] Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Tzafrir, Danny.
El jueves 21 de mayo del 2009 a las 06:55:14 -0300,
Tzafrir Cohen escribió:
Quote:
> > Mmmm... but I believe that it had done already in that order. In fact, I
> > reviewed the existence of the module and it was in the directory. For that
> > reasonI said that perhaps it was bug by the following thing:
> >
> > [May 20 20:49:07] WARNING[23599]: loader.c:359 load_dynamic_module:
> > Error loading module 'chan_dadhi.so':
> > /usr/lib/asterisk/modules/chan_dadhi.so: cannot open shared object file:
> > ^^^^^^^^^^^^^
> > No such file or directory
> > [May 20 20:49:07] WARNING[23599]: loader.c:653 load_resource: Module
> > 'chan_dadhi.so' could not be loaded.
> >
> > Apparently Asterisk is looking for the module using an incorrect name.
> > Whatever happens, I compile Asterisk again but I got the same error
> > message.
Quote:
> Now that I see the error with a little more of thoroughness, it seems
> that when doing a copy/paste in the CLI, the name of the module was
> incorrect and for that reason I got that error message :-). Now get a
> different error:
>
> alderamin*CLI> module unload chan_dahdi.so
> alderamin*CLI> module load chan_dahdi.so
> [May 21 06:15:34] WARNING[25314]: chan_dahdi.c:1233 dahdi_open: Unable
> to specify channel 2: No such device or address
> [May 21 06:15:34] ERROR[25314]: chan_dahdi.c:7662 mkintf: Unable to open
> channel 2: No such device or address
> here = 0, tmp->channel = 2, channel = 2
> [May 21 06:15:34] ERROR[25314]: chan_dahdi.c:11270 build_channels:
> Unable to register channel '2'
In your configuration channel 2 is the first one, so this could be just
about anything related to accessing dahdi / zaptel .
* what means the word 'RED' associated to zero channel? I observed when
I connect the telephone line here, the word 'RED' disappears.
* I have the impression that the execution of this command is necessary
for the correct detection of the modules. This execution is made
automatically during bootstrapping of the operating system?
Good, now it seems that it would be working... but is there any form to
doing that this module is also automatically load when bootstrappiong of
the operating system? I was looking for in the configuration files of
example that are in /etc/asterisk but I did not find some reference.
After this, I was doing some tests of connection calling from an SIP
extension to the PSTN and this worked perfectly, but didn't get yet to
connect an extension SIP with a conventional analog telephone to each
other.
If you can give me some guide line (unnecessary configurations or
something that are lacking and could be useful) to know what to correct
in this aspect, it would be very useful. From an analog telephone I can
to call to a SIP extension, but from an SIP extension I cannot to call
to the analog telephone.
These are the configuration files that I am using:
context=phones
signalling=fxo_ks
channel => 2 ; Telephone attached to port 2
context=incomming
signalling=fxs_ks ; Use FXS signalling for an FXS channel
channel => 1 ; PSTN attached to port 1
- ----------------------------------------------------------------------
* what means the word 'RED' associated to zero channel? I observed when
I connect the telephone line here, the word 'RED' disappears.
As you guessed: it means that the line is connected to a working FXS (as
I wrote in my previous mail).
Quote:
* I have the impression that the execution of this command is necessary
for the correct detection of the modules.
It's not really detection. It is the DAHDI indicating you that the
channel is actually configured.
Quote:
This execution is made
automatically during bootstrapping of the operating system?
Yes. At boot you run /etc/init.d/dahdi which runs dahdi_cfg after the
modules are loaded. There's a deprecated method of running dahdi_cfg as
a post-load command of a module, but it is an ugly workaround that
causes too many problems.
Good, now it seems that it would be working... but is there any form to
doing that this module is also automatically load when bootstrappiong of
the operating system? I was looking for in the configuration files of
example that are in /etc/asterisk but I did not find some reference.
Yes. If /etc/inint.d/asterisk is run after /etc/init.d/dahdi (which
should happen with default installs of Asterisk and DAHDI) this should
be the case.
Posted: Sun May 24, 2009 9:46 pm Post subject: [asterisk-users] Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Tzafrir.
El domingo 24 de mayo del 2009 a las 17:33:36 -0300,
Tzafrir Cohen escribió:
Quote:
> # cat /proc/dahdi/*
> Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
>
> 1 WCTDM/4/0 RED
> 2 WCTDM/4/1
> 3 WCTDM/4/2
> 4 WCTDM/4/3
>
>
> After to run dahdi_cfg -vvv:
>
> # cat /proc/dahdi/*
> Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
>
> 1 WCTDM/4/0 FXSKS RED
> 2 WCTDM/4/1 FXOKS
> 3 WCTDM/4/2
> 4 WCTDM/4/3
>
> Two doubts related to this:
>
> * what means the word 'RED' associated to zero channel? I observed when
> I connect the telephone line here, the word 'RED' disappears.
Quote:
As you guessed: it means that the line is connected to a working FXS
(as I wrote in my previous mail).
Perfect.
Quote:
> * I have the impression that the execution of this command is necessary
> for the correct detection of the modules.
Quote:
It's not really detection. It is the DAHDI indicating you that the
channel is actually configured.
I spoke of 'detection' because after the execution of dahdi_cfg only is
that 'cat /proc/dahdi/*' shows FXSKS and FXOKS. Perhaps, it would have
been more correct to say the execution of this command is necessary to
configure the channels signaling.
Quote:
> This execution is made automatically during bootstrapping of the
> operating system?
Quote:
Yes. At boot you run /etc/init.d/dahdi which runs dahdi_cfg after the
modules are loaded. There's a deprecated method of running dahdi_cfg
as a post-load command of a module, but it is an ugly workaround that
causes too many problems.
Perfect.
Quote:
> Then I test the following thing in the CLI:
>
> alderamin*CLI> dahdi show channel
> No such command 'dahdi show channel' (type 'help dahdi show' for other possible commands)
> alderamin*CLI> module load chan_dahdi.so
> == Parsing '/etc/asterisk/chan_dahdi.conf': Found
> -- Registered channel 2, FXO Kewlstart signalling
> [May 24 15:04:54] WARNING[5306]: chan_dahdi.c:4090 handle_alarms:
> Detected alarm on channel 1: Red Alarm
> -- Registered channel 1, FXS Kewlstart signalling
> -- Automatically generated pseudo channel
> == Parsing '/etc/asterisk/users.conf': Found
> == Registered channel type 'DAHDI' (DAHDI Telephony Driver)
> == Manager registered action DAHDITransfer
> == Manager registered action ZapTransfer
> == Manager registered action DAHDIHangup
> == Manager registered action ZapHangup
> == Manager registered action DAHDIDialOffHook
> == Manager registered action ZapDialOffHook
> == Manager registered action DAHDIDNDon
> == Manager registered action ZapDNDon
> == Manager registered action DAHDIDNDoff
> == Manager registered action ZapDNDoff
> == Manager registered action DAHDIShowChannels
> == Manager registered action ZapShowChannels
> == Manager registered action DAHDIRestart
> == Manager registered action ZapRestart
> Loaded chan_dahdi.so => (DAHDI Telephony)
> alderamin*CLI>
> alderamin*CLI>
> alderamin*CLI>
> alderamin*CLI> dahdi show channels
> Chan Extension Context Language MOH Interpret
> pseudo default default
> 1 incomming es default
> 2 phones es default
>
>
> Good, now it seems that it would be working... but is there any form
> to doing that this module is also automatically load when
> bootstrappiong of the operating system? I was looking for in the
> configuration files of example that are in /etc/asterisk but I did
> not find some reference.
Quote:
Yes. If /etc/inint.d/asterisk is run after /etc/init.d/dahdi (which
should happen with default installs of Asterisk and DAHDI) this should
be the case.
This is consistent:
/etc/rc2.d/S50asterisk
/etc/rc2.d/S15dahdi
I tried only leaving uncommented in the file /etc/dahdi/modules the line
'wctdm' and after to reboot the operating system, both the card as
FXS/FXO channels signaling was detected without problems.
Now it would remain to find the cause of why I cannot call from a SIP
extension to an analog telephone. Perhaps it is by something related to
the contexts in the mentioned configuration files?
Posted: Mon May 25, 2009 9:32 pm Post subject: [asterisk-users] Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El domingo 24 de mayo del 2009 a las 19:38:30 -0300,
Daniel Bareiro escribió:
Quote:
Now it would remain to find the cause of why I cannot call from a SIP
extension to an analog telephone. Perhaps it is by something related
to the contexts in the mentioned configuration files?
I forgot to copy the output that I obtain in the CLI when I call to a
SIP extension:
[May 25 19:22:57] NOTICE[4813]: chan_sip.c:14721 handle_request_invite:
Call from '201' to extension '1010' rejected because extension not
found.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum