SIP Toolbox v1.5.0

Release Notes:

  • Added SIP Trunk Dashboard. You can monitor call activity for any SIP trunk. Refreshes every 15 seconds
  • Fix bugs with SDL retrival and packet captures
  • Add Jabber log file parser


Download SIP Toolbox

UC Configurator v0.3.9 released

Release Notes:

  • Updated Device Pools to allow for Local Route Groups to be added and configured besides the Standard Local Route Group


BetterBAT v2.5.3 released

Release Notes:

  • Fixed/improved User Validation
  • Line voicemail profile dropdown is now working
  • Check for Ring, Flash, etc on each line is now a part of validation
  • Unity user validation after import and console failed by name correctly shows up


BetterBAT v2.5.2 released

Release Notes:

  • Added AXL caching. If you connect to the same server repeatedly only changes will be pulled down from AXL data.
  • Added option to make console window smaller and draggable.
  • End user validation added
  • Phone Device Name validation added
  • Fixed issue with systems that have large phone button templates
  • Added DYMO LabelWriter printing option (Beta feature)
  • Changed phone csv output to phone.csv instead of phones.csv


Call Manager 12.0 UC Profile Bug

Recently ran into an issue with our new Call Manager cluster. We’re running a fresh install of 12.0 and we migrated all of our users from an old 10.5 cluster to the new one. Within a week we noticed that our new installation was operating at 90% CPU throughout the day. After some troubleshooting we found out that our Jabber users were sending UDS request to the publisher at an alarming rate. After doing a bit more digging, we realized that we had to go with UDS for contact resolution because of another bug in 12.0 that would not let us enter our AD credentials into our UC Service Profile.

We ended up solving this via SQL. Note: that updating the profile via the GUI after applying the SQL statement will remove the Username and Password

run sql update ucserviceprofiledetailxml set xml = '<UseUDS>false</UseUDS><UseUserCredential>false</UseUserCredential><DN>INSERT USERNAME</DN><Password>INSERT PASSWORD</Password><SearchContext1>INSERT SEARCH CONTEXT</SearchContext1><SearchContext2></SearchContext2><SearchContext3></SearchContext3><RecursiveSearch1>true</RecursiveSearch1><SearchTimeout>5</SearchTimeout><BaseFilter></BaseFilter><PredictiveSearchFilter></PredictiveSearchFilter><AllowJabberUserstoSearchandAddSecurityGroups>false</AllowJabberUserstoSearchandAddSecurityGroups>' where pkid = 'INSERT PKID OF PROFILE'

Jabber Directory Options



Centralized IM and Presence Deployment

Recently I deployed a centralized IMP cluster within our multisite SME model. This allowed us to provide IM and Presence to our telephony clusters without having to do a 1 to 1 deployment. I started by following this guide:

Configuration and Administration of the IM and Presence Service on Cisco Unified Communications Manager, Release 12.0(1)

However the guide wasn’t clear regarding a number of things. So here are my notes that took to get it to work:

  1. Your IM and Presence central cluster should not be a part of your ILS network.
  2. User ID on the IM&P central cluster should have (See image below):
    • ‘Home Cluster’ - checked
    • ‘Enable User for Unified CM IM and Presence’ - checked
  3. User ID on the telephony cluster should have (See image below):
    • ‘Home Cluster’ - checked
    • ‘Enable User for Unified CM IM and Presence’ - unchecked
    • Service Profile that references the centralized IMP cluster
  4. SRV Records

User ID configuration on IM and Presence central cluster

User ID configuration on telephony cluster