On 10/3/07, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > On Tue, Oct 02, 2007 at 06:20:54PM +0200, Artifex Maximus wrote: > > On 10/2/07, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > > > On Tue, Oct 02, 2007 at 12:47:55PM +0200, Artifex Maximus wrote: > > > > On 10/2/07, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > > > > > On Tue, Oct 02, 2007 at 10:06:06AM +0200, Artifex Maximus wrote: > > > > > > Hello! > > > > > > > > > > > > I have been trying upgrade zaptel from 1.2.10 to 1.2.20.1. I am > > > > > > using > > > > > > asterisk 1.2.10 with one TDM2400P (all 6 module in use) and one > > > > > > TE405P. When I upgrade to 1.2.20.1 the order of cards mess up and > > > > > > therefore zaptel.conf is unusable and gives error. Why is it happen > > > > > > and what do I need to change in zaptel.conf? > > > > > > > > > > > > now zaptel.conf is: > > > > > > loadzone=hu > > > > > > defaultzone=hu > > > > > > # GSM > > > > > > fxsks=1-4 > > > > > > # FAX > > > > > > fxoks=5-8 > > > > > > # EXT > > > > > > fxoks=9-24 > > > > > > # PRI > > > > > > span=2,1,0,ccs,hdb3,crc4 > > > > > > bchan=25-39 > > > > > > dchan=40 > > > > > > bchan=41-55 > > > > > > > > > > > > zttool shows that my TDM is the first device and T4XXP is from > > > > > > second > > > > > > to fifth. Nice. After zaptel upgrade TDM is on the fifth position. > > > > > > And > > > > > > channels in zaptel.conf were messed up of course because 1-24 is not > > > > > > for TDM. > > > > > > > > > > Was there also a change in the kernel ? > > > > > > > > > > In the value of MODULES in /etc/{sysconfig,default}/zaptel ? > > > > Thanks for your answer. Same kernel (2.6.11) and no change in zaptel: > > > > > > > > MODULES="$MODULES wct4xxp" # TE405P - Quad Span T1/E1 Card (5v > > > > version) > > > > MODULES="$MODULES wctdm24xxp" # TDM2400P - Modular FXS/FXO interface > > > > (1-24 ports) > > > > > > > > Might MODULES order count? If so why that wasn't count with zaptel > > > > 1.2.10? > > > > > > It counts if the modules weren't loaded earlier on boot time, and if you > > > use the proper init.d script. > > I see. I've been using the init.d script from release which I think > > proper. Is it means there is logical difference between 1.2.10 and > > 1.2.20.1 on init.d script level? Because 1.2.10 is working flawless > > with this MODULES setup. > Are you sure you use zaptel.init from 1.2.20.1 ? I am absolutely sure because I had to copy with my own hands.
> I really don't think you can guarantee that the MODULES list will > triumph any automalic load the system has on startup (which is why > Astribank drivers won't auto-register by default). > > I can't think of any change that should have affected the modules > loading order by default. Unless this is some timing issue - a race > between automatic loading and manual loading. I will try with MODULES in right order and report the result. I think there must be difference between two init.d script because of different effect. bye, a _______________________________________________ --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