Set up mobile presence

This information is primarily for administrators and/or people who manage Zylinc solutions

Zylinc solutions support that you can get mobile phone presence information from a number of mobile network providers. If you set up your Zylinc solution's mobile presence service, you'll get the following features:

  • Make mobile presence indication—and optionally other status information, such as caller id and roaming country information—available in the Zylinc solution

  • Get mobile presence from many mobile network operators, for example, TDC, Telia, and Telenor in different countries

  • Automatically set Skype for Business presence to busy when a user’s mobile phone becomes busy

  • If your mobile network operator requires an open port on the internet, and if your organization requires that servers that listen to open ports on the internet must be placed in DMZ, you can install and set up Zylinc Proxy

If you need to get mobile presence from a mobile network operator that isn't supported (that is the operator isn't available when you select NETWORK > Mobile Status in the Administration Portal menu), you have some alternatives:

  • You can use SIP User Proxy to get mobile presence via the SIP protocol, for example for Sonera Finland

  • You can use BroadWorks User Proxy to get mobile presence via BroadWorks mobile events

To find out if your mobile network operator’s presence service is designed in such a way that it requires your organization to open up a port in the firewall that listens to traffic from the internet:

  1. In Excel, open Set up firewall rules and network port monitoring.xlsx
  2. If Excel says that you use PROTECTED VIEW, click Enable Editing. Otherwise you can’t use the filter in the following step.
  3. Select cell A1, and click to set up a filter on column A.
  4. Set up the filter so that it only includes the rows that represent Mobile presence for your mobile network operator.

If you see rows that contain Global internet port forward in the Other source column, and the Destination host column shows WinAppServer or DMZ, it means that the specified port must be opened in your organization's firewall. When that's the case, the source is the mobile network operator's presence host on the internet, and the destination is Zylinc Windows Application Server on the LAN, or a server in your organizations DMZ.

The Excel sheet contains known presence hosts and ports for a number of mobile network operators. We recommend that you verify the information with the mobile network operator to make sure that you have up-to-date information.

If your organization must open a firewall port, check whether your organization’s IT policies require that servers with open ports on the internet must be placed in DMZ.

If you don’t need to use DMZ, you can directly forward the internet port to the Zylinc Windows Application Server. That way, you don’t need Zylinc Proxy.

If you need to use DMZ, you can set up Zylinc Proxy on a DMZ server, and set up the accompanying Zylinc Proxy Client on a LAN server.

With this method you don’t need to open a port from the DMZ to the LAN, or from the internet to the LAN, because the connection is initiated in the outgoing direction from LAN to DMZ. The only open port from the internet goes to the DMZ.

Zylinc Proxy and Zylinc Proxy Client work like this:

  1. Zylinc Proxy Client on the LAN server initiates an outgoing connection to Zylinc Proxy’s internal (LAN) port on the DMZ server.
  2. Zylinc Proxy Client on the LAN then uses the established connection and a protocol to instruct Zylinc Proxy on the DMZ server to begin to listen to the specified Wan Port (that’s the port that has been opened in the firewall from internet to DMZ).
  3. Zylinc Proxy on the DMZ server then begins to relay network traffic back to Zylinc Proxy Client on the LAN via the established connection.
  4. Zylinc Proxy Client on the LAN server connects to the specified Service Address and Port on the LAN, and then begins to relay network traffic to that address and port.
  5. Zylinc Proxy and Zylinc Proxy Client use a protocol to detect if the established connection becomes disconnected. If that’s the case, the process will repeat itself from step 1 to reestablish the connection.

On the DMZ server, do the following:

  1. Open the unzipped Zylinc release folder:

    C:\Zylinc install\Release_6.5u4.12\Release_6.5u4.12\

  2. Locate the DeploymentManager.exe file, and double-click it to start the program. Run DeploymentManager.exe directly from the unzipped folder.

    You'll need Deployment Manager more than once, so pin it to the taskbar.

  3. In the Deployment Manager menu, select Deployment > Installation.

  4. Maximize the Window to view all the available features.

  5. In the Installers list, select Java.

  6. Click Install Applications. When Java installation is complete, status changes from uninstalled to installed, and Java changes color to green in the Installers list.

  7. In the Installers list, select Tomcat.

  8. Click Install Applications.

Set up a new Tomcat instance with the following parameters:

Application server name (example): DMZserver

New instance name (example): ZyTomcatDMZ-8080

Use the admin user password for: Windows Tomcat DMZ 8080 user admin

Java and Tomcat versions: Most recent versions available in Deployment Manager

Initial memory: 512MB

Max memory: 2048MB

Port numbers (HTTP / AJP / Shutdown): 8080 / 8009 / 8005

Set service startup type to: Automatic

  1. In the Deployment Manager menu, select Application Administration > Apache Tomcat Administration

  2. In Instances, click New instance

  3. In Apache, select the most recent Tomcat version available in the list

  4. In Java, select the most recent Java version available in the list

  5. In Initial Memory (MB), enter 512

  6. In Max Memory (MB), enter 2048

  7. In Name, enter a name to use for the new instance in Deployment Manager, for example: ZyTomcatDMZ-8080

  8. In User, enter admin

  9. In Password, enter a password to use for Windows Tomcat DMZ 8080 user admin

    You’ll need this username and password when you're going to use a web browser to log in to Manager App for the new instance. This is useful, for example, when you need to test that HTTP works.

  10. Click Save instance

  11. A new instance with the name ZyTomcatDMZ-8080 should be visible in the Instances list

  12. Click Save instance

  13. In the Deployment Manager menu, select Deployment > Windows Services

  14. Click Refresh Services

    A new service with a name that ends with ZyTomcatDMZ-8080 should be visible in the Deployed Services list.

  15. Start the new service

  16. Select the new service, and in Change Startup Type, select Automatic, and click Change Startup Type.

  1. Go to the following address in a web browser: http://<DMZserver>:8080/

    Example: The complete URL could be http://DMZserver:8080/

  2. You should see a Tomcat welcome page that says If you're seeing this, you've successfully installed Tomcat. Congratulations!

  3. Click Manager App

  4. In User name, enter admin

  5. In Password, enter the password for Windows Tomcat DMZ 8080 user admin

  6. You should see a list of Applications, for example /docs and /examples

Now you know that HTTP works.

On the DMZ server, do the following:

  1. In the Deployment Manager menu, select Deployment > Tomcat Services
  2. In Instance, select ZyTomcatDMZ-8080
  3. In Available Tomcat applications, select Zylinc Proxy
  4. Click Deploy Services

On the DMZ server, do the following:

  1. In a browser open this URL: http://localhost:8080/
  2. Click Manager App, and log in as admin with the password for Windows Tomcat DMZ 8080
  3. Click ZylincProxy
  4. Click Configure
  5. In Internal port, enter the port number for the Zylinc Proxy internal (LAN) port that you opened from LAN to DMZ (typical value: 35031)
  6. Click Save

Do the following to restart Zylinc Proxy:

  1. In the Deployment Manager menu, select Deployment > Tomcat Services
  2. In Instance, select ZyTomcatDMZ-8080
  3. In Available Tomcat applications, select Zylinc Proxy
  4. Click Stop Services
  5. In Available Tomcat applications, select Zylinc Proxy
  6. Click Start Services
  1. In the Administration Portal menu, select INSTALL > Portal Configuration
  2. Make sure that Zylinc Proxy is selected.
  3. In the Administration Portal menu, select NETWORK > Zylinc Proxy
  4. In Host address, enter the hostname or IP address of the DMZ server
  5. In Port, enter the port number for the Zylinc Proxy internal (LAN) port that you opened from LAN to DMZ (typical value: 35031)
  6. Click Save
  7. Click Add Client Proxy Config
  8. In Client Proxy Context Name, enter ZXC_MobilePresence1
  9. In Service Address, enter the IP address or hostname of the Zylinc Windows Application Server, for example: winappserver
  10. In Port and Wan Port, enter the port number that the service on the LAN listens on. This port numbers should be identical to the one that you've opened in the firewall.
  11. Click Save.

On the Zylinc Windows Application Server, do the following:

  1. In the Deployment Manager menu, select Deployment > Tomcat Services
  2. In Instance, select ZyTomcat1-8080-8443
  3. In Available Tomcat applications, select Zylinc Proxy Client
  4. In Context Path, change the value to /ZXC_MobilePresence1
  5. Click Deploy Services

On the Zylinc Windows Application Server:

  1. In a text editor, open C:\Program Files\Zylinc\ApacheInstances\<instance name>\logs\ZXC_MobilePresence1.log
  2. The log file should have lines that contain the phrases TRACE - ping and TRACE - pong

What the phrases TRACE - ping and TRACE - pong mean:

  • Zylinc Proxy Client in the LAN successfully connected to Zylinc Proxy in the DMZ on the Zylinc Proxy internal (LAN) port.
  • Zylinc Proxy Client in the LAN successfully loaded the configuration that you previously set up in the Administration Portal.
  • The configuration was sent to Zylinc Proxy in the DMZ. The system successfully listened to the port and relayed network traffic back to the LAN.
  • Together, that confirms that the proxy configuration is working as expected.
  1. Go back and double-check that you correctly carried out the previous steps that relate to Zylinc Proxy. Then restart the Tomcat service on DMZ server, and restart the Tomcat service on Zylinc Windows Application Server.
  2. In the log file, search for lines that contain the words error or exception. Often, such lines also contain additional information about the possible causes of problems, and what to do to solve them.
  3. Go to the DMZ server and use a text editor to open C:\Program Files\Zylinc\ApacheInstances\ZyTomcatDMZ-8080\logs\ZylincProxy.log, and repeat the previous test procedure.

To open a port in the firewall, and to set up your organization's public IP address and port number with the mobile network operator, do the following:

  1. Ask your organization's firewall administrator to open up the relevant ports from the internet to the Zylinc Windows Application Server or to a DMZ server

    If you’re going to use DMZ, also ask the administrator to open the Zylinc Proxy internal (LAN) port from the LAN to the DMZ, but not from the internet to the DMZ.

    You can view the port number in the Excel sheet. A typical value is 35031.

  2. Ask your organization's mobile phone administrator to use mobile network operator self-service portal (or their support service) to register your organization’s public IP address and public port number for presence callback or push updates.

Zylinc Mobile Status service on the Zylinc Windows Application Server in the LAN will initiate an outgoing connection to the Zylinc Mobile presence service on the internet.

You don’t need to open a firewall port that listens to traffic from the internet. Just make sure that the outgoing connection from your organization’s LAN to the Zylinc Mobile presence service hosts and ports aren't blocked by firewalls.

  1. In the Zylinc Administration Portal menu, select INSTALL > Portal Configuration.

  2. Make sure that Mobile Status is selected.

  3. In the Administration Portal menu, select NETWORK > Mobile Status.

  4. If you need to hide caller id and roaming country information., select Privacy.

  5. In Home Country, select the country whose prefix you want to be automatically added to phone numbers that don't have a prefix.

  6. For each mobile network operator you need, select Active.

  7. Depending on the provider, enter the following information:

    1. In Adapter Port, if you needed to open a port, enter the port number for the Mobile Status service to listen on. This port number should be identical to the one that you've opened in the firewall.

    2. In Adapter Context, enter /

      If you need to receive mobile presence for more than one customer on the same public IP address and port, you can set up different contexts for each customer, in the mobile network operators’ self-service portal. In this case, enter the same context value in Adapter Context and in the self-service portal.

    3. In Company/VPN ID, enter the value supplied by TDC.

      If you use TDC, and you don't know your VPN ID, contact TDC to get it. You can't test the mobile presence configuration without it.

    4. In Telenor Hostname and in Telenor Port, enter the host name and port for the Telenor presence server, supplied by Telenor. For more information see Installations- og konfigurationsvejledning Telenor Mobile Unified Communications Service

    5. Select Use HTTPS

    6. In User and Password, enter the credentials supplied by the mobile network operator.

  8. Click Save.

On the Zylinc Windows application server, do the following:

  1. In the Deployment Manager menu, select Deployment > Installation
  2. In Installers, select Mobile Presence and click Install Applications
  3. In the Deployment Manager menu, select Deployment > Windows Services
  4. In Deployed Services, select Mobile Presence
  5. In Change Startup Type, select AutomaticDelayed, and click Change Startup Type
  6. In Deployed Services, select Mobile Presence
  7. Click Start Services

  1. Log in to ZyDesk as a normal end user

    Why shouldn't I log in as an administrator?Closed If you log in to ZyDesk as the special user administrator@zylinc.com on Zylinc releases older than 6.5, you can view presence from mobile phones, but you can’t view presence from Cisco or BroadWorks or Skype for Business, unless you change the agent’s operator device to the same PBX type as the presence you need to view. This is because administrator@zylinc.com uses Internal or None as Operator Device, and you can only view presence from users on the same PBX type (operator device) as the agent, if use the old ZyDesk version.

  2. Make a search that returns a user that have a mobile phone that supports presence

  3. Check that a mobile presence icon is visible in the Mobile status column

  4. Call the mobile phone, and check that mobile status changes to busy

  1. Open the latest mobile presence log file in a text editor (see Open latest log file from specific Zylinc module

  2. If your organization needed to open a port in the firewall, search for lines that contain the text New client connection from. Such lines in the log file indicate that the Zylinc Mobile Status service has received incoming connections to the port that it listens on.

    If you can’t find such lines, it indicates that something prevents events from being sent from the mobile network operator presence service to the port that the Mobile Status service listens on. Check your organization's firewall configuration, and check with the mobile network operator that mobile presence events are sent to the specified IP address and port.

  3. Search for lines that contain the text Sending Zylinc presence info to server. Such lines in the log file indicate that the Mobile Status service has received valid mobile presence data from the mobile network operator, and that the data has been sent to the Zylinc presence service (ZyGo). The log file line will also contain an XML representation of the actual data.

    If you can’t find such lines, search for lines that contain the words error or exception. Such lines will often contain information about what caused the error.