Skip to main content
Skip table of contents

Network Requirements

Imagicle Emergency Notifications needs to communicate with Cisco UCM for various protocols and services. Please find below the full list of required ports/protocols in use:

Application

Source

Destination

Protocols/ports

Max RTT Delay

Synchronization and Hot Standby

Imagicle EN server

Imagicle EN server

http 80 or https 443, TCP 2010, http 8081 or https 8444

1000ms

AXL SOAP & Serviceability

Imagicle EN server

CUCM

https post 8443

500ms

Extension Mobility & Web Dialer SOAP

Imagicle EN server

CUCM

https post 8443

500ms

CTI (JTAPI)

Imagicle EN server

CUCM

TCP 2748 or TCP 2749 (Secured)

200ms

Reverse Lookup with External Call Control Profile

CUCM

Imagicle EN server

http post 80 or https post 443

200ms

EN Administration

PC workstation

Imagicle EN server

https get 443

1000ms

Page alerts

PC workstation

Imagicle EN server

http get 80 or https get 443

1000ms

Email notifications

Imagicle EN server

Customer’s email system/service

SMTP 25 or 587

500ms

Push text to IP Phone via http

Imagicle EN server

IP Phones

http post 80

1000ms

Push audio messages to IP Phones

Imagicle EN server

IP Phones

RTP 24576 - 32768

500ms

dry contact input

Dry Contact-to-IP device

Imagicle EN server

http 8081

1000ms

Windows Firewall Setting

Imagicle EN installation setup automatically creates exceptions within the Windows Firewall for the IP ports used by the different applications.

Anyway, it is highly recommended to keep Windows Firewall disabled, at least during the apps configuration and testing phase.

Other requirements

  • Please make sure Windows Date/Time is synchronized against a local NTP server, reachable from Imagicle EN instance.

  • Please keep IPv6 disabled.

Outdated components

Imagicle EN installation setup includes the following packages:

  • Postgresql 11.3

  • OpenSSL Libraries 1.0.2r

Both of them are not used by Emergency Notifications, so they can be safely disabled.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.