[SFtrack] Updated: (XECS-1307) RLS Server should randomize the expiration parameter for a user subscribing to RLS Server
[
http://track.sipfoundry.org/browse/XECS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale R. Worley updated XECS-1307:
---------------------------------
Remaining Estimate: 1 day
Original Estimate: 1 day
1d is the estimate for the remaining work -- I'm assuming that Arjun's work is
largely complete.
> RLS Server should randomize the expiration parameter for a user subscribing
> to RLS Server
> -----------------------------------------------------------------------------------------
>
> Key: XECS-1307
> URL: http://track.sipfoundry.org/browse/XECS-1307
> Project: sipXecs
> Issue Type: Sub-task
> Components: sipXrls
> Affects Versions: 3.10.1
> Environment: sipxproxy 3.10.1-012210 2008-04-04T01:39:37 oem-centos5
> sipxconfig 3.10.1-012210 2008-04-04T01:49:05 oem-centos5
> Reporter: Shruthi Sarpamale
> Fix For: 4.0
>
> Attachments: sipx-configuration-earth.qantom.int.tar.gz,
> xecs-1307-2.diff
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Precondition:
> 1. Register users 701 and 702.
> 2. Setup Speed dial with BLF on user 702(monitoring phone) for 701(Monitored
> phone).
> 3. Apply and Save changes for 702 and phone should be rebooted.
> Steps:
> 1. Verify the Subscription of 702(monitoring phone) and 701(Monitored phone)
> with RLS Server.
> Expected result:
> The expiration value for 701 and 702 should be randomized anywhere between
> 2400 and 3600 seconds.
> Actual Result:
> The expiration value for 701 and 702 sis not randomized and it subscribes for
> 3600 seconds.
> Call-ID for Monitoring phone: e8a2bc36-c1d72268-2bfc7f91@xxxxxxxxxxxx
> Call-ID for Monitored phone: s-2f6639e58af20d6e-2
> Note:
> The expiration values for subscription and registration from status and
> registrar servers are being randomized. Its only the RLS server which is not
> randomizing the expiration values.
> Attached Files:
> sipx-configuration-earth.qantom.int.tar.gz
--
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
