[asterisk-bugs] [JIRA] (ASTERISK-24209) Webrtc ICE negotiation - RTCP port is even number

[Vikas Agarwal (JIRA)]

Vikas Agarwal created ASTERISK-24209:
----------------------------------------

             Summary: Webrtc ICE negotiation - RTCP port is even number
                 Key: ASTERISK-24209
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24209
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
    Affects Versions: 11.11.0
         Environment: Asterisk 11 on centos, chrome 36
            Reporter: Vikas Agarwal


As per definition of RTCP, RTCP port should be a odd number and should be +1 to TCP port. In my set-up, following is the candidates sent by asterisk to chrome-
a=candidate:Ha0000fa 1 UDP 2130706431 10.0.0.250 18012 typ host
a=candidate:Sd0b1264a 1 UDP 1694498815 208.177.38.74 18012 typ srflx
a=candidate:Ha0000fa 2 UDP 2130706430 10.0.0.250 18013 typ host
a=candidate:Sd0b1264a 2 UDP 1694498814 208.177.38.74 18014 typ srflx


If IP 10.0.0.250 is reachable to chrome then call works. But when chrome can reach IP 208.177.38.74 then ICE negotiation never completes. This is because ports for TCP and RTCP both are even numbers. 

I tried to a complied version of asterisk after making some custom changes so that RTCP always gets +1 port number (a odd number). This time ICE negotiation completed as expected.



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