> On Thu, Apr 8, 2010 at 3:37 PM, Lazy Burd <[email protected]> wrote: > > > On Thu, Apr 8, 2010 at 12:30 PM, JOLY, ROBERT (ROBERT) > <[email protected]> wrote: > > > I just committed something. Could you please > try again with revision 18532 or better? Thanks > > > i don't see any errors, i think that fixed it! thank you! > > > > I'm back. The original exception went away, but now i get a > new one (at least i think it's new) when a NOTIFY message comes in > > http://pastie.org/913687.txt > > There's a warning about a null transaction in the sip request > object and i'm hoping you can tell by looking at the notify > message in the link above if sip message should trigger this error. >
Hi, this is one of those 'normal errors'. When sipXopenfire starts it establishes a subscription with sipXrls. If sipXopenfire gets restarted, it forgets about any old subscription and is going to establish a brand new one with sipXrls however sipXrls will continue to track the old subscription until is expires. The exception you are seeing is caused by sipXrls sending a NOTIFY for the old subscription dialog that the new instance of sipXopenfire knows nothing about. Although the exception that you have noted has no user-noticeable effect, I should really go in and clean up that code... Adding it to my to-do list. _______________________________________________ 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/
