To answer both of your questions... Yes this functionality is broken, which is why we have a bug filed.
Just getting in to semantics here, but I wouldn't use the words cosmetic nor enhancment to describe the problem. Cosmetic implies there is no effect beyond what you see, and ehancment typically means we are going to add some functionality to the product. This is not cosmetic, because selecting the SRV option will change CUCM's behavior. Specifically, it will query for an SRV record, not an A record. And if there is no SRV record in DNS it won't work at all. This is not an enhancment request, because this is a deviation from the designed behavior. We aren't adding some new functionality, just getting what should be there working. This is just a bug that needs fixing.
Thanks for your supportive answers here. I have two questions.
1. The DNS SRV record example is great, but I'm confused. If I need to also add a DNS SRV record for the Jabber client auto resolution, is this a separate record? I'm thinking so, but am doing my first install. If I'm right, then for HA I would want 3 records - one for the Presence Cluster for HA (subject to the BUG), one for the CUCM cluster for resiliency of the Gateway and then one for the Jabber Clients...right?
2. The bug is not fixed yet, is it? BugTool Kit seems unresolved. Can you help me with a sample FQDN naming convention for the cluster DNS SRV record and for the Supplemental work around record?
Here is the example from the guide:
DNS SRV Records
You must add a DNS SRV record for the _cuplogin service name in the DNS server on the presence server
domain. If this DNS SRV record does not exist, Cisco Jabber for Windows cannot perform DNS SRV lookups.
The following is an example of a DNS SRV record:
_cuplogin._tcp.company.com SRV service location:
srv hostname =cupserver.company.com
internet address =10.53.56.57
In the preceding example, _cuplogin is the service name. The presence server domain name is company.com.
The SRV record defined in the DNS server for the company.com domain is _cuplogin._tcp.company.com.
Cisco Jabber for Windows 9.1.x Installation and Configuration Guide
Plan for Cisco Jabber for Windows
Automatic Server Discovery
Note Cisco Jabber for Windows
• Uses port 8443 by default, not the port that is mapped in the SRV record.
• Supports weight and priority during DNS SRV lookup.
Hello Experts,We have configured a Hunt pilot which includes 2 line groups.one line group with 5 extensions rings with Algorithm as broadcast and 2nd line group contains 1 extension as their manager.All these extensions configured with single number reach...
I am setting up a bulk update in CUCM to add jabber phones to all my deskphone users. I have a bat phone template I adapted from one I made for desk phones and I have a user template for use with "Update Users - Custom File". I have used the users t...
Hi community, maybe someone has already experienced this issue. When using conference now you define a number which triggers an IVR prompt where you can setup your meetings. I the ani is associated with an active SNR number the IVR script won't let t...
I need to get 100 VCS-C traversal and 200 VCS-E traversal calls VM servers running 12.5. I am also trying to convert my old VCS licenses fromVCSC/E. Can't find any reliable guide on CCO about licenses, and conversion of old licenses....
I'm want to video conference from a Cisco Web Room Kit Pro end point to Virtual Webex and have my customers be able to view/collaborate via Microsoft Teams. What licenses would be required to make this happen?