similar to: AMI Originate CDRs

Hello, i have call time irregularites in my asterisk CDR. I a currently using a mysqly backent to save CDR records and use this to generate bills at the end of each month. However, my users are complaining that they gety charged for even uncompleted calls (i.e. calls they make whaich have already be setup but canclled). i have noticed that only 'AWNSERED' and 'Busy' show up in my

Hello Everyone, I want to send a few numbers (variables) when doing Asterisk AMI Originate command and then have Festival read them back to customer in the context. How should this be done? Following is my not working example and also reference on AMI Originate Command: Command: Originate Channel: SIP/123 Context: TestFestival Priority: 1 Exten: 555 Variable: $numberONE, $numberTWO, $numberTHREE

Hi All, I have been running a environment with asterisk 1.4.20.1 for some time now with no issue but have recently added some extra functionality (enabled call recording via MixMonitor) and ran into some deadlock issues which seem to be well documented with earlier 1.4.x releases so have decided to take the plunge and upgrade. I decided to start testing with 1.6.2 but have run into a couple

How can I download the asterisk-addons and setup CDR support for mysql? I reviewed the wiki but did not find instructions on dowloading. Just a sample of the cdr_mysql.conf file. DaL -- David A. Lauer Network Engineer Tristar Communications dalauer@tristarcorp.net 954.977.8081 ext. 21

Hello, I'm working on some dialplan rules to pull multiple users into a conference call. I have some fairly straightforward rules which start up a new MeetMe conference, allow escape with the * key to invite more users, then use a features.conf sequence to bring the new user into the conference with ChannelRedirect. The problem I'm running into is the time in the MeetMe conference

Hello guys, I need to be able to throw cdrs on more than one servers at a time. Please let me know how this can be done. Thanks

Hi list! Running Asterisk 20.0.0 on CentOS 7, logging CDRs using cdr_adaptive_odbc to mariadb-server-5.5.68 (via mariadb-connector-odbc-3.1.7-ga-rhel7) Using chan_sip. I'm facing the problem when there is a sudden spike of calls, some of the calls that are being made during those spikes hang forever basically. This looks like this: [root at voip]# asterisk -rx 'core show channels

Greyman-- I'm taking this discussion to the list. Folks, what we are talking about here, is me trying to get a grasp around Greyman's (Aaron's) request for a bare-bones CDR generation that describes just total connect time for channels, stripping out all the details. Who cares about xfer, park, hold, etc.? So in the following is our discussion about what *should* be there, and in

hi, all asterisk 1.4.24 , zaptel 1.4.10.1 , E1 Manager API Action : Action: Originate Channel: ZAP/G1/8888888 Callerid: 12345678 Context: callout Exten: s Priority: 1 extensions.conf [callout] exten => s,1,Answer() exten => s,n,Wait(10) exten => s,n,Hangup() when the phone 8888888 pick up , it will come to callout context, after hangup, one cdr generate, but the

How is the billsec field calculated in CDRs? I have a situation where billsec is being reported as 0 despite the call being answered and a conversation occurring. An example record follows: '2007-11-06 21:36:50', '6495566778', '6495566778', '0116495566778', '1100012_1', 'Local/0116495566778 at 1100012_1-887b,2',

Hi, I've got a dialplan that transfers all outgoing calls to a Local channel before dialling out via SIP. I did this because sometimes i'm dialling two numbers at the same time and need to know which call is answered for billing purposes. However, I've just noticed that billsec is always equal to 0 even though i know the calls were answered. I now have to take the cdrs from my

Hi I'm using asterisk 1.8.23.1 but I've seen this same issue in previous versions of 1.8. I have created some work arounds but the behaviour is incorrect. This is the scenario: Call comes in and goes to appropriate dialplan In the dialplan the call is forwarded to another number using a Local channel (and using /n ) e.g. Dial(Local/<my-number>@outbound-context/n,60) The number is

Hi, in dialplan -Asterisk 16.2 from Debian Buster- we have  same = n,Dial(PJSIP/101&PJSIP/102&PJSIP/103,15,tT) If thew call is not answered after 20 seconds, we launch a new dial with same and/or other extensions  same = n,Dial(PJSIP/101&PJSIP/104&PJSIP/110,20,tT) Looking in CDR we have at the end of the call (here we called 3 extensions which where ringing, let say 110

Hi, Using FOP, I've met a situation which makes me ask this simple question : Are both A and B commands bellow equivalent ? A. CLI: originate SIP/9122 application dial Local/9123 at local B. AMI/FOP: 192.168.64.5 -> Action: Originate 192.168.64.5 -> Channel: SIP/9122 192.168.64.5 -> Async: True 192.168.64.5 -> Callerid: 9122 Guest2 <9122> 192.168.64.5 -> Exten: 9123

Hi, I'm tryng to place a call through Asterisk Manager Originate Action. Since I want separate CDR for each of the two legs of the call, I'm forking CDR with ForkCDR as the first Channel has picked up. The problem is that, while the first CDR is fine, in the second one the "answer" field is always empty, "billsec" field is 0 and "disposition" field is

Hi, Is there a way to enable the usage of UNIQUEID CDR field using a MySQL database backend for storing CDRs without having to recompile asterisk-addons as stated here http://www.voip-info.org/wiki-Asterisk+cdr+mysql ? After version 1.4 it is said in release that it can be done (not sure if it applies to mysql backend) How would it be the syntax in cdr.conf? I tried this without success in

When using call files I see Dial command when on the CLI however when using the AMI I dont see the originate Dial. Is there a logging level that will show the originate dial on the CLI? If there isnt currently a log state for that shouldnt it do that just like the call files do? My logger.conf has: ; debug => debug console => notice,warning,error,dtmf ;console =>

Hello. I've been trying to use the AMI to originate phone calls. I'm trying to call the SIP phone 'zoiper' with the SIP phone 'yziquel'. So, the AMI interaction is: > Action: originate > Channel: SIP/zoiper > Exten: yziquel > Priority: 1 > Timeout: 30 > Context: internal > > Response: Error > Message: Originate failed > > Event:

Hi, I'm getting an issue while executing AMI Originate. I'm getting "extension does not exists" on Originate's Response, and on the other hand Asterisk CLI say "fwrite() returned error: Broken pipe" Please suggest me what is wrong. Muhammad Faheem ### my originate code block ...

My application fires several calls thru AMI ORIGINATE command. For example if I have 3 operators I do 3 ORIGINATEs. My trouble is when one operator quit for some reason, I should kill the corresponding ORIGINATE. Of course, I could let the call ring and hangup after the customer pick-up. But this is not the case, I do have to kill the corresponding ORIGINATE. I could execute a soft hangup,