Hi Someone complained in #asterisk-gui that the Zaptel hardware detection did not work. It seems that zapscan.bin did not work properly, as no /etc/asterisk/zapscan.conf was generated.
Solution: detect zaptel hardware with genzaptelconf, and generate zapscan.conf from it. genzaptelconf grep '^fx[os][kl]s=' /etc/zaptel.conf \ | sed 's/\(fx[os]\)..=\(.*\)/[\2]\nport=\1\n/' >/etc/asterisk/zapscan.conf # this needs to be run only once: echo '#include zapata-channels.conf' >>/etc/asterisk/zapata.conf Any need for genzaptelconf to generate zapspan.conf ? Note that genzaptelconf tried to add hints (in the form of comments) to its generated zaptel.conf. E.g: # astbanktype: output fxoks=9 for Astribank output ports, and: # termtype: nt bchan=10-11 dchan=12 for a ISDN span that is NT (vs. TE. Saner default is to assume TE). I don't like using a separate file, because it goes against the logic of the asterisk GUI of using valid configuration data. One may edit zaptel.conf manually and not bother updating zapscan.conf . -- Tzafrir Cohen icq#16849755 jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir _______________________________________________ --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