Document Name iPECS Cloud, UCE and iPECS ONE port usage  Author  Jess Portugal Publish Date 28/03/2019 Version 1.2

 

1. Version Information 

 

Date Author  Update Information Version 28/03/2019 Jess Portugal 1st Draft 1.0 04/02/2020 Jess Portugal 2nd Draft 1.1 11/01/2020 Jess Portugal  3rd Draft 1.2 07/06/2021 Robert Smith 4th Draft 1.3 28/01/2022 Simon Smith 5t Draft 1.4 23/06/2023 Simon Smith Restructure 1.5

 

 

2. Document Purpose & History

 

This document is intended to provide the reader with information on iPECS Cloud, UCE and iPECS ONE port usage 

 

 

iPECS Cloud and iPECS ONE port usage 

 

 

iPECS Cloud:

 

IPKTS and SIP phonesThe table below shows the flows that are used for LIP and SIP phones (this includes IP DECT). The flows are all client server, with the cloud platform acting as server. This makes it easier for the flow to traverse NAT router in most setups. The information is provided where customers want to operate a locked down environment where the devices (phones and iPECS One) can only communicate with the destinations required.

 

Each flow is bi-directional, but the LIP or SIP phone originates the connection, making the protocols capable of passing through NAT with no port forwarding requirements.

 

You can obtain the Server IP addresses for the Reseller Portal, Customer -> Customer Information

 

The  flows are described below. The 1st packet in each flow is described. Src Dev and Src Port originate the flow (the client), the Dst Dev and Port receive the 1st packet (the server). 

Protocol

Transport

Src Dev

Src Port

Dst Dev

Dst Port

IPKTS Signalling1

UDP/TCP

LIP Phone

5588

IPKTS Relay

5588

IPKTS Voice

UDP

LIP Phones

8002-8005

IPKTS Relay

30000-60000

1000i Provisioning

TCP

LIP Phones (1000i only)

Any

IPKTS Relay

7871

SIP 5060

UDP/TCP

SIP Phone

5060

SIP Signalling

5060

SIP Speech2

UDP/TCP

SIP Phone

Any

SIP Media

16384-27384

IP-DECT Central Directory

TCP

IP-DECT Base

Any

IPKTS Relay

7878

 

1 – When using UDP, the udp session timer on NAT routers, should be set to 60 seconds.

2 – Includes IP-DECT, the exact algorithm used to determine source port varies by specific phone.

 

IP Addresses used for 3rd Party SIP Devices:

3rd party SIP Signalling: 185.110.180.13
3rd party SIP Media : 185.110.180.149
 

IPECS One

The IPECS One server are reached by URL, currently each iPECS One URL will resolve to a single IP address, so this can be used in any firewall rules.

IP address for iPECS ONE will depend on the server you need to connect to:

https://one1.ipecs-cloud.co.uk – 185.110.180.73 

https://one2.ipecs-cloud.co.uk – 185.110.180.74 

https://one3.ipecs-cloud.co.uk – 185.110.180.75

https://one4.ipecs-cloud.co.uk – 185.110.180.164 

 

The call control and web api used by IPECS One is TCP (Web Socket) based, so is much friendlier for NAT routers. The IPECS One client uses Web RTC NAT traversal technologies (ICE, TURN and STUN) to perform NAT traversal, so once again no port forwards should be necessary for IPECS One

Protocol

Transport

Src Dev

Src Port

Dst Dev

Dst Port

Web & Websocket

TCP

iPECS-One PC and Mobile

Any

IPECS One Server

443

Voice/Video/App Sharing

UDP

iPECS-One PC and Mobile

Any

IPECS One Server

49152 – 65535

 

UCE Ports:

9080 TCP
9443 TCP
9701 TCP
5222 TCP
5060 UDP
16384-26383 UDP

 

Please note if you are a VSP/ SP the IP addresses may differ from what is highlighted here. If you have any questions please contact support.

“