How To Deploy Pep; Configuring Ip Aggregates; Hardware Configuration - Vocality V200 User Manual

Vocality User Manual
User Manual for V200
Valid for V08_08.02 or V08_48.02
On most Vocality products a maximum of 32 concurrent TCP sessions may be handled
by PEP, with any additional connections passing through transparently without benefit.
Any PEP sessions that naturally time out are cleared and the PEP applied to new ones.
The High-Speed CPU card can provide up to 255 concurrent sessions.

5.12.2 How to deploy PEP

PEP is fully transparent – no changes, modifications, proxies, or settings required to end
user devices. PEP's efficient architecture delivers higher performance and scalability.
V200s with a High Speed CPU card will find the feature is enabled as standard – they do
not need a Feature Key.
The figure below shows how TCPGw settings should then be set up, using the IP >
Networks menu, to allow PEP to operate.
Figure 5-37 TCPGw settings to enable PEP
Note: You will need to enable TCPGw on both ends of the IP virtual circuit (0:10
etc) and the associated physical interfaces (ENET1/ENET2).
5.13

Configuring IP aggregates

You can configure an IP connection as an aggregate link. The IP aggregate enables use
of an IP connection as a normal aggregate link, to multiplex voice and data between
two Vocality units. Whilst the voice is carried over an IP link, this is not industry
standard Voice over IP (VoIP).
Since there is no clock relationship maintained over an ethernet connection, a clocking
protocol has been designed to enable Vocality units at either end of an IP aggregate
link to maintain clock synchronisation. One unit is assigned as clock master and the
other unit changes clock to stay in synchronisation with the master unit. When using IP
aggregate mode, your unit assumes that it will be provided with the required Quality of
Service (QoS) from the network, including Committed Information Rate (CIR) measured
in kbps. If this QoS is not provided then packets may be dropped on the aggregate
link. Due to aggregation of multiple services over the aggregate, loss of a single packet
may impact several services. With default settings, the aggregate link itself will not drop
unless there have been no packets received for at least 30 seconds. As with any IP
network there will be instantaneous values of IP packet size that will be greater than the
CIR, in which case the network access device will be expected to handle these, by use of
a buffer.

5.13.1 Hardware configuration

You need IP connectivity between the units at either end of an IP aggregate tunnel.
Page 74 of 114