That is horribly wrong. If you are using wanpipe under zaptel you forget it is a wanpipe device and configure it under zaptel. with [span zt] There are specific instructions for setting up the wanpipe in standalone mode that does not require zaptel at all. in the /etc/wanpipe/wanpipe1.conf you have to change TDM_VOICE to TDM_VOICE_API This will create the dev entries we were "assuming" to be there because it's the correct assumption when the drivers are properly configured. Essentially what you did was configure wanpipe to be a zaptel device then hack the zap_wanpipe code to open zaptel devices. On Tue, May 20, 2008 at 11:24 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
sorry for my last post here. It was wrong. So here the correct message ;)
I fixed it. Problem is, that my zaptel API, which was automaticly compiled and configured by sangoma's wanpipe driver setup, creates all channel devices in /dev/zap with numbers as filename.
freeswitch's openzap module expects the channel devices directly under /dev with the name format wptdm_sXcY, where X=span number and Y=channel number.
So I changed libs/openzap/src/zap.wanpipe.c around line 319 from
snprintf(fname, FNAME_LEN, "/dev/wptdm_s%dc%d",span,chan);
to
snprintf(fname, FNAME_LEN, "/dev/zap/%d",chan);
additionally all devices in /dev/zap have to be accessible for freeswitch's user.
After recompiling and reinstall of mod_openzap I got this loglines in freeswitch console:
2008-05-20 17:34:08 [NOTICE] switch_loadable_module.c:380 switch_loadable_module_process() Adding Management interface 'mod_sofia' OID[.1.3.6.1.4.1.27880.1] 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c1 as OpenZAP device 1:1 fd:38 [..] 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c16 as OpenZAP device 1:31 fd:68 2008-05-20 17:34:08 [INFO] zap_io.c:1984 load_config() Configured 31 channel(s) 2008-05-20 17:34:08 [CONSOLE] switch_loadable_module.c:749 switch_loadable_module_load_file() Successfully Loaded [mod_openzap]
So far it looks quite good to me. I think it's good to have the device path configurable as long as I did not a mistake configuring wanpipe.
regards Helmut
Helmut Kuper schrieb: | Hi, | | I found that the console lines | | 2008-05-20 16:30:59 [ERR] zap_zt.c:721 zt_init() Cannot open control device | 2008-05-20 16:30:59 [ERR] zap_io.c:2050 zap_global_init() Error | initilizing zt. | | | Were caused by having wrong permissions on /dev/zap/ctl. That device | must be accessible by freswitch's user. | | | The "2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure | configuring device ..." problems are still there. | | regards | helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgy+z0ACgkQ4tZeNddg3dz0WwCgn/ASHRZWc2nV7x18NRbKBkRU 4vsAoI6Vd5WnfKcL9dstsonL2I8WoWjh =/uCB -----END PGP SIGNATURE-----
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400