similar to: AppKonference 2.4

Hi, I have released AppKonference 2.5 today. This release fixes a bug that can cause audio problems when conference frame caching is enabled. It also fixes the spy feature so that more than one spyer can spy on a channel at the same time. If more than one spyer is unmuted, their audio is mixed and whispered to the spyee. -- Paul Albrecht

I have released an updated AppKonference that compiles with Asterisk 13. You can download the latest code from source forge: sourceforge.net/projects/appkonference That said Asterisk 13 doesn?t get that much attention because I use Asterisk 1.4 + some hacks. Here?s a link to my Asterisk 1.4 github repository: https://github.com/pjalbrecht/asterisk You don?t need these hacks to use the module, but

Hi All, I am running asterisk on Linux machine and trying to use confbridge application. Please have a look at Conf files. sip.conf ====== [general] context=default allowoverlap=no bindport=5060 bindaddr=0.0.0.0 srvlookup=yes disallow = all allow=ulaw allow=alaw defaultexpiry=100 [5001] type=friend nat=yes host=dynamic canreinvite=no context= conferences disallow = all

Hi I am new to mailing list ,please correct me if the way of posting is not correct Relpying to : Re: make asterisk do something when an outgoing call is picked up (lee) For making asterisk do something on outgoing call Dial application is itself used Like for Playing an announcement to the caller on pick up the is an option A(x) where x is the file to play to the called party. Also

I have a call from a call file: Action: Originate Async: yes Channel: SIP/2012 Codecs: ulaw,alaw,gsm Context: dialout Exten: callprogress Priority: 1 Timeout: 20000 Variable: SIPADDHEADER="Alert-Info: Ring Answer" ActionID: 100014 CallerID: Axis < 525 > The SIP/2012 is a IP Speaker on the computer. The error is: [Jun 11 15:44:45] WARNING[8132]: chan_sip.c:24191

On Oct 22, 2014, at 10:33 AM, Joshua Colp <jcolp at digium.com> wrote: > Paul Albrecht wrote: >> Really? Shouldn?t something this major affecting the entire Asterisk >> community get discussed on the lists? Any idea what Leif is talking >> about when he says the community is in transition, moving from dial >> plan model to external control. > > It was

One thing that concerns me is that this post is from 2009, even though the newest version of the app on Sourceforge is up to date. I have a customer who has been using a conference server that I built for him using app_konference for several years now and he routinely runs conferences with anywhere from 10 ? 125 active users. The ultimate goal is several hundred concurrent users and I can see that

Hello, After I have re-read the "PJSIP Advanced Codec negotiation" document, it occurred to me that the desired behavior should actually happen automatically, just due to the codec negotiation logic, but it looks like asterisk doesn't actually follow the described logic which is likely a bug. Can you please follow with me through a simple sip call and see if I'm missing

Hello! Client is using ulaw, however server sometimes fills the log with following: [2011-03-09 21:23:07] WARNING[27204] chan_sip.c: Asked to transmit frame type slin, while native formats is 0x8 (alaw) read/write = 0x4 (ulaw)/0x8 (alaw) [2011-03-09 21:23:07] WARNING[27204] chan_sip.c: Asked to transmit frame type slin, while native formats is 0x8 (alaw) read/write = 0x4 (ulaw)/0x8 (alaw)

Hello people, I've ran into two problem that I can't seem to be able to solve on my own. Here's my scenario (running Asterisk 13.28.1): In short: - Asterisk behaves unexpectedly (at least to me) when negotiating between endpoints             that have a different but intersecting set of codecs (preventing direct media flow).           - Also, when an endpoint sends RTP with an

Hi What is special control 16? I am getting this error quite often -- special control 16, then for some reason it puts on hold and then logs is full of Asked to transmit frame type ulaw, while native formats is 0x8 (alaw) read/write = 0x8 (alaw)/0x8 (alaw) Both peer and trunk have same codec priority (disallow=all then allow=alaw then alllow=ulaw) Any ideas how to fix this ? --

Dear all, I'm trying to use ulaw and alaw with Diax and Asterisk but I'm not able to, I got the following error message: Mar 20 11:47:59 NOTICE[7099]: chan_iax2.c:6350 socket_read: Rejected connect attempt from 192.168.0.55, requested/capability 0x8/0xc incompatible with our capability 0xfe02. I do not understand why because my Asterisk box load these codecs properly! Does somebody

So the call used Alaw as Codec. > Am 13.06.2020 um 17:23 schrieb Luca Bertoncello <lucabert at lucabert.de>: > > Am 13.06.2020 um 13:47 schrieb Michael Keuter: > > Hi > >> Try "sip show peer <peername>" for a phone. > > So: > > mobile phone: > bpi*CLI> sip show peer 0049177xxxxxxx > > > > > * Name :

Hello! On 20.10.20 at 14:00 Asterisk Development Team wrote: > The Asterisk Development Team would like to announce the release of Asterisk 18.0.0. > This release is available for immediate download at > https://downloads.asterisk.org/pub/telephony/asterisk I just tested the new codec negotiation feature and unfortunately wasn't able to get it working as expected. I tried several

Hi there I europe alaw is usual. I have a SIP Phone which perferes ulaw. When my * box has to transcode alaw to ulaw the sound get's one way choppy. (alaw => ulaw is choppy, ulaw => alaw is fine). I managed to fix the issue by forcing my SIP phone to use alaw only, but is this a know issue with asterisk 1.2.13? -Benoit-

I am unable to get re-invite to work on a new system. Also, unwanted transcoding is occurring on PSTN calls. The new system (FreePBX 2.11.0.37, Asterisk 11.9.0, CentOS 6.5) will eventually replace an old system (FreePBX 2.8.1, Asterisk 1.8.7.2, CentOS 5.8) currently in production. Both systems are on VPS with public IP addresses. Goals for the new system include: HD (g722) connections on

Hi, When ever I put g729 in allow for trunk the other two codecs (ulaw and alaw) stop working and I get the frame type error for them, but g729 works fine. I've cleared general part of sip.conf of codec info to be on safe side. If ulaw and alaw are the only ones allowed they work fine. Asterisk shouldn't be doing any encoding or decoding, all codecs should be passing through. Any

Am 13.06.2020 um 13:47 schrieb Michael Keuter: Hi > Try "sip show peer <peername>" for a phone. So: mobile phone: bpi*CLI> sip show peer 0049177xxxxxxx * Name : 0049177xxxxxxx Description : Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : default Record On feature : automon

Hi, at my Asterisk box, I have a few of IAX2 phones (configured with alaw/ulaw/gsm codecs, in this order) and a PRI E1 line. In iax.conf I hav: disallow=all allow=alaw allow=ulaw allow=gsm During some incoming call, I read at console: -- Executing Dial("Zap/2-1", "IAX2/215|20|TtwW") in new stack -- Called 215 -- Call accepted by 10.97.1.7 (format ulaw) --

A previous poster mentioned the same thing, with no response: http://lists.digium.com/pipermail/asterisk-users/2004- December/080161.html Fresh asterisk 1.0.5 install on FC3, started with "make samples", nothing fancy. It's so bland, I'm surprised the list isn't full of people having the same trouble. I have several Uniden UIP200 phones and a single Grandstream BudgetTone