I just read more of rfc3261 and it apears openSER is not compliant for doing this, but we should probably still cope..
Charlie Charlie Hedlin wrote: >I have been using the sipXtapi-branch head revision (as of an hour ago >at least) to register against a SER installation. A protocol analyzer >shows SER is not setting an expire in the register response even though >it is returning 200 OK. X-Lite handles this and still reports that it >is registered, but sipXtapi-branch fails to fire the event. It apears >that the code was meant to. > >The problem is in SipRefreshMgr::processOkRepsponse. On line 993. On >LIne 1012 it calls rescheduleAfterTime, which never fires the event. > >Thank you, >Charlie Hedlin >_______________________________________________ >sipxtapi-dev mailing list >[email protected] >List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ > > _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
