similar to: CDR problems with Queue

Hi, I have read that DAHDI automagically turns of echo cansellation when it sees that it is a FAX. So I checked this out. I have a fax call into asterisk which is immediately called out to an external fax machine via DAHDI again.. For example, the result is: DAHDI/1-1 = incoming call, DAHDI/2-1 outgoing call. Now, with the help of dahdi show channel, if I check channel 2: echo cancellation is

Hi, Is it possible to have MOH in early audio, while waiting for someone to pick up a Dial() call? (When using zap channels, I have early audio working with playback) H?kon Nessj?en Loopback Systems AS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070429/c901ff90/attachment.htm

Only a warning, and doesn't seem to do anything bad. But I can't seem to figure out what these warnings mean? -- Requested transfer capability: 0x00 - SPEECH [Feb 17 12:33:03] WARNING[10750]: chan_dahdi.c:3096 dahdi_call: Unrecognized prilocaldialplan NPI modifier: k [Feb 17 12:33:03] WARNING[10750]: chan_dahdi.c:3096 dahdi_call: Unrecognized prilocaldialplan NPI modifier: o [Feb 17

Hi, This is the output from queue show 28: 47 (DAHDI/g0/12345678) (realtime) (Ringing) has taken no calls yet Why is the devicestate "Ringing" when no channels is calling this number, and the queue says "has taken no calls yet"? Is it picking up the general state of a random channel on g0 in dahdi? Or what is happening? It only seems to happen with this particular

Hi, I'm now thinking of always dialing out to Local/xxx at outbound/n on all my queue members. The reason for this, is both to be able to limit the number of calls to one agent, and to have fail-over-lines on the agents. (for example, if dahdi fails, go sip) But for a few years ago, I did some testing with Local/ channels, and they seemed somewhat unstable in large quantity. Are they more

System have been working great for weeks, using an average 40 of 120 dahdi channels. But today, I suddenly see scary things like this: -- Moving call from channel 5 to channel 7 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing

I want to create a script for IVR that compiles responses, aggregates them to a total number. Then, run an equation based on the result. Press 1 for X (X is a positive number 500) Press 2 for Y (Y is a positive number 200) Press 3 for Z (Z is a positive number 300) Press 20 to calculate the results = 500+200+300 =1000 then, exten => s,n,Read(NUMBER,,1000) exten => s,n,SayDigits(${NUMBER})

Hello, I have transcoding card TC400P installed in server running Debian with Asterisk 1.4.23. Everything seams to be fine and after I boot up server I see in dmesg: 7.590966] Zapata Telephony Interface Registered on major 196 [ 7.590966] Zaptel Version: 1.4.12.1 [ 7.590966] Zaptel Echo Canceller: MG2 [ 7.610963] zttranscode: Loaded. [ 7.618969] wctc4xxp: tc400b0: Attached to

Dears, I need to save some information on userfield when calls end in Asterisk13, but I have two error cases: 1. With endbeforehexten=no in cdr.conf, I have a registry in cdr, but userfield is not set. 2. With endbeforehexten=yes, I have two lines in cdr, one with duration, src e dst correct, and a second line with userfield setting and dst h. I am using cdr_odbc.conf, with Asterisk11.14.0 it

Hi, I'm trying to migrate from Asterisk 1.8 to Asterisk 13 and can't figure this one out. I'm pretty sure the question has been already asked, but I failed to find a solution. Can you modify CDR values in an h-extension? My cdr.conf contains: [general] enable=yes unanswered=yes endbeforehexten=yes initiatedseconds=no batch=no The diaplan contains a simple "h" extension

Ok I can't get my CDR values to set from the h extension in either 1.6.2 or 1.8 What is wrong? Here is what I found in the cdr.conf ; Normally, CDR's are not closed out until after all extensions are finished ; executing. By enabling this option, the CDR will be ended before executing ; the "h" extension so that CDR values such as "end" and "billsec" may

With endbeforehexten=no I actually get two CDR entries. One for the call and a second one for the "h" extension. "","13","10","sip-locals","""13"" <13>","SIP/13-00000006","SIP/10-00000007","Dial","SIP/10","2015-08-04 06:28:44","2015-08-04

Hi, Reading this old thread, may I ask if keeping hangup handlers from updating CDR values still enforced in Asterisk 15 ? If positive, would it be very complex to add in Asterisk, a configuration option allowing a system administrator to list in cdr.conf, the CDR fields allowed to be updated in hangup handlers ? I'm planning to store some RTCP stats. Saving them in CDR(userfield) would be

I can get the size of a ulaw file using STAT. And I can get the duration in seconds by doing filesize/8000. Your tea-break challenge is to help me find the shortest most Asterisk-like way of saying: "The following file is [<n> minutes and] <s> seconds long". ...without referring to external applications! Yes, I'm aware of the math behind it, but I was hoping for a

Hi, I have the following code that operates when a channel is hung-up: [record-hangupcause]exten => 1,n,Set(CDR(hangupcause)=${HANGUPCAUSE})exten => s,n,Return() Before the dial a hangup handler is registered: Set(CHANNEL(hangup_handler_push)=record-hangupcause,s,1) The routine is called and the variables are being set, however not on the channel's CDR which made the call. I believe this

2013/3/29 Julian Lyndon-Smith <asterisk at dotr.com> > check out the endbeforehexten option in cdr.conf > > this needs to set to "yes" > > Julian > Unfortunately, this doesn't help. Let's drop the hangup handler at the moment, and focus on the "saving to file" part. Then my issue is I can't update CDR value is hangup exten. Here is a

Can someone tell me what I am doing wrong? Why doesn't CDR(duration) or CDR(billsec) return the correct values? cdr.conf endbeforehexten=yes extensions.conf [macro-Dial] ; ${ARG1} - Dial String exten => s,1,Dial(${ARG1},,M(post-dial)) exten => h,1,NoOp(Call was hung up - ${CDR(duration)} seconds long, billed for ${CDR(billsec)} seconds) The log shows: -- Executing [h

So... I'm trying to access CDR(duration) and CDR(billsec) inside h... I keep getting 0. Can I access the CDR function inside a hangup extensions? Asterisk 1.4.13 Thanks, Doug. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

I am using the new 1.8.5 and I just found out that Asterisk won't record the call if the call just hangup. I did a test like this: exten => 1009, 1, Hangup() Then I called 1009: == Using UDPTL CoS mark 5 == Using SIP RTP CoS mark 5 -- Executing [1009 at init-1005:1] Hangup("SIP/1007-0000003c", "") in new stack == Spawn extension (init-1005, 1009, 1)

This was always possible in the past, however does not work in the current release. I believe this is a bug. To: asterisk-users at lists.digium.com From: cervajs at fpf.slu.cz Date: Fri, 9 Oct 2015 10:04:47 +0200 Subject: Re: [asterisk-users] Storing HANGUPCAUSE in CDR search in archives save the records to another table like cdr_extended Dne