We are facing an issue with the WebRTC snap-in. We could see that the call takes about 40s after initiate to reach the Extension. This is happening only if we configure a Avaya SBC STUN server address and port in the WebRTC Snap in attributes.

There is connectivity between the STUN server address and the PC where the browser is located.

Also in the SBC trace we could observe that it has received a Binding Request from the Browser and has responded with a Binding Success message, but after that there is a 10s gap and the browser repeats the Binding request. This happens 4 times after which the call is connected.


NOTE: We are using the sample application to test, the call is connected immediately if the STUN server attribute is left blank.

Regards,
Vishal

Hello Vishal,
Are you connecting through SBCE from outside the LAN network and how many interfaces do you have on the Browser PC? The ICE negotiation between Browser -> SBCE -> AMS could take time based on number of interfaces you have.

Thanks,
Amit