similar to: Specific SIP answers on incoming calls?

Hi, I was switching from zaptel to dahdi and got latest SVN from everything. Compiling works fine. kernel module dahdi_dummy is loaded. /dev/dahdi/pseudo exists Trying to go into a meetme does not work: [Aug 11 14:04:45] -- Executing [8001 at client_int_sgmobile:1] MeetMe("SCCP/6000-00000001", "444|dcIM") in new stack [Aug 11 14:04:45] WARNING[4184]: app_meetme.c:775

That does not make too much sense to me... Configuration should be ok... [Aug 8 23:30:13] SSL certificate ok [Aug 8 23:30:13] == Problem setting up ssl connection: error:00000000:lib(0):func(0):reason(0) [Aug 8 23:30:13] WARNING[23835]: tcptls.c:463 ast_make_file_from_fd: FILE * open failed! Terve, Stefan -- Last words of a stormchaser: "Where is that rotation on the radar?!"

Hi, I have the following symptoms: Call X-lite / Nokia E51 X-lite press hold: Nokia DOES hear MOH Nokia press hold: X-lite does NOT hear MOH Call X-lite / SCCP phone MOH works as supposed Call SCCP phone / Nokia E51 SCCP press hold: Nokia DOES hear MOH Nokia press hold: X-lite does NOT hear MOH In addition, the BLF on the SCCP phones does NOT show the hinted SIP extension on hold. With 1.4

Hi, all Is there someway ability to insert custom Header to "SIP 486" message, when HANGUP application is invoked? Our use case is to set that Header, when call-limit is reached, to analyze elsewhere, but we do not want to set some custom causecode in HANGUP application because this can confuse a calling equipment.

Hi, I've recently reinstalled a Diva in my asterisk server (alongside a QuadBRI :-) to test the nice features Armin has been adding in chan_capi. The capi.conf format has changed, so my question is how do I define a deflect= statement for different incoming MSN's? I've tried to define a section for each (group of) MSN with a different "deflect". Is that correct? [DIVA1]

On Sat, Oct 17, 2015 at 8:24 PM, Pasi Parviainen via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 14.10.2015 23:36, Chandler Carruth via llvm-dev wrote: > >> * **Be welcoming.** We strive to be a community that welcomes and supports >> people of all backgrounds and identities. This includes, but is not >> limited >> to members of any race,

<div>Is there any chance to create feature request for that useful functionality?</div><div>š</div><div>02.07.2015, 14:03, "Rusty Newton" <rnewton@digium.com>:</div><blockquote type="cite"><div><div><div>On Wed, Jul 1, 2015 at 4:46 AM, <span><<a href="mailto:royj@yandex.ru"

Okay, I think I need a sanity check here - If I call a person that's on the phone, I should get a busy signal. Now more specifically, a call comes into the pbx via PRI. The destination dialplan runs busy(20). Now, the PRI causecode should get set to 17 (user busy) so that the originating end can play a busy tone, correct? -Justin -------------- next part -------------- An HTML attachment

On Thu, 2015-04-02 at 16:12 -0400, Lamar Owen wrote: > On 04/02/2015 03:55 PM, Always Learning wrote: > > Is there a commercial motive for this 'unwelcome by most' change ? > > Do you have data to prove that it is unwelcome by most? Although most people in the world will privately complain the vast majority do not complain in public. Where is your contrary evidence that

<div>Thanks for the tip. Our goal is to know that call-limit is triggered. And later analyze this info, maybe do some action.</div><div>Yes, we can parse CDRs or execute AGI script but we do not want inmplement this logic on Asterisk because it can affectš<span>performance.</span></div><div>š</div><div>02.07.2015, 15:31, "jg"

On Feb 17, 2014, at 5:13 AM, Kostya Serebryany <kcc at google.com> wrote: > Then my question: will there be any objection if I disentangle AsanCoverage from ASan and make it a separate LLVM phase with the proper clang driver support? > Or it will be an unwelcome competition with the planned clang coverage? I don’t view it as a competition, but assuming that we both succeed in our

Hi all, I am trying to get Capi Dial to use a specific outgoing msn. I can't get it to work. If I make a test call to 0703241494 (same isdn line, just one of the other numbers) I don't get CLID at all. Any ideas? ; use 0703241432 as outgoing msn exten => _070.,1,Dial(CAPI/@0703241432:${EXTEN}|30|r) in capi.conf I have: [general] nationalprefix=0 internationalprefix=00 rxgain=0.8

Hi, I have a problem with Cisco 7906G and SIP protocol use with Asterisk 1.2.26. I have uploaded in my tftp server the firmware 'cmterm-7911_7906-sip.8-0-4SR1' that use 'SIP11.8-0-4SR1S.loads' and in SEPmacaddress.cnf.xml I have: <loadInformation>SIP11.8-0-4SR1S</loadInformation> ..but in tftp log server I have: Oct 07 11:56:22 asterisk1.local

Hi, I tried to use the version 0.6 of chan_capi-cm for outgoing calls it works perfectly but for incoming calls it will not work: --- snip --- *CLI> capi debug CAPI Debugging Enabled -- CONNECT_IND (PLCI=0x101,DID=97,CID=0179903xxxx,CIP=0x1,CONTROLLER=0x1) == reventix: Incoming call '0179903xxxx' -> '97' -- reventix: info element CALLED PARTY NUMBER --

Hi I've got a script like this exten => s,1,SetVar(CALLFILENAME=/var/www/recordings/${TIMESTAMP:0:8:7}/${UNIQUEID}) exten => s,2,AGI(recordstart.py,${ARG1},${CALLERIDNUM},${CALLFILENAME},Ind) exten => s,3,DIAL(ZAP/g2/${ARG1},70) exten => s,4,AGI(logerror.py,${ARG1},${CALLERIDNUM},${CHANNEL},${DIALSTATUS},${DATETIME}, ${CAUSECODE}) exten => s,5,hangup exten =>

Dear friends - below is a subset of a much larger material showing two ways of generating two "lines". The intention is to have the colour reflect a variable, pH, but the legend is disturbed. The little part marked "3" above the colour scale is unwelcome. Why did it appear? How could I avoid it? I'm on Windows 7, R version 3.4.1 (2017-06-30) -- "Single

Hi, we?re currently seeing trouble with klibc on several architectures, cf. http://www.zytor.com/pipermail/klibc/2012-May/003277.html and armhf is being one of them, when using klibc to compile mksh-static with it. I can look into it (asked zumbi for build-deps in a sid chroot on harris already), but not 100% sure I?ll find it, so more eyes on klibc would not be unwelcome ;-) maks, does klibc

Hi Tanya, > > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > > that be llvm-1.9? > > We have always labeled the dir just llvm which is fine. If you build > llvm it will know its version 1.9. I think that's missing the point. Convention is the foo-4.2.tar unpacks to a directory called foo-4.2. It's a unwelcome surprise when it

>>> * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't >>> that be llvm-1.9? >> >> We have always labeled the dir just llvm which is fine. If you build >> llvm it will know its version 1.9. > > I think that's missing the point. Convention is the foo-4.2.tar unpacks > to a directory called foo-4.2. It's a

Neither do_menu nor do_readln (in src/main/scan.c) call the function InitConsoleGetchar. They need to do this to reset ConsolePrompt. If you use "scan" to read in data from the terminal, then ConsolePrompt is set to "n:" for some integer n and this prompt makes an unwelcome appearance when you use the "menu" or "readline" functions. Incidentally, could we