|
Posted by stephen on May 11, 2005, 9:30 pm
> > So what I'm left with is either finding a way to MAKE this work, or
> > putting a bunch of really expensive equipment up on eBay :( We are
> > looking for a way to override this behavior, either by extending the
> > timeout or forcing the phone to register somehow. By the way, I'm
> > willing to pay for advice that works...
> Talk to your ISPs on each end. Improve the network latency between them.
> If you're expecting to get by on the cheap using the internet then you're
> not going to get it to work reliably. If you're outsourcing overseas then
> you'll have to deal with increased networking costs. Possibly even going
so
> far as dedicated virtual circuits.
it is worth working out what the "inherent" latency is between the
locations - if you are close to that then you need to alter the topology.
if you cant fix it, then you will need a more local call processor - maybe
you can make the local 8300 the default and fall back to the remote
processor?
> It's not the equipment that's at fault here, its the network you're
putting
> it on.
well sort of - but good network gear should not have built in limiting
assumptions about bounded delay. (or at least if it does there should be
something in the documentation).
--
Regards
Stephen Hope - return address needs fewer xxs
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map
> putting a bunch of really expensive equipment up on eBay :( We are
> looking for a way to override this behavior, either by extending the
> timeout or forcing the phone to register somehow. By the way, I'm
> willing to pay for advice that works...