Evening, My latest asterisk box is having a difficult problem. It is configured with one TE210P and TDM400P with four FXO modules. I'm running FC6. The TE210P only has a single PRI. When the system boots, it is completely random what order the zaptel modules will get loaded in. Sometimes zttool shows the FXO as the last span, sometimes as the first. When it does load as the first, which happens more often, nothing will initialize properly. When this happens, I have to unload all the zaptel modules, and re-load them over and over again, until the hardware comes up in the correct order. The order it is loaded is in no way related to what order I load the modules on the command line. This problems makes it unlikely that asterisk will start properly if the system is rebooted. Is there something I can do to ensure the modules get loaded in the correct order? Here's my config files, if they will help... # cat /etc/zaptel.conf span=1,1,0,esf,b8zs bchan=1-23 dchan=24 defaultzone=us loadzone=us span=2,1,0,esf,b8zs bchan=25-47 dchan=48 defaultzone=us loadzone=us fxoks=49-52 defaultzone=us loadzone=us # cat /etc/asterisk/zapata.conf [channels] language=en switchtype=national context=incoming faxdetect=none signalling=pri_cpe group=1 echocancel=yes resetinterval=never channel => 1-23 language=en switchtype=national context=incoming faxdetect=none signalling=pri_cpe group=3 echocancel=yes resetinterval=never channel => 25-47 signalling=fxo_ks usecallerid=yes callerid=Fidelity Reserves group=2 threewaycalling=no context=outgoing channel => 49-52 Thanks for any help, /Mitch
mitch, not that I can answer your problem but is this ver 1.4.1? I had a similiar problem in that zapscan was updating the zaptel.conf and nothing would work until I mucked with zaptel.conf.zapscan... I might have the filename wrong as I have multiple files now :(... it has zapscan in the filename... daveC Mitch Jackson wrote:> Evening, > > My latest asterisk box is having a difficult problem. It is > configured with one TE210P and TDM400P with four FXO modules. I'm > running FC6. > > The TE210P only has a single PRI. > > When the system boots, it is completely random what order the zaptel > modules will get loaded in. Sometimes zttool shows the FXO as the > last span, sometimes as the first. When it does load as the first, > which happens more often, nothing will initialize properly. When this > happens, I have to unload all the zaptel modules, and re-load them > over and over again, until the hardware comes up in the correct order. > The order it is loaded is in no way related to what order I load the > modules on the command line. This problems makes it unlikely that > asterisk will start properly if the system is rebooted. > > Is there something I can do to ensure the modules get loaded in the > correct order? > > Here's my config files, if they will help... > > # cat /etc/zaptel.conf > span=1,1,0,esf,b8zs > bchan=1-23 > dchan=24 > defaultzone=us > loadzone=us > > span=2,1,0,esf,b8zs > bchan=25-47 > dchan=48 > defaultzone=us > loadzone=us > > fxoks=49-52 > defaultzone=us > loadzone=us > > # cat /etc/asterisk/zapata.conf > [channels] > language=en > switchtype=national > context=incoming > faxdetect=none > signalling=pri_cpe > group=1 > echocancel=yes > resetinterval=never > channel => 1-23 > > language=en > switchtype=national > context=incoming > faxdetect=none > signalling=pri_cpe > group=3 > echocancel=yes > resetinterval=never > channel => 25-47 > > > signalling=fxo_ks > usecallerid=yes > callerid=Fidelity Reserves > group=2 > threewaycalling=no > context=outgoing > channel => 49-52 > > > > > > Thanks for any help, > > /Mitch > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >-- Building Strong Relationships w/ Intelligent Customer Service -- Interlocking Business Solutions, LLC 856-380-0894 x5000
It's generally not recommended to put an analog and digital card in the same box, however that being said.... Try this. Write a little hack in /etc/rc.local /sbin/modprobe wct4xxp sleep 5 /sbin/modprobe wct4xxp sleep 5 /sbin/ztcfg sleep 5 /sbin/modprobe wctdm sleep 5 /sbin/ztcfg /usr/sbin/safe_asterisk the rc.local script is loaded after all the others so it won't effect anything else, and we had some trouble with some low heat VIA motherboards so we did the modprobe twice for the PRI. Hope this helps. Cheers, Joel Hill Support Engineer Asterisk IT On Mon, 2007-04-30 at 19:14 -0500, Mitch Jackson wrote:> Evening, > > My latest asterisk box is having a difficult problem. It is > configured with one TE210P and TDM400P with four FXO modules. I'm > running FC6. > > The TE210P only has a single PRI. > > When the system boots, it is completely random what order the zaptel > modules will get loaded in. Sometimes zttool shows the FXO as the > last span, sometimes as the first. When it does load as the first, > which happens more often, nothing will initialize properly. When this > happens, I have to unload all the zaptel modules, and re-load them > over and over again, until the hardware comes up in the correct order. > The order it is loaded is in no way related to what order I load the > modules on the command line. This problems makes it unlikely that > asterisk will start properly if the system is rebooted. > > Is there something I can do to ensure the modules get loaded in the > correct order? > > Here's my config files, if they will help... > > # cat /etc/zaptel.conf > span=1,1,0,esf,b8zs > bchan=1-23 > dchan=24 > defaultzone=us > loadzone=us > > span=2,1,0,esf,b8zs > bchan=25-47 > dchan=48 > defaultzone=us > loadzone=us > > fxoks=49-52 > defaultzone=us > loadzone=us > > # cat /etc/asterisk/zapata.conf > [channels] > language=en > switchtype=national > context=incoming > faxdetect=none > signalling=pri_cpe > group=1 > echocancel=yes > resetinterval=never > channel => 1-23 > > language=en > switchtype=national > context=incoming > faxdetect=none > signalling=pri_cpe > group=3 > echocancel=yes > resetinterval=never > channel => 25-47 > > > signalling=fxo_ks > usecallerid=yes > callerid=Fidelity Reserves > group=2 > threewaycalling=no > context=outgoing > channel => 49-52 > > > > > > Thanks for any help, > > /Mitch > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
On Mon, Apr 30, 2007 at 07:14:22PM -0500, Mitch Jackson wrote:> Evening, > > My latest asterisk box is having a difficult problem. It is > configured with one TE210P and TDM400P with four FXO modules. I'm > running FC6. > > The TE210P only has a single PRI.You have exactly two modules. either wctdm loads and registers its span first or wct4xxp loads first and registers its spans. There are three cases to consider: 1. system boot 2. Modules load in the zaptel init script 3. manual load It would make much sense to put the T1 card first, o it will automatically become the master, and you have indeed configured the cards so, The order in (1) is arbitrary but fixed. It is affected by the order of scanning of the PCI bus by udev or someone near-by. It may be modified by changing PCI slots and such. (2) is normally mostly meaningful on "reastart": unloading and reloading of the modules. The order in the init.d script is set manually. The order is set by the value of MODULES, as set in /etc/sysconfig/zaptel . With (3) you do what you want. But this is no way for automation...> > When the system boots, it is completely random what order the zaptel > modules will get loaded in. Sometimes zttool shows the FXO as the > last span, sometimes as the first. When it does load as the first, > which happens more often, nothing will initialize properly. When this > happens, I have to unload all the zaptel modules, and re-load them > over and over again, until the hardware comes up in the correct order. > The order it is loaded is in no way related to what order I load the > modules on the command line. This problems makes it unlikely that > asterisk will start properly if the system is rebooted. > > Is there something I can do to ensure the modules get loaded in the > correct order? > > Here's my config files, if they will help... > > # cat /etc/zaptel.conf > span=1,1,0,esf,b8zs > bchan=1-23 > dchan=24 > defaultzone=us > loadzone=us > > span=2,1,0,esf,b8zsoff-topic, but: span=2,2,0,esf,b8zs (give it lower priority), right?> bchan=25-47 > dchan=48 > defaultzone=us > loadzone=us > > fxoks=49-52 > defaultzone=us > loadzone=usYou only need to put defaultzone and loadzone once (harmless, though). -- Tzafrir Cohen icq#16849755 jabber:tzafrir@jabber.org +972-50-7952406 mailto:tzafrir.cohen@xorcom.com http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mitch Jackson wrote:> Evening, > > My latest asterisk box is having a difficult problem. It is > configured with one TE210P and TDM400P with four FXO modules. I'm > running FC6. > > The TE210P only has a single PRI. > > When the system boots, it is completely random what order the zaptel > modules will get loaded in. Sometimes zttool shows the FXO as the > last span, sometimes as the first. When it does load as the first, > which happens more often, nothing will initialize properly. When this > happens, I have to unload all the zaptel modules, and re-load them > over and over again, until the hardware comes up in the correct order. > The order it is loaded is in no way related to what order I load the > modules on the command line. This problems makes it unlikely that > asterisk will start properly if the system is rebooted. > > Is there something I can do to ensure the modules get loaded in the > correct order?If you use udev (and subsequently modprobe), you can override the install command for the TDM card to load the T1 card first: Create a file in the /etc/modprobe.d directory, and put the following line in it: install wctdm4xxp modprobe wcte21xp && modprobe --ignore-install wctdm4xxp $CMDLINE_OPTS && /sbin/ztcfg (Make sure it's all one line; your mail reader might break it.) This method works for me, with a TE110P and a TDM2400P in the same box. However, I am using Debian, and I'm not sure if modprobe and udev work the same way in FC6. TTYL. - -- C. Chad Wallace, B.Sc. The Lodging Company http://www.skihills.com/ OpenPGP Public Key ID: 0x262208A0 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGN7bcKeSNHCYiCKARAoefAKDAh/V2W3cwd/ASfHH5JsMOdj3wOgCgnexb yMh5TUnMZzHdM572J67oxmU=pHCB -----END PGP SIGNATURE-----