[asterisk-users] Ztdummy and Asterisk
Hi to all, The problem was finally solved by installing Asterisk-1.4.18. Versions 1.4.20 and current (1.4.22) produce the issue. Version 1.4.18 does not. May this be a bug? Aldo Sudak___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Ztdummy and Asterisk
Hi again, Thanks for your answer, Stefan. In fact, ztcfg is automatically running from the startup script. Anyhow this seems harmless and not the cause of the problem. I have confirmed this with two other Asterisk servers, both having a zaptel card installed in them, but one running the same Debian Etch OS as the troublesome machine, and the other one running Fedora Core 6. In both cases I restricted the zaptel modules loaded to just ztdummy and modified zaptel.conf in order not to configure anything. Then I restarted zaptel and attempted to start Asterisk. In the first case I obtained the same error message as I reported before. In the case of the machine running Fedora, Asterisk started normally (and it's worth to say that ztcfg does also automatically run in it). So it is apparent that the problem involves Debian. Greetings. Aldo Sudak On Sat, Nov 01, 2008 at 11:03:09PM -0200, Aldo D. Sudak wrote: Loading zaptel hardware modules: ztdummy. Running ztcfg: done. There is no need to run ztcfg if you just want to use ztdummy. The call to ztcfg is probably just part of some standard init script. -- Stefan Tichy ( asterisk2 at pi4tel dot de )___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Ztdummy and Asterisk
Hi to all, Thank you Dobry an Tzafrir for your answers. I agree with Tzafrir in the sense that ztdummy needs no configuration. Moreover, the .conf file generated by genzaptelconf does not contain any configuration at all for ztdummy (tonezone and defaultzone are the only uncommented text in it). I must also say that I have tried again with the current versions of Asterisk and Zaptel, with the same result. So I'm still wondering where the problem lies... Cordially, Aldo Hi there, Try running genzaptelconf -v and restart asterisk. Here's what I have in /etc/zaptel.conf in order to have the MeetMe working. -v doesn't change the output . zaptel.conf is not needed for ztdummy, as ztdummy does not handle spanconfig, start or whatever. It simply starts operating at the moment it is probed. # Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit # Zaptel Configuration File # # This file is parsed by the Zaptel Configurator, ztcfg # # It must be in the module loading order # Span 1: ZTDUMMY/1 ZTDUMMY/1 (source: RTC) 1 (MASTER) # Global data loadzone= us defaultzone = us This thing might have been useful for zaptel channels, if you had any. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Ztdummy and Asterisk
Hi, I have installed Asterisk 1.4.20 on Debian Etch. The server has no telephony card installed, but I have anyhow installed Zaptel (Zaptel-1.4.9) in order to be able to use MeetMe. The Zaptel modules load normally. I obtain the following prompts: kerplunk:/# /etc/init.d/zaptel start Loading zaptel framework: done. Waiting for zap to come online...OK Loading zaptel hardware modules: ztdummy. Running ztcfg: done. I can confirm that Zaptel is loaded: kerplunk:/# lsmod | grep zaptel zaptel184548 1 ztdummy crc_ccitt 2240 1 zaptel Anyhow, when I attempt to start Asterisk, I obtain the following: = == Parsing '/etc/asterisk/asterisk.conf':Found == Parsing '/etc/asterisk/extconfig.conf':Found == Parsing '/etc/asterisk/logger.conf':Found Asterisk Event Logger Started /var/log/asterisk/event_log [Nov 1 21:40:41] ERROR[1873]: asterisk.c:2954 main: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options: 1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support. 2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them. 3. If you need Zaptel services, you must correctly configure Zaptel. Of course, because I have no Zaptel hardware I did not configure zaptel.conf. I really would not know what to configure. Ideas are welcome. Thanks in advance. Aldo ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Asterisk Initial Set-up - 'Registration Refused' at FWD
Hi to all! I'm glad to be of any help. I had the same issue and sent an e-mail directly to FWD. I paste the answer below. Greetings, Aldo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Aldo, FWD IAX is experimental and not supported. Please create a SIP trunk which will be more reliable. Regards, Juan Vides On 10/16/07, Aldo D. Sudak [EMAIL PROTECTED] wrote: Dear sirs, I am aware that this is perhaps not the appropriate address to write to, but I was not able to find any solution on the Internet. So I shall be very grateful if you send me an answer suggesting the possible cause for my problem. I have recently obtained an account at FWD, #869178. I have enabled IAX service for this account. I then configured my Asterisk server according to your instructions but always obtain a 'registration rejected' message. In order to verify whether this was an Asterisk configuration problem, I introduced my account data to an Iax-Lite soft phone installed in another computer but the result was the same. On the other hand, I configured an X-Lite SIP phone for this account and it worked fine. Same number, same password; so I wonder if there is something happening related with your iax2.fwdnet.net server. Thank you in advance. Aldo D. Sudak -- Juan Vides Fax:631-293-3996 115 Broadhollow Road, Suite 225 Melville, NY 11747 www.freeworlddialup.com FWD# 393464 Yahoo: pulverCommunicator MSN:[EMAIL PROTECTED] AOL:plvrcomcator ICQ: 341693563 El mail recibido, fue verificado por el Servicio de Antivirus para mail de Fullzero y se encuentra libre de virus ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Issues with Zaptel 1.4.5.1
Hi Tzafrir! Thank you for your answer, and my apologies for my delayed response. I regret to say that the patch test's results were not succesful. I shall describe the whole procedure in detail for you to establish whether I did something wrong. The fact is that I am as much a Linux beginner as I am an Asterisk one, and so I had first to learn how to stick the patch. Since I found no instructions to apply it, perhaps this was not the right procedure... After initially attempting with 3M self-adhessive tape with little success..., I finally did the following: 1) I copied the autoztcgf.diff to the /usr/src/zaptel-1.4.5.1 directory 2) I run patch -b autoztcfg.diff 3) Since a file named zaptel.c did not exist, patch offered me to enter the filename. I entered zaptel-base.c which I thought was the most probable file to be patched. 4) I obtained 6 out of 6 success messages indicating however very variable offsets, ranging between 13 and 224 lines, which called my attention. May be this was normal, however. Then I performed the following actions: 1) I sent the zaptel file in /etc/modprobe.d/ to trash (remember this file had been artificially grafted by me by means of zaptel 1.4.4). By the way I want to make clear that zaptel files in /etc/init.d and in /etc/rc.d/init.d were created by version 1.4.5.1, and that zaptel modules were loaded during bootup (they just were not configured). 2) I stopped Asterisk and unloaded zttranscode, wctdm24xxp and zaptel by means of rmmod. (My card is a TDM800P) 3) I then installed the patched zaptel-1.4.5.1 starting with a make clear command. Everything went OK. A new zaptel.conf replaced the previous one. I properly configured it by hand. I restarted the machine. Results: 1) Zaptel was not automatically configured. I ran zttool: 'unconfigured' statement 2) I ran /sbin/ztcfg -vv. The result was a wonderful computer crash. I had to restart it from the CPU button :-( Finally I returned to my original installation and re-sent the zaptel script to the /etc/modprobe.d directory. Everything began to work properly again. In my humble and newbie's opinion, a patch to simply install this script would have to solve the problem. Considering that previous versions did it, I cannot understand well why this action has been eliminated in version 1.4.5.1. Greetings, Aldo --- On Wed Oct 17 16:57:31 CDT 2007 Tzafrir Cohen wrote: On Wed, Oct 17, 2007 at 06:37:21PM -0300, Aldo D. Sudak wrote: Greetings to all list members! My name is Aldo Sudak and I am an Asterisk newbie. I am writing now because I have not been able to find any mention to the issues described below, neither in this list nor in the wiki. I am performing preliminary tests with Asterisk 1.4.11 and Zaptel 1.4.5.1 on Fedora Core 6. Installation of all of the Asterisk packages was straightforward and I always obtained success messages. Following Asterisk and Zaptel installation I ran the corresponding make config commands in order to have both Asterisk and Zaptel running at startup. With Zaptel, however, two issues arose: 1) zaptel.conf in the /etc/ directory had not been created. The GUI loaded itself a very rudimentary zaptel.conf file which lacked loadzone and defaultzone definitions, so I prefered to manually copy and paste zaptel.conf.sample from the sources and rename it. use zapconf or genzaptelconf to generate one that actually works. Both are included with Zaptel and installed by default (genzaptelconf is being phased out). 2) Zaptel modules loaded during bootup but were not automatically configured, and so I had to manually run ztcfg and afterwards restart Asterisk each time I started the computer. I discovered that there did not exist a 'zaptel' file in the /etc/modprobe.c/ directory, so I made an experiment by installing Zaptel 1.4.4, which generated the file, and then re-installing Zaptel 1.4.5.1. The experience was successful and now Zaptel 1.4.5.1 is loaded and configured during bootup. /etc/init.d/zaptel start is required to properly start zaptel. It will also run ztcfg. Otherwise users run into issues where misconfigured zaptel.conf fails loading of a module. That is a buggy behaviour. If your card is an analog one, take a look at http://bugs.digium.com/7613 and tell me what you think. Something similar for digital spans would require more information in sysfs. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE
[asterisk-users] Issues with Zaptel 1.4.5.1
Greetings to all list members! My name is Aldo Sudak and I am an Asterisk newbie. I am writing now because I have not been able to find any mention to the issues described below, neither in this list nor in the wiki. I am performing preliminary tests with Asterisk 1.4.11 and Zaptel 1.4.5.1 on Fedora Core 6. Installation of all of the Asterisk packages was straightforward and I always obtained success messages. Following Asterisk and Zaptel installation I ran the corresponding make config commands in order to have both Asterisk and Zaptel running at startup. With Zaptel, however, two issues arose: 1) zaptel.conf in the /etc/ directory had not been created. The GUI loaded itself a very rudimentary zaptel.conf file which lacked loadzone and defaultzone definitions, so I prefered to manually copy and paste zaptel.conf.sample from the sources and rename it. 2) Zaptel modules loaded during bootup but were not automatically configured, and so I had to manually run ztcfg and afterwards restart Asterisk each time I started the computer. I discovered that there did not exist a 'zaptel' file in the /etc/modprobe.c/ directory, so I made an experiment by installing Zaptel 1.4.4, which generated the file, and then re-installing Zaptel 1.4.5.1. The experience was successful and now Zaptel 1.4.5.1 is loaded and configured during bootup. Anyhow , I think all these manipulations should not be necessary, and I would like to know if I did something wrong in order for all this to be happening. Suggestions are welcome. Thanks in advance. Aldo ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
