Get presence from Cisco phones that don’t support CTI

You must add a new SIP trunk with a destination address that points to the server on which SIP User Proxy is runs (that's the Zylinc Windows Application Server).

Sip Profile should support Redirect by Application, and SIP security Profile should support Accept presence subscription and Accept unsolicited notification.

Inbound calls Calling Search Space and SIP Information SUBSCRIBE Calling Search Space should support the phones from which you’re going to get SIP presence.

1. Log in to the Cisco Unified CM Administration (CCMAdmin) web page (typical user name: ccmadmin)
2. Add a new SIP Trunk Security Profile
   1. In the menu, select System > Security > SIP Trunk Security Profile
   2. Click Add New
   3. In Name, enter ZylincPresence
   4. In Device Security Mode, select Non Secure
   5. In Incoming Transport Type, select TCP+UDP
   6. In Outgoing Transport Type, select TCP
   7. In Incoming Port, enter 5060
   8. Select Accept presence subscription
   9. Select Accept unsolicited notification
   10. Click Save
3. Add new SIP Profile
   1. In the menu, select Device > Device Settings > SIP Profile
   2. Click Add New
   3. In Name, enter ZylincPresence
   4. Select Redirect by Application
   5. Click Save
4. Add new SIP Trunk
   1. In the menu, select Device > Trunk
   2. Click Add New
   3. In Trunk Type, select SIP Trunk
   4. In Device Protocol, select SIP
   5. In Trunk Service Type, select None(Default)
   6. Click Next
   7. In Device Name, enter ZylincPresence
   8. In Device Pool, enter the value provided by the customer (typical value: Default)
   9. In Inbound Calls:
      1. In Calling Search Space, enter the information provided by the customer (typical value: Phones-CSS)
   10. In SIP Information:
       1. In Destination Address, enter the IP address or fully qualified DNS name of the Zylinc Windows Application Server, for example winappserver.domain.local
       2. In Destination Port, enter 5060
       3. In SIP Trunk Security Profile, select ZylincPresence
       4. In SUBSCRIBE Calling Search Space, enter the information provided by the customer (typical value: Phones-CSS)
       5. In SIP Profile, select ZylincPresence
   11. Click Save
   12. Click Reset
   13. In Device Reset
       1. Click Reset
       2. Click Close

1. In the Zylinc Administration Portal menu, select USERS > ZyDesk Users
2. Click the name of a user whose Cisco presence should be collected via SIP
3. In the User (Operator) section:
   1. Clear Default
   2. In Device, select SIP
   3. In both ID and Office Number, enter the user’s short Cisco phone number (example: 1901)
4. Click Save

Clear Client Manager cache:

1. Open the following URL in a browser: https://<Zylinc Windows Application Server>:8443/ClientManager/

   Example: https://WinAppServer:8443/ClientManager

2. Ignore the security warning about the certificate, and continue to the website

3. Click Configuration

4. Log in with user name admin and the password for Tomcat instance ZyTomcat1-8080-8443 user admin

5. Click Reload Settings

1. In the Administration Portal menu, select INSTALL > Portal Configuration
2. Check that SIP Presence is selected.
3. In the Administration Portal menu, select NETWORK > Sip User Proxy
4. In SIP connection settings, select Enable Service
5. In Local IP, enter the hostname or IP address of the Zylinc Windows Application Server
6. In Port, enter 35056
7. Click Save

1. In the Administration Portal menu, select NETWORK > Sip User Proxy
2. Click the Add SIP Provider link
3. In SIP Provider Connection:
   1. Select Enable SIP provider
   2. In SIP display name, enter a name for the SIP provider, for example: CiscoPresence
   3. In Adapter Address, enter the hostname or IP address of the Cisco Call Manager Server that you previously created a SIP trunk on
   4. In Port, enter 5060
   5. In Protocol, select TCP
   6. In XML Format, Select PIDF (rfc3863)
4. In SIP Simple Subscription:
   1. In Subscription Type, select Single Subscriptions
   2. In Timeout, enter 3600
   3. In Userpart Mobile - Db Column, select None
   4. In Userpart Office - Db Column, select Office Number
   5. In Userdomain, enter the IP address or host name of your Cisco Call Manager Server
5. Click Save

1. In the Zylinc Deployment Manger menu, select Deployment > Installation
2. In Installers, select SIP User Proxy
3. Click Install Applications
4. In the Deployment Manager menu, select Deployment > Windows Services
5. Select SIP User Proxy
6. In Change Startup Type, select AutomaticDelayed
7. Click Change Startup Type
8. Select SIP User Proxy
9. Click Start Services

1. Decide which user you’re going to use for this test. It should be one of the users you’ve set up for Cisco presence via SIP.

2. Make sure that the test user is logged in to a Cisco softphone, or that a connected and working desktop phone is mapped to the test user. This is because you’ll not see a presence icon for users who aren’t logged in to a softphone or desktop phone.

3. Log in to ZyDesk as a normal end user.

4. In ZyDesk, make a search that returns the test user.

5. In the search results, you should see a presence icon in the Line State column, next to the test user’s name.

6. Make a call from the test user’s Cisco phone. The line state icon should change to Busy.

7. End the call. The line state icon should change to Idle.

If the presence icon for the test user is missing, or if the icon doesn’t change state when the test user becomes idle or busy, do the following:

1. Make sure that the user is actively logged in to a working desktop phone or softphone.

2. In the Administration Portal menu, select USERS > ZyDesk Users, and click the name of the user whose presence icon doesn't work. Check that User (Operator), Device is set to SIP, and that both ID and Office Number contains the user’s Cisco short number.

3. Clear Client Manager cache:

   1. Open the following URL in a browser: https://<Zylinc Windows Application Server>:8443/ClientManager/

      Example: https://WinAppServer:8443/ClientManager

   2. Ignore the security warning about the certificate, and continue to the website

   3. Click Configuration

   4. Log in with user name admin and the password for Tomcat instance ZyTomcat1-8080-8443 user admin

   5. Click Reload Settings

4. Restart ZyGo. This will clear old presence data that may not be current.

5. Restart SIP User Proxy.

6. Make a call from one of the phones that you've set up for Cisco presence via SIP.

7. Open SIP User Proxy log file (see Open latest log file from specific Zylinc module), and look for lines that contain the following phrases:

   Contents of line in SIP User Proxy log file	Type	Action to take
   Search for lines that contain the words error or exception	Error	Lines that contain one of those words will often also contain additional information about the possible causes of the error, and what to do to resolve it.
   Lines that contain the phrase No data rows found	Error	The log file line means SIP User Proxy doesn't have any users to work with, and effectively doesn’t do anything. Make sure that users exist in the Administration Portal with User (Operator), Device set to SIP.
   Lines that contain the phrase SUBSCRIBE sip:	Ok	SIP User Proxy found a user and will (try to) subscribe to the SIP URI (user) that you can see in the line. This is expected and indicates normal operation, but the SIP URI is useful when you need to check number mappings. You can compare the phone number and the domain part of the SIP URI against the expected value on the presence provider. If the numbers don’t match, you can add a suffix or prefix, or update Userdomain in the Administration Portal, to make the numbers and domain match what the presence provider expects.
   Lines that contain the phrase Request received (Remote tcp:	Ok	SIP User Proxy correctly receives data from the presence provider. This is expected and indicates normal operation. If no line contains this, you need to find out what prevents SIP User Proxy from receiving notifications from the presence provider. Use log files from the presence provider or Wireshark to verify that the provider sends the presence data, and check that your network allows the data to pass through routers and firewalls.
   Lines that contain the phrase Sending Zylinc presence info to server:	Ok	Presence changed for a user, and SIP User Proxy correctly received presence data. The line also contains an XML representation of the presence data. <ContactID> contains the phone number for the user, and <State> contains the state, for example: busy or idle. This is expected and indicates normal operation. If no line contains this, no calls were made within the time window of the log file.
   Lines that contain the phrase ErrorCode: 404[tab]Reason: NotFound	Error	Userdomain is wrong. In the Administration Portal menu, select NETWORK > SIP User Proxy Go to the relevant SIP provider Change Userdomain to either the IP address or hostname of your Cisco Call Manager Server