-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: root@ip-pbx:/usr/src/wanpipe-3.1.4# ls -l /dev/zap/ total 0 crw-rw---- 1 root dialout 196, 1 2008-05-20 16:24 1 crw-rw---- 1 root dialout 196, 10 2008-05-20 16:24 10 crw-rw---- 1 root dialout 196, 11 2008-05-20 16:24 11 crw-rw---- 1 root dialout 196, 12 2008-05-20 16:24 12 crw-rw---- 1 root dialout 196, 13 2008-05-20 16:24 13 crw-rw---- 1 root dialout 196, 14 2008-05-20 16:24 14 crw-rw---- 1 root dialout 196, 15 2008-05-20 16:24 15 crw-rw---- 1 root dialout 196, 16 2008-05-20 16:24 16 crw-rw---- 1 root dialout 196, 17 2008-05-20 16:24 17 crw-rw---- 1 root dialout 196, 18 2008-05-20 16:24 18 crw-rw---- 1 root dialout 196, 19 2008-05-20 16:24 19 crw-rw---- 1 root dialout 196, 2 2008-05-20 16:24 2 crw-rw---- 1 root dialout 196, 20 2008-05-20 16:24 20 crw-rw---- 1 root dialout 196, 21 2008-05-20 16:24 21 crw-rw---- 1 root dialout 196, 22 2008-05-20 16:24 22 crw-rw---- 1 root dialout 196, 23 2008-05-20 16:24 23 crw-rw---- 1 root dialout 196, 24 2008-05-20 16:24 24 crw-rw---- 1 root dialout 196, 25 2008-05-20 16:24 25 crw-rw---- 1 root dialout 196, 26 2008-05-20 16:24 26 crw-rw---- 1 root dialout 196, 27 2008-05-20 16:24 27 crw-rw---- 1 root dialout 196, 28 2008-05-20 16:24 28 crw-rw---- 1 root dialout 196, 29 2008-05-20 16:24 29 crw-rw---- 1 root dialout 196, 3 2008-05-20 16:24 3 crw-rw---- 1 root dialout 196, 30 2008-05-20 16:24 30 crw-rw---- 1 root dialout 196, 31 2008-05-20 16:24 31 crw-rw---- 1 root dialout 196, 4 2008-05-20 16:24 4 crw-rw---- 1 root dialout 196, 5 2008-05-20 16:24 5 crw-rw---- 1 root dialout 196, 6 2008-05-20 16:24 6 crw-rw---- 1 root dialout 196, 7 2008-05-20 16:24 7 crw-rw---- 1 root dialout 196, 8 2008-05-20 16:24 8 crw-rw---- 1 root dialout 196, 9 2008-05-20 16:24 9 crw-rw---- 1 root dialout 196, 254 2008-05-20 16:24 channel crw-rw---- 1 root dialout 196, 0 2008-05-20 16:24 ctl crw-rw---- 1 root dialout 196, 255 2008-05-20 16:24 pseudo crw-rw---- 1 root dialout 196, 253 2008-05-20 16:24 timer crw-rw---- 1 asterisk asterisk 196, 250 2008-05-20 16:24 transcode Freeswitch was compiled with openzap. openzap.conf.xml is in autoload_configs and has this content: <configuration name="openzap.conf" description="OpenZAP Configuration"> ~ <settings> ~ <param name="debug" value="7"/> ~ </settings> ~ <pri_spans> ~ <span id="1"> ~ <param name="mode" value="user"/> ~ <param name="dialect" value="euro"/> ~ <param name="dialplan" value="XML"/> ~ <param name="context" value="default"/> ~ </span> ~ </pri_spans> ~ </configuration> /etc/openzap/openzap.conf has this content: [span wanpipe] trunk_type => e1 b-channel => 1:1-15, 1:17-31 d-channel=> 1:16 freeswitch console log is: 2008-05-20 16:30:59 [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 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. 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c1 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c2 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c3 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c4 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c5 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c6 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c7 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c8 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c9 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c10 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c11 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c12 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c13 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c14 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c15 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c17 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c18 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c19 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c20 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c21 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c22 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c23 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c24 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c25 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c26 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c27 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c28 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c29 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c30 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c31 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c16 2008-05-20 16:30:59 [INFO] zap_io.c:1984 load_config() Configured 0 channel(s) 2008-05-20 16:30:59 [ERR] zap_io.c:2077 zap_global_init() No modules configured! 2008-05-20 16:30:59 [ERR] mod_openzap.c:1855 mod_openzap_load() Error loading OpenZAP 2008-05-20 16:30:59 [CRIT] switch_loadable_module.c:727 switch_loadable_module_load_file() Error Loading module /opt/app/freeswitch/mod/mod_openzap.so **Module load routine returned an error** 2008-05-20 16:30:59 [NOTICE] switch_loadable_module.c:245 switch_loadable_module_process() Adding API Function 'originate' any ideas? regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgy61YACgkQ4tZeNddg3dzGdgCdEqgGISo4UYUcHQE7tTlehG10 JxYAnAyvl4qd0YBg1v+EE3h63Q2bMQDB =ZQ+R -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgy8CcACgkQ4tZeNddg3dxBsQCgqaI+m4lHjeFGyHRGuqxm3g70 m4QAn2e1pwkp7+Ruxmp/JmgTcR7A6prc =tSZS -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again, further debugging shows that zap_wanpipe assumes that channel devices are directly located in /dev called e.g. "wptdm_s1c22" for span 1 channel 22. Is there a way to configure the device path and name? 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 iEYEARECAAYFAkgy8lEACgkQ4tZeNddg3dxTpwCfUIzAUUjD/UgIHXtaCD3QJhgV FWYAnAzlDj09V8h1tNAGAAgTn/wwCiwO =8dKB -----END PGP SIGNATURE-----
-----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-----
-----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-----
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Anthony, thanks for your explanations. I undid my changes to zip_wanpipe.c and reconfigured wanpipe1.conf as explained manually. That works :) But there is still the problem that freeswitch has to be root user to get access to the TDM devices created by wanpipe driver. I solve that with a wrapper until there is a better way. regards helmut Anthony Minessale schrieb: | 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. | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgzBpwACgkQ4tZeNddg3dwOlACfQqckrmOVMSMGEKgYnbfnYz3d Hb4AmwUuhh2VyXBwZyYAyhBmUbGMDbuO =xsYy -----END PGP SIGNATURE-----
You can chown the devices or change the permissions so the non-root user can access those. I think the udev rules would need to be changed also so that they are created with the right permissions next time you start. /b On May 20, 2008, at 12:13 PM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello Anthony,
thanks for your explanations. I undid my changes to zip_wanpipe.c and reconfigured wanpipe1.conf as explained manually. That works :)
But there is still the problem that freeswitch has to be root user to get access to the TDM devices created by wanpipe driver. I solve that with a wrapper until there is a better way.
regards helmut
Anthony Minessale schrieb: | 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. | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgzBpwACgkQ4tZeNddg3dwOlACfQqckrmOVMSMGEKgYnbfnYz3d Hb4AmwUuhh2VyXBwZyYAyhBmUbGMDbuO =xsYy -----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
Brian West sip:brian@freeswitch.org
you can also try to add freeswitch user to the group owning the devices take a look to usermod and -G switch 2008/5/20 Brian West <brian@freeswitch.org>:
You can chown the devices or change the permissions so the non-root user can access those. I think the udev rules would need to be changed also so that they are created with the right permissions next time you start.
/b
On May 20, 2008, at 12:13 PM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello Anthony,
thanks for your explanations. I undid my changes to zip_wanpipe.c and reconfigured wanpipe1.conf as explained manually. That works :)
But there is still the problem that freeswitch has to be root user to get access to the TDM devices created by wanpipe driver. I solve that with a wrapper until there is a better way.
regards helmut
Anthony Minessale schrieb: | 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. | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgzBpwACgkQ4tZeNddg3dwOlACfQqckrmOVMSMGEKgYnbfnYz3d Hb4AmwUuhh2VyXBwZyYAyhBmUbGMDbuO =xsYy -----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
Brian West sip:brian@freeswitch.org <sip%3Abrian@freeswitch.org>
_______________________________________________ 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
-- ----------------------------------- Albano Daniele Salvatore aka daniele_dll Sito: http://www.phpsoft.it Servizi Offerti: - Sviluppo software C# - Sviluppo siti web PHP - Gestione Fedora, Centos, Gentoo -----------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Anthony, I reinstalled wanpipe driver. I configured it with freeswitch option (TDM_VOICE_API) and no zaptel. openzap.conf is same as before (span wanpipe). Wanpipe channel devices are created in /dev by wanrouter as it should be. when freeswitch starts it still looks for /dev/zap/ctl device, which wasn't created. Log: 2008-05-21 11:02:37 [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-21 11:02:37 [ERR] zap_zt.c:721 zt_init() Cannot open control device 2008-05-21 11:02:37 [ERR] zap_io.c:2050 zap_global_init() Error initilizing zt. 2008-05-21 11:02:37 [INFO] zap_wanpipe.c:362 wp_open_range() configuring device s1c1 as OpenZAP device 1:1 fd:36 Is this critical? If not, when I enter oz dump 1 31 (which is my d-channel) I get this: freeswitch@ip-pbx> oz dump 1 31 API CALL [oz(dump 1 31)] output: span_id: 1 chan_id: 31 physical_span_id: 1 physical_chan_id: 16 type: DQ921 state: DOWN last_state: DOWN cid_date: cid_name: cid_num: ani: aniII: dnis: rdnis: cause: (null) State is DOWN, but shouldn't it be UP or so? The LED on sangoma card is green. regards Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgz6CgACgkQ4tZeNddg3dzD7ACdEjccPayBWqci2IkP/vSnJAR/ ElMAoIw0RTFQNcHqL4ujuKYf36u0ula9 =8uMt -----END PGP SIGNATURE-----
It's not critical it just means there are no zaptel devices configured. The D channel does not use the state mechanism at the moment so the state probably will always say down. I might change that to show up in the future but it's more of an aesthetic change. On Wed, May 21, 2008 at 4:15 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Anthony,
I reinstalled wanpipe driver. I configured it with freeswitch option (TDM_VOICE_API) and no zaptel. openzap.conf is same as before (span wanpipe). Wanpipe channel devices are created in /dev by wanrouter as it should be. when freeswitch starts it still looks for /dev/zap/ctl device, which wasn't created.
Log: 2008-05-21 11:02:37 [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-21 11:02:37 [ERR] zap_zt.c:721 zt_init() Cannot open control device 2008-05-21 11:02:37 [ERR] zap_io.c:2050 zap_global_init() Error initilizing zt. 2008-05-21 11:02:37 [INFO] zap_wanpipe.c:362 wp_open_range() configuring device s1c1 as OpenZAP device 1:1 fd:36
Is this critical?
If not, when I enter oz dump 1 31 (which is my d-channel) I get this: freeswitch@ip-pbx> oz dump 1 31 API CALL [oz(dump 1 31)] output: span_id: 1 chan_id: 31 physical_span_id: 1 physical_chan_id: 16 type: DQ921 state: DOWN last_state: DOWN cid_date: cid_name: cid_num: ani: aniII: dnis: rdnis: cause: (null)
State is DOWN, but shouldn't it be UP or so? The LED on sangoma card is green.
regards Helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgz6CgACgkQ4tZeNddg3dzD7ACdEjccPayBWqci2IkP/vSnJAR/ ElMAoIw0RTFQNcHqL4ujuKYf36u0ula9 =8uMt -----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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, hm, I still can't find a reproducable way for setting up FS with sangoma A101. I comiled wanpipe with Compilation mode 3 (TDM Voice (Zaptel) + WAN Protocol Support). My last way leds to a seg fault (GD-Backtrace): Program terminated with signal 11, Segmentation fault. #0 0xa3c9d465 in zap_channel_open_any (span_id=5566664, direction=ZAP_TOP_DOWN, caller_data=0x9f823ed8, zchan=0x9f823ed4) at src/zap_io.c:721 721 if (globals.spans[span_id].active_count >= globals.spans[span_id].chan_count) { (gdb) bt #0 0xa3c9d465 in zap_channel_open_any (span_id=5566664, direction=ZAP_TOP_DOWN, caller_data=0x9f823ed8, zchan=0x9f823ed4) at src/zap_io.c:721 #1 0xa3c986e2 in channel_outgoing_channel (session=0x81c74b0, var_event=0x80adc30, outbound_profile=0x81d2b40, new_session=0x9f827e24, ~ pool=0x9f827e18, flags=SOF_NONE) at mod_openzap.c:906 #2 0xb7ddd083 in switch_core_session_outgoing_channel (session=0x81c74b0, var_event=0x80adc30, endpoint_name=0x81c4f68 "openzap", ~ caller_profile=0x81d2a10, new_session=0x9f827e24, pool=0x9f827e18, flags=SOF_NONE) at src/switch_core_session.c:252 #3 0xb7dfd153 in switch_ivr_originate (session=0x81c74b0, bleg=0x9f8280f0, cause=0x9f8280ec, bridgeto=0x81bf5e0 "openzap/05566664", ~ timelimit_sec=60, table=0x0, cid_name_override=0x0, cid_num_override=0x0, caller_profile_override=0x0, flags=<value optimized out>) ~ at src/switch_ivr_originate.c:824 #4 0xa2bfd0e5 in audio_bridge_function (session=0x81c74b0, data=0x81bf5e0 "openzap/05566664") at mod_dptools.c:1753 #5 0xb7ddaa35 in switch_core_session_exec (session=0x81c74b0, application_interface=0x81213e0, arg=0x81bf5e0 "openzap/05566664") ~ at src/switch_core_session.c:1045 #6 0xb7ddae8c in switch_core_session_execute_application (session=0x81c74b0, app=0x81d2940 "bridge", arg=0x81d2948 "openzap/${dialed_ext}") ~ at src/switch_core_session.c:1003 #7 0xb7ddf0f4 in switch_core_session_run (session=0x81c74b0) at src/switch_core_state_machine.c:144 #8 0xb7ddbe75 in switch_core_session_thread (thread=0x81c6bc0, obj=0x81c74b0) at src/switch_core_session.c:734 #9 0xb7e31b36 in dummy_worker (opaque=0x81c6bc0) at threadproc/unix/thread.c:138 #10 0xb7d4c31b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #11 0xb7c9257e in clone () from /lib/tls/i686/cmov/libc.so.6 I use wanpipe-3.2.5, latest FS trunk and zaptel 1.4.5 (it seems FS need zaptel for E1 access). my openzap.conf is: [span zt] trunk_type => e1 b-channel => 1-15,17-31 d-channel=> 16 my /etc/wanpipe/wanpipe1.conf is: #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================ [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 8 PCIBUS = 2 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = CRC4 FE_LINE = 1 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO [w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = NO my dialplan for an outgoing call is: <extension name="outgoing-pstn"> ~ <condition field="destination_number" expression="^0([0-9]+)$"> ~ <action application="set" data="dialed_ext=$1"/> ~ <action application="bridge" data="openzap/${dialed_ext}"/> ~ </condition> ~ </extension> Freeswitch log is: 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 1 as OpenZAP device 1:1 fd:40 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 2 as OpenZAP device 1:2 fd:41 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 3 as OpenZAP device 1:3 fd:42 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 4 as OpenZAP device 1:4 fd:43 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 5 as OpenZAP device 1:5 fd:44 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 6 as OpenZAP device 1:6 fd:45 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 7 as OpenZAP device 1:7 fd:46 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 8 as OpenZAP device 1:8 fd:47 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 9 as OpenZAP device 1:9 fd:48 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 10 as OpenZAP device 1:10 fd:49 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 11 as OpenZAP device 1:11 fd:50 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 12 as OpenZAP device 1:12 fd:51 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 13 as OpenZAP device 1:13 fd:52 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 14 as OpenZAP device 1:14 fd:53 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 15 as OpenZAP device 1:15 fd:54 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 17 as OpenZAP device 1:16 fd:55 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 18 as OpenZAP device 1:17 fd:56 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 19 as OpenZAP device 1:18 fd:57 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 20 as OpenZAP device 1:19 fd:58 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 21 as OpenZAP device 1:20 fd:59 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 22 as OpenZAP device 1:21 fd:60 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 23 as OpenZAP device 1:22 fd:61 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 24 as OpenZAP device 1:23 fd:62 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 25 as OpenZAP device 1:24 fd:63 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 26 as OpenZAP device 1:25 fd:64 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 27 as OpenZAP device 1:26 fd:65 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 28 as OpenZAP device 1:27 fd:66 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 29 as OpenZAP device 1:28 fd:67 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 30 as OpenZAP device 1:29 fd:68 2008-05-21 15:55:32 [INFO] zap_zt.c:170 zt_open_range() configuring device /dev/zap/channel channel 31 as OpenZAP device 1:30 fd:69 2008-05-21 15:55:32 [ERR] zap_zt.c:164 zt_open_range() failure configuring device /dev/zap/channel as OpenZAP device 1:31 fd:70 2008-05-21 15:55:32 [INFO] zap_io.c:1984 load_config() Configured 30 channel(s) 2008-05-21 15:55:32 [CONSOLE] switch_loadable_module.c:749 switch_loadable_module_load_file() Successfully Loaded [mod_openzap] 2008-05-21 15:55:32 [NOTICE] switch_loadable_module.c:139 switch_loadable_module_process() Adding Endpoint 'openzap' 2008-05-21 15:55:32 [NOTICE] switch_loadable_module.c:245 switch_loadable_module_process() Adding API Function 'oz' strange here is that zap_zt tries to open a 31st channel ... As soon as I call 0XXXX FS crashes with seg fault. Nevertheless I flying blind around, hoping to find the right setup. regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg0LfYACgkQ4tZeNddg3dwIKACfaVOmm8gpNnZE1z8D1hYieJh9 1pQAn1t3nF/x9sRHbFOw3RRNvalG+hq4 =aofb -----END PGP SIGNATURE-----
As stated before, this is the WRONG way to set this up. Please setup sangoma as TDM-api and use span_wanpipe. Mike On May 21, 2008, at 10:13 AM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
hm, I still can't find a reproducable way for setting up FS with sangoma A101. I comiled wanpipe with Compilation mode 3 (TDM Voice (Zaptel) + WAN Protocol Support).
I thought I already explained this. You have to choose between setting up wanpipe for ZAPTEL or wanpipe in standalone mode. when you set it up for ZAPTEL then you forget all about wanpipe in OPENZAP and just treat it like a zaptel span. when you set it up in standalone mode, you need to configure wanpipe1.conf for TDM_VOICE_API and all the proper settings for an E1. You keep doing mixtures of the above when it's one of the other you must choose. On Wed, May 21, 2008 at 9:30 AM, Michael Jerris <mike@jerris.com> wrote:
As stated before, this is the WRONG way to set this up. Please setup sangoma as TDM-api and use span_wanpipe.
Mike
On May 21, 2008, at 10:13 AM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
hm, I still can't find a reproducable way for setting up FS with sangoma A101. I comiled wanpipe with Compilation mode 3 (TDM Voice (Zaptel) + WAN Protocol Support).
_______________________________________________ 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I compiled wanpipe now with compilation mode 6 (freeswitch Default). wanpipe1.conf is now: # WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================ [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE_API, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 8 PCIBUS = 2 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = CRC4 FE_LINE = 1 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO [w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = NO MTU = 80 openzap.conf.xml is now: <configuration name="openzap.conf" description="OpenZAP Configuration"> ~ <settings> ~ <param name="debug" value="7"/> ~ </settings> ~ <pri_spans> ~ <span id="1"> ~ <param name="mode" value="user"/> ~ <param name="dialect" value="euro"/> ~ <param name="dialplan" value="XML"/> ~ <param name="context" value="default"/> ~ </span> ~ </pri_spans> ~ </configuration> openzap.conf is now: [span wanpipe] trunk_type => e1 b-channel => 1:1-15,1:17-31 d-channel=> 1:16 /dev/zap/ctl and wptdm_* devices were created. I recompiled FS with "make current". FS starts up with no errors. Openzap device were successfully configured. Dialplan is still: <extension name="outgoing-pstn"> ~ <condition field="destination_number" expression="^0([0-9]+)$"> ~ <action application="set" data="dialed_ext=$1"/> ~ <action application="bridge" data="openzap/${dialed_ext}"/> ~ </condition> ~ </extension> Call to 0XXXX leads still to segfault. Program terminated with signal 11, Segmentation fault. #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 721 if (globals.spans[span_id].active_count >= globals.spans[span_id].chan_count) { (gdb) bt #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 #1 0xa3d576e2 in channel_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, outbound_profile=0x81d2008, new_session=0x9f8e6e24, ~ pool=0x9f8e6e18, flags=SOF_NONE) at mod_openzap.c:906 #2 0xb7e9c083 in switch_core_session_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, endpoint_name=0x81d5ab8 "openzap", ~ caller_profile=0x81d1ee8, new_session=0x9f8e6e24, pool=0x9f8e6e18, flags=SOF_NONE) at src/switch_core_session.c:252 #3 0xb7ebc153 in switch_ivr_originate (session=0x81c61b8, bleg=0x9f8e70f0, cause=0x9f8e70ec, bridgeto=0x81d4c48 "openzap/0123", ~ timelimit_sec=60, table=0x0, cid_name_override=0x0, cid_num_override=0x0, caller_profile_override=0x0, flags=<value optimized out>) ~ at src/switch_ivr_originate.c:824 #4 0xa2cbc0e5 in audio_bridge_function (session=0x81c61b8, data=0x81d4c48 "openzap/0123") at mod_dptools.c:1753 #5 0xb7e99a35 in switch_core_session_exec (session=0x81c61b8, application_interface=0x81244c8, arg=0x81d4c48 "openzap/0123") ~ at src/switch_core_session.c:1045 #6 0xb7e99e8c in switch_core_session_execute_application (session=0x81c61b8, app=0x81d1e20 "bridge", arg=0x81d1e28 "openzap/${dialed_ext}") ~ at src/switch_core_session.c:1003 #7 0xb7e9e0f4 in switch_core_session_run (session=0x81c61b8) at src/switch_core_state_machine.c:144 #8 0xb7e9ae75 in switch_core_session_thread (thread=0x81c58a0, obj=0x81c61b8) at src/switch_core_session.c:734 #9 0xb7ef0b36 in dummy_worker (opaque=0x81c58a0) at threadproc/unix/thread.c:138 #10 0xb7e0b31b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #11 0xb7d5157e in clone () from /lib/tls/i686/cmov/libc.so.6 Any ideas? regards helmut Anthony Minessale schrieb: | I thought I already explained this. | | | You have to choose between setting up wanpipe for ZAPTEL or wanpipe in | standalone mode. | | when you set it up for ZAPTEL then you forget all about wanpipe in OPENZAP | and just treat it like a zaptel span. | | when you set it up in standalone mode, you need to configure wanpipe1.conf | for TDM_VOICE_API and all the proper settings for an E1. | | | You keep doing mixtures of the above when it's one of the other you must | choose. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg0OrIACgkQ4tZeNddg3dx7jACfcLVuFZ4ruKy6HbOnfD8TFa/n mAoAnjzwYWFJP5UzTWxIt5Y1809B9L59 =AlHg -----END PGP SIGNATURE-----
you are putting in the dial string wrong and we are not taint checking it. Try openzap/1/a/0123 meaning span 1, any channel, dest 0123 we think you want span 123 and we didnt check for it being too big On Wed, May 21, 2008 at 10:07 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I compiled wanpipe now with compilation mode 6 (freeswitch Default).
wanpipe1.conf is now:
# WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================
[devices] wanpipe1 = WAN_AFT_TE1, Comment
[interfaces] w1g1 = wanpipe1, , TDM_VOICE_API, Comment
[wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 8 PCIBUS = 2 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = CRC4 FE_LINE = 1 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO
[w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = NO MTU = 80
openzap.conf.xml is now: <configuration name="openzap.conf" description="OpenZAP Configuration"> ~ <settings> ~ <param name="debug" value="7"/> ~ </settings> ~ <pri_spans> ~ <span id="1"> ~ <param name="mode" value="user"/> ~ <param name="dialect" value="euro"/> ~ <param name="dialplan" value="XML"/> ~ <param name="context" value="default"/> ~ </span> ~ </pri_spans> ~ </configuration>
openzap.conf is now: [span wanpipe] trunk_type => e1 b-channel => 1:1-15,1:17-31 d-channel=> 1:16
/dev/zap/ctl and wptdm_* devices were created.
I recompiled FS with "make current". FS starts up with no errors. Openzap device were successfully configured.
Dialplan is still:
<extension name="outgoing-pstn"> ~ <condition field="destination_number" expression="^0([0-9]+)$"> ~ <action application="set" data="dialed_ext=$1"/> ~ <action application="bridge" data="openzap/${dialed_ext}"/> ~ </condition> ~ </extension>
Call to 0XXXX leads still to segfault.
Program terminated with signal 11, Segmentation fault. #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 721 if (globals.spans[span_id].active_count >= globals.spans[span_id].chan_count) { (gdb) bt #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 #1 0xa3d576e2 in channel_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, outbound_profile=0x81d2008, new_session=0x9f8e6e24, ~ pool=0x9f8e6e18, flags=SOF_NONE) at mod_openzap.c:906 #2 0xb7e9c083 in switch_core_session_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, endpoint_name=0x81d5ab8 "openzap", ~ caller_profile=0x81d1ee8, new_session=0x9f8e6e24, pool=0x9f8e6e18, flags=SOF_NONE) at src/switch_core_session.c:252 #3 0xb7ebc153 in switch_ivr_originate (session=0x81c61b8, bleg=0x9f8e70f0, cause=0x9f8e70ec, bridgeto=0x81d4c48 "openzap/0123", ~ timelimit_sec=60, table=0x0, cid_name_override=0x0, cid_num_override=0x0, caller_profile_override=0x0, flags=<value optimized out>) ~ at src/switch_ivr_originate.c:824 #4 0xa2cbc0e5 in audio_bridge_function (session=0x81c61b8, data=0x81d4c48 "openzap/0123") at mod_dptools.c:1753 #5 0xb7e99a35 in switch_core_session_exec (session=0x81c61b8, application_interface=0x81244c8, arg=0x81d4c48 "openzap/0123") ~ at src/switch_core_session.c:1045 #6 0xb7e99e8c in switch_core_session_execute_application (session=0x81c61b8, app=0x81d1e20 "bridge", arg=0x81d1e28 "openzap/${dialed_ext}") ~ at src/switch_core_session.c:1003 #7 0xb7e9e0f4 in switch_core_session_run (session=0x81c61b8) at src/switch_core_state_machine.c:144 #8 0xb7e9ae75 in switch_core_session_thread (thread=0x81c58a0, obj=0x81c61b8) at src/switch_core_session.c:734 #9 0xb7ef0b36 in dummy_worker (opaque=0x81c58a0) at threadproc/unix/thread.c:138 #10 0xb7e0b31b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #11 0xb7d5157e in clone () from /lib/tls/i686/cmov/libc.so.6
Any ideas?
regards helmut
Anthony Minessale schrieb: | I thought I already explained this. | | | You have to choose between setting up wanpipe for ZAPTEL or wanpipe in | standalone mode. | | when you set it up for ZAPTEL then you forget all about wanpipe in OPENZAP | and just treat it like a zaptel span. | | when you set it up in standalone mode, you need to configure wanpipe1.conf | for TDM_VOICE_API and all the proper settings for an E1. | | | You keep doing mixtures of the above when it's one of the other you must | choose. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkg0OrIACgkQ4tZeNddg3dx7jACfcLVuFZ4ruKy6HbOnfD8TFa/n mAoAnjzwYWFJP5UzTWxIt5Y1809B9L59 =AlHg -----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
So I'm not the only one who can PEBKAC OpenZAP into segging? :) -MC Sent from my iPhone On May 21, 2008, at 9:28 AM, "Anthony Minessale" <anthony.minessale@gmail.com
wrote:
you are putting in the dial string wrong and we are not taint checking it.
Try openzap/1/a/0123 meaning span 1, any channel, dest 0123
we think you want span 123 and we didnt check for it being too big
On Wed, May 21, 2008 at 10:07 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I compiled wanpipe now with compilation mode 6 (freeswitch Default).
wanpipe1.conf is now:
# WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================
[devices] wanpipe1 = WAN_AFT_TE1, Comment
[interfaces] w1g1 = wanpipe1, , TDM_VOICE_API, Comment
[wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 8 PCIBUS = 2 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = CRC4 FE_LINE = 1 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO
[w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = NO MTU = 80
openzap.conf.xml is now: <configuration name="openzap.conf" description="OpenZAP Configuration"> ~ <settings> ~ <param name="debug" value="7"/> ~ </settings> ~ <pri_spans> ~ <span id="1"> ~ <param name="mode" value="user"/> ~ <param name="dialect" value="euro"/> ~ <param name="dialplan" value="XML"/> ~ <param name="context" value="default"/> ~ </span> ~ </pri_spans> ~ </configuration>
openzap.conf is now: [span wanpipe] trunk_type => e1 b-channel => 1:1-15,1:17-31 d-channel=> 1:16
/dev/zap/ctl and wptdm_* devices were created.
I recompiled FS with "make current". FS starts up with no errors. Openzap device were successfully configured.
Dialplan is still:
<extension name="outgoing-pstn"> ~ <condition field="destination_number" expression="^0([0-9]+)$"> ~ <action application="set" data="dialed_ext=$1"/> ~ <action application="bridge" data="openzap/${dialed_ext}"/> ~ </condition> ~ </extension>
Call to 0XXXX leads still to segfault.
Program terminated with signal 11, Segmentation fault. #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 721 if (globals.spans[span_id].active_count >= globals.spans[span_id].chan_count) { (gdb) bt #0 0xa3d5c465 in zap_channel_open_any (span_id=123, direction=ZAP_TOP_DOWN, caller_data=0x9f8e2ed8, zchan=0x9f8e2ed4) at src/zap_io.c:721 #1 0xa3d576e2 in channel_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, outbound_profile=0x81d2008, new_session=0x9f8e6e24, ~ pool=0x9f8e6e18, flags=SOF_NONE) at mod_openzap.c:906 #2 0xb7e9c083 in switch_core_session_outgoing_channel (session=0x81c61b8, var_event=0x80e7798, endpoint_name=0x81d5ab8 "openzap", ~ caller_profile=0x81d1ee8, new_session=0x9f8e6e24, pool=0x9f8e6e18, flags=SOF_NONE) at src/switch_core_session.c:252 #3 0xb7ebc153 in switch_ivr_originate (session=0x81c61b8, bleg=0x9f8e70f0, cause=0x9f8e70ec, bridgeto=0x81d4c48 "openzap/0123", ~ timelimit_sec=60, table=0x0, cid_name_override=0x0, cid_num_override=0x0, caller_profile_override=0x0, flags=<value optimized out>) ~ at src/switch_ivr_originate.c:824 #4 0xa2cbc0e5 in audio_bridge_function (session=0x81c61b8, data=0x81d4c48 "openzap/0123") at mod_dptools.c:1753 #5 0xb7e99a35 in switch_core_session_exec (session=0x81c61b8, application_interface=0x81244c8, arg=0x81d4c48 "openzap/0123") ~ at src/switch_core_session.c:1045 #6 0xb7e99e8c in switch_core_session_execute_application (session=0x81c61b8, app=0x81d1e20 "bridge", arg=0x81d1e28 "openzap/${dialed_ext}") ~ at src/switch_core_session.c:1003 #7 0xb7e9e0f4 in switch_core_session_run (session=0x81c61b8) at src/switch_core_state_machine.c:144 #8 0xb7e9ae75 in switch_core_session_thread (thread=0x81c58a0, obj=0x81c61b8) at src/switch_core_session.c:734 #9 0xb7ef0b36 in dummy_worker (opaque=0x81c58a0) at threadproc/unix/thread.c:138 #10 0xb7e0b31b in start_thread () from /lib/tls/i686/cmov/ libpthread.so.0 #11 0xb7d5157e in clone () from /lib/tls/i686/cmov/libc.so.6
Any ideas?
regards helmut
Anthony Minessale schrieb: | I thought I already explained this. | | | You have to choose between setting up wanpipe for ZAPTEL or wanpipe in | standalone mode. | | when you set it up for ZAPTEL then you forget all about wanpipe in OPENZAP | and just treat it like a zaptel span. | | when you set it up in standalone mode, you need to configure wanpipe1.conf | for TDM_VOICE_API and all the proper settings for an E1. | | | You keep doing mixtures of the above when it's one of the other you must | choose. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkg0OrIACgkQ4tZeNddg3dx7jACfcLVuFZ4ruKy6HbOnfD8TFa/n mAoAnjzwYWFJP5UzTWxIt5Y1809B9L59 =AlHg -----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 GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org pstn:213-799-1400 _______________________________________________ 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 SIGNED MESSAGE----- Hash: SHA1 Hi Michael, Michael S Collins schrieb: | So I'm not the only one who can PEBKAC OpenZAP into segging? :) Looks like as not ;) "PEBKAC" hehe, nice! regards Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg1GQwACgkQ4tZeNddg3dy2RACeOeXcNiIc2LjXRE0l1GQA0mE/ QwsAn0mT0UEgRwNon5Fs3jiFaOi9DG1u =xeGF -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Anthony, hmmmmmmmmmmm, that's soo nice!! Works fine now. Thx for your help! :) regards Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg1GCwACgkQ4tZeNddg3dzxqgCfQJSdkwdu+l4KSu+sjLKdd+pu whgAoIKojvxAL3YCGuCnBWq+NYLpeW/z =hg1j -----END PGP SIGNATURE-----
Was there any recent change in local_stream? I've upgraded from RC4 to RC6 (windows XP platform) and got a "missing stream" error message on the console when attempting to call the default conference bridge (ext 3011). When downgraded back to RC4, the problem disappeared. Before I send the entire console log output and environment setting, did anyone try that on the latest version?
Nothing intentional or anything I can think of. Mike On May 21, 2008, at 10:35 AM, UV wrote:
Was there any recent change in local_stream?
I've upgraded from RC4 to RC6 (windows XP platform) and got a "missing stream" error message on the console when attempting to call the default conference bridge (ext 3011). When downgraded back to RC4, the problem disappeared.
Before I send the entire console log output and environment setting, did anyone try that on the latest version?
_______________________________________________ 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
Another quick question: In the latest build (and earlier), I've noticed mod_shout is ticked off from the build file and the source files are missing (although present in the SVN). Was this module deprecated?
mod_shout was never added to the windows build. It should still be in the tarballs. I would happily accept patches that add it to the windows build. Mike On May 21, 2008, at 10:39 AM, UV wrote:
Another quick question: In the latest build (and earlier), I've noticed mod_shout is ticked off from the build file and the source files are missing (although present in the SVN).
Was this module deprecated?
_______________________________________________ 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
Hi, I don't know if this solve your problems but if you use zaptel and wanpipe then /etc/openzap/openzap.conf should have: [span zt] If you use wanpipie with tdm api then /etc/openzap/openzap.conf should have: [span wanpipe] Regards, Lukasz Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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:
root@ip-pbx:/usr/src/wanpipe-3.1.4# ls -l /dev/zap/ total 0 crw-rw---- 1 root dialout 196, 1 2008-05-20 16:24 1 crw-rw---- 1 root dialout 196, 10 2008-05-20 16:24 10 crw-rw---- 1 root dialout 196, 11 2008-05-20 16:24 11 crw-rw---- 1 root dialout 196, 12 2008-05-20 16:24 12 crw-rw---- 1 root dialout 196, 13 2008-05-20 16:24 13 crw-rw---- 1 root dialout 196, 14 2008-05-20 16:24 14 crw-rw---- 1 root dialout 196, 15 2008-05-20 16:24 15 crw-rw---- 1 root dialout 196, 16 2008-05-20 16:24 16 crw-rw---- 1 root dialout 196, 17 2008-05-20 16:24 17 crw-rw---- 1 root dialout 196, 18 2008-05-20 16:24 18 crw-rw---- 1 root dialout 196, 19 2008-05-20 16:24 19 crw-rw---- 1 root dialout 196, 2 2008-05-20 16:24 2 crw-rw---- 1 root dialout 196, 20 2008-05-20 16:24 20 crw-rw---- 1 root dialout 196, 21 2008-05-20 16:24 21 crw-rw---- 1 root dialout 196, 22 2008-05-20 16:24 22 crw-rw---- 1 root dialout 196, 23 2008-05-20 16:24 23 crw-rw---- 1 root dialout 196, 24 2008-05-20 16:24 24 crw-rw---- 1 root dialout 196, 25 2008-05-20 16:24 25 crw-rw---- 1 root dialout 196, 26 2008-05-20 16:24 26 crw-rw---- 1 root dialout 196, 27 2008-05-20 16:24 27 crw-rw---- 1 root dialout 196, 28 2008-05-20 16:24 28 crw-rw---- 1 root dialout 196, 29 2008-05-20 16:24 29 crw-rw---- 1 root dialout 196, 3 2008-05-20 16:24 3 crw-rw---- 1 root dialout 196, 30 2008-05-20 16:24 30 crw-rw---- 1 root dialout 196, 31 2008-05-20 16:24 31 crw-rw---- 1 root dialout 196, 4 2008-05-20 16:24 4 crw-rw---- 1 root dialout 196, 5 2008-05-20 16:24 5 crw-rw---- 1 root dialout 196, 6 2008-05-20 16:24 6 crw-rw---- 1 root dialout 196, 7 2008-05-20 16:24 7 crw-rw---- 1 root dialout 196, 8 2008-05-20 16:24 8 crw-rw---- 1 root dialout 196, 9 2008-05-20 16:24 9 crw-rw---- 1 root dialout 196, 254 2008-05-20 16:24 channel crw-rw---- 1 root dialout 196, 0 2008-05-20 16:24 ctl crw-rw---- 1 root dialout 196, 255 2008-05-20 16:24 pseudo crw-rw---- 1 root dialout 196, 253 2008-05-20 16:24 timer crw-rw---- 1 asterisk asterisk 196, 250 2008-05-20 16:24 transcode
Freeswitch was compiled with openzap. openzap.conf.xml is in autoload_configs and has this content:
<configuration name="openzap.conf" description="OpenZAP Configuration"> ~ <settings> ~ <param name="debug" value="7"/> ~ </settings> ~ <pri_spans> ~ <span id="1"> ~ <param name="mode" value="user"/> ~ <param name="dialect" value="euro"/> ~ <param name="dialplan" value="XML"/> ~ <param name="context" value="default"/> ~ </span> ~ </pri_spans> ~ </configuration>
/etc/openzap/openzap.conf has this content: [span wanpipe] trunk_type => e1 b-channel => 1:1-15, 1:17-31 d-channel=> 1:16
freeswitch console log is:
2008-05-20 16:30:59 [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 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. 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c1 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c2 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c3 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c4 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c5 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c6 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c7 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c8 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c9 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c10 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c11 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c12 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c13 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c14 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c15 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c17 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c18 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c19 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c20 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c21 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c22 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c23 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c24 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c25 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c26 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c27 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c28 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c29 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c30 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c31 2008-05-20 16:30:59 [ERR] zap_wanpipe.c:414 wp_open_range() failure configuring device s1c16 2008-05-20 16:30:59 [INFO] zap_io.c:1984 load_config() Configured 0 channel(s) 2008-05-20 16:30:59 [ERR] zap_io.c:2077 zap_global_init() No modules configured! 2008-05-20 16:30:59 [ERR] mod_openzap.c:1855 mod_openzap_load() Error loading OpenZAP 2008-05-20 16:30:59 [CRIT] switch_loadable_module.c:727 switch_loadable_module_load_file() Error Loading module /opt/app/freeswitch/mod/mod_openzap.so **Module load routine returned an error** 2008-05-20 16:30:59 [NOTICE] switch_loadable_module.c:245 switch_loadable_module_process() Adding API Function 'originate'
any ideas?
regards helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgy61YACgkQ4tZeNddg3dzGdgCdEqgGISo4UYUcHQE7tTlehG10 JxYAnAyvl4qd0YBg1v+EE3h63Q2bMQDB =ZQ+R -----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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Lukasz, yeah, I learned that yesterday ;) Anthony explained it already, you confirmed it and I got it up and running. Thx! regards Helmut Lukasz Kutkowski schrieb: | Hi, | | I don't know if this solve your problems but if you use zaptel and | wanpipe then /etc/openzap/openzap.conf should have: | | [span zt] | | If you use wanpipie with tdm api then /etc/openzap/openzap.conf should have: | | [span wanpipe] | | Regards, | Lukasz | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgzytYACgkQ4tZeNddg3dxfjQCfY+CFPvCr2aPcO4+0jiJctJ9U Bl0Anjkk676Bd2B7iL45DEJkeuVXHIv7 =6s/u -----END PGP SIGNATURE-----
On Tue, 2008-05-20 at 17:16 +0200, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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:
I'm rather clueless how to solve your problem but I do see that the zaptel and wanpipe versions you use are very old. Might be an idea to update zaptel to 1.4.19 and wanpipe to 3.3.10. At least that were the latest versions I saw earlier this week. Hopefully someone more in the know can confirm if this makes sense or acknowledge my cluelessness :) Regards, Patrick
participants (9)
-
Anthony Minessale
-
Brian West
-
daniele_dll
-
Helmut Kuper
-
Lukasz Kutkowski
-
Michael Jerris
-
Michael S Collins
-
Patrick
-
UV