WebRTC Wowza Server Ice Candidates

[Samson_Radu]

I have set up WebRTC with my dev Wowza server but the connection doesn’t go through.

When publishing the browser receives only one ICE candidate from the server, probably not enough. I’m not sure if I configured the properties properly.

in the browser I can see one ice candidate coming in from the server:

candidate:0 1 UDP 50 [PUBLIC_IP] 6972 typ host generation 0

Does the server need a STUN/TURN config? Can’t find docs related to this.

How should I configure the Ice candidates? Do I need to fill a UDPBindAddress value?

<Property>
    <!-- comma separated list of IP addresses and the transport information. For multiple IP's use a pipe character to separate the lists -->

    <Name>webrtcIceCandidateIpAddresses</Name>
    <Value>[PUBLIC_IP],udp</Value>
    <Type>String</Type>
</Property>
<Property>
    <Name>webrtcUDPBindAddress</Name>
    <Value></Value>
    <Type>String</Type>
</Property>

Here’s the networks of the server. There is no local network/IP that I should add to the application config.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:b5:15:56 brd ff:ff:ff:ff:ff:ff
    inet [PUBLIC_IP]/24 brd [IP_MASK].255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 [IP_V6]/64 scope link 
       valid_lft forever preferred_lft forever
 

[Alex_C]

Hello,

Go ahead and try adding 0.0.0.0 to the of the webrtcUDPBindAddress property.

The readme for WebRTC has this section describing this property.

webrtcUDPBindAddress: Local IP address of the network card you want to use for WebRTC UDP traffic. (This value is not used if streaming WebRTC over TCP.) For UDP delivery in general, it’s OK to leave this property blank. The property is only needed if the machine has multiple network interfaces. For some network situations, like running on a cloud instance, a value of 0.0.0.0 would be best instead of the local IP address of the network card to prevent connection problems.

Hope this helps,

Alex

[Samson_Radu]

Wow that was an easy one! Thanks a lot!