Ports used by Chronicall

Chronicall Port Numbers

This article contains the default port numbers used by Chronicall. Instructions on changing these can be found below.

 In v3.10, we have consolidated our ports in use so 9082, 9087, 9093, 9094, and 9096 have all been consolidated. (Note: This is only on the host chronicall machine, disregard for nodes.)

Inbound (Listening) Ports

  • TCP Port 9080 – Used by the Chronicall server to communicate with web clients

    • Also accepts inbound connections from the Recording Library service

  • TCP Port 9081 – On a dedicated Recording Library server, this port is used by the Recording Library service to listen for inbound connections from the Chronicall server. The Recording Library then relays recordings to web clients

    • This port can be changed in the Recording Library section of System Settings

  • TCP Port 9082 – Used by Realtime on Chronicall 3.95 and earlier

    • Consolidated into TCP Port 9092 on later versions

    • When the Realtime interface is open in a web client, this port is used.

  • TCP Port 9087 - Dashboard Chat Port.

  • TCP Port 9092 - Used by Realtime on Chronicall 3.10 and up

  • TCP Port 19080 - Used by Dashboards

    • Chronicall Desktop connects to this port from an end-user PC

  • TCP Port 80 and 443 - Used by Chronicall and Avaya Call Reporting for CCAC and WebRTC

  • TCP Port 5060 & UDP Port 6970 - Used by Active Recording for SIP Message Port & RTP Frames
    • Note: Multimedia/Contact Service may not be able to connect to the ACR service if the SIP Message Port is changed in the IPO

  • TCP Port 9089 (Avaya CM) - Used by Chronicall to acquire CDR data

    • Also known as the "Remote Port" on CM, this can be modified on both Chronicall and the CM if need be

  • TCP Port 450 (Avaya CM) - Used by Chronicall to listen for T-link data

  • TCP Port 1050 (Avaya CM) - Used by Chronicall to listen for Unencrypted T-Link data

  • TCP Port 5022 (Avaya CM) - Used by Chronicall to acquire Station, Agent, Hunt Group, VDN, Vector, and Dial plan data via the AES/SMS

  • TCP Port 5000 (Cisco UCM) - Used by Chronicall to monitor Unity Events

  • TCP Port 2789 & 2749 (Cisco UCM) - Used by Chronicall to monitor phone-based JTAPI events on the CUCM

  • TCP Port 12028 (Cisco UCM) - Used by Chronicall to receive events from the UCCX

Outbound Ports

  • UDP Port 69 (IP Office) – Used to request agent and group information from IP Office

    • This information is required before Chronicall can begin logging data

    • This port is defined by Avaya, and is used to pull users and groups from the IP Office, even if they have migrated to TCP based Devlink3

  • UDP Port 50794 (IP Office) – Used to request an event stream from IP Office for the Monitor connection.

  • TCP Port 50797 (IP Office) - Devlink connection port

  • TCP Port 50796 (IP Office) - Devlink + TLS encryption

  • TCP Port 9081 – The Chronicall server uses this port to communicate with the Recording Library service on the dedicated Recording Library server

  • TCP Ports 80 and 443 – Used to request license information from Xima Software's servers

  • TCP Port 9095 - Used by client applications (Agent Dashboards) to connect to the Multimedia Server for license pull & current Agent Dashboard statuses

    • Also replaces 9080 for Dashboard Chat when using Multimedia

  • TCP Port 450 (Avaya CM) - Used by Chronicall to listen for T-link data

  • TCP Port 1050 (Avaya CM) - Used by Chronicall to listen for Unencrypted T-Link data
  • TCP Port 5022 (Avaya CM) - Used by Chronicall to acquire Station, Agent, Hunt Group, VDN, Vector, and Dial plan data via the AES/SMS

Internal (Localhost) Ports

  • TCP Port 5432 – Used by the Chronicall Database (versions 3.1 and older)

  • TCP Port 9086 – Used by the Chronicall Database (versions 3.2 and newer)

  • TCP Ports 9083, 9084, and 9085 – Used by the Tomcat web server for various functions

  • TCP Ports 9090, 9091 - Used by Orient Database in Chronicall 3.12.6 and earlier

Ports used for SSL/HTTPS Proxy (nginx)

  • TCP Port 80
  • TCP Port 443
  • TCP Port 9443
    • TCP Port 8443 on versions 4.2.10 and above

*Note: For more information on troubleshooting these ports, please see our article for Troubleshooting SSL/TLS (HTTPS) Connection.

Changing Chronicall's Ports

Chronicall uses a number of TCP and UDP ports to communicate on the network. It is strongly recommended that you do not change these ports unless instructed to do so by Xima support.

However, it may be necessary to change the default ports if another application on the server is already using them.

For example, many Avaya application servers, along with IP Office Server Edition 8.1 and newer, use port 9080, one of Chronicall's default ports, for a different purpose. (This means that Chronicall will be unable to use that port.) Telling Chronicall to use port 9090 instead will solve this issue. These ports can be changed within Chronicall's System Status.

If you are unable to access the GUI (perhaps because the required ports are already in use) you will need to take the following steps:

Windows

These instructions assume that Chronicall has been installed in its default location:

 Program Files(x86)/Xima Software/Chronicall
  • Chronicall (4.0 and later)

    1. Stop the Chronicall service

      1. See Stopping and Starting Chronicall Services for more information

    2. Navigate to 

      • Program Files(x86)/Xima Software/Chronicall

    3. Edit the settings.xml file

    4. Change the line that reads setting key="webserver.port" value="9080" to setting key="webserver.port" value="9090"

    5. Save and exit

    6. Start the Chronicall service
  • Also, perform this step for Chronicall (3.12.5 and earlier)
    1. Stop the Chronicall service
    2. Navigate to  
      • Program Files(x86)/Xima Software/Chronicall/tomcat/conf

    3. Edit the server.xml file

    4. Search through the text to find Connector port="9080" and change it to Connector port="9090"

    5. Save and exit.

    6. Start the Chronicall service.

If you also have Recording Library installed, you will need to take a few more steps.

  1. Stop the Recording Library service.

  2. Navigate to 
    • Program Files(x86)/Xima Software/Chronicall/recording library

  3. Edit the settings.txt file in that directory.

  4. Change the line that reads CHRONICALL_SERVER_PORT=9080 to CHRONICALL_SERVER_PORT=9090

  5. Save and exit.

  6. Log in to Chronicall

  7. Open the Admin (System) > System Settings menu, and expand the Recording Library section

  8. Change the Chronicall Server Port to 9090

  9. Click Save.

  10. Start the Recording Library service.

Linux

These instructions assume that Chronicall has been installed in its default location:

 /var/lib/Xima Software/Chronicall
  • Chronicall (4.0 and later)

    1. Stop the Chronicall service

    2. Edit the settings.xml file

      • E.g.

        • nano /var/lib/Xima\ Software/Chronicall/settings.xml

    3. Change the line that reads setting key="webserver.port" value="9080" to setting key="webserver.port" value="9090"

    4. Save and exit

    5. Start the Chronicall service
  • Also, perform this step for Chronicall (3.12.5 and earlier)
    1. Stop the Chronicall service

    2. Edit the server.xml file

      • nano /var/lib/Xima\ Software/Chronicall/tomcat/conf/server.xml

    3. Search through the text to find Connector port="9080" and change it to Connector port="9090"

    4. Save and exit.

    5. Start the Chronicall service

If you also have Recording Library installed, you will need to take a few more steps.

  1. Stop the Recording Library service

  2. Edit the settings.txt file

    • E.g. 
      • nano var/lib/Xima\ Software/Chronicall/recording\ library/settings.txt

  3. Change the line that reads CHRONICALL_SERVER_PORT=9080 to CHRONICALL_SERVER_PORT=9090

  4. Save and exit.

  5. Log in to Chronicall

  6. Open the Admin (System) > System Settings menu, and expand the Recording Library section

  7. Change the Chronicall Server Port to 9090

  8. Click Save

  9. Start the Recording Library service

Was this article helpful?
12 out of 12 found this helpful

Table of Contents

    Environment

    Operating System

    PBX System

    • Avaya IP Office

    Chronicall Version