On Tue, Mar 30, 2010 at 3:30 PM, JOLY, ROBERT (ROBERT) <[email protected]> wrote: >> As of 18224, SipSubscribeServer.cpp is sending a NOTIFY >> before a new subscription has been accepted. The code that >> used to send the response "ASAP" was moved down below where >> NOTIFY is sent. This causes problems for the Polycom sets, >> which reject the NOTIFY with 500 Internal Server Error, thus >> triggering a bunch of subscription retries which eventually >> do succeed, but much later than would have happened if we had >> just sent things in the correct order. Can I move this >> sending of the response back up to where it was? > > This new behavior also caused problems in the sipXopenfire subcribe client > which ended up requiring a JAIN-SIP stack change.
The NOTIFY can be sent before 202 per the subscribe notify RFC. So the polycomm really has a bug and it should be reported to them. Ranga > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- 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 sipXecs IP PBX -- http://www.sipfoundry.org/
