jonas kellens
2009-Apr-29 17:41 UTC
[asterisk-users] Something wrong with DAHDI signalling according to the CLI
I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. When I plug one PSTN-line into a FXO-port I am able to receive calls on this line and I can also make calls from an internal SIP-phone to the external PSTN-network. Still I am bothered about something that appears on the CLI when I do a reload chan_dahdi.so : asterisk*CLI> reload chan_dahdi.so -- Reloading module 'chan_dahdi' (DAHDI Telephony w/PRI) == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:11951 process_dahdi: Ignoring any changes to 'signalling' (on reload) [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:4090 handle_alarms: Detected alarm on channel 1: Red Alarm -- Reconfigured channel 1, FXS Kewlstart signalling [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:11951 process_dahdi: Ignoring any changes to 'signalling' (on reload) [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:4090 handle_alarms: Detected alarm on channel 2: Red Alarm -- Reconfigured channel 2, FXS Kewlstart signalling [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:11951 process_dahdi: Ignoring any changes to 'signalling' (on reload) -- Reconfigured channel 3, FXS Kewlstart signalling == Parsing '/etc/asterisk/users.conf': Found What about this "ignoring any changes to 'signalling' ??? It's not a notice, its really a warning... I would gladly see no warning at all when reloading DAHDI. This is my chan_dahdi.conf (created manually) : [trunkgroups] [channels] language=be busydetect=yes busycount=6 callerid=asreceived ;threewaycaling=yes transfer=yes ; Note that if any of your DAHDI cards have hardware echo cancellers, ; then this setting only turns them on and off. There are no special ; settings required for hardware echo cancellers; when present and ; enabled in their kernel modules, they take precedence over the ; software echo canceller compiled into DAHDI automatically. echocancel=yes ;internationalprefix: 00 ;nationalprefix:0 context=tel2268191 ; E.U. signalling=fxs_ks group=1 channel => 1 context=tel2362334 ; KMO signalling=fxs_ks group=1 channel => 2 context=telunknown signalling=fxs_ks group=1 channel => 3 This is what DAHDI config tells me : [root at asterisk asterisk]# /usr/sbin/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: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXS Kewlstart (Default) (Slaves: 03) 3 channels to configure. It keeps telling me that the channels need to be configured, in stead of saying that my channels ARE configured. Thanks for the feedback ! Jonas. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090429/5a559ecc/attachment.htm
Tzafrir Cohen
2009-Apr-29 19:47 UTC
[asterisk-users] Something wrong with DAHDI signalling according to the CLI
On Wed, Apr 29, 2009 at 07:41:14PM +0200, jonas kellens wrote:> I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO > modules. > > When I plug one PSTN-line into a FXO-port I am able to receive calls on > this line and I can also make calls from an internal SIP-phone to the > external PSTN-network. > > Still I am bothered about something that appears on the CLI when I do a > reload chan_dahdi.so : > > asterisk*CLI> reload chan_dahdi.so > -- Reloading module 'chan_dahdi' (DAHDI Telephony w/PRI) > == Parsing '/etc/asterisk/chan_dahdi.conf': Found > [Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:11951 process_dahdi: > Ignoring any changes to 'signalling' (on reload)chan_dahdi does not add channels, remove channels or changes the signalling of channels (as well as most configurations of PRI spans) on reload. Either restart Asterisk or use 'dahdi restart'. Both methods will disconnect all existing DAHDI calls. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Matt Riddell
2009-Apr-29 21:38 UTC
[asterisk-users] Something wrong with DAHDI signalling according to the CLI
On 30/04/2009 5:41 a.m., jonas kellens wrote:> I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. > [*Apr 29 16:26:53] WARNING[8927]: chan_dahdi.c:11951 process_dahdi: > Ignoring any changes to 'signalling' (on reload) *Changes to signalling are not used when you reload - the warning tells you about this. I.E. if you changed the signalling to PRI_NET or whatever, you would need to restart rather than reload - maybe it should be a notice rather than a warning. -- Kind Regards, Matt Riddell Director _______________________________________________ http://www.venturevoip.com (Great new VoIP end to end solution) http://www.venturevoip.com/news.php (Daily Asterisk News - html) http://www.venturevoip.com/newrssfeed.php (Daily Asterisk News - rss)