Preview Tool

Cisco Bug: CSCun77163 - Cisco TelePresence Conductor poses issue with Firefox

Last Modified

Mar 17, 2015

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

Cisco TelePresence Conductor poses issue when SIP Trunk selected has name same as that of Conference bridge and further renders page non functional when action performed from Firefox browser

1)Login to CCMAdmin.
2)Access the path Media Resource->Conference Bridge. From Find and List Conference Bridge, click on Add New button and select Cisco TelePresence Conductor from Firefox browser.
3)In Cisco TelePresence Conductor configuration page, make sure that Cisco TelePresence Conductor name is same as SIP trunk selected from SIP Trunk dropdown box , keyin other mandatory items and click on Save button.

First click on Save button yields below warning message
"Add failed. One of the required fields on the page has the same value as an entry that already exists in the database. Please check the corresponding Find List page to verify your entry does not exist."

If the user is not aware of the fact that SIP Trunk name and Conference Bridge name cannot be same and clicks on Save button for second time..following message is displayed leaving page blank

"The attempted action was a violation of security protocols and will not be allowed. This may be caused by having multiple concurrent windows open or using browser buttons (back, refresh, etc). Please retry the operation" 

The page becomes non functional ,Save button is no longer functional and Page is blank with above warning message and no CFB is added.

Further the user has to access the Find And List Conference Bridge..perform all operations again , provide different and Unique name to Conference Bridge and click on Save button again.

On this occasion.. same attempt action....warning message is displayed leaving page non functional again.. however when viewed from Find And List CFB.. added CFB can be seen.

same scenario was working fine in -310 Mainline build.
Bug details contain sensitive information and therefore require a 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.