Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Download This Guide
Examples: Configuring Voice Services
Configure voice services using a T1 physical interface and MLPPP bundle encapsulation:
[edit interfaces]
t1-0/2/0:1 {encapsulation ppp;unit 0 {family mlppp {bundle lsq-1/3/0.1;}}}
lsq-1/3/0 {unit 1 {encapsulation mlppp;family inet {address 10.5.5.2/30;}compression {rtp {f-max-period 100;queues [ q1 q2 ];port {minimum 16384;maximum 32767;}}}fragment-threshold 128;}}
Configure voice services using Frame Relay encapsulation without bundling:
[edit interfaces]
t1-1/0/0 {encapsulation frame-relay;unit 0 {dlci 100;encapsulation frame-relay-ppp;compression-device lsq-2/0/0.0;}}
lsq-2/0/0 {unit 0 {compression {rtp {f-max-period 100;queues [ q1 q2 ];port {minimum 16000;maximum 32000;}}}family inet {address 10.1.1.1/32;}}}
Configure voice services using an ATM2 physical interface (the corresponding class-of-service configuration is provided for illustration):
[edit interfaces]
at-1/2/0 {atm-options {vpi 0;pic-type atm2; # only ATM2 PICs are supported}unit 0 {vci 0.69;encapsulation atm-mlppp-llc;family mlppp {bundle lsq-1/3/0.10;}}unit 1 {vci 0.42;encapsulation atm-mlppp-llc;family mlppp {bundle lsq-1/3/0.11;}}}
lsq-1/3/0 {unit 10 {encapsulation multilink-ppp;}# Large packets need to be fragmented.# Fragmentation can also be specified per forwarding class.fragment-threshold 320;compression {rtp {port minimum 2000 maximum 64009;}}}
unit 11 {encapsulation multilink-ppp;}
fragment-threshold 160;[edit class-of-service]scheduler-maps {sched {# Scheduling parameters apply to bundles on the AS or Multiservices PIC.# Unlike DS3/SONET interfaces, there is no need to create# a separate scheduler map for the ATM PIC. ATM defines# CoS constructs under the [edit interfaces at-fpc/pic/port] hierarchy....}}
fragmentation-maps {fragmap {forwarding-class {ef {# In this example, voice is carried in the ef queue.# It is interleaved with bulk data.# Alternatively, you could use multiclass MLPPP to# carry multiple classes of traffic in different# multilink classes.no-fragmentation;}}}}
interfaces {# Assign fragmentation and scheduling parameters to LSQ interfaces.lsq-1/3/0 {unit 0 {shaping-rate 512k;scheduler-map sched;fragmentation-map fragmap;}unit 1 {shaping-rate 128k;scheduler-map sched;fragmentation-map fragmap;}}}
