-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I fixed it. problem is, that my zaptel API, which was automaticly compiled and configured by sangoma's wanpipe driver setup, expects all channel devices in /dev with the name format wptdm_sXcY, where X=span number and Y=channel number. My Zaptel-API creates the devices in /dev/zap with different device name format. 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 s1c2 as OpenZAP device 1:2 fd:39 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c3 as OpenZAP device 1:3 fd:40 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c4 as OpenZAP device 1:4 fd:41 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c5 as OpenZAP device 1:5 fd:42 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c6 as OpenZAP device 1:6 fd:43 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c7 as OpenZAP device 1:7 fd:44 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c8 as OpenZAP device 1:8 fd:45 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c9 as OpenZAP device 1:9 fd:46 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c10 as OpenZAP device 1:10 fd:47 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c11 as OpenZAP device 1:11 fd:48 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c12 as OpenZAP device 1:12 fd:49 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c13 as OpenZAP device 1:13 fd:50 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c14 as OpenZAP device 1:14 fd:51 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c15 as OpenZAP device 1:15 fd:52 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c17 as OpenZAP device 1:16 fd:53 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c18 as OpenZAP device 1:17 fd:54 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c19 as OpenZAP device 1:18 fd:55 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c20 as OpenZAP device 1:19 fd:56 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c21 as OpenZAP device 1:20 fd:57 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c22 as OpenZAP device 1:21 fd:58 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c23 as OpenZAP device 1:22 fd:59 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c24 as OpenZAP device 1:23 fd:60 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c25 as OpenZAP device 1:24 fd:61 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c26 as OpenZAP device 1:25 fd:62 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c27 as OpenZAP device 1:26 fd:63 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c28 as OpenZAP device 1:27 fd:64 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c29 as OpenZAP device 1:28 fd:65 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c30 as OpenZAP device 1:29 fd:66 2008-05-20 17:34:08 [INFO] zap_wanpipe.c:364 wp_open_range() configuring device s1c31 as OpenZAP device 1:30 fd:67 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 | | | Helmut Kuper schrieb: | | Hello, | | | | since mod_wanpipe is depricated, I try to get freeswitch with openzap, | | zaptel, wanpipe and Sangoma A101 E1-Pri-card running. | | | | I use zaptel-1.4.2, wanpipe-3.1.4 and ubuntu 2.6.20-16-server. ztcfg -vv | | ~ detects all channels and "wanrouter list" shows the card as active. In | | /dev/zap I have this devices: _______________________________________________ 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgy+CQACgkQ4tZeNddg3dzN4wCgvo12htOknAEb9SSg6yZ4qNbf MCUAoKoAy6BzfXIfXBLuQ92/lHtrqi4c =4xxU -----END PGP SIGNATURE-----