Skip to main content
Skip table of contents

ipSCAPE Minimum Operating Specifications

Overview

Workstation

OS Windows 7 or later, with Intel Core i3 CPU or equivalent and a minimum of 4GB RAM

Supported web browsers include:

Security software/firewalls disabled or correctly configured not to interfere with ipSCAPE traffic.

Clear access for traffic on the following ports between workstations and the ipSCAPE systems:

  • TCP 80 (HTTP), 443 (HTTPS)

  • UDP 16384-32768 (RTP)

  • TCP/UDP 5060 (SIP, unencrypted), 5061 (SIP, encrypted)

Processor (CPU) load on workstations must be generally low (<10%)

LAN Infrastructure

Switched Ethernet network or a strong and consistent WiFi connection, with sufficient overhead (20%) maintained to accommodate any spike in usage

Firewalls, routers, intrusion detections systems and other LAN infrastructure must not interfere in any way with ipSCAPE traffic.

Clear access for traffic on the following ports between workstations and the ipSCAPE systems:

  • TCP 80 (HTTP), 443 (HTTPS)

  • UDP 16384-32768 (RTP)

  • TCP/UDP 5060 (SIP, unencrypted), 5061 (SIP, encrypted)

Load on LAN infrastructure (e.g. firewalls, routers, etc.) must be monitored and managed for performance.

Latency across the LAN (from workstation to gateway; i.e. NTU/router) must be consistently <3ms with 0% packet loss.

Data

Network connectivity for data (web) traffic between customer site and ipSCAPE systems.

Network quality between customer workstations and the ipSCAPE systems to be:

  • <1% packet loss

  • <150ms latency (one-way)

  • <30ms jitter (average one-way)

Bandwidth capacity of 40kbps per agent must be maintained for access to the ipSCAPE application.

No filtering or proxying devices to be in place on ipSCAPE related traffic.

Clear access for traffic on the following ports between workstations and the ipSCAPE systems:

  • TCP 80 (HTTP), 443 (HTTPS)

  • UDP 16384-32768 (RTP)

  • TCP/UDP 5060 (SIP, unencrypted), 5061 (SIP, encrypted)

Voice

Network connectivity for voice traffic between customer site and ipSCAPE systems

Network quality between customer workstations and the ipSCAPE systems must be:

  • <1% packet loss

  • <150ms latency (one-way)

  • <30ms jitter (average one-way)

Bandwidth capacity of 100kbps per agent end-to-end - this is exclusive of any other applications that use the network (CRMs, softphones), especially applications with high bandwidth requirements (such as video conferencing)

The customer is responsible for ensuring that this capacity level is maintained; i.e. provisioned in advance of adding additional agents

ipSCAPE recommends that voice traffic be transferred over a dedicated link to ensure consistent voice quality

Connected endpoints must support SIP protocol and G.711 audio codec


1. ipSCAPE Web Connect Softphone

In addition to the requirements above:

  • The network where the agent is connected, firewall and/or NAT servers are compliant with RFC4787 https://tools.ietf.org/html/rfc4787 ). This means the NAT rules and filtering MUST be carefully reviewed by the customer network administrators. Non-compliant networks may have the following behaviour for the RTP media stream:

    • There is one way audio, usually, the customer can hear the agent but not the opposite.

    • Call is completely mute.

  • The customer network MUST allow access (in the firewall or in any other access control device) from/to the SBC network

  • Agent workstations MUST have speaker and microphone capabilities, and the browser MUST be able to support these devices with access permissions


2. Microsoft Teams Phone

In addition to the requirements above:


3. Bria Softphone

In addition to the requirements above, see Bria Bandwidth Requirements


4. Additional Notes

  • Data and voice traffic can share the same link, but a minimum of 20% capacity overhead must be maintained at all times

  • The customer must retain sufficient IT capability to ensure correct diagnosis of local technical issues prior to escalating to ipSCAPE


5. Terminology

Term

Meaning

Jitter

A measure of the time interval between data packets as they reach their destination. A low degree of jitter indicates a relatively steady stream of data packets.

Packet loss

Data, such as a VoIP transmission, is sent over the Internet in the form of packets. Packet loss occurs when some of these packets do not arrive at their destination. For each packet loss, a small amount of speech is cut out. If the degree of packet loss is high, conversation audio can sound very choppy, delayed, or unclear.

Latency

Network latency describes a delay that takes place during communication over a network (including across the Internet between a user or Agent and ipSCAPE servers).

Bandwidth

The maximum amount of data that can pass through the network at any given time

Disclaimer

ipSCAPE will not provide support services or recognise SLAs for platform performance where the customer does not meet these minimum requirements.

JavaScript errors detected

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

If this problem persists, please contact our support.