[SFtrack] Updated: (XECS-1363) Record-Route's not handled correctly in SUBSCRIBE/NOTIFY by SipSubscriptionManager
[
http://track.sipfoundry.org/browse/XECS-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Nair updated XECS-1363:
-----------------------------
Attachment: subscribeRecordRoute.diff
Problem:
1. NOTIFYs sent from SipSubscribeServer do not include any Route sets set by
the dialog initiating SUBSCRIBE
2. Dialog forming "202 ACCEPTED" Response sent from SipSubscribeServer, does
not echo any Record-Routes present in the dialog initiating SUBSCRIBE
Root Cause:
1. Bug in class SipDialog. SipDialog does not save any Route sets for remotely
initiated dialogs.
2. By default sipXtack does not echo Record-Routes in Responses. Applications
are responsible for filtering out dialog-forming Responses and add the
Record-Routes to them.
Soultion:
1. In the SipDialog constructor, check for dialog initiating Requests, that are
initiated from the remote side. If found, set the Route sets from this Request.
2. Add an extra function argument - "UtlBoolean responseIsDialogForming" to
SipMessage::setResponseData(), with a default value of "FALSE". If this argment
is set to "TRUE" then any Record-Routes present in the Request is added to the
Response.
In SipSubscriptionMgr::updateDialogInfo(), where the "202 Accepted"
dialog-forming Response is build, call the SipMessage::setResponseData() with
"UtlBoolean responseIsDialogForming" set to "TRUE".
> Record-Route's not handled correctly in SUBSCRIBE/NOTIFY by
> SipSubscriptionManager
> ----------------------------------------------------------------------------------
>
> Key: XECS-1363
> URL: http://track.sipfoundry.org/browse/XECS-1363
> Project: sipXecs
> Issue Type: Bug
> Components: sipXtackLib
> Affects Versions: 3.11.4
> Reporter: Dale R. Worley
> Assignee: Arjun Nair
> Fix For: 3.11.5, 4.0
>
> Attachments: subscribeRecordRoute.diff
>
>
> In the subscriptions to ext. 403 described in XECS-1353, you can see that the
> RLS is not processing the Record-Route's in the incoming SUBSCRIBE correctly
> -- they are not copied into the response, and they are not used to add
> Route's to the generated NOTIFYs. This causes at least some of the failures
> seen in XECS-1353. It is likely that this problem affects all other sipX
> notifiers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
