Timeout Problems

Timeout Problems

NewsGroups | Search | Tools
 comp.dcom.videoconf  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Timeout Problems mo 04-09-2005
Posted by mo on April 9, 2005, 7:18 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


I know enough about our equipment (an Accord MGC-100 bridge and several
Polycom units) to be dangerous. Outside our in-house network, our
endpoints seem to have no problem with this, but we cannot keep
connected to a conference for more than 1 hour, 59 minutes, 59 seconds.
I'm thinking it's a firewall issue, but what do I know? I've found
nothing in the MGC Manager, PathNavigator, or the individual in-house
Polycoms (VSX7000, an older v.35, and a FX) setups to indicate
otherwise. The bridge doesn't disconnect anyone, the endpoints are
still connected, it's just our in-house equipment disconnects. Has
anyone else experienced this? I need to be able to discuss this
intelligently with our IS folks, who manage the firewall.



Pure Networks
Posted by Alpha@Beta.com on April 10, 2005, 11:16 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


You don't have the "Max Time In Call" set too low do you?


>I know enough about our equipment (an Accord MGC-100 bridge and several
>Polycom units) to be dangerous. Outside our in-house network, our
>endpoints seem to have no problem with this, but we cannot keep
>connected to a conference for more than 1 hour, 59 minutes, 59 seconds.
>I'm thinking it's a firewall issue, but what do I know? I've found
>nothing in the MGC Manager, PathNavigator, or the individual in-house
>Polycoms (VSX7000, an older v.35, and a FX) setups to indicate
>otherwise. The bridge doesn't disconnect anyone, the endpoints are
>still connected, it's just our in-house equipment disconnects. Has
>anyone else experienced this? I need to be able to discuss this
>intelligently with our IS folks, who manage the firewall.



Posted by mo on April 11, 2005, 7:10 am
If you were  Registered and logged in, you could reply and use other advanced thread options


It's set for 480 minutes, which is the max "max time in call" I
believe. That was one of the first things I checked.



Posted by marc cooper on April 11, 2005, 6:46 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


mo wrote:
> It's set for 480 minutes, which is the max "max time in call" I
> believe. That was one of the first things I checked.
>
Just for kicks, set the max time in call to 0 (I believe that is how you
deactivate the feature) and see if you still experience the disconnect
problems.


Posted by mo on May 5, 2005, 7:29 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


A kind soul emailed a link, which discussed a timeout value on H225, in
the PIX. I sent this information to our firewall commander, who checked
it out. The solution was indeed a timeout value, but not on H225. It
was aTCP timeout, which he set for 10 hours.

I hope this information helps someone else who might be experiencing
this.



Similar ThreadsPosted
D-link i2Eye between two Cisco Pix 501's -- premature timeout January 8, 2006, 6:48 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map