[Contents][Prev][Next][Index][Report an Error]
Voice Services Configuration Guidelines
The Adaptive
Services (AS) and MultiServices PICs support the compressed Real-Time
Transport Protocol (CRTP) on the lsq-fpc/pic/port interface type. This
enables voice over IP (VoIP) traffic to use low-speed links more effectively,
by compressing the 40-byte IP/User Datagram Protocol (UDP)/RTP header
down to from 2 to 4 bytes in most cases.
 |
Note:
J-series Services Routers use the link services
(ls) interface to configure CRTP with MLPPP or PPP logical
interface encapsulation. For more information, see Configuring Compressed RTP with MLPPP Encapsulation and Configuring Compressed RTP with PPP Encapsulation.
J-series Services Routers also support VoIP routing
through the Avaya TGM550 media gateway module. This is a separate
product from the adaptive services suite and is not supported on M-series
and T-series routing platforms. For more information, see the J-series Services Router Advanced WAN Access Configuration Guide.
|
For link services IQ interfaces (lsq)
only, you can configure CRTP with multiclass MLPPP (MCML). MCML greatly
simplifies packet ordering issues that occur when multiple links are
used. Without MCML, all voice traffic belonging to a single flow is
hashed to a single link in order to avoid packet ordering issues.
With MCML, you can assign voice traffic to a high-priority class,
and you can use multiple links. For more information about MCML support
on link services IQ interfaces, see Configuring Link Services and CoS.
Link services IQ interfaces use a bundle configuration.
For more information, see Link Services IQ Interfaces Configuration Guidelines and Configuring Multilink and Link Services Logical Interface Properties.
|
Note:
On LSQ interfaces, all multilink traffic
for a single bundle is sent to a single processor. If CRTP is enabled
on the bundle, it adds overhead to the CPU. Because T3 network interfaces
support only one link per bundle, make sure you configure a fragmentation
map for compressed traffic on these interfaces and specify the no-fragmentation option. For more information, see Configuring Delay-Sensitive Packet Interleaving and Configuring Fragmentation by Forwarding Class.
|
To configure voice services interface properties,
include the following statements on the network interface:
- [edit interfaces]
-
interface-name {
-
encapsulation (frame-relay | ppp);
-
-
unit logical-unit-number {
-
encapsulation (atm-mlppp-llc | frame-relay-ppp);
-
compression-device lsq-fpc/pic/port;
-
-
dynamic-call-admission-control {
-
activation-priority value;
-
bearer-bandwidth-limit value;
- }
-
-
family mlppp {
-
bundle lsq-fpc/pic/port.logical-unit;
- }
- }
- }
To configure voice services interface
properties, include the following statements on the services interface:
- (lsq | ls)-fpc/pic/port {
-
-
unit logical-unit-number {
-
encapsulation mlppp;
-
-
family inet {
-
address address;
- }
-
-
compression {
-
-
rtp {
-
f-max-period number;
-
maximum-contexts number <force>;
-
-
port {
- minimum port-number;
- maximum port-number;
- }
-
queues [ queue-numbers ];
- }
- }
-
fragment-threshold bytes;
- }
- }
Voice services do not require a separate
service rules configuration.
This chapter contains the following sections:
[Contents][Prev][Next][Index][Report an Error]
