Guest

Preview Tool

Cisco Bug: CSCsz49541 - UC Greeting Admin Search scope incorrect while using CSS and partitions

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unity Connection

Known Affected Releases

7.0(2)ES1

Description (partial)

Symptom:

Unity connection Greeting Administrator search scope for Call hanlders is broken when using a routing rule with CSS and partitions

Conditions:

Config is as follows: (As a sampe example)
 
CallManager 4.1(3) with CTI route points forwarded to VM pilot 
 
Partitions configured: 
 
· Partition A applied to à GAdmin Pilot (call handler) that sends the call to the Greeting Administrator
· Partition B applied to à User (owner of the call handler to edit)
· Partition C applied to à Test (call handler that we are trying to edit)
 
CSS Configured:
 
· CSS X applied to à GAdmin Pilot, contains partition B
· CSS Y applied to à User, contains partitions A and C
· CSS Z applied to à F/w routing rule, contains partition A
 
Forwarded rule to the GAdmin Pilot 
 
Callflow:  
 
 * phone calls GAdmin Pilot 
 * caller hears alternate/standard greeting of custom GADMIN pilot 
 * after the greeting, caller hears Cisco GADMIN greeting 
 * caller enters userID of 'user' and password 
 
 * this userID is in a partition which is contained in the SS of the custom GADMIN pilot 
 * if this was not the case, the user would NOT be able to log in 
 * caller hears Cisco GADMIN prompt to enter extension of call hander to edit     
 * callerenters ext of the "Test" handler that we are trying to edit. 
 
 * this call handler DN is in the partition which is contained in the SS of the user, and 
 * the user above is the owner of "Test" 

However the user hears the greeting of the "GAdmin pilot" NOT of "Test" Call handler. 

The Greeting admin search scope selected the next available call hanlder as per the CSS setting of the routing rule. The routing rules CSS should not matter in selection of the Call Handler when using Greeting Adminsrator. Only the users CSS should matter.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.