Janus demo issues behind a NAT

[Frank Sebastián Franco Hernández]

Hello,

We have found some issues configuring the Janus SIP Gateway Demo with the Janus Server behind a NAT.

We have two scenarios:

1) RTC Client directly connected with a public IP  

2) RTC Client behind a NAT

On 1) we see Janus is trying to check connectivity to the candidates with no luck and then ends the call. On 2) we see Janus validates candidates and receives STUN succesful responses but doesn't select a candidate and stays in a validation loop over and over again. Call is connected, but no audio is heard on both sides. We have set the NAT configuration on janus.jcfg, logs for each scenario are attached in the pastebin links. What can be happening?

https://pastebin.com/LLqBXePC

https://pastebin.com/mN4gbwjK

[Alessandro Amirante]

Use the Admin API to debug issues like this. Also make sure you're using a recent version of libnice.

A.

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/meetecho-janus/f8c5577d-d3b5-4dbd-8ad7-b76295a304d0%40googlegroups.com.

[Alessandro Toppi]

Notice that Janus network configuration is different among the two scenarios.

1)

1.     nat: {
2.         stun_server: stun.voip.eutelia.it
3.         stun_port: 3478
4.         nice_debug: true
5.         full_trickle: true
6.         ice_lite: true
7.         ice_tcp: true
8.         ice_ignore_list: vmnet
9.     }

2)

1.     nat: {
2.         nice_debug: true
3.         full_trickle: true
4.         nat_1_1_mapping: 181.49.5.74
5.         ice_ignore_list: vmnet
6.     }