On Wed, 26 May 2021, Jonathan H wrote:
AGI Rx << SET AUTOHANGUP 5
AGI Tx >> 200 result=0
AGI Tx >> HANGUP <<
This does raise a question in my mind...
The AGI protocol is: your AGI sends a request (the Rx line) and receives
a response (the Tx line). 1 line out, 1 line in.
If the 'HANGUP'
On Wed, 26 May 2021, Jonathan H wrote:
It just causes AGI to send "HANGUP" and any audio to stop playing. It
does NOT hangup the channel, or even send any SIP event. The line just
goes silent.
I wouldn't expect the AGI() application to send a SIP event. The AGI()
application does not care
I think I can confidently say, after most of a day and reading the following
https://stackoverflow.com/questions/66768885/why-doesnt-asterisk-17-catch-hangup-request-from-pjsip-client-solved
https://wiki.asterisk.org/wiki/display/AST/Asterisk+18+AGICommand_set+autohangup
On Wed, May 26, 2021 at 1:58 PM Jonathan H wrote:
> I have also tried configuring pjsip wizard like this.
>
> endpoint/rtp_timeout=5
>
> And I see this shortly after the "hangup" command has been sent, so
> that part is working:
>
> [May 26 17:36:37] NOTICE[1276]: res_pjsip_sdp_rtp.c:150
>
I have also tried configuring pjsip wizard like this.
endpoint/rtp_timeout=5
And I see this shortly after the "hangup" command has been sent, so
that part is working:
[May 26 17:36:37] NOTICE[1276]: res_pjsip_sdp_rtp.c:150
rtp_check_timeout: Disconnecting channel
https://wiki.asterisk.org/wiki/display/AST/Asterisk+18+AGICommand_set+autohangup
"Cause the channel to automatically hangup at time seconds in the future"
SET AUTOHANGUP TIME
Looks great. Except... it doesn't. It just causes AGI to send "HANGUP"
and any audio to stop playing.
It does NOT hangup
