[asterisk-bugs] [JIRA] (ASTERISK-24404) When controlling inbound calls via AMI + async AGI, sometimes asterisk itself issues an EXEC Congestion command
Gabriel Gayan (JIRA)
noreply at issues.asterisk.org
Thu Oct 9 12:37:30 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222948#comment-222948 ]
Gabriel Gayan commented on ASTERISK-24404:
------------------------------------------
It was indeed what Ben mentioned. Closing the issue.
> When controlling inbound calls via AMI + async AGI, sometimes asterisk itself issues an EXEC Congestion command
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-24404
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24404
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_agi
> Affects Versions: 11.13.0
> Environment: - Ubuntu 14.04.1 x86_64 on VMware Fusion 7
> - Adhearsion 2.5.4
> Reporter: Gabriel Gayan
>
> From what I understand, when controlling a call via async AGI and AMI, the client application is the one that issues the commands and waits for a response.
> I am seeing in some inbound calls that Asterisk itself is issuing an "Exec Congestion", not being requested by the client application.
> Since the client app has not issued the command, it is not expecting such responses and it assumes that the call is running without any problem, so it keeps issuing agi commands without receiving any response, thus waiting indefinitely until asterisk hangs up the call (in my case because of RTP inactivity timeouts).
> I extracted several logs for one of these calls:
> https://gist.github.com/ggayan/256204da1efce6a66ecc
> The default dialplan context is adhearsion and it is defined like this:
> [adhearsion]
> exten => _.,1,AGI(agi:async)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list