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

[Max Norba (JIRA)]

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

Max Norba edited comment on ASTERISK-26850 at 3/21/17 8:06 AM:
---------------------------------------------------------------

When client use UDP all work correctly. With TCP client I see in HOMER on incoming packets UDP on outgoing TCP. As I see in your patch you add some code to logging_on_tx_msg() in res_hep_pjsip.c but maybe forget add same thing in logging_on_rx_msg()?


was (Author: miralin):
When client use UDP all work correctly. With TCP client I see in HOMER on incoming packets UDP on outgoing TCP. As I see in your patch you add some code to logging_on_tx_msg() in res_hep_pjsip.c but may be forget add same thing in logging_on_rx_msg()?

> 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
>         Attachments: 0001-res_hep-Capture-actual-transport-type-in-use.patch
>
>
> 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)