> > http://track.sipfoundry.org/browse/XECS-1594 > > Hi, > > I am looking into using in-dialog OPTIONs to implement a > keep-alive mechanism for the MOH and park server. > > >From the RFC: > > 11.2 Processing of OPTIONS Request > > An OPTIONS request received within a dialog generates a 200 (OK) > response that is identical to one constructed outside a dialog and > does not have any impact on the dialog. > > This use of OPTIONS has limitations due to the differences in proxy > handling of OPTIONS and INVITE requests. While a forked INVITE can > result in multiple 200 (OK) responses being returned, a forked > OPTIONS will only result in a single 200 (OK) response, since it is > treated by proxies using the non-INVITE handling. See Section 16.7 > for the normative details. > > > I don't think this limitation affects us.. While using > re-INVITEs would be ideal for keep-alives, most phones don't > don't seem to support handling re-INVITEs from the MOH > server. Does anyone have opinion against this method? >
As a point of reference, the NAT Traversal feature also relies on sending OPTIONS to keep NAT bindings alive and that is not causing any trouble with the phones that I tested with: LG, Polycom and Counterpath. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
