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

Cisco Meeting Server call drop over WebRTC from LAN

Andrei Fokin
Level 1
Level 1

I have problem with CMS combined single server. All work fine (ad-hoc and scheduled meetings, external webrtc access to spaces and outgoing call to external from webrtc) except for WebRTC calls then I connect from LAN.  Login is succesfully but when I push Join to Space then Chrome freeze up in "Connecting" and some time later i see Login screen.

 

External and internal domain name is the same. I tryed to connect over WebRTC from same network with CMS but problem but no success - same problem.

 

how to solve this problem?

 

Extended (Webbridge) logs from CMS:

2018-02-21 14:41:06.374 Info new session created for user "bt_fokin@example.com"
2018-02-21 14:41:11.570 Info call 41: allocated for bt_fokin@example.com "Web client" conference participation
2018-02-21 14:41:11.570 Info call 41: setting up combined RTP session for DTLS (combined media and control)
2018-02-21 14:41:11.742 Info participant "bt_fokin@example.com" joined space 0f983276-4653-4de5-898e-f208e1ba049a (Андрей Фокин Space)
2018-02-21 14:41:22.016 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:22.016 Info calls lacking reports; 1 / 1
2018-02-21 14:41:22.016 Info resolved / unresolved object IDs = 14695 / 5 (last unresolved 00080008)
2018-02-21 14:41:22.016 Info num act_on_changes() = 5899 (for objects with / without owner = 5897 / 0
2018-02-21 14:41:22.016 Info num profile / decoder / encoder reports seen = 7442 / 2623 / 1777
2018-02-21 14:41:23.017 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:23.017 Info calls lacking reports; 1 / 1
2018-02-21 14:41:24.017 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:24.017 Info calls lacking reports; 1 / 1
2018-02-21 14:41:25.017 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:25.017 Info calls lacking reports; 1 / 1
2018-02-21 14:41:26.017 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:26.017 Info calls lacking reports; 1 / 1
2018-02-21 14:41:27.018 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:27.018 Info calls lacking reports; 1 / 1
2018-02-21 14:41:27.018 Info resolved / unresolved object IDs = 14710 / 5 (last unresolved 00080008)
2018-02-21 14:41:27.018 Info num act_on_changes() = 5902 (for objects with / without owner = 5900 / 0
2018-02-21 14:41:27.018 Info num profile / decoder / encoder reports seen = 7448 / 2626 / 1777
2018-02-21 14:41:28.018 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:28.018 Info calls lacking reports; 1 / 1
2018-02-21 14:41:29.018 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:29.018 Info calls lacking reports; 1 / 1
2018-02-21 14:41:30.019 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:30.019 Info calls lacking reports; 1 / 1
2018-02-21 14:41:31.019 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:31.019 Info calls lacking reports; 1 / 1
2018-02-21 14:41:32.019 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:32.019 Info calls lacking reports; 1 / 1
2018-02-21 14:41:32.019 Info resolved / unresolved object IDs = 14726 / 5 (last unresolved 00080008)
2018-02-21 14:41:32.019 Info num act_on_changes() = 5906 (for objects with / without owner = 5904 / 0
2018-02-21 14:41:32.019 Info num profile / decoder / encoder reports seen = 7454 / 2630 / 1777
2018-02-21 14:41:33.019 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:33.019 Info calls lacking reports; 1 / 1
2018-02-21 14:41:34.020 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:34.020 Info calls lacking reports; 1 / 1
2018-02-21 14:41:35.020 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:35.020 Info calls lacking reports; 1 / 1
2018-02-21 14:41:36.020 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:36.020 Info calls lacking reports; 1 / 1
2018-02-21 14:41:37.020 Info call 41: lack of expected reports for received audio
2018-02-21 14:41:37.020 Info calls lacking reports; 1 / 1
2018-02-21 14:41:37.021 Info resolved / unresolved object IDs = 14740 / 5 (last unresolved 00080008)
2018-02-21 14:41:37.021 Info num act_on_changes() = 5909 (for objects with / without owner = 5907 / 0
2018-02-21 14:41:37.021 Info num profile / decoder / encoder reports seen = 7459 / 2633 / 1777
2018-02-21 14:41:37.021 Info call 41: inactivity notification; tearing down...
2018-02-21 14:41:37.021 Info resource 0:0 for "bt_fokin@example.com"; deactivating due to call drop
2018-02-21 14:41:37.021 Info resource 0:0 for "bt_fokin@example.com"; sending stream failure indication, size 98
2018-02-21 14:41:37.172 Info user "bt_fokin@example.com", ephemeral invitation no longer valid due to inactivity call drop
2018-02-21 14:41:37.172 Info participant "bt_fokin@example.com" left space 0f983276-4653-4de5-898e-f208e1ba049a (Андрей Фокин Space)
2018-02-21 14:41:52.274 Info Web bridge connections tracing now disabled

1 Accepted Solution

Accepted Solutions

Source of problem is Checkpoint firewall between users an CMS subnet. Problem is solved.

View solution in original post

5 Replies 5

Hello,
I think you use CMS TURN, not Expressway TURN.
Check web, api and cli parameters for your TURN.

Hi Oleksandr

 

I use Expressway TURN (not CMS Turn) and connections over WebRTC is succesfully. I can call to space or to other participants. Problem is only when I connect to CMS WebRTC from LAN.

Source of problem is Checkpoint firewall between users an CMS subnet. Problem is solved.

Hi Andrei,

 

I have a similar problem.

You say that the problem is the CheckPoint firewall.

Can you explain what was exactly the problem and how you resolve it?

Thanks

 

Michel

Hi Michel

 

I needed to check that CMS is set correctly. I didn't solve a problem with connectivity between problem client and CMS subnets. I only change IPv4 settings of client  to same with CMS server subnet and after with I succesfully connected WebRTC client and established call.