Samudra E. Haque
2005-Jan-05 06:52 UTC
[Asterisk-Users] TDM400P + Asterisk + zaptel timer ?
Hello, I thought that my Digium TDM400P would be the right hardware to support the zaptel timer, and put the following IAX.CONF entry to test, (trunk=yes) in the example below [VHAX] type=peer auth=md5 username=whoknows jitterbuffer=yes ;trunk=yes secret=terriblesecret host=4.5.6.7 qualify=1200 disallow=all allow=ulaw allow=gsm ;allow=g711u ;allow=g711a But, it didn't work. So I had to comment it out. When trunk=yes was set, the following result happened, and literally the audio was very unstable. Otherwise the system has been working great. I am using ax1*CLI> show version Asterisk CVS-HEAD-12/02/04-17:57:31 built by root@ax1 on a i686 running Linux Jan 5 13:40:53 WARNING[1928]: Unable to open pseudo channel for timing... Sound may be choppy. Jan 5 13:40:54 WARNING[1928]: Unable to open IAX timing interface: No such file or directory Jan 5 13:40:57 NOTICE[1928]: Request to schedule in the past?!?! Jan 5 13:41:00 WARNING[1928]: Unable to support trunking on peer 'VHAX' without zaptel timing Jan 5 13:41:06 WARNING[1928]: Unable to specify channel 1: No such device or address Jan 5 13:41:06 ERROR[1928]: Unable to open channel 1: No such device or address Jan 5 13:41:06 ERROR[1928]: Unable to register channel '1' Jan 5 13:41:06 WARNING[1928]: chan_zap.so: load_module failed, returning -1 Jan 5 13:41:06 WARNING[1928]: Loading module chan_zap.so failed! However, in my /dev/zap directory from original installation: (Fedora Core 3) [root@ax1 asterisk]# ls -l /dev/zap total 0 crw------- 1 root root 196, 1 Jan 5 15:36 1 crw------- 1 root root 196, 2 Jan 5 15:36 2 crw------- 1 root root 196, 3 Jan 5 15:36 3 crw------- 1 root root 196, 4 Jan 5 15:36 4 crw------- 1 root root 196, 254 Jan 5 15:36 channel crw------- 1 root root 196, 0 Jan 5 15:36 ctl crw------- 1 root root 196, 255 Jan 5 15:36 pseudo crw------- 1 root root 196, 253 Jan 5 15:36 timer [root@ax1 asterisk]# so, I'm puzzled, what / where is the zaptel timer supposed to be defined ? the TDM400P has FXO and FXS interfaces and is a Digium. -samudra -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.7 - Release Date: 12/30/2004
On Wed, 2005-01-05 at 19:52 +0600, Samudra E. Haque wrote:> Hello, I thought that my Digium TDM400P would be the right hardware to > support the zaptel timer, and put the following IAX.CONF entry to test, > (trunk=yes) in the example below >[snip]> But, it didn't work. So I had to comment it out. When trunk=yes was set, the > following result happened, and literally the audio was very unstable. > Otherwise the system has been working great. I am using ax1*CLI> show > version > Asterisk CVS-HEAD-12/02/04-17:57:31 built by root@ax1 on a i686 running > Linux > > Jan 5 13:41:06 WARNING[1928]: chan_zap.so: load_module failed, returning -1 > Jan 5 13:41:06 WARNING[1928]: Loading module chan_zap.so failed!You should first solve this problem. If chan_zap.so can't load, then you don't have a timing device. Do this: Get zaptel source/compile/install in /usr/src/asterisk make clean;make install then modprobe zaptel and modprobe wcfxs (or wctdm if using current CVS) then ztcfg If you get *NO* error messages, then continue, else report back to the list your /etc/zaptel.conf and details of your TDM card modules, and the errors Start asterisk If you can do a zap show channels and see your channels, then continue, else report back to the list the output of ztcfg -vv, and your /etc/asterisk/zapata.conf and the error messages when starting asterisk. If you have done all the above correctly, then it will probably work. Remember that you need to enable trunk'ing at BOTH ends as well. Hope this helps you... Regards, Adam -- -- Adam Goryachev Website Managers Ph: +61 2 9345 4395 adam@websitemanagers.com.au Fax: +61 2 9345 4396 www.websitemanagers.com.au