Hi All,
The new version of sipXtackLib (4.2) doesn't seem to support sending of NOTIFY
messages
with empty body.It treats Subscription as failure instead.
Below is the code segment in SipSubscribeServer::handleSubscribe()
// Note that since this NOTIFY is due to a SUBSCRIBE,
// it should contain 'full' content. Hence,
// the fullState parameter of getNotifyContent is TRUE,
// and is not taken from
// eventPackageInfo->mEventSpecificFullState.
UtlString availableMediaTypes;
if (handler->getNotifyContent(resourceId,
eventTypeKey,
eventType,
*(eventPackageInfo->mpEventSpecificContentMgr),
acceptHeaderValue,
notifyRequest,
TRUE,
&availableMediaTypes))
{
....
}
else
{
// No content was available, so the subscription fails.
// Determine the reason and set the response code.
....
}
However as per RFC 3265
If the resource has no meaningful state at the time that the SUBSCRIBE message
is processed,
this NOTIFY message MAY contain an empty or neutral body.See section 3.2.2. for
further details on NOTIFY message generation
Is this a bug in the stack or am I missing something?
Regards,
Gauri
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
