[asterisk-bugs] [JIRA] (ASTERISK-26293) Asterisk 13 resets ami connection

Joshua Colp (JIRA) noreply at issues.asterisk.org
Mon Aug 15 05:13:57 CDT 2016


    [ https://issues.asterisk.org/jira/browse/ASTERISK-26293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231826#comment-231826 ] 

Joshua Colp commented on ASTERISK-26293:
----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> Asterisk 13 resets ami connection
> ---------------------------------
>
>                 Key: ASTERISK-26293
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26293
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.10.0
>         Environment: Centos 7
>            Reporter: Andrey Ovchinnikov
>            Severity: Critical
>
> Asterisk 13 resets ami connection under load after application sends PingAction via ami. That time asterisk handles 80-130 calls.
> Application log:
> 18:10:28.7359 [3 ManagerReader-20160809180955.579-10] WARN AsterNET - ManagerReader:Run - Ping timeout - send disconnect. 
> 18:10:28.7359 [3 ManagerReader-20160809180955.579-10] WARN AsteriskEventListener - Disconnect occured:{
>   "$type": "AsterNET.Manager.Event.DisconnectEvent, AsterNET",
>   "Reconnect": true,
>   "Timestamp": 0.0,
>   "DateReceived": "2016-08-09T18:10:28.7359084+03:00"
> }.
> net dump:
> 50218	63.856719	10.216.42.35	Asterisk	TCP	119	58888 > 5038 [PSH, ACK] Seq=125 Ack=1305132 Win=131328 Len=61
> 50219	63.856738	Asterisk	10.216.42.35	TCP	58	5038 > 58888 [RST] Seq=1305132 Win=0 Len=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list