Skip to Content
EIS
VoIP Services

Technical requirements

Local network, firewalls, protocols, NAT, codecs and bandwidth required

To ensure the proper functioning of the EIS SIP Trunk service in the DSS system, prepare the local network and firewall according to the requirements shown on this page.

Local network

Wiring

The LAN must be wired with cables Category 5 or higher, so as to ensure a proper bandwidth for VoIP traffic. Lower category cablings can cause instability and performance problems.

Traffic separation and priority

It is advisable to separate the traffic of VoIP devices from generic computer traffic. You can adopt one of the following solutions:

  • create a LAN dedicated exclusively to VoIP devices;
  • configure VLAN and priority mechanisms to assign voice traffic a greater priority than ordinary data traffic.

Separation reduces the impact of congestion, delays and latency changes on call quality.

Firewall requirements

The firewall must allow traffic to the following services and networks.

Disable the SIP ALG on firewalls and routers. The manipulation of SIP messages carried out by this function can prevent recording, altering signaling or causing monodirectional audio.

EnablementValue
DNS SIPsip.teameis.it
Datacenter 1217.28.136.0/24
Datacenter 2194.76.135.0/24
Doors SIP5060 and 5061, TCP and UDP
Ports RTPFrom 10000 a 50000, UDP

Configure the rules in the direction required by the client’s architecture and limit the sources and destinations to the necessary networks.

Supported RFC

Protocol or functionSupport
SIP — RFC 3261Supported
SDP — RFC 2327Supported
Expedited Forwarding (EF) for RTP — RFC 3246Supported
Assured Forwarding (AF31) for SIP — RFC 2597Supported
DTMF — RFC 2833Supported, preferred method
Offer/Answer — RFC 3264Supported, preferred method
SIP — RFC 2543Supported
Privacy and identity — RFC 3323 and RFC 3325Supported
Diversion Header — RFC 5806Supported

NAT Traversal

The DSS system supports NAT Traversal: a telephone system can also make calls when using a private IP address behind NAT instead of a public address.

NAT Traversal is not supported for trunks IP to IP.

Codec supported

Codec or ProtocolSupport
G.711Supported
G.729Supported
T.38Supported

Call Band

  • for a call G.711, consider 168 Kbps;
  • for a call G.729, consider 50 Kbps;
  • for fax is supported protocol T.38, with fallback in pass-through G.711.

Determine connectivity on the maximum number of contemporary calls, considering both incoming and outbound traffic and maintaining a margin for other network services.

Content transferred and reorganized by the page Technical Requirements EIS SIP Trunk on EIS Wiki.