ipv6 and ipv4

[bharath]

Does flashphoner listen on both IPv6 and Ipv4 simultaneously.

 

[Max]

Yes, IPv6 support is added since build 5.2.660. By default, it is is disabled. Please see here about the required configuration.

 

[bharath]

Yes, IPv6 support is added since build 5.2.660. By default, it is is disabled. Please see here about the required configuration.

We have modified the settings,but after these settings,application listens only on ipv6 and not accepting ipv4.

 

[Max]

If possible, please provide us SSH access to your server using this link.

 

[Max]

Good day.
We checked your server settings.
First, you must update WCS to 5.2.660 or later. In 5.2.259 that you're using now, tcp6 ports can be listened, but IPv6 WebRTC candidates are not supported yet:

cd /usr/local/FlashphonerWebCallServer
./webcallserver stop
./webcallserver update

After update, you should add external IPv6 address to flashphoner.properties

ip_v6=server_ipv6_external_address

Then, WebRTC over IPv6 should work.

 

[bharath]

Hi

We have updated the flashphoner as per your instructions, but flashphoner is listening only on IPv6 address only,it is not listening on IPv4 address.
Please resolve the issue.

 

[Max]

Please correct the parameter ip_v6 from

ip_v6=server_ipv6_external_address=2400:xxxx:xxx:xx::xxx:7001

to

ip_v6=2400:xxxx:xxx:xx::xxx:7001

restart WCS and check if stream can be published
The example of this parameter is shown in documentation

 

[bharath]

Hi

Application is listening only for IPv6 connections,the application is not listening for IPv4 connections.Following is the output of netstat

# netstat -tpln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 28826/rpcbind
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 20948/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 21066/master
tcp 0 0 127.0.0.1:8125 0.0.0.0:* LISTEN 14981/netdata
tcp 0 0 0.0.0.0:19999 0.0.0.0:* LISTEN 14981/netdata
tcp6 0 0 :::554 :::* LISTEN 14738/java
tcp6 0 0 :::1098 :::* LISTEN 14738/java
tcp6 0 0 :::843 :::* LISTEN 14738/java
tcp6 0 0 :::1935 :::* LISTEN 14738/java
tcp6 0 0 :::111 :::* LISTEN 28826/rpcbind
tcp6 0 0 :::8080 :::* LISTEN 14738/java
tcp6 0 0 XXXXXXXXXX:30000 :::* LISTEN 14738/java
tcp6 0 0 :::2001 :::* LISTEN 14738/java
tcp6 0 0 :::8081 :::* LISTEN 14738/java
tcp6 0 0 :::2002 :::* LISTEN 14738/java
tcp6 0 0 :::8082 :::* LISTEN 14738/java
tcp6 0 0 XXXXXXXXX:3478 :::* LISTEN 14738/java
tcp6 0 0 :::22 :::* LISTEN 20948/sshd
tcp6 0 0 :::50999 :::* LISTEN 14738/java
tcp6 0 0 :::8888 :::* LISTEN 14738/java
tcp6 0 0 ::1:25 :::* LISTEN 21066/master
tcp6 0 0 :::8443 :::* LISTEN 14738/java
tcp6 0 0 :::8444 :::* LISTEN 14738/java
tcp6 0 0 :::8445 :::* LISTEN 14738/java
tcp6 0 0 ::1:8125 :::* LISTEN 14981/netdata
tcp6 0 0 :::19999 :::* LISTEN 14981/netdata
tcp6 0 0 :::9091 :::* LISTEN 14738/java
tcp6 0 0 :::34915 :::* LISTEN 14738/java

 

[Max]

Please check WebRTC publishing/playback, it seems working right now

When IPv6 is enabled, netstat can show pots listened as tcp6 however in fact they are IPv4 (we've published IPv4 for test)
Please check stream publishing from your client side.