01-20-2018 04:23 PM - edited 03-17-2019 12:00 PM
Hi All,
I have configure Cisco meeting server with single split deployement, I have 1 core meeting server (call bridge,xmpp) and 1 edge meeting server (turn, we bridge, loadbalancer, sipedge).
Edge server use single IP local and Nated with the firewall. I can use webrtc from external but I can not use Cisco meeting server from external, the Cisco meeting server is only able to use for signing user, but cannot use the video.
If I check the Call Logs for Cisco meeting application session on webadmin, the log is always no audio (as attach)
Is Cisco Meeting Application is blocked by the firewall ? Is there any experience how to allow stun protocol on F5 and Cisco ASA firewall ?
Many thanks for you're help.
Solved! Go to Solution.
04-03-2018 11:48 PM
Its solved.. Reason firewall issue..
We need to open TCP and UDP as requires on the guidance document..
Many thanks for your support all
01-22-2018 02:10 AM
for external CMA users connectivity issue. do the following
1. check External DNS SRV record for _xmpp-client
2. check if loadbalancer trunk is active. xmpp trunk certificate and loadbalancer must trust each other.
3. for calls check your sipedge config.
HTH
AMMAR
please rate & mark answered if helpful.
01-22-2018 10:29 PM
I got UDP 3478 (stun) filtered from public facing. Is UDP 3478 default service for turn or I have manually configure UDP 3478 on turn server? Sorry for my fool question..
01-23-2018 06:07 AM
no UDP 3478 is default TURN port. and CMS listens on it. you do not need to configure it.
make sure 1st interface in TURN should be the NATTED interface. usually turn config involves 2 interfaces.. one facing internet (NAT) other facing towards callbridge. and you declare your internet interface as default in CMS Edge.
HTH
AMMAR
rate and mark answered if helpful.
01-24-2018 05:59 PM
Hi Ammar,
I only using 1 interface for the turn server which NATTED by the firewall. Should I use different interface for facing the internet and callbridge?
04-03-2018 11:47 PM
04-03-2018 11:48 PM
Its solved.. Reason firewall issue..
We need to open TCP and UDP as requires on the guidance document..
Many thanks for your support all
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide