Not that sure: if the error is related to absence of content, the error
message shouldn't be "481 call/transaction doesn't exist", but something else (e.g.: 406, 488, ...). This seems to be more related to a SIP dialog issue.
IMMO, absence of body is allowed within the event notification framework
in certain circumstances.
IMMO, I tend to align with a previous post pointing to the absence
of Contact header (?).
Hope this helps,
David
-------- Original Message --------
Subject: Re: [Sip-implementors] Notification fails - why?
From: Zarko Coklin <[EMAIL PROTECTED]>
Date: Wed, April 25, 2007 11:36 am
To: [EMAIL PROTECTED]
Cc: [email protected]I agree with Dale! Your NOTIFY is not valid for 2 reasons: 1. Content-Length is set to 0 2. In its SUBSCRIBE, XLite offered what are acceptable message bodies: "Accept: multipart/related, application/rlmi+xml, application/pidf+xml". Your NOTIFY should have had some offered Content-Type and provided valid content in a message body. None of this happened. Regards, Zarko Coklin >I see that the NOTIFY has a zero-length body. I'm no expert, but >that's probably no a valid body for the "presence" event package. >Perhaps X-Lite is giving the wrong error response for this error >condition? Dale __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
