cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
997
Views
0
Helpful
5
Replies

Cisco Meeting Server, A call from WebRTC(internet) fail


I have a new installation site which deploy the single split solution

 

The problem is that the client from internet(outside firewall) call to the space, the call connected but no video and audio, then a few second later call is disconnected itself, this problem happened with both webRTC and CMA.

 

Hence, the call from inside clients has no problem

Please help me solve the problem

5 Replies 5

Jaime Valencia
Cisco Employee
Cisco Employee

What versions are  being used??

What troubleshooting has been done??

HTH

java

if this helps, please rate

Hi Jaime

At the web client diagnostics, I think Turn server has been chosen correctly, 27.254.182.149 is the public IP of Turn server

TURN configuration debug
Ever signalled by core: yes
Valid: yes
Num TURN servers: 1
00. GUID: b77299e7-1441-4140-8427-ce4789edf91d
address: 27.254.182.149
server address: 10.104.5.176
port: 3478
Chosen: no
Chooser 7F25E80969A0
last processed 5496ms ago
bestLastSignalled 00000000-0000-0000-0000-000000000000
never signalled chosen
Turn chooser debug
Num DNS states:1
00. b77299e7-1441-4140-8427-ce4789edf91d
turn : 1
ms-edge : 0
acano : 1
hostname : 27.254.182.149
port : 3478
Num TURN servers monitored:1
00. 27.254.182.149:3478
reachable: 0
STUN response : never received
Chooser 7F25E8097120
last processed 5495ms ago
bestLastSignalled 00000000-0000-0000-0000-000000000000
never signalled chosen
Turn chooser debug
Num DNS states:1
00. b77299e7-1441-4140-8427-ce4789edf91d
turn : 1
ms-edge : 0
acano : 1
hostname : 10.104.5.176
port : 3478
Num TURN servers monitored:1
00. 10.104.5.176:3478
reachable: 0
STUN response : never received

I also capture traffic at the web client and compare the log with the working one(in my lab). I saw the difference in STUN protocol, something seem to be missing on the non-working one.

Is it works now? if so, can you share how to fix it?

Finally i found it, that was the firewall issue.

The RTP flow in my deployment is strange

And how many CMS did you use? core and edge or only one?