Capacity and Limitations

Device Board Interface

Table 1. Capacity and limitations in Device Board Interface
Signaling Protocols	2 Mbit HDLC (long signal format, i.e. up to 300 bytes payload) 128 Kbit UART short format 128 Kbit UART long format UART protocol with slow signaling is not supported

Digital Trunk Interface

Table 2. Capacity and limitations in Digital Trunk Interface
Number of PRIs	8 ISDN PRI:s. Each 30B+D or 23B+D

Fax Relay T.38

In the following table, settings are fixed and are not configurable.

Table 3. Fax support and settings
Max T.38 sessions	128 simultaneous sessions if only running T.38 sessions in MSP.
Supported fax signals	V.21, V.25 and V.8 (Preamble/flags, CED, Ans and ANSam)

Table 4. T.38 Fax Configuration data used in MGU
TCF Procedure	Remote TCF, the TCF data is passed across the IP network in the same way as any other page data.
Redundancy	Allow ECM faxes in T.38.
No maximal speed limit negotiated	No speed limit.
Redundancy count for T30 messages	Total 7 counts.
Redundancy Count Page Data	Total 7 counts.
ECM faxes in T38	ECM Allow.
T.38 Packet loss concealment	No T.38 Packet loss concealment
Small ECM packet handling	Enable small T4 ECM packet instead of waiting for complete HDLC ECM frame.

Keycode Receiver

Table 5. KR resources
KR latency	In serial connection KR adds a delay of about 65 ms per default, but can be tuned down to about 18 ms at the cost of performance (see below). In parallel connection KR adds no delay.
Max KR resources	400 simultaneous KR if DetectionDelay = 40 ms, and only running KR resources in MSP 114 simultaneous KR if DetectionDelay = 18 ms, and only running KR resources in MSP
Start KR session	Less than 15 ms
Stop KR session	Less than 10 ms

Keycode Sender

Table 6. KS resources
Max KS resources	400 simultaneous KS
DTMF/MFC duration	1-255 ms, and continuous (=0)
DTMF/MFC level	0 to -36dBm0

Tone Sender

Table 7. TS resources
Max TS resources	400 simultaneous TS.

Recorded Voice Announcement

Table 8. Recorded Voice Announcement
RVA download time (unloaded MGU)	This time is dependent not only on MGU load, but also on network and web-server conditions.
RVA activation time (unloaded MGU)	To activate media files takes about 12s/Mbyte before they are active and can be used. For a maximum file size installation, installation time is about 6-7 minutes. During activation, RVA feature is disabled (RVA sessions will be rejected by MGU).
Max RVA sessions	195 simultaneous sessions if only running RVA in MSP
Supported file formats	- RIFF (little-endian) data, WAV audio, ITU-T G.711 A-law, mono 8000 Hz - RIFF (little-endian) data, WAV audio, ITU-T G.711 µ-law, mono 8000 Hz
Max number of RVA files	250
Max file size	60 minutes (approximately 30Mbyte)
Start RVA session	To allocate and start a media player (RVA) session takes less than 50 ms
Stop RVA session	To stop a media player session takes less than 50 ms

Multi Party

Table 9. MP Resources
Max MP resources	64 simultaneous MP resources
Max participants per MP resource	16 (Note: The MX-ONE Service Node limits the number of participants to 8)

Voice over IP

Note: Only symmetric Voice traffic are supported. Receiving and sending channel must use the same type of codec and packetization interval.

Table 10. Supported codecs and packetization intervals
Codec	Packetization intervals
G.711 a-law/µ-law	5, 10, 20, 30, 40, 50 and 60 [ms]
G.729a	10, 20, 30, 40, 50, 60, 70 and 80 [ms]
G.729ab	10, 20, 30, 40, 50, 60, 70 and 80 [ms]
Clear channel	5, 10, 20, 30, 40, 50 and 60 [ms]
RTP/RTCP port range	Configurable from MX-ONE Service Node. Default range if not set is 50000..57768
Crypto Suites (SRTP)	The following encryption / authentication combos are supported: 1) AES-128 / HMAC-SHA1-80 2) AES-128 / HMAC-SHA1-32 3) AES-128 4) AES-192 / HMAC-SHA1-80 5) AES-192 / HMAC-SHA1-32 6) AES-256 / HMAC-SHA1-80 7) AES-256 / HMAC-SHA1-32
Fax PassThrough	Switching on detection of CNG, CED ,V.21 flags, ANSam ANS/, COT V8bis, V22 and Bell 103 tones.
Max RTP sessions	Up to 290 sessions if only RTP is running in MSP, but depends heavily on settings and speech characteristics. Note: With "clear channel" max RTP sessions could be up to 404, but lower with other codecs. See Table 11 for a few examples.
Time to establish new RTP session	To allocate and start a new RTP session takes less than 30 ms
Time to close RTP session	To stop and free RTP session takes less than 20 ms

In the following table, Max RTP sessions for various settings STD = Standard EC with default settings, DFE = Dual Filter EC with default settings (EC type and settings is configurable through TDM MO)

Table 11. Max RTP sessions for various settings
Codec	Echo Canceller	Crypto suite	Packetization Interval
Codec	Echo Canceller	Crypto suite	10 ms	20 ms	30 ms
G.711	STD	-	140	240	290
G.711	DFE	-	140	200	230
G.711	STD	6	72	122	150
G.711	DFE	6	66	108	136
G.729ab	STD	-	114	134	154
G.729ab	DFE	-	114	110	124
G.729ab	STD	6	50	82	106
G.729ab	DFE	6	52	78	100

Note: In density figures above it has not been included the effect of using "Silence Suppression", which when enabled might lower DSP load and thus increasing channel density.

In table below, the latency on VoIP channels is stated for different codecs and packetization intervals. Latency includes the path from TDM to VoIP encoding to packet network to decoding to TDM, i.e. GW to GW VoIP delay. Latency has been measured with fixed jitter buffer of same size as packetization interval. These are minimum latencies to be expected in GW to GW calls, and external packet network and endpoints might increase latency. Also use of encryption increases latency slightly.

Table 12. End to End VoIP delays with fixed jitter buffer equals packetization interval
Codec	Packetization Interval
Codec	5 ms	10 ms	20 ms	30 ms
G.711	25	35	45	Not measured
G.729ab	N/A	58	58	Not measured

IPsec Standards

Table 13. IPsec
Protocols	IKEv1, AH, ESP, IP Compression
CBC ciphers	AES-128 (default), AES-256, DES, 3DES, Blowfish, Twofish, Serpent
Digests	SHA1 (default), SHA2 (SHA-256, SHA-384, SHA-512), MD5
Diffie Hellman groups	1, 2 (default), 5
IP Compression	Deflate

Network Redundancy

Table 14. Network Redundancy fail over-time
Fail over time (Subnet Redundancy)	Fail over time will be approximately 8 seconds
Fail over time (Switched redundancy)	Fail over time is about 1 second when the active link fails. Fail over occurs also if the subnet's gateway is not reachable and no control traffic packets are received on the LAN port. The fail over time in these case will be approximately 8 seconds.

Factory Default Parameters

Table 15. Factory default parameters
Parameter	Value
eth0_ip	192.168.1.2/24
eth1_ip	192.168.2.2/24
eth2_ip	192.168.1.3/24
eth3_ip	192.168.2.3/24
default_route	192.168.1.1
default_route1	192.168.2.1

Speech Switching Time in case of GARP or NA

The following table indicates about the switch time of ongoing speech to another MAC-address when a Gratuitous ARP (Address Resolution Protocol) and/or unsolicited Neighbor Advertisement is received. The time also depends on the current load of the MGU.

Table 16. Speech Switching Time
No Calls	Switch Time (ms)
1	20
2	20
5	30
10	40
20	60
40	110
60	150
80	210
100	290