Cisco Bug: CSCun07598 - Allowing to add existing Directory Numbers in Call Park list
Mar 25, 2014
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Adding existing Directory Numbers in Call Park list Conditions: Register 10 phones with following DN format(call routing-Directory Number) - 1000,1001,1002,1003,1004,1005,1006,1007,1008,1009 Go to call routing-call park - add new Case 1: True If we try to add 1000 or 1001 or 1002 or...1009 in call park list then it will through error like "Add failed. Cannot insert or update pattern. A DN exists with the same pattern and partition." Case 2: False If we go to add 100X in call park list ,then its accepting it. But X is the range from 0 to 9. That means it accepts 1000 to 1009 Directory Numbers. In case 1 its throwing error.In case 2 it is accepting existing directory numbers. Let me explain in Scenario wise. Register phone like this. A-1000 B-1001 C-1002 D-1003 E-1004 F-1005 G-1006 H-1007 I-1008 J-1009 Scenario 1: A(1000) goes to call B(1001). B decides to do call parking. Automatically call parking number will start from 1000(Because we have registered 100X in call park list.so X will start from 0). So B goes to retrieve parked call by dialling 1000 from C. Suppose A disconnects call during the retrieve time and going away. When B dials 1000 , it will think it is going to retrieve call but thing is ,B goes to originate a new call to A. Scenario 2: A(1000) calls B(1001). B parks call and going to retrieve it by dialling 1000(Refer above scenario) from E. Meanwhile C(1002) calls D(1003). D goes to do park & will go to retrieve it by dialling 1001 from F. At the moment A,B & c disconnect call. So when D goes to dial 1001 ,it will think its going to retrieve parked call from C. But actually D is making a new call to B (Bcoz parked number and B's directory number both are same).
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