similar to: Voicemail2 crashing on replay

Since firmware 1.0.3.81, unless I'm imagining things, Voicemail2 seems to be having problems. The Grandstream and sip.conf were set to RFC2833 now with that setting I get extra digits during "Mailbox" and "Password" phases. 222001 instead of 2201 for example. When both are changed to "SIP info" there is no problem. But what is the new setting "DTMF Payload

We've been testing (aim:frziegler and aim:end1r) the Voicemail2 app for a few days now, based on a CVS build from Monday, 5/12/03-23:15. Works good! Thanks Mark! We seem to have found a bug in the MWI (Message Waiting Indicator) logic. By simply creating msg0000.txt files in both structures, e.g.: for extension 4000: voicemail1: /var/spool/asterisk/vm/4000/INBOX/msg0000.txt

Just idly watching * in console mode and saw that someone from 50.49.54.102 tried to register with my *. whois gives:- OrgName: Internet Assigned Numbers Authority OrgID: IANA Address: 4676 Admiralty Way, Suite 330 City: Marina del Rey StateProv: CA PostalCode: 90292-6695 Country: US NetRange: 50.0.0.0 - 50.255.255.255 CIDR: 50.0.0.0/8 NetName: RESERVED-50

I've had a few problems with my system holding the line after a call has been made, just now I rebooted and noticed the following in /var/log/messages Aug 13 17:23:15 Sheriff kernel: wcfxo: DAA mode is 'FCC' in the file wcfxo.c the following structure is initialised as below which would suggest that FCC is wrong for France or pretty well all of Europe. static struct fxo_mode {

For those who don't wake up at 5.00 am and start reading /. http://searchnetworking.techtarget.com/originalContent/0,289142,sid7_gci935769,00.html -- Dave Cotton <dcotton@linuxautrement.com>

I just got an email from SIPphone advising that there have been problems with the above firmware and advising to reload from their server. This does in fact reload 1.0.4.35 into the phone. And now voicemail has gone AWOL again. -- Dave Cotton <dcotton@linuxautrement.com>

I'm getting this message when I start Asterisk chan_capi.c:2205 capi_handle_msg: Command.Subcommand = 0x5.0x81 but when I try and recompile I get this chan_capi.c:60: error: `__use_AST_MUTEX_DEFINE_STATIC_rather_than_AST_MUTEX_INITIALIZER__' undeclared here (not in a function) any help would be greatly appreciated. -- Dave Cotton <dcotton@linuxautrement.com>

I really can't understand what is happening. I have the same set up in two locations:- 2 fritz cards in each with the patches and the same capi.conf except for the MSNs. One installation calls in on controller 1 and starts calls out on controller 2, i.e. perfect. The other calls come in on both controllers at the same time. I have checked the patches etc. Is this possibly a problem caused

I'm getting this error when compiling:- make[1]: Entering directory `/usr/src/asterisk.svn/sounds' --09:22:12-- http://ftp.digium.com/pub/telephony/sounds/releases/asterisk-core-sounds-en-wav-1.4.0.tar.gz => `asterisk-core-sounds-en-wav-1.4.0.tar.gz' Resolving ftp.digium.com... 216.27.40.102, 69.16.138.164 Connecting to ftp.digium.com|216.27.40.102|:80... connected. HTTP

This one is for the archives. I got a call today that the * at one of my clients was not working. The switchboard is set up to ring for a while and then the rest of the phones start up if the switchboard doesn't pick up. This was not happening. Instead the mobile phone of one of the people there was ringing and after the delay the internals started ringing. When I connected to the web

I went to the Linux Solutions exhibition in Paris yesterday, visited the well stocked O'Reilly stand and saw a nice pile of Asterisk TFOT, 6 hours later there was only one left. It must say something, also it was the English version. -- Dave Cotton <dcotton@linuxautrement.com>

On a different note using Fedora Core 3 I get CC [M] /usr/src/zaptel/zaptel.o /usr/src/zaptel/zaptel.c: In function `zt_chan_write': /usr/src/zaptel/zaptel.c:1745: warning: ignoring return value of `copy_from_user', declared with attribute warn_unused_result /usr/src/zaptel/zaptel.c: In function `ioctl_load_zone': /usr/src/zaptel/zaptel.c:2392: warning: ignoring return value of

Just done a clean install of rc5 on a totally new machine and found the following:- /etc/init.d/asterisk start errors on line 109 - there is no 0 before $VERBOSITY as in the other lines. More interesting is that after make samples I have no iax2 available. Dave Cotton

Hello all. Has anyone managed to get SIPCALL.co.uk's service working with the [*] box? I've managed to register with other SIP providers but not SIPcall. The debug just show's [*] attempting to register. But receiving a 401 error everytime. Cheers Matt

I'm running the a very recent CVS version of asterisk on an RH9 machine. My problem is that my x100p takes about 10 seconds to detect a hangup. After that it takes about 10 more seconds for the the zaptel device to release the line. Here's an example of my console report: == Parsing '/var/spool/asterisk/voicemail/default/101/INBOX/msg0000.txt': == Parsing

Hi, (sorry for my mistake in not deleting the rest of the message just now) The problem seems to be here in zaptel.c (and torisa.c) #ifdef DEFINE_SPINLOCK static DEFINE_SPINLOCK(zaptimerlock); static DEFINE_SPINLOCK(bigzaplock); #else static spinlock_t zaptimerlock = SPIN_LOCK_UNLOCKED; static spinlock_t bigzaplock = SPIN_LOCK_UNLOCKED; #endif If I remark out as follows: //#ifdef

Hi, I used to have a Grandstream phone connected to Asterisk a few months ago. Worked just great! Then today I do a new install, rather than an upgrade, and all of a sudden I cannot check voicemail with it. No problem calling or receiving call. It simply speeds through the vm greetings but I cannot hear them. If I check the same VM with an analog phone it works fine. So I wanted to check

I have the voicemail format set to wav49 in my voicemail.conf file. When retrieving voicemails, the first message plays back ok - but then Asterisk hangs up and the log shows the following error. Any idea what's up? May 19 12:57:24 VERBOSE[7860]: Asterisk Ready. May 19 13:48:51 WARNING[7860]: Not a wav file 49 May 19 13:48:51 WARNING[7860]: Unable to open fd on

I had a compile problem with the CVS I downloaded on 21 June. I have a Debian box with 2.4.18 kernel (version needed for support of Conexant ADSL). There is a difficulty with Zaptel build regarding HDLC detection. It tries to build it in and then results in unresolved kernel symbols and fails to load. I have had to comment out the entire HDLC defines in zconfig.h to get a driver to install at

Asterisk 1.2, Fedora Core 4: When I leave a voicemail message, it writes the necessary files to the INBOX: msg0000.gsm msg0000.txt msg0000.wav msg0000.WAV When I hang up, the files are erased. There is no indication of anything untoward in the logs: -- x=0, open writing: [...]/INBOX/msg0000 format: wav49, 0x99ce778 -- x=1, open writing: [...]/INBOX/msg0000 format: