[SFtrack] Commented: (XECS-1940) LG set's transferred call not always tracked by BLF on Polycom set
[
http://track.sipfoundry.org/browse/XECS-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32985
]
David Saint commented on XECS-1940:
-----------------------------------
Perhaps the Polycom650 is being overwhelmed by too many NOTIFY messages? See
issue XECS-1915.
> LG set's transferred call not always tracked by BLF on Polycom set
> ------------------------------------------------------------------
>
> Key: XECS-1940
> URL: http://track.sipfoundry.org/browse/XECS-1940
> Project: sipXecs
> Issue Type: Bug
> Components: sipXrls
> Affects Versions: 3.11.8
> Environment: SW = SIPx main stream 3.11.8-14071
> HW = 64-bit SLES10SP1 on PPC
> Reporter: David Saint
> Assignee: David Saint
> Priority: Minor
> Attachments: sipx-configuration.tar.gz
>
>
> 201 = Polycom650 with BLF for 280, 202, and 203
> 202 = LG6812
> 203 = LG6804
> 280 = park server
> Call from set 203 to set 202, answer on set 202. BLF tracks correctly.
> Transfer call from set 202 to park server 280, after the transfer completes
> the BLF lamp for 280 is on but the BLF lamp for 202 is sometimes on and
> sometimes off.
> In the attached trace: for the first call at 08:47:03 EST has the BLF working
> properly but in the second call at 08:47:56 the BLF for 202 is off.
--
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
