similar to: Handling a non-responsive peer after it answers

Response below... On Fri, Dec 27, 2019 at 12:02 PM David P <davidswalkabout at gmail.com> wrote: > > > > > I'm looking for a way of detecting in my dialplan when a peer becomes > > non-responsive after answering. [deleted] Is there a way to configure > > a handler for this state? > > > > We use v14.7.6 and we dial the peer this way: > > >

This has been super-helpful, Eric. However, the handleHangupByPeer priorities below are still not run when the peer hangs-up. The last line in the cli when the peer hangs-up is still: Strict RTP learning complete - Locking on source address (Although sometimes there is also: Retransmission timeout reached on transmission) same =>

Thanks, Eric. I just tried a hangup handler, but it's showing a similar problem: When the peer hangs-up, the hangup handler is not invoked and the caller channel remains open. same => n(callPeer),Set(GLOBAL(Peer${IndexIntoPeers}CurrentCallsCount)=$[${PeerCurrentCallsCount} + 1]) same => n,Set(CHANNEL(hangup_handler_push)=handleHangupByCallerOrPeer,doesntMatter,1(args)) same =>

Please point me to samples of popping and wiping hangup handlers. I don't need to use the values returned; I just need to clear any handlers before I push a new one. It's not clear at https://wiki.asterisk.org/wiki/display/AST/Hangup+Handlers+Specification how to provide vars on the right-hand side. Cheers, David -------------- next part -------------- An HTML attachment was scrubbed...

It seems that what ever I set in my answer handler does not show up in the hangup handler. In order to do billing I can't rely on the g option where the caller hangs up the call. Looks like I can either use h or a hangup handler along with the shared function. On Tue, Dec 26, 2017 at 4:40 PM, Eric Wieling <ewieling at nyigc.com> wrote: > Don't use an 'h' extension, use

Hello, I've started to play with PJSIP and got stuck at the following problem. I need to retrieve SIP Call-ID associated with PJSIP channel. For inbound channel I can use ${PJSIP_HEADER(read,Call-ID)}, but that doesn't work for outbound channel even in pre-dial or hangup handler. Whatever I do PJSIP_HEADER seem to be unable to read headers for outbound channel. Here's what I do:

Last question for today, I promise! The problem: In order to disconnect calls after x minutes, I need to do this: [setup] exten => setup,1,Answer() same => n,Set(LIMIT_PLAYAUDIO_CALLER=yes) same => n,Set(LIMIT_WARNING_FILE=/var/lib/asterisk/sounds/en_GB_TNS/time_limit_reached) same => n,Dial(Local/s at root/n,3,L(3540000:60000)) same => n,Hangup() [root] exten

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/26 Richard Mudgett <rmudgett at digium.com> > > On 03/25/2013 05:17 PM, Olivier wrote: > > > Hello, > > > > > > I'm giving hangup-handlers a try on a new Asterisk 11.2.1 setup. > > > My plan is to use this handler to update my CDRs with values such > > > as > > > Asterish and Tech cause (see function HANGUP_CAUSE). >

I think HANGUPCAUSE is channel agnostic. See: core show function HANGUPCAUSE Some thing like this IIRC: Set(my_cause=${HANGUPCAUSE(${CHANNEL(name)},tech)}) Remember the incoming leg of the call and the outgoing leg of the call are different channels. Make sure you are giving HANGUPCAUSE the correct channel. On 06/09/2018 02:01 PM, Khalil Khamlichi wrote: > It seems very weird to me

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

Hello, I have a setup with asterisk 16.8.0, I'm facing a problem where calls that fail (CONGESTION) don't have filled in some extra fields we add to the CDRs in the database. We use cdr_adaptive_odbc with MySQL as backend. To simplify the scenario: [sub-hanguphandler] exten => s,1,Set(CDR(foo)=${bar}) same => n,Return() [default] exten => _X.,1,NoOp(New test call) same =>

hi, I hope someone can help me:-) we’ve got a freepbx server. there are 2 special extensions (2001, 2002). if someone calls this extensions (or a call is forwarded to these extensions) and these extension hangup (not the caller party), then we’d like to put the calls back into a queue (1000) and wouldn’t like to hangup. I read your description about hangup hooks:

Hi, I have a dial plan where I need to notify an external system when a call was answered and when the call hung up. In both requests the start time needs to be the same. My Dialplan looks something like this: [outbound] Exten => _X.,1,Dial(SIP/${EXTEN}@1.1.1.1,,U(call-answer-from-carrier)) Exten => h,1,NoOp(ANSWERED_TIME: ${ANSWEREDTIME} >>> DIAL_TIME: ${DIALEDTIME}

Thanks, Anthony. I added both 'g' and 'F' options. Now, when the caller hangs-up, my cleanup code is run by both the caller channel and the peer channel, but I only want the caller channel to do that. Also, when the peer hangs-up, there is no execution of the priorities following the Dial. Finally, is there a way to reset all globals, maybe as a variant of "dialplan

Hello, Could save.image() be redesigned so that it promptly responds to Ctrl+C? It prevents the command line from being used for a number of hours if the contents of the workspace are large. -------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia

It starts to become a non-responsive from time to time with 100% cpu usage eventhough there is no applications running except a browser. I have been running centos 4 for the past 6 months without any problem with regular update. Now, I have to reboot whenever it shows signs of a non-response. It starts to exhibit this behaviour a cople of days ago. I could not figure it out the reason and need

We have a samba 3.0.22 server which acts as file storage for our mail system (Mercury/32 & Pegasus Mail), serving about 600 users, with a typical load of 150 concurrent users. We have been seeing an increase in stability problems such as: 1. shared win32 executable files become "locked" to the point where the win2k client reports the file is corrupt, or access is denied. Clients

? Sat, 29 Apr 2023 00:00:02 +0000 Dario Strbenac via R-devel <r-devel at r-project.org> ?????: > Could save.image() be redesigned so that it promptly responds to > Ctrl+C? It prevents the command line from being used for a number of > hours if the contents of the workspace are large. This is ultimately caused by serialize() being non-interruptible. A relatively simple way to hang

I have read what I could about SEL_UPDATE and I understand that the block(s) that get called "from" SEL_UPDATE only get called when "there is no more work to do". I took the splitter.rb example that comes with FXRuby. I put in a "puts" in one of the SEL_UPDATE blocks and I get about 4 a second. Not awful ... but ... why is it so slow? In my code which is ... more