It's still a work in progress and has many rough edges (meaning its not yet fully automatic). You can track the progress on the Trixbox website (www.trixbox.com). Here is the link to the post:
http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=1367&forum=7 Rehan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tomas Vilda Sent: 19 July 2006 11:31 To: [email protected] Subject: Re: [Visdn-hackers] VoiSmart vGSM install problem... Could you provide automatic creation of device-pci-xxxxx files? On 7/19/06, rehan khan <[EMAIL PROTECTED]> wrote: > Hehe. I thought it would probably work. It's just good software. > > Any idea where I can buy a card from? I live in the UK so anywhere in EU > is fine. > > Also any news on the vISDN development? I understand it is under a > feature freeze. Asterisk is about to go to 1.4. At a guess the patches > will probably work but has anyone tested this? I love living on the > bleeding edge! :) > > I tried to get Digium to included the patches but as I didn't code them > I didn't want to post them without VISDN devs permission. I sent a mail > to Daniel to that effect. I guess I have learned more since then (about > the dual licensing issue) and the reason for openpbx. > > However I still think the patches can be submitted (without the vISDN > drivers) as an improvement to the asterisk code. Then vISDN/vGSM will > just work out of the box so to speak. If this gets done then Junghaans > and mISDN will just fall away into obscurity ('cause they are rubbish). > With respect, I really urge you to do this as soon as possible. It might > even make the 1.4 release. See here for the discussion on digium > bugtracker: > > http://bugs.digium.com/view.php?id=7405 > > A chap from the Trixbox forum and I are working on the vISDN init > scripts to get them to work with Centos and other Linuxes. Our plan is > to take the zaptel init script, remove all the zaptel stuff leaving the > multi-linux install code and push the vISDN requirements into there. If > you guys have something already let us know, will save a bunch of time. > We have a solution for the automatic creation of the device-pci- file > already. This will mean that the visdn_configurator does not need to run > and that visdn can be run using runlevels. Also will mean an automated > installation will be possible. > > The great stuff I learned from the vISDN drivers also directly led to > this fix: > > http://bugs.digium.com/view.php?id=7539 > > Many thanks. > Rehan > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Matteo > Brancaleoni > Sent: 19 July 2006 10:16 > To: [email protected] > Subject: RE: [Visdn-hackers] VoiSmart vGSM install problem... > > ssssh :) > > I tell you a secret. > VGSM is ok under centos 4.3 , since redhat patches make it > more versus 2.6.11 and so on... > let's say that you need 2.6.11 vanilla... or redhat > enhanced kernels. > > We currently develop under centos 4.3 :) > > matteo. > > On Tue, 2006-07-18 at 22:43 +0100, rehan khan wrote: > > You will need to modify the install instructions according to: > > > > http://open.voismart.it/index.php/VGSM > > > > So don't install the visdn_configurator in rc.local. You might want to > > create a script with the modprobe commands and then call this from > > rc.local. > > > > You should probably also delete the device-pci- file as that may > > conflict when you load the kernel drivers. Matteo can you confirm > this? > > > > There may be a huge showstopper here!! vGSM has a requirement for > kernel > > version 2.6.13. Centos (Linux distro in Trixbox) has kernel version > > 2.6.9 + some redhat patches. You may not have met the minimum > > requirements. You can of course upgrade the kernel but you will then > > have fallen out of the Centos kernel updates via yum. Anyway you > should > > try it and see..! > > > > If there are any issues maybe we can findout what exactly vGSM needs > in > > the 2.6.13 kernel that is not in the 2.6.9 kernel and update that much > > like we did for udev. > > > > Matteo: > > > > I can't seem to find anywhere to buy any of your cards :( > > > > Rehan > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Marcin M. > > Sent: 18 July 2006 21:45 > > To: [email protected] > > Subject: [Visdn-hackers] VoiSmart vGSM install problem... > > > > Hi, > > > > I have big problem with installing Voismart vGsm card.. > > I had installed Trixbox 1.1 and vISDN support.. > > > (http://www.trixbox.org/modules/newbb/viewtopic.php?viewmode=thread&topi > > c_id=1367&forum=7&post_id=6207#6207 > > > <http://www.trixbox.org/modules/newbb/viewtopic.php?viewmode=thread&topi > > c_id=1367&forum=7&post_id=6207#6207>) > > > > isdn-devel-20060704 > > udev-094 > > zaptel 1.2.6 > > > > after that : > > lspci > > 01:08.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN > > > interface > > > > lsmod > > lapd 60976 0 > > visdn_hfc_e1 60164 0 > > visdn_hfc_usb 26628 0 > > visdn_hfc_pci 38788 0 > > visdn_hfc_4s 66052 0 > > visdn_ec 16988 0 > > visdn_timer_system 3156 0 > > visdn_ppp 11112 0 > > ppp_generic 35157 1 visdn_ppp > > slhc 7233 1 ppp_generic > > visdn_streamport 11112 0 > > kfifo 3328 2 visdn_ec,visdn_streamport > > visdn_netdev 19176 0 > > visdn_softcxc 6244 8 > > > visdn_hfc_e1,visdn_hfc_usb,visdn_hfc_pci,visdn_hfc_4s,visdn_ec,visdn_ppp > > ,visdn_streamport,visdn_netdev > > > > visdn_core 55308 14 > > > visdn_hfc_e1,visdn_hfc_usb,visdn_hfc_pci,visdn_hfc_4s,visdn_ec,visdn_tim > > er_system,visdn_ppp,visdn_streamport,visdn_netdev,visdn_softcxc > > > > md5 4033 1 > > ipv6 235137 14 > > autofs4 24773 0 > > i2c_dev 11329 0 > > i2c_core 22081 1 i2c_dev > > sunrpc 162725 1 > > zaptel 206852 0 > > crc_ccitt 2113 1 zaptel > > dm_mirror 27825 0 > > dm_mod 57556 1 dm_mirror > > button 6481 0 > > battery 8901 0 > > ac 4805 0 > > sk98lin 146217 1 > > sata_nv 9285 0 > > ext3 116809 2 > > jbd 71385 1 ext3 > > sata_sil 9029 0 > > libata 56477 2 sata_nv,sata_sil > > sd_mod 17217 0 > > scsi_mod 121933 2 libata,sd_mod > > > > asterisk1*CLI> show vgsm interfaces > > era : FAILED > > NOT_SEARCHING > > wind : FAILED > > NOT_SEARCHING > > vodafone: FAILED > > NOT_SEARCHING > > blu : FAILED > > NOT_SEARCHING > > > > asterisk1*CLI>show vgsm interfaces era > > Device: /dev/vgsm0s0 > > Context: vgsm_tim_in > > Rx-gain: 255 > > Tx-gain: 255 > > Set clock: yes > > > > Module: > > Status :FAILED > > Reason: Error configuring CODEC > > > > > > asterisk1*CLI> show visdn interfaces > > Interface Role Mode TEI Status Calls > > asterisk1*CLI> > > > > > > visdn_configurator says: > > D: 000001 > > E: 000002 > > Port object st0 not found > > > > > > And i wondered how it should looks vgsm.config,visdn.config and > > device-pci-0000:01:08:0 for the vGSM card??? > > > > Maybe someone had installed this card on Trixbox??? > > > > Thanks for any help... > > emDWAem > > > > ---------------------------------------------------------------------- > > PS. Fajny portal... >>> http://link.interia.pl/f196a > > > > _______________________________________________ > > Visdn-hackers mailing list > > [email protected] > > https://mailman.uli.it/mailman/listinfo/visdn-hackers > > > > > > _______________________________________________ > > Visdn-hackers mailing list > > [email protected] > > https://mailman.uli.it/mailman/listinfo/visdn-hackers > -- > Matteo Brancaleoni > R&D Director > Tel +39.02.70633354 > Sip [EMAIL PROTECTED] > Iax2 [EMAIL PROTECTED] > > _______________________________________________ > Visdn-hackers mailing list > [email protected] > https://mailman.uli.it/mailman/listinfo/visdn-hackers > > > _______________________________________________ > Visdn-hackers mailing list > [email protected] > https://mailman.uli.it/mailman/listinfo/visdn-hackers > _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers
