Cisco Bug: CSCta00887 - LP: UCM core & geoloc issue during Split/Join for shared line on >5 devs
Nov 03, 2012
- Cisco Unified Communications Manager (CallManager)
- Cisco Unity Connection Version 7.1
- Cisco Unified Communications Manager Version 7.1
Known Affected Releases
Symptom: 1. UCM cores and restarts service. 2. Possible wrong LP policy check for a join feature scenario later than first Early Attended Transfer to shared line. This is applicable for multinode scenarios and only when LPSessions joined are across UCM nodes. Won't be issue for intranode joins. Conditions: 1. Using >5 shared lines. 2. Multinode transfer cases say, PSTN Trunk on node1 calls a Phone A on node2 (LPSession on node1). Phone A presses Xfer and dials shared line B on node2 (LPSession on node2). Performs early attended case. When transfer is completed LPSession is created on node1. The internode communication of geolocation happens in Policy signals. The LPSession will only remember the "last" geolocation from list of geolocs. If this happens to be different than that of the answering device then LPSession will retain wrong geoloc for a given device. Furture policy checking may be impacted for the same LPSession in any feature scenario.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases