I think that even 2 seconds isn't that bad. I would say yes to MOH ON by default.
-MM On Tue, Mar 24, 2009 at 3:59 PM, M. Ranganathan <[email protected]> wrote: > This note applies to phones that do the right thing for MOH by > signaling the ITSP with re-INVITE (no SDP) in order to set up MOH : > > Since I now detect race conditions in sipXbridge and delay the start > of MOH by 500 ms, it should, in theory, be possible to turn MOH ON > for both sipXbridge and the phone. However, since the phone does not > have the race detection ( nor does it in fact know of the presence of > sipxBridge ), the delay has to be long enough so that the signaling > from the phone always runs through SipXBridge first. I think 500 ms > may be enough ( the default delay I have right now is 500 ms. ). 1 > second might be better but users may be able to detect the dead > interval. 2 seconds would be better yet but impatient users may hang > up etc. So whats the right delay to ensure maximum user satisfaction > while still allowing max flexibility while still allowing this scheme > to work reliably? > > Second, I dont have a lot of experience with several different types > of phones in this regard. Would it be a safe default to allow MOH on > sipxbridge and MOH on phone to both be ON by default. > > > > -- > M. Ranganathan > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
