Bartosz Wegrzyn
2004-Sep-27 19:07 UTC
[Asterisk-Users] Fedora2 and zaptel - using the udev
Hi, I am sorry if this message has been reposted, but for some reason I am having problems with posting it. I configured asterisk and zaptel modules with fedora2. I want to be able to load the zaptel wcfxo and wcfxs modules. For now I will use only the Wildcard TDM400P card. I am able to load the modules but I cant configure them using ztcfg or zttool because the tools are compiled to use the devices in the dev directory instead of udev which is the one I use. I tried to change the source code to include the udev instead of dev, nut this didnot help. I was only able to load the zttool. The other tool still points to devices in dev directory. I am not familiar with the dynamic devices creatition in new kernel. Also, probably my changes to the source files were not necessary. I am not a developer so I am not sure if this should be done. Should the ztcfg automatically point to the devices in udev directory or it is written to use the devices in dev directory. Can anyone explain??? This is my log file which proves that modules works fine. Sep 26 22:39:07 voip kernel: Zapata Telephony Interface Registered on major 196 Sep 26 22:39:07 voip zaptel: Loading zaptel framework: succeeded Sep 26 22:39:07 voip udev[3564]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 31 applied, 'zaptimer' becomes 'zap/timer' Sep 26 22:39:07 voip udev[3564]: creating device node '/udev/zap/timer' Sep 26 22:39:07 voip udev[3571]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 32 applied, 'zapchannel' becomes 'zap/channel' Sep 26 22:39:07 voip udev[3571]: creating device node '/udev/zap/channel' Sep 26 22:39:09 voip kernel: Freshmaker version: 63 Sep 26 22:39:09 voip kernel: Freshmaker passed register test Sep 26 22:39:09 voip kernel: Module 0: Installed -- AUTO FXS/DPO Sep 26 22:39:09 voip kernel: Module 1: Not installed Sep 26 22:39:09 voip kernel: Module 2: Not installed Sep 26 22:39:09 voip kernel: Module 3: Not installed Sep 26 22:39:09 voip kernel: Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Sep 26 22:39:09 voip ztcfg: Notice: Configuration file is /etc/zaptel.conf Sep 26 22:39:09 voip ztcfg: line 143: Unable to open master device '/dev/zap/ctl' Sep 26 22:39:09 voip zaptel: Running ztcfg: succeeded Sep 26 22:39:09 voip udev[3578]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 33 applied, 'zappseudo' becomes 'zap/pseudo' Sep 26 22:39:09 voip udev[3578]: creating device node '/udev/zap/pseudo' Sep 26 22:39:09 voip udev[3585]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 30 applied, 'zapctl' becomes 'zap/ctl' Sep 26 22:39:09 voip udev[3585]: creating device node '/udev/zap/ctl' Sep 26 22:39:09 voip udev[3608]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap1' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3608]: creating device node '/udev/zap/1' Sep 26 22:39:09 voip udev[3615]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap2' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3615]: creating device node '/udev/zap/2' Sep 26 22:39:09 voip udev[3622]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap3' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3622]: creating device node '/udev/zap/3' Sep 26 22:39:09 voip udev[3629]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap4' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3629]: creating device node '/udev/zap/4' Thanks Bart
Tony da Costa
2004-Sep-27 19:33 UTC
[Asterisk-Users] Re: Fedora2 and zaptel - using the udev
Hi Bart, My solution was to create a soft link in the /dev directory pointing at /udev/zap: ln -s /udev/zap /dev/zap All the tools have worked fine for me since doing that. Cheers, Tony -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of asterisk-users-request@lists.digium.com Sent: Monday, September 27, 2004 8:11 PM To: asterisk-users@lists.digium.com Subject: Asterisk-Users Digest, Vol 2, Issue 292 Send Asterisk-Users mailing list submissions to asterisk-users@lists.digium.com Hi, I am sorry if this message has been reposted, but for some reason I am having problems with posting it. I configured asterisk and zaptel modules with fedora2. I want to be able to load the zaptel wcfxo and wcfxs modules. For now I will use only the Wildcard TDM400P card. I am able to load the modules but I cant configure them using ztcfg or zttool because the tools are compiled to use the devices in the dev directory instead of udev which is the one I use. I tried to change the source code to include the udev instead of dev, nut this didnot help. I was only able to load the zttool. The other tool still points to devices in dev directory. I am not familiar with the dynamic devices creatition in new kernel. Also, probably my changes to the source files were not necessary. I am not a developer so I am not sure if this should be done. Should the ztcfg automatically point to the devices in udev directory or it is written to use the devices in dev directory. Can anyone explain??? This is my log file which proves that modules works fine. Sep 26 22:39:07 voip kernel: Zapata Telephony Interface Registered on major 196 Sep 26 22:39:07 voip zaptel: Loading zaptel framework: succeeded Sep 26 22:39:07 voip udev[3564]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 31 applied, 'zaptimer' becomes 'zap/timer' Sep 26 22:39:07 voip udev[3564]: creating device node '/udev/zap/timer' Sep 26 22:39:07 voip udev[3571]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 32 applied, 'zapchannel' becomes 'zap/channel' Sep 26 22:39:07 voip udev[3571]: creating device node '/udev/zap/channel' Sep 26 22:39:09 voip kernel: Freshmaker version: 63 Sep 26 22:39:09 voip kernel: Freshmaker passed register test Sep 26 22:39:09 voip kernel: Module 0: Installed -- AUTO FXS/DPO Sep 26 22:39:09 voip kernel: Module 1: Not installed Sep 26 22:39:09 voip kernel: Module 2: Not installed Sep 26 22:39:09 voip kernel: Module 3: Not installed Sep 26 22:39:09 voip kernel: Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Sep 26 22:39:09 voip ztcfg: Notice: Configuration file is /etc/zaptel.conf Sep 26 22:39:09 voip ztcfg: line 143: Unable to open master device '/dev/zap/ctl' Sep 26 22:39:09 voip zaptel: Running ztcfg: succeeded Sep 26 22:39:09 voip udev[3578]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 33 applied, 'zappseudo' becomes 'zap/pseudo' Sep 26 22:39:09 voip udev[3578]: creating device node '/udev/zap/pseudo' Sep 26 22:39:09 voip udev[3585]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 30 applied, 'zapctl' becomes 'zap/ctl' Sep 26 22:39:09 voip udev[3585]: creating device node '/udev/zap/ctl' Sep 26 22:39:09 voip udev[3608]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap1' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3608]: creating device node '/udev/zap/1' Sep 26 22:39:09 voip udev[3615]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap2' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3615]: creating device node '/udev/zap/2' Sep 26 22:39:09 voip udev[3622]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap3' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3622]: creating device node '/udev/zap/3' Sep 26 22:39:09 voip udev[3629]: configured rule in '/etc/udev/rules.d//50-udev.rules' at line 34 applied, 'zap4' becomes 'zap/%n' Sep 26 22:39:09 voip udev[3629]: creating device node '/udev/zap/4' Thanks Bart ------------------------------ Message: 11 Date: Mon, 27 Sep 2004 22:11:08 -0400 From: "Shilliday, Jim" <JShilliday@ejcenter.org> Subject: [Asterisk-Users] Cisco 7940 -60 firmware upgrades To: "Daniel Poulsen" <dpoulsen@gmail.com>, "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com> Message-ID: <45FFA3EE8D83614E9DE7395D953326E5643443@arcturus.ejcenter.org> Content-Type: text/plain; charset="us-ascii" This for the archives in case it may help someone: I was able to upgrade two Cisco 7940's from firmware P0030301MFG2 to SIP 7.1 as follows: 1. Installed 7.1 images from the Cisco zip file to the TFTP server. 2. Specified "image_version: P0S3-07-1-00" in SIP<MAC>.cnf and SIPDefault.cnf 3. For the older of the two phones, renamed P003-07-1-00.bin to P0S3-07-.bin, making it an 8.3 filename as expected by the version 3 firmware. For the later (apparently new enough to handle long filenames), renamed it to P0S3-07-1-00.bin. No, that's NOT a misprint. I renamed P003-07-1-00.bin to P0S3-07-.bin -- in Version 7.1, P003 isn't the Call Manager software, it's the Universal Application Loader that needs to load first to install everything else. 4. Rebooted the phones. Jim Shilliday IT Director Equal Justice Center 1315 Walnut St. Suite 400 Philadelphia PA 19107 215-238-6970 -----Original Message----- From: Daniel Poulsen [mailto:dpoulsen@gmail.com] Sent: Monday, September 20, 2004 3:36 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Cc: mboehm@cytelcom.com Subject: Re: [Asterisk-Users] Re: cisco 7960 CTLSEP I had this same problem and I only found out how to upgrade the phones by trial an error. I even opened a Cisco case to get help on it but they couldn't help me! I think the problem is that 79xx firmware prior to 7.x doesn't know to look for the .loads file, and without the loads file it will only load the SCCP .sbn file. It need the loads file to load the SIP .sb2 file. This is contrary to Cisco docs, but this is how I did it. 1. Expand the 7.2 firmware files into the tftp-root. 2. By default OS79XX.txt has P003-07-2-00. Change this to P0S3-07-2-00, but leave the image_version in your SIPDefaults set to P003-07-2-00. 3. Reboot. The phone will load an image and you will get the protocol invalid error as noted earlier in this thread. 4. Change your SIPDefauls.cnf to P0S3-07-2-00. 5. Reboot. The phone will look for the loads file and load the proper sb2 image bringing you to version 7.2. Dan On Mon, 20 Sep 2004 10:58:54 +0200, Jan Baggen <jbaggen@ip2.nl> wrote:> > >I have about 10 of these phones. All of them started with sccpfirmware on> >them. I used the XMLDefault.xml file to upgrade them all to SIP 3.7.The> >phones "should" look for a CTL<mac> file, then a SEP<mac>, thenSIP<mac>.> >XMLDefault.xml should be in there somewhere. > > > >I've never had to 'trick' my phones. All of them started with sccpfirmware> >on them. I used the XMLDefault.xml file to upgrade them. You do haveall> the > >firmware files in your tftp directory right? > > > >None of my phones have EVER looked for that OS79XX.txt file. Ichunked it.> > > >I can send you SIP<mac> files for configuration if you need. > > > >Matthew > > Yes, please send me your configuration files. CTLSEP<mac>.tnl SEP<mac> > and SIP<mac> > > The SIP fimware is on my TFTP server. > > Thank you! > > > > --- > Jan Baggen - jbaggen@ip2.nl > IP2 Internet BV / http://www.ip2.nl > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ------------------------------ _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users End of Asterisk-Users Digest, Vol 2, Issue 292 **********************************************