Network Requirement
- Use the VoIP-jitter entity on Device1 and detect the network transmitting VoIP packets from Device1 to Device3.
Network Topology
Figure 3–4 Networking of configuring the VoIP-jitter entity
Configuration Steps
Step 1: Configure VLAN and add the port to the corresponding VLAN. (Omitted)
Step 2: Configure the IP address and route of the interface, making Device1 communicate with Device3. (Omitted)
Step 3: Configure ntp and synchronize the clock.
#Configure Device3.
|
Device3#config terminal
Device3(config)#ntp master
|
#Configure Device1.
|
Device1(config)#ntp server 192.0.0.2
|
#View that Device3 becomes the clock server successfully and prompt that the clock is synchronized.
|
Device3#show ntp status
Current NTP status information
Clock is synchronized, stratum 8, reference is 127.127.8.10
reference time is D4321EF4.7BBBBB68 (08:01:56.483 Wed Oct 24 2012)
|
#View that Device1 becomes the clock client successfully, prompt that the clock is synchronized and display the server address.
|
Device1#show ntp status
Current NTP status information
Clock is synchronized, stratum 9, reference is 192.0.0.2
reference time is D43222C1.91110F31 (08:18:09.566 Wed Oct 24 2012)
|
Step 4: Configure responder on Device3 as the responder end.
#Configure Device3
|
Device3(config)#rtr enable
Device3(config)#rtr responder
|
Step 5: Configure the VoIP-jitter entity on Device1 and add the attribute parameters.
#Configure Device1.
|
Device1#config terminal
Device1(config)#rtr enable
Device1(config)#rtr 1 jitter
Device1(config-rtr-jitter)#set dest-ipaddr 192.0.0.2 dest-port 1234 g711alaw source-ipaddr 110.1.0.1 source-port 1234
Device1(config-rtr-jitter)#number-of-history-kept 255
Device1(config-rtr-jitter)#exit
|
#View the entity parameter.
Device1#show rtr entity 1
----------------------------------------------------------
ID:1 name:Jitter1 Created:TRUE
*********************type:JITTER**************************
CreatedTime:WED OCT 24 16:02:32 2012
LatestModifiedTime:WED OCT 24 16:02:58 2012
Times-of-schedule:0
Entry-state:Pend
TargetIp:192.0.0.2 targetPort:1234
Codec:G.711 A-Law Packet-size:172 Packet-number:1000
Packet-transmit-interval:20(ms)
frequency:60(s)
SourceIp:110.1.0.1 Soure-port:1234
TimeOut:50000(ms)
Alarm-type:none
Threshold-of-dsDelay:5000(ms) direction:be
Threshold-of-dsJitter:6000(ms) direction:be
Threshold-of-dsPktLoss:200000000 direction:be
Threshold-of-sdDelay:5000(ms) direction:be
Threshold-of-sdJitter:6000(ms) direction:be
Threshold-of-sdPktLoss:200000000 direction:be
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-mos:10000000 direction:be
Threshold-of-icpif:100000000 direction:be
Number-of-history-kept:255
Periods:1
Status:DEFAULT
----------------------------------------------------------
The result shows that the entity parameters are consistent with the configuration.
Status:DEFAULT indicates that the entity status is DEFAULT.
Step 6: Schedule the defined VoIP-jitter entity and define the attribute parameters of the scheduling.
#Configure Device1.
|
Device1(config)#rtr schedule 1 entity 1 start now ageout 100 life 600 repeat 10
|
Step7: Check the result.
Device1#show rtr entity 1
------------------------------------------------------------
ID:1 name:Jitter1 Created:TRUE
*********************type:JITTER****************************
CreatedTime:WED OCT 24 16:02:32 2012
LatestModifiedTime:WED OCT 24 16:06:02 2012
Times-of-schedule:3
Time-of-last-schedule:WED OCT 24 16:08:29 2012
Entry-state:Transmit
TargetIp:192.0.0.2 targetPort:1234
Codec:G.711 A-Law Packet-size:172
Packet-number:1000
Packet-transmit-interval:20(ms)
frequency:60(s)
SourceIp:110.1.0.1 Soure-port:1234
TimeOut:50000(ms)
Alarm-type:none
Threshold-of-dsDelay:5000(ms) direction:be
Threshold-of-dsJitter:6000(ms) direction:be
Threshold-of-dsPktLoss:200000000 direction:be
Threshold-of-sdDelay:5000(ms) direction:be
Threshold-of-sdJitter:6000(ms) direction:be
Threshold-of-sdPktLoss:200000000 direction:be
Threshold-of-rtt:9000(ms) direction:be
Threshold-of-mos:10000000 direction:be
Threshold-of-icpif:100000000 direction:be
Number-of-history-kept:255
Periods:1
Status:REACHABLE
---------------------------------------------------------------
Entry-state:Transmit indicates that the entity is being scheduled.
Status:REACHABLE indicates that the entity status is reachable and the network from Device1 to Device3 transmits the VoIP packets normally.
#View the history record contents.
Device1#show rtr history 1
--------------------------------------------------------------
ID:1 Name:Jitter1 CurHistorySize:3 MaxHistorysize:255 History
recorded as following:
WED OCT 24 16:08:46 2012
SdPktLoss:0 ,DsPktLoss:0 ,Rtt:185 (ms),
SdDelay:14 (ms),DsDelay:178 (ms),SdJitter:8 (ms),DsJitter:183 (ms),
Mos:5.000000 ,icpif:0.000000
WED OCT 24 16:07:45 2012
SdPktLoss:0 ,DsPktLoss:0 ,Rtt:14 (ms),
SdDelay:16 (ms),DsDelay:7 (ms),SdJitter:10 (ms),DsJitter:13 (ms),
Mos:5.000000 ,icpif:0.000000
WED OCT 24 16:06:46 2012
SdPktLoss:0 ,DsPktLoss:0 ,Rtt:17 (ms),
SdDelay:16 (ms),DsDelay:9 (ms),SdJitter:11 (ms),DsJitter:13 (ms),
Mos:5.000000 ,icpif:0.000000
-------------------------------------------------------------------
In the history records, record the uni-directional packet loss, turnaround delay, uni- directional delay, and uni-directional jitter of each scheduling.
-
Before configuring the VoIP-jitter entity, we need to configure the NTP service to realize the network clock synchronization and configure the rtr responder command at the destination end as the responder. Note that if the clock is not synchronized or not configuring the responder end, the scheduling result is wrong.
Switch
.png){kind=icon}
.png){kind=logo}
