On Tue, 2008-09-09 at 11:46 -0400, Hesham Abdelrahman wrote: > The problem when the Default Serial Fork Expiration timer expires "now > at 20 seconds" the call fails so we need to set the Default Serial > Fork Expiration timer to a long period, like 40 seconds, when that > happen the normal operation of voice mail on no answer, etc. would be > impacted and voice mail will not kick in till 40 seconds when the > Serial Fork Expiration timer expires and that is a long time. > > So we are looking for a work around that would allow nested hunt group > to work with out having the Default Serial Fork Expiration timer to > impact this operation.
What is probably needed is a reassessment of how the forking timeouts are handled. Each stage of forking has its own timers. In this case, we want the fallback forks to each have a long timeout within their own proxy transaction, so that all time-outs are effectively delegated to the child transactions (after looping back to the proxy). This probably requires code changes in the proxy (to seperate the timer kept in the proxy from the Expires value passed to the outgoing message) and changes in sipXconfig to allow these timers to be configured. That could be messy. Could you file an improvement request? Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
