search for: gblades

Displaying 5 results from an estimated 5 matches for "gblades".

Did you mean: blades
2014 Aug 18
1
log caller hangup events
All, I would like to log a message whenever a party hangs up a call or session, i.e. no Dial(), user drops off a menu. The message should include the length of the user's session, the session's start time, and called ID. Theoretically, I could set up a channel variable and then ... Any advice would be most welcome! Regards, Paul -------------- next part -------------- An HTML
2014 Feb 20
2
Variables are empty after Redirecting a channel
Guys, I am using Asterisk 1.8.20.0 built by mockbuild @ buildvm-24.phx2.fedoraproject.org on a x86_64 running Linux on 2013-01-18 19:52:25 UTC How can I set variable in one context and then Redirect a channel to another context and use variable there? The code below doesn't work, so I've got empty VAR1 in context_2 [context_1] exten => s,1,SET(__VAR1=VALUE1) exten =>
2014 Oct 30
2
${HASH(SIP_CAUSE,<channel-name>)}
Hello, I read on the wiki : Asterisk 1.8 will allow to read SIP response codes in the dialplan via *${HASH(SIP_CAUSE,<channel-name>)}*. Additionally make sure you're using the destination channel, not the source channel. But when I use this in my dialplan, this 'variable' is empty. Dialplan : exten => h,n,NoOp(sip cause = ${HASH(SIP_CAUSE,${CHANNEL})}) exten =>
2007 Mar 15
0
Re: busy/hangup/answer detection in PRI E1 channels (Vidura Senadeera)
...erisk@linguaphone.co.uk > > Subject: Re: [asterisk-users] busy/hangup/answer detection in PRI E1 > channels > To: Asterisk Users Mailing List - Non-Commercial Discussion > < asterisk-users@lists.digium.com> > Message-ID: > <1173954916.31406.2.camel@gblades-suse.linguaphone-intranet.co.uk> > Content-Type: text/plain > > You can use the hangupcause variable which us the pri cause code > supplied when a call is ended over a PRI line. For example this is the > maco we use to dial a number over PRI. > > [macro-pridial] > exten =...
2013 Aug 22
2
How to get the original SIP result code
B.H. Hello, i'm using AMI Originate action (with async=true) to send outgoing calls to a SIP trunk (using asterisk-java library to connect to AMI). The problem is that in case of failed originate, OriginateResponse event is returning only the reason code which is sometimes not sufficient to determine the real cause of failure. Also, there's no way to link between the channel that was