search for: zapchannel

----- Original Message ----- <snip> > That's what I was afraid of - we have more extensions than channels ... the number of extensions isn't the issue. it is the signal the meridian broadcasts when your digital telephone on your desk is on/off hook, or ringing or whatever. if you could tap into that information and monitor it with something similar to *'s manager interface

----- Original Message ----- > Ooooh, I've got it working a treat, thanks to some great help from people on > this list. I *am* currently writing up a how to, and will post it as soon as > I'm done. > > Basically, take the line from the meridian, and chop the rj45 off. (!) put > another RJ45 on, but with the wires crossed (IOW a cross over cable). Plug > the meridian

...ble to register channel '1' Mar 13 20:43:35 WARNING[5779]: loader.c:345 ast_load_resource: chan_zap.so: load_module failed, returning -1 ] As a matter of fact this is what is listed in /dev/: aaberga@epsilon-stargate:~/sources/voip/zaptel-1.0.6> ls /dev [....] z2ram zap1 zap2 zap3 zap4 zapchannel zapctl zappseudo zaptimer zero zkshim zqft0 I edited the list to avoid a huge message. As said I am not a Linux low level expert ... still it's striking that Asterisk does not find a pesudo file /zap/channel and there is something similar, ie zapchannel. Anyways the zaptel modules are there:...

...aging ]# more /etc/udev/permissions.d/50-udev.permissions zap/*:asterisk:asterisk:660 [beta@staging ]# grep zap /etc/udev/rules.d/50-udev.rules # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer", NAME="zap/timer" KERNEL="zapchannel", NAME="zap/channel" KERNEL="zappseudo", NAME="zap/pseudo" KERNEL="zap[0-9]*", NAME="zap/%n" [beta@staging ]# ls /dev/*z* /dev/zero [beta@staging zaptel-1.2.6] make ; make linux26 ; make install [beta@staging zaptel-1.2.6]# make devices bu...

...el: Freed a Wildcard Jan 1 10:48:16 bu kernel: Zapata Telephony Interface Unloaded Jan 1 10:48:16 bu udev[27206]: removing device node '/udev/zap1' Jan 1 10:48:17 bu udev[27207]: removing device node '/udev/zaptimer' Jan 1 10:48:17 bu udev[27222]: removing device node '/udev/zapchannel' Jan 1 10:48:17 bu udev[27233]: removing device node '/udev/zappseudo' Jan 1 10:48:17 bu udev[27244]: removing device node '/udev/zapctl' Jan 1 10:48:17 bu zaptel: Removing zaptel module: succeeded Jan 1 10:48:18 bu kernel: Zapata Telephony Interface Registered on major 196...

...l '2' Jan 2 06:28:08 WARNING[3473]: loader.c:402 __load_resource: chan_zap.so: load_module failed, returning -1 Jan 2 06:28:08 WARNING[3473]: loader.c:523 load_modules: Loading module chan_zap.so failed! Ok, I look in the /dev and I could not find /dev/zap at all! But, there is a /dev/zapchannel character device. Any ideas what can be wrong? And last question. Does zaptel driver reads configuration file on startup? If so, how do I force the driver to update if config file was changed? Thanks, Rudolf

...T100P PCI Card -------------------------------- In order to get the card to work you MUST edit /etc/udev/rules.d/50-udev.rules Goto the end of the file and add....... KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer", NAME="zap/timer" KERNEL="zapchannel", NAME="zap/channel" KERNEL="zappseudo", NAME="zap/pseudo" KERNEL="zap[0-9]*", NAME="zap/%n" Then for good measure, recompile asterisk. Hope this helps! Ty Carter, President Strategic Network Consultants, Inc. 524 East 9th Street Washingto...

...5038 login ---------------------- action: login username: ******* secret: *********** make call: ---------------------- action: originate channel: zap/1/98744207 context: default exten: 5196 priority: 1 callerid: test async: yes dial digits: ---------------------- (try#1) Action: ZapDialOffhook ZapChannel: 1-1 Number: 12334556 (try#2) Action: ZapDialOffhook ZapChannel: 1 Number: 12334556 (both do the same thing) record call: (zap) ---------------------- Action: Monitor Channel: Zap/1-1 File: recordingtest14 Mix: 1 stop recording call: ---------------------- Action: StopMonitor Channel: Zap/1-1...

Hi everyone, Sometimes i am having problems with Zap channels on asterisk 1.2 (Disc-OS 1.1), after some calls, the channel continues in use, even after hanging the call up, then i need to run the "soft hangup Zap/<zapchannel>" in the asterisk CLI to release the channel. Here is my zapata.conf: [trunkgroups] [channels] language=pt_BR context=default usecallerid=yes hidecallerid=no callwaiting => yes usecallingpres=> yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callretur...

...nning as non-root KERNEL=="zapctl", NAME="zap/ctl", OWNER="asterisk", GROUP="asterisk", MODE="0660" KERNEL=="zaptimer", NAME="zap/timer", OWNER="asterisk", GROUP="asterisk", MODE="0660" KERNEL=="zapchannel", NAME="zap/channel", OWNER="asterisk", GROUP="asterisk", MODE="0660" KERNEL=="zappseudo", NAME="zap/pseudo", OWNER="asterisk", GROUP="asterisk", MODE="0660" KERNEL=="zap[0-9]*", NAME="zap/...

...96 Zaptel Version: 1.2.16 Zaptel Echo Canceller: KB1 Zaptel Transcoder support loaded vi /etc/udev/rules.d/50-udev.rules # Section for zaptel device KERNEL=="zapctl", NAME="zap/ctl" KERNEL=="zaptimer", NAME="zap/timer" KERNEL=="zapchannel", NAME="zap/channel" KERNEL=="zappseudo", NAME="zap/pseudo" KERNEL=="zap[0-9]*", NAME="zap/%n" vi /etc/modprobe.conf install wctdm /sbin/modprobe --ignore-install wctdm opermode=NEWZEALAND fxshonormode=1 boostr...

Hi, I would like to know how to see which channels are used in my PRI E1 link from Asterisk to another locally-connected commercial PBX. If I run "dahdi show channels", I can see the used channels in the second column "extension" but only if it's an "incoming" call (ie. legacy PBX to Asterisk). If I dial from an Asterisk extension to an extension in the other

...39; properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug- devel@lists.sourceforge.net> Nov 24 10:23:40 jfd wait_for_sysfs[3368]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/zaptel/zapchannel' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug- devel@lists.sourceforge.net> Nov 24 10:23:40 jfd wait_for_sysfs[3370]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/zapte...

...that use FXS signaling" I tried this both in /etc/udev/rules.d/50-udev.rules and /etc/udev/rules.d/zaptel.rules (rebooting after each change) Zaptel devices KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer", NAME="zap/timer" KERNEL="zapchannel", NAME="zap/channel" KERNEL="zappseudo", NAME="zap/pseudo" KERNEL="zap[0-9]*", NAME="zap/%n" When I run ztcfg I get the following error: line 0: Unable to open master device '/dev/zap/ctl' When I run zttool I get the fol...

...tel wcfxo loaded on the server correctly. I run dual P3 500 Mhz box. After reading README.udev I put a file 60-zaptel.rules /etc/udev/rules.d # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer", NAME="zap/timer" KERNEL="zapchannel", NAME="zap/channel" KERNEL="zappseudo", NAME="zap/pseudo" KERNEL="zap[0-9]*", NAME="zap/%n" In /etc/udev/permissions.d/50-udev.permissions I added: # zaptel devices zap/ctl:root:root:0664 zap/timer:root:root:0664 zap/channel:root:root:0664...

...l here /etc/udev/rules.d/10- zaptel.rules and it looks like this: KERNEL="zapctl", NAME="zap/ctl", MODE="0660", GROUP="dialout" KERNEL="zaptimer", NAME="zap/timer", MODE="0660", GROUP="dialout" KERNEL="zapchannel", NAME="zap/channel", MODE="0660", GROUP="dialout" KERNEL="zappseudo", NAME="zap/pseudo", MODE="0660", GROUP="dialout" KERNEL="zap[0-9]*", NAME="zap/%n", MODE="0660", GROUP="dial...

...------------- fxsks=1 loadzone = us defaultzone=us UDEV file /etc/udev/rules.d/50-udev.rules: ----------------------------------------- # Asterisk Zaptel devices KERNEL=="zapctl", NAME="zap/ctl" KERNEL=="zaptimer", NAME="zap/timer" KERNEL=="zapchannel", NAME="zap/channel" KERNEL=="zappseudo", NAME="zap/pseudo" KERNEL=="zap[0-9]*", NAME="zap/%n" ZAPATA file: ----------- gigli # cat /etc/asterisk/zapata.conf [trunkgroups] [channels] context=default switchtype=national signalling=f...

...a udev rules file in >/etc/udev/rules.d with the rules in /usr/src/zaptel/README.udev > >/etc/udev/rules.d/zaptel.rules ># section for zaptel device >KERNEL="zapctl", NAME="zap/ctl" >KERNEL="zaptimer", NAME="zap/timer" >KERNEL="zapchannel", NAME="zap/channel" >KERNEL="zappseudo", NAME="zap/pseudo" >KERNEL="zap[0-9]*", NAME="zap/%n" > >Now I get this error, I will troubleshoot it later tonight. >[root@asterisk zaptel]# ztcfg -vv >Zaptel Configuration >====...

...39;/dev/zap/ctl' I added the suggested lines to /etc/udev/rules.d/50-udev.rules that were in the zaptel README.udev, as I understood them? # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer", NAME="zap/timer" KERNEL="zapchannel", NAME="zap/channel" KERNEL="zappseudo", NAME="zap/pseudo" KERNEL="zap[0-9]*", NAME="zap/%n" When I load the zaptel modules, they work the errors are just distracting. Any suggestions would be great. James

hi all, I wanted to call my asterisk on the Zapchannel with mainnumber+DID number: it's ok for calls from handy and from sip i get the right extension(DID) on phone, but when i call from an analog telephone the DID number is not mentioned by asterisk. in my zapata.conf: overlapdial = yes immediate = no That should take care of the waiting for DID...