Re: [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ó: 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. Thanks for your reply. Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkobGyoACgkQZpa/GxTmHTcYdgCfW8RUyUY5e4pbxs5xC/9Fcpp7 58UAnRAfj2eUL8ZAtvgUxIwHvCv2OXDM =o+On -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [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ó: 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 . Do you use dahdi or zaptel? What is the output of: cat /proc/zaptel/* cat /proc/dahdi/* # 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. * 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? 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 pseudodefaultdefault 1incomming es default 2phones 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. 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
Re: [asterisk-users] Channels configuration with DAHDI
On Sun, May 24, 2009 at 04:53:41PM -0300, Daniel Bareiro wrote: # 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. As you guessed: it means that the line is connected to a working FXS (as I wrote in my previous mail). * 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. 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. 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 pseudodefaultdefault 1incomming es default 2phones 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. 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. If this is not the case for you: What version of Asterisk do you use? What version of DAHDI? (linux, tools) What Linux distribution do you use? What version? What do you get after a normal boot? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [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ó: # 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. As you guessed: it means that the line is connected to a working FXS (as I wrote in my previous mail). Perfect. * 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. 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. 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. Perfect. 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 pseudodefaultdefault 1incomming es default 2phones 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. 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? Thank for your reply. Regads, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoZzKMACgkQZpa/GxTmHTfPcgCfUL5muSBicoU3bAdDKC0ZSkzM 7z4AnRg2YWyeEM5CEhYeuoj3RAQyH4K3 =Ywas -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
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ó: 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 marks...@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' 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? Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoVIU8ACgkQZpa/GxTmHTcLaACZAdNfwO5l1ZRZlX4swvJJhpjI 27MAoJEK3SOw3nsTFgU0TgYJ9NhmbrUz =ln/i -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
On Thu, May 21, 2009 at 06:38:27AM -0300, Daniel Bareiro wrote: -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 marks...@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 . Do you use dahdi or zaptel? What is the output of: cat /proc/zaptel/* cat /proc/dahdi/* -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
What are you getting if you do a dahdi_cfg -vv? -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@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ó: 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 marks...@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' 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? Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoVIU8ACgkQZpa/GxTmHTcLaACZAdNfwO5l1ZRZlX4swvJJhpjI 27MAoJEK3SOw3nsTFgU0TgYJ9NhmbrUz =ln/i -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
On Wed, May 20, 2009 at 07:03:15AM -0300, Daniel Bareiro wrote: -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: # lspci [...] 00:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface [...] # cat /proc/dahdi/* Span 1: DAHDI_DUMMY/1 DAHDI_DUMMY/1 (source: HRtimer) 1 (MASTER) Span 2: WCTDM/4 Wildcard TDM400P REV E/F Board 5 1 WCTDM/4/0 FXSKS RED 2 WCTDM/4/1 FXOKS 3 WCTDM/4/2 4 WCTDM/4/3 # dahdi_hardware pci::00:0a.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F # dahdi_cfg -vvv DAHDI Tools Version - 2.1.0.2 DAHDI Version: 2.1.0.4 Echo Canceller(s): Configuration == Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXO Kewlstart (Default) (Slaves: 02) 2 channels to configure. In the configuration files I made the following modifications: /etc/dahdi/system.conf: # DGB - 20090518 fxoks=2 fxsks=1 DGB #[channels] #language=en #context=incoming #signalling=fxs_ks #usecallerid=yes #hidecallerid=no #callwaiting=yes #callwaitingcallerid=yes #threewaycalling=yes #transfer=yes #cancallforward=yes #callreturn=yes #echocancel=yes #echocancelwhenbridged=yes #rxgain=0.0 #txgain=0.0 #group=1 #pickupgroup=1 #immediate=yes #musiconhold=default channel = 1 DGB /etc/asterisk/chan_dahdi.conf: ; DGB - 20090518 group=0 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... signaling=fxo_ks channel = 2 signaling=fxs_ks channel = 1 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. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Tzafrir. El miércoles 20 de mayo del 2009 a las 10:00:46 -0300, Tzafrir Cohen escribió: 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 marks...@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 Thanks for your reply. Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoUb1QACgkQZpa/GxTmHTdOfgCeKIw4uNyP6MOboezpFBrYBB2B H4YAoIm+CfhEpWMBFyg2cbUyxNIh6ivL =JgUc -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
Daniel Bareiro wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Tzafrir. El miércoles 20 de mayo del 2009 a las 10:00:46 -0300, Tzafrir Cohen escribió: 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 marks...@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 -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Channels configuration with DAHDI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dave. El miércoles 20 de mayo del 2009 a las 18:12:04 -0300, Dave Fullerton 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 marks...@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. Thanks for your reply. Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoUnkMACgkQZpa/GxTmHTfKeACffr1Q2vgJnyDVrA+hCN3DtHd5 e4UAoJUSl6JjjMCX+SiUA2/cyHJhwtfN =wCSV -END PGP SIGNATURE- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
