Jabber move to mobile

Hi, this is a sort guide on how to setup move to mobile.
This feature is available only for Android and iOS Jabber, not for Windows etc.

First create a Mobility Profile, Call Routing -> Mobility -> Mobility Profile.

This is a global setting.



Go to end user and assign mobility for the user needed

Then go to device configuration and make sure for the following

1. Assign a softkey template that has Mobility key assigned on "On Hook" and "Connected", Create on if needed.
2. Assign the English United States on User Locale (Required as stated)
3. Assign an Owner ID and Mobility user ID
4. Assign a CSS that allows you to reach the mobile number on "Rerouting Calling Search Space"
5. On "Transfer to Mobile Network" select "Use Mobility softkey (user Receives Call)"
6. On "Dial via Office" select Enable
7. On "Associated Mobility Identity" create a new mobility as follows

Apply configuration and logoff - login from mobile jabber and test.

Cisco reference
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_6/cjab_b_feature-configuration-for-cisco-jabber/cjab_b_feature-configuration-for-cisco-jabber_chapter_0100.html#CJAB_TK_S6472988_00

Cisco Jabber Certificates

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-presence/116917-technote-certificate-00.html 

https://supportforums.cisco.com/t5/jabber-clients/cucm-and-imp-ip-address-to-fqdn/td-p/2588634

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_6/cjab_b_planning-guide-cisco-jabber-116/cjab_b_planning-guide-cisco-jabber-116_chapter_0111.html

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_6/cjab_b_on-premises-deployment-ciscojabber-116/cjab_b_on-premises-deployment-ciscojabber-116_chapter_01100.html

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211393-Change-CUCM-Server-Definition-from-IP-Ad.html

Windows QoS settings

Windows 10 don't allow applications to mark outgoing packets with QoS DSCP values.

In order to overcome this you have 2 options

• Create a group policy QoS which works only on domain networks
• Run a powershell command to create a group policy attached to all network connections Domain / Private / Public

The powershell command is (Match on executable name):

New-NetQosPolicy -Name "CiscoJabber" -AppPathNameMatchCondition "CiscoJabber.exe" -DSCPAction 46 

Use the following command to view the QoS policies as the powershell created policies don't show up in Local Computer Policy snap-in.

Get-NetQosPolicy

References:
Microsoft New-NetQoSPolicy
Microsoft   Get-NetQosPolicy

CUCM Remove prefix from call presentation

Hi,

If you have a translate rule in your gateway that adds 9 to the caller number for incoming calls, for call history, redial etc. Then you are facing an issue where your Jabber will not do Caller ID based on your contacts.
To override this behavior you can do the following:

1. Create a new partition not used anywhere else. e.g. Transform_PT
2. Create a new Calling Party Transformation Pattern 

1. Pattern 9.!
2. Partition  Transform_PT
3. Discard Digits PreDot
3.  Create a CSS e.g. Transform_CSS
1. Assign the Transform_PT partition to the CSS
4. Go to a test device and assign the Transform_CSS  
   
   
   
1. under "Number Presentation Transformation"
2. un-check "Use Device Pool Calling Party Transformation CSS"
3. Assign the created CSS Transform_CSS
4. Apply & Reset
5. Test and if happy apply that to the Trunk for all users using step 4 guide.

Call Manager Secure LDAP (LDAPS) integration

In order to proceed the following must be met

- DNS servers configured on all CUCM servers
- Export Certificates from all Domain Controllers
- Check who Domain Controllers have the Global Catalog role installed
- Upload DC certificates on all CUCM and Presence servers using "tomcat-trust" for versions 8.x and newer.
- Restart Tomcat service from CLI/SSH using utils service restart Cisco Tomcat
- Declare your LDAP servers with SSL and use port 3269 for GC enabled DCs and port 636 for non-GC servers.

Cisco Call Manager Certificates with Microsoft CA

Hi, in order to renew the certificates you must create a Certificate CSR, in this CSR you MUST include the server FQDN in subject name and in SAN also.
You must also note the old certificate attributes such extended key usage e.g.

Then you must create the certificate sign template on Microsoft CA. You must use the desktop application to do this.
Open Certificate Authority and then Certificate templates -> manage.
Find the Web server template and copy that on to a new.
Change the Name in General and then add the correct settings based on the previous step.
Check encryption for modulus not more than 4096.

Before you close the application add the Template in the template shortcuts.

Now open a browser and point to your CA
Open the CSR file and copy all the contents to your CA request website, generate the certificate and download in base64 format.
Then upload the certificate, along with the Root CA and any Intermediate CA (Full Chain) to CUCM and restart the appropriate service e.g. tomcat.

If the CA is trusted by your browser / application, then you will see no warnings when you visit the page.

CUCM TFTP File download

In order to download a file from CUCM TFTP use a browser to go to
http://<cucm IP or FQDN>:6970/<TFTP filename>

Example: http://CUCM1:6970/jabber-config.xml