I agree with Maxim here. You should try to classify traffic to various destinations and configure application timers (possibly in a table) to these destinations.A logging mechanism can help you fine tune these values and find new destinations that have high RTT and hence are timing out.
2009/1/3 Maxim Sobolev <sobo...@sippysoft.com> > Dale Worley wrote: > > On Thu, 2009-01-01 at 13:15 -0800, Maxim Sobolev wrote: > >> It allows you to have different failover timeouts within the same > >> application and select particular one depending on destination. > > > > And interesting idea. My application is a SIP proxy, which will send to > > many destinations, some of which it has never heard of before. What do > > you suggest as an algorithm for choosing retry timeouts? > > There is no magic bullet. You should either rely on pre-configured > timeouts or somehow collect statistics and set based on that. It's > really out of scope of this list. > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: sa...@sippysoft.com > Skype: SippySoft > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > -- Regards Harsha _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
