02-20-2012 08:23 AM - edited 02-20-2012 08:25 AM
I have a CMA 4000 , version 5.5.0.
When i make point to point or multipoint visioconférence (RMX1500), after 2 hours of communication that's automatically finish.
The problem is not from my visio (8h duration call)
I don't think the problem is from my CMA because if I use CMAD with CMAD on point to point that's working fine, but if I use a videoconference system VSX/HDX my call is finish after 2 hours.
If my systems are not recorded to my CMA 4000, there is no problem.
So i think the problem if on the network my the network team don't find anything.
They say there is no timing on the firewall.
Here the screen with Wireshark when we loose the communication.
Have you an idea about test to make?
Thanks for your help.
02-21-2012 01:55 AM
Most common 2 hours disconnect issue cause "TCP Keep-Alive".
End Points send TCP Keep-Alive packet every 2 hours, but it is discarded by firewall.
Please check and change the value of TCP Keep-Alive Timer on Firewall.
Change the value of TCP Keep-Alive Timer more than 2 hours.
HDX Release 3.0.1 or later, TCP Keep-Alive packet send every 30 min.
VSX 188.8.131.52 or later, TCP Keep-Alive packet send every 15 min.
You can change the value of TCP Keep-Alive Timer on HDX and VSX above software release.
How to change the value:
You should connect to HDX or VSX by telnet.
tcp kaInterval value
tcp kaInterval 1800
A keep-alive packet will be sent per 1800 seconds (30 minutes).
Hope it help
02-21-2012 05:29 AM
Thank you for the answer.
Our FW don't "working" (not monitored) TCP keepalive , the global TCP time out is 8 hours.
The call is all time cut at 2H (VSX and HDX).
02-23-2012 10:13 PM
Sorry I wrote mistake below my previous comments:
- VSX 184.108.40.206 or later, TCP Keep-Alive packet send every 15 min.
- VSX 220.127.116.11 or later, TCP Keep-Alive packet send every 120 min. (7200 sec.)
*I confirmed it on VSX6000.
02-24-2012 01:05 AM
Is there possibility with telnet to change the timing of TCP Keepalive ?
If yes what is the command plz?
My network team say we have no TCP keepalive on the FW, if i can change the time ( + or -) and that's change the timing of the cut ......
03-16-2012 02:14 AM
I have the same kind of issue here. Increse the Keep Alive settings on each HDX end point is from my point of view only a work around and not the real solution. Besides the maximum value accepted is 9000 seconds. In next week i'll do a test connecting with a cross cable (or only with an hub) two HDX to check what happens. If Polycoms says that's a problem on internal firewall settings (and i don't think so..) i expect that the connection will not be cut off after the "keep alive".
The time is always: Keep Alive time setting + ~10 min:
Keep Alive set to 300 seconds => Call was 0:16:13
Keep Alive set to 600 seconds => Call was 0:21:13
Keep Alive set to 1800 seconds (as defualt) => Call was 0:41:13
I'll update you on my test.
03-16-2012 02:25 AM
The problem is probably from the Firewall.
There's some month all connection with my RMX 15000 was cutting after 10mn, and that was the firewall that was reject something.
Actually, for my problem, my network team working to find a solution with the firewall, because when i use system on the same switch than my CMA/Bridge that is working fine.
04-02-2012 09:37 AM
If you change this setting to 0 then the codec wont disconnect on its own
2 Hour disconnects are almost always a firewall issue. We use Cisco products on the firewall the setting is this like this increase the timeout and that should fixes the problem
timeout h323 0:09:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
The other 2 hour disconnect problem we encoutered was also firewall related one of the firmwares release last year for ASA's caused the 2 hour disconnect even though the setting was correct they released a new firmware to fix this