[asterisk-bugs] [JIRA] (ASTERISK-27434) [patch] chan_sip/ICE: Square brackets around IPv6 addresses.

[Alexander Traud (JIRA)]

Alexander Traud created ASTERISK-27434:
------------------------------------------

             Summary: [patch] chan_sip/ICE: Square brackets around IPv6 addresses.
                 Key: ASTERISK-27434
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27434
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Channels/chan_sip/IPv6
    Affects Versions: 15.1.2, 13.18.2
            Reporter: Alexander Traud


Very similar to ASTERISK-26256, IPv6 addresses in the ICE candidates should not be represented with square brackets around them.

*Steps to reproduce*
# channel driver _chan_sip_
# configuration file _sip.conf_ enabled for IPv6: {{bindaddr=::}}
# configuration file _sip.conf_ enabled for ICE: {{icesupport=yes}}
# call an extension on this Asterisk server, trace with Wireshark

*Expected results*
The answer to the SIP-INVITE contains an SDP media session with ICE candidates, like:
{{a=candidate:1 1 UDP 2130706431 2001:470:e0d4::ee 8998 typ host}}

*Actual results*
The answer to the SIP-INVITE contains an SDP media session with ICE candidates, like:
{{a=candidate:1 1 UDP 2130706431 \[2001:470:e0d4::ee\] 8998 typ host}}

*Notes*
The IP address and the port are separated through a space and not through a colon. Therefore, no brackets are required. Although every implementation should cope with that (see [RFC 5952|http://tools.ietf.org/html/rfc5952#section-6]), according to [RFC 5245 section 15.1|http://tools.ietf.org/html/rfc5245#section-15.1], no brackets are defined at that place:
{code}
connection-address = multicast-address / unicast-address
   unicast-address = IP4-address / IP6-address / FQDN / extn-addr
       IP6-address = hexpart [ ":" IP4-address ]
           hexpart = hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ]
            hexseq = hex4 *( ":" hex4)
              hex4 = 1*4HEXDIG
{code}



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