[asterisk-bugs] [JIRA] (ASTERISK-25817) SIP keep alive messages contain trailing null byte
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Fri Feb 26 12:30:56 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229733#comment-229733 ]
Asterisk Team commented on ASTERISK-25817:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> SIP keep alive messages contain trailing null byte
> --------------------------------------------------
>
> Key: ASTERISK-25817
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25817
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_keepalive
> Affects Versions: 13.7.2
> Environment: Fedora 20
> Reporter: hypherion
> Severity: Minor
> Attachments: keepalive_packet.png
>
>
> When configured with the 'keepalive' option (keepalive = 30 in sip.conf), Asterisk sends periodic keep alive packets to peers. These packets as sent with content '\r\n\0' instead of 'r\n\r\n' as indicated by RFC5626 section 4.4.1.
> This has the potential to confuse clients and not be interpreted as 'ping' packets.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list