similar to: MP3s not decoding properly for MusicOnHold.

Hi All Somebody knows as resolv the error below? Already I compiled asterisk-addons-1.2.3, but exactly thus it reports this error, could help me? -- Executing WaitMusicOnHold("SIP/3205-d9ef", "30") in new stack -- Started music on hold, class 'default', on SIP/3205-d9ef Jun 23 02:14:21 WARNING[24960]: interface.c:215 decodeMP3: Junk at the beginning of frame

This past holiday weekend has resulted in some real groaners when it comes to bugs in our dialplan, making obvious the need for some changes in our procedures. First, our hours of operation for Christmas Eve, Christmas, Boxing Day and New Year's Eve had changed with little to no notice. Okay, fine, whatever, I fix. Our Christmas Eve hours (made worse by being Monday this year) dialplan

On 2016-02-17 15:32, Richard Mudgett wrote: > On Wed, Feb 17, 2016 at 5:15 PM, Ernie Dunbar <maillist at lightspeed.ca> > wrote: > >> Hi everyone. >> >> We have an Asterisk server running Debian Squeeze, with Asterisk >> v1.8.13.1 (basically, the Debian Stable version for Squeeze, but >> with some minor source code changes specific to our site).

Hi, i configured Musiconhold and Works, but the sound is very low. I haved put the volume in the max, but is equal. I tested to my voice, and the sound is also low. exten=>8000,1,Wait(2) exten=>8000,2,Record(menu:gsm) exten=>8000,3,Wait(2) exten=>8000,4,Playback(menu) exten=>8000,5,Hangup() when the musicaonhold is play e recieved this warning. ?exten =>

We have an issue with our Asterisk install where Asterisk produces many Zombie processes (on the order of several hundred per minute) until either the Asterisk server is restarted (and the zombies die a natural death), or the kernel runs out of PID space (happens within hours) and brings the system to a halt. This problem only happens when the server is under some non-trivial load. We were

Okay, so here's the configuration I have for MySQL Realtime (Asterisk version 1.6.2.17): In /etc/asterisk/extconfig.conf: sipusers => mysql,mya2billing,cc_sip_buddies In /etc/asterisk/res_mysql.conf: [mya2billing] dbhost = localhost dbname = mya2billing dbuser = a2billinguser dbpass = REDACTED dbport = 3306 And here's the error messages I get: voip2*CLI> realtime mysql status

This *should* be something that's easy to fix, but apparently I'm not doing something right. Our SIP long distance provider is telling us to only use formats G.723 and G.729, so I've set up their trunk configuration in sip.conf as such: [t564] type=friend host=XXX.XX.56.4 context=default disallow=all allow=g723 allow=g729 However, the Dial application gives the following error:

Hi everyone. We have an Asterisk server running Debian Squeeze, with Asterisk v1.8.13.1 (basically, the Debian Stable version for Squeeze, but with some minor source code changes specific to our site). We're trying to upgrade to 11.13.1 (The Debian Stable version for Jessie), but I've run into a snag when compiling res_fax_spandsp (and yes, we really need that module). The old

You need to ensure that traffic to the SIP box is sent to the correct IP. Also if you use split-tunnel (eg: not redirect-gateway def1) you must make sure NAT and traffic redirection works as is so the Asus router knows it should send the traffic through tunnel and not via WAN. IMPORTANT: Then you must, in the ASUS RT-N66U make a port forward inwards from TUN to the phone client. I would suggest

We have two Asterisk servers. One is a live server supporting our customers, and the other is a backup server that's being upgraded and pressed into service. Both servers have a Digium TE405P T1 card in them, and in order to test the T1 service on the backup server, I've created a T1 crossover cable (as per http://www.voip-info.org/wiki/view/crossover+T1+cable) that goes from port 4 on the

Dear all, I have a data similar to this: myframe<- data.frame (ID=c("Ernie", "Ernie","Ernie","Ernie"), Timestamp=c("24.09.2012 08:00", "24.09.2012 09:00", "24.09.2012 10:00", "25.09.2012 10:00"), Longitude=c("8.481","8.482","8.483","8.481"),

I'm kind of at a loss to diagnose problems like this, yet we get them a lot. - The ATA (Thomson 784 in this particular case) is logged into the Asterisk server. 'sip show peer' shows their IP address, port, and useragent. - The ATA is connected directly to the internet (no NAT, but the sip configuration has nat=always) and logs in to our server, which is also directly connected to the

Hello, I have a data frame somewhat like that: myframe <- data.frame (ID=c("Ernie", "Ernie", "Ernie", "Bert", "Bert", "Bert"), Timestamp=c("24.09.2012 09:00", "24.09.2012 10:00", "24.09.2012 11:00"), Hunger=c(1,1,1,2,2,1) ) myframestime <- as.POSIXct (strptime(as.character(myframe$Timestamp),

Thank you for providing the example code... for the request of running it multiple times it would have helped if you could have confirmed that the example ran through without errors... there were a lot of mistakes in it. Look into using the reprex package to check your example next time. I don't do this kind of analysis... I really don't know what to expect from the functions. The

At the bottom is what I got returned from AMANDA 2.3.0.5 after patching Samba 1.9.16p11 to give estimates. Any idea what I might not have done yet? My disklist reads: shokk \\thor\depot nocomp-user-gnutar To connect successfully to that server with smbclient, I have to do this, giving the same password that I now have in /etc/amandapass: smbclient \\\\THOR\\DEPOT -U BACKUP Also, the

Hello, I tried for about three hours now to solve this problem but I can't figure it out. I am sure someone knows how do it. At least I hope so. I have a data frame somewhat like this: myframe <- data.frame (ID=c("Ernie", "Ernie", "Bert", "Bert"), Timestamp=c("24.09.2012 09:00", "24.09.2012 09:00", "24.09.2012 10:00",

David Allan Finch wrote: > Has anyone considerd modify the Unix encypt to use > the same system as NT. IE the encypted pasword in the > /etc/passwd or NIS/NIS+ table is the same for both? Err. That would be a *really* bad idea. See the l0phtcrack source for details :-). Seriously, though. The password hashes used on NT are very poor. They don't use salt and people are now