FWIW, I added the following after the Dial, and it doesn't appear in cli
after peer hangup:
same => n,NoOp(After Dial ${AddressToReachPeer})
I also tried putting 'g' before the 'b'.
I also tried removing the context headers of the hangup handlers and
predial handler, and just referring to those
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
Don't use the _. pattern. Ever.
The call has two channels so it needs two hangup handlers, something
like this, though I've not tested it.
[some_context]
exten => _X.,1,Noop
same => n,Set(CHANNEL(hangup_handler_push)=my_caller_hangup_handler)
same => n,Dial(SIP/number@peer,b(pre_dial^s^1))
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 =>
Check the footer at the bottom of this message for instructions on how
to unsubscribe :-)
Matthew Fredrickson
On Fri, Jun 1, 2018 at 12:11 PM, David Mutterer wrote:
>
> --
> _
> -- Bandwidth and Colocation Provided by
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
The Asterisk Development Team would like to announce the release of Certified
Asterisk 13.21-cert1.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/certified-asterisk
The release of Certified Asterisk 13.21-cert1 resolves several issues reported
On Tue, Jun 5, 2018 at 10:59 AM Olivier wrote:
>
>
> 2018-06-05 15:27 GMT+02:00 George Joseph :
> Thank you very much, George for replying.
>
>>
>>
>> On Tue, Jun 5, 2018 at 3:35 AM Olivier wrote:
>>
>>> Hi,
>>>
>>> After a long discussion with a friend, I would like to ask here:
>>>
>>>
2018-06-05 15:27 GMT+02:00 George Joseph :
Thank you very much, George for replying.
>
>
> On Tue, Jun 5, 2018 at 3:35 AM Olivier wrote:
>
>> Hi,
>>
>> After a long discussion with a friend, I would like to ask here:
>>
>> 1.According SIP RFCs, is possible/recommended to have different values
Use hangup handlers, they work around the issues with the 'h' extension.
On 06/05/2018 05:33 AM, David P wrote:
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
On Tue, Jun 5, 2018 at 3:35 AM Olivier wrote:
> Hi,
>
> After a long discussion with a friend, I would like to ask here:
>
> 1.According SIP RFCs, is possible/recommended to have different values in
> From and P-Asserted-Id fields ?
> For instance, From field showing 123456789 and P-Asserted-Id
On Tue, Jun 05, 2018 at 11:34:51AM +0200, Olivier wrote:
> 1.According SIP RFCs, is possible/recommended to have different values in
> From and P-Asserted-Id fields ?
> For instance, From field showing 123456789 and P-Asserted-Id showing
> 987654321 (beside privacy considerations) ?
Yes, most
Hi,
After a long discussion with a friend, I would like to ask here:
1.According SIP RFCs, is possible/recommended to have different values in
>From and P-Asserted-Id fields ?
For instance, From field showing 123456789 and P-Asserted-Id showing
987654321 (beside privacy considerations) ?
2.
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.
On Tuesday 05 June 2018 at 08:33:26, David P wrote:
> We're using Asterisk 14.7.6 and I have a dialplan that ends like this:
>
> same => n,Dial(SIP/${EXTEN:0:4}@peer1)
> same => n,Set(GLOBAL(EpochAtCallEnd)=${EPOCH})
> same => n,Hangup()
>
> When peer1 hangsup, the priorities after the Dial
We're using Asterisk 14.7.6 and I have a dialplan that ends like this:
same => n,Dial(SIP/${EXTEN:0:4}@peer1)
same => n,Set(GLOBAL(EpochAtCallEnd)=${EPOCH})
same => n,Hangup()
When peer1 hangsup, the priorities after the Dial are executed fine. But
when the caller hangsup during the Dial, the
16 matches
Mail list logo
