[asterisk-bugs] [JIRA] (ASTERISK-26850) res_hep_pjsip: Asterisk insert wrong protocol name in "Protocol ID" field in HEP packets

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Mar 9 08:28:10 CST 2017


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

Asterisk Team commented on ASTERISK-26850:
------------------------------------------

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].

> res_hep_pjsip: Asterisk insert wrong protocol name in "Protocol ID" field in HEP packets
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26850
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26850
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_hep_pjsip
>    Affects Versions: 14.3.0
>         Environment: Centos 7, HOMER 5.0.5, PJSIP 2.5.5
>            Reporter: Max Norba
>            Severity: Minor
>
> For clients that connect through TCP transport Asterisk insert in HEP packet  "UDP" in "Protocol ID" field. As we can see in payload in VIA header our client use TCP as transport:
> {noformat}
> HEP3 Protocol
>     HEP ID: HEP3
>     Length (Bytes): 1009
>     Protocol family: IPv4
>     Protocol ID: UDP
>     Source port: 58926
>     Destination port: 5060
>     Timestamp: 1489067611
>     Timestamp us: 879000
>     Protocol Type: SIP
>     Capture ID: 4321
>     Source IP address: 192.168.10.63
>     Destination IP address: 192.168.1.78
>     Authentication Key: foo
>     Correlation ID: NDE2YmJiYTA3M2EwMmZhYzQ5MDQ3ZWQ4ZmUyYmRhOWU.
>     Payload [truncated]: REGISTER sip:192.168.1.78:5060 SIP/2.0\r\nVia: SIP/2.0/TCP 192.168.10.63:61255;branch=z9hG4bK-d8754z-a8057771fb6fc927-1---d8754z-;rport\r\nMax-Forwards: 70\r\nContact: <sip:1 at 192.168.10.63:61255;rinstance=bc512d3059da4
> Session Initiation Protocol (REGISTER)
> {noformat}



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



More information about the asterisk-bugs mailing list