Monday, May 19, 2014

Cisco Jabber, Expressway and MRA random notes

These notes can get dated pretty quickly so please use with a grain of salt:

MRA
  • 8841 and 8845 phones while registered through  MRA will experience issues dialing while off-hook if the CUCM user controlling them is not in the Access Control Groups Standard CTI Allow Control of Phones supporting Connected Xfer and conf and Standard CTI Allow Control of Phones supporting Rollover Mode.
 Jabber for Windows:
  • Assuming Win7, client configuration files will be found at C:\Users\your user\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF
  • Assuming Win7 and Jabber for Windows 10.6.X, client configuration files will be found at C:\Users\your user\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config\Cache\cachedTFTPConfigStore.xml
  • Assuming Win7, the phot cache can be found at C:\Users\your user\AppData\Local\Cisco\Unified Communications\Jabber\CSF
  • Jabber config files must be named with lower case letters.
  • Jabber config files must use UTF-8 encoding.
  • The default Jabber config file is called jabber-config.xml.
  • Different groups of users can use different config files.
    1. Create a new config file.
    2. Name it with lower case letters and UTF-8 encoding.
    3. Upload it to your CUCM TFTP server(s).
    4. Apply the new config file to one or more CSF devices.
      1. In the Product Specific Configuration Layout | Cisco Support Field, enter configurationfile=your-group-jabber-config-file-name.xml    
    5. Apply Config / reset the CSF device, quit and restart the Jabber client.
  • BDI = Basic Directory Integration and refers to situations where one needs to do a basic LDAP bind instead of relying on the Windows Active Directory Services Interface APIs (see Jabber for MAC, iPhone, etc.).
  • Can download jabber-config.xml from TFTP servers via http://yourTFTPserver:6970/jabber-config.xml 
  • Can verify CUCM response to Jabber client UDS server list via  https://<homeCluster>:8443/cucm-uds/servers 
  • Can verify CUCM response to Jabber client authentication with user via https://<homeCluster>:8443/cucm-uds/clusterUser?username=<user>
  • _cisco-uds._tcp.example.com (on Internal DNS)
  • _cuplogin._tcp.example.com (on Internal DNS) 
  • _collab-edge._tls.example.com (on External DNS)
  • USE nslookup, then set type=SRV  to verify records.
VCS Expressway Edge and VCS Expressway Core
  • the SIP trunk in CUCM to VCS Experssway Core is only for B2B video
  • the SIP trunk in CUCM to VCS Experssway Core is not even used for MRA
  • the automated neighbor zones on Expressway Core are what's used for MRA

Other links:

Nice write up re: Collaboration Edge with split DNS
https://ciscocollab.wordpress.com/2014/07/23/collaboration-edge-mra-with-split-dns-domains/

Basic Collaboration Edge rehash:
https://ciscocollab.wordpress.com/2014/01/29/deploying-collaboration-edge/



No comments:

Post a Comment