Home » Cisco Manuals » Bridges & Routers » Cisco 3825 » Manual Viewer

Cisco 3825 Software Configuration Guide - Page 174

The passive Keyword, The iphc-format Keyword, Support for Serial Lines, rtp header-compression

UPC - 746320981505

Add to My Manuals
Save this manual to your list of manuals

Page 174 highlights

ip rtp header-compression Appendix A Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference The passive Keyword By default, the ip rtp header-compression command compresses outgoing RTP traffic. If you specify the passive keyword, outgoing RTP traffic is compressed only if incoming RTP traffic on the same interface is compressed. If you do not specify the passive keyword, all outgoing RTP traffic is compressed. The passive keyword is ignored on PPP interfaces. PPP interfaces negotiate the use of header-compression, regardless of whether the passive keyword is specified. Therefore, on PPP interfaces, the passive keyword is replaced by the IPHC format, the default format for PPP interfaces. The iphc-format Keyword The iphc-format keyword indicates that the IPHC format of header compression that will be used. For PPP and HDLC interfaces, when the iphc-format keyword is specified, TCP header compression is also enabled. For this reason, the ip tcp header-compression command appears in the output of the show running-config command. Since both RTP header compression and TCP header compression are enabled, both UDP packets and TCP packets are compressed. The iphc-format keyword includes checking whether the destination port number is even and is in the ranges of 16,385 to 32,767 (for Cisco audio) or 49,152 to 65,535 (for Cisco video). Valid RTP packets that meet the criteria (that is, the port number is even and is within the specified range) are compressed using the compressed RTP packet format. Otherwise, packets are compressed using the less-efficient compressed non-TCP packet format. The iphc-format keyword is not available for interfaces that use Frame Relay encapsulation. Note The header compression format (in this case, IPHC) must be the same at both ends of the network. That is, if you specify the iphc-format keyword on the local router, you must also specify the iphc-format keyword on the remote router. The ietf-format Keyword The ietf-format keyword indicates that the IETF format of header compression will be used. For HDLC interfaces, the ietf-format keyword compresses only UDP packets. For PPP interfaces, when the ietf-format keyword is specified, TCP header compression is also enabled. For this reason, the ip tcp header-compression command appears in the output of the show running-config command. Since both RTP header compression and TCP header compression are enabled, both UDP packets and TCP packets are compressed. With the ietf-format keyword, any even destination port number higher than 1024 can be used. Valid RTP packets that meet the criteria (that is, the port number is even and is higher than 1024) are compressed using the compressed RTP packet format. Otherwise, packets are compressed using the less-efficient compressed non-TCP packet format. The ietf-format keyword is not available for interfaces that use Frame Relay encapsulation. Note The header compression format (in this case, IETF) must be the same at both ends of the network. That is, if you specify the ietf-format keyword on the local router, you must also specify the ietf-format keyword on the remote router. Support for Serial Lines RTP header compression is supported on serial lines using Frame Relay, HDLC, or PPP encapsulation. You must enable compression on both ends of a serial connection. A-42 Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide OL-15667-03

Section	Page
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide	1
Contents	3
Preface	7
Overview of the Cisco 3825 Mobile Wireless Edge Router	11
Introduction	11
RAN-Optimization Implementation	12
Cisco Abis and Iub Optimization over IP Implementation	12
Cisco GSM Abis Optimization over IP	13
Cisco Pseudowire Emulation Edge-to-Edge (PWE3)	14
Cisco Iub Optimization over IP	15
Intelligent Cell Site IP Services	15
Cell Site Points-of-Presence (POPs)	15
Cisco IOS Software Features	16
Software features for the RAN-O Implementation	16
Software Features	17
Redundancy Support	17
HSRP	17
Configuration Statements for CISCO-IP-RAN-BACKHAUL-MIB	18
MIB Support	20
Limitations and Restrictions	21
RAN-O Implementation Limitations and Restrictions	22
Hardware not Supported on the Cisco 3825 Router	22
UMTS Iub and GSM Abis Implementation Limitations and Restrictions	22
Hardware not Supported for UMTS Iub	22
Hardware not Supported for GSM Abis	22
New Features in Cisco IOS Release 12.4(16)MR2	23
Keyword ignore-vpi-vci Added to xconnect Command	23
New Features in Cisco IOS Release 12.4(16)MR1	23
Emulation of TDM Circuit via MPLS/IP (PWE3/TDM)	24
Structure-agnostic TDM over Packet (SAToP)	26
Structure-aware TDM CESoPSN	26
Transportation of ATM Service via MPLS/IP (PWE3/ATM)	27
Transparent Cell Transport Service/ATM Port Mode	27
ATM N-to-One VCC Cell Mode	27
ATM AAL5 CPCS-SDU Mode	28
ATM One-to-One VCC Cell Mode	28
Cell Packing	29
PVC Mapping	29
Transportation of ATM Service via L2TPv3	30
ATM Port Cell Relay Service	30
ATM VCC Cell Relay Service	30
ATM AAL5-SDU Mode	31
Cell Packing	31
PVC Mapping	32
Asymmetric PWE3	32
Ethernet over MPLS	33
VLAN Mode	33
Port Mode	33
PWE3 over MLPPP	34
PWE3 Redundancy	34
TDM PWE3 Redundancy	35
ATM PWE3 Redundancy	35
Ethernet PWE3 Redundancy	35
Maximum Number of Supported ATM Ports	36
ATM Cell Switching	36
New Features in Cisco IOS Release 12.4(16)MR	37
GSMmux-Global System for Mobile Communication (GSM) Abis Optimization over IP	37
UMTSmux-Universal Mobile Telecommunication System (UMTS) Iub Optimization over IP	37
UMTS Congestion Management Control	38
Inverse Multiplexing over ATM (IMA)	39
Permanent Virtual Circuit (PVC) Routing	40
Behavior Changes	42
UMTS QoS	43
Cisco IOS Software Basics	47
Getting Help	47
Understanding Command Modes	48
Undoing a Command or Feature	49
Saving Configuration Changes	49
Where to Go Next	49
First-Time Configuration	51
Understanding Boot Images	51
Understanding the Cisco 3825 Router Interface Numbering	51
Slot and Port Numbering	52
Setup Command Facility	53
Before Starting Your Router	53
Using the Setup Command Facility	54
Configuring Global Parameters	54
Completing the Configuration	57
Configuring the Cisco 3825 Mobile Wireless Edge Router in a RAN-O Solution with the Command-Line Interface	59
Before You Begin	60
Verifying the Version of Cisco IOS Software	60
Clocking Requirements for Cisco 3825 Router	60
Clock-Related Commands	61
Network-Clock-Participate Command	61
Network-Clock-Select Command	61
Clock Source Command	62
Example Configurations	63
Show Controller Command	63
Configuration Sequence	64
Summary of Steps	64
Configuring the Hostname and Password	64
Verifying the Hostname and Password	65
Configuring Gigabit Ethernet Interfaces	66
Configuring the GE Interface IP Address	66
Setting the Speed and Duplex Mode	66
Enabling the GE Interface	67
Configuring the Backhaul Links	67
Configuring the Card Type for the Cisco 2-port T1/E1-RAN	68
Configuring E1 Controllers	69
Configuring T1 Controllers	70
Configuring Network Clocking Support	72
Configuring Multilink Backhaul Interface	73
Creating a Multilink Bundle	73
Handling PFC and ACFC	74
Configuring PFC	74
Configuring ACFC	75
Enable Multilink and Identify the Multilink Interface	75
Enable Real-Time Transport Protocol (RTP) Header-Compression	76
Configuring the PPP Backhaul Interfaces	77
Extended Availability Drop and Insert (EADI)	78
Configuring GSM-Abis Links	78
Configuring UMTS Links	82
Configuring Redundancy	86
Redundant Cisco 3825 Routers	86
Standalone Cisco 3825 Router	91
Configuring for SNMP Support	91
Configuring Inverse Multiplexing over ATM (IMA)	95
Configuring PVC Routing (HSDPA Offload)	99
Configuring UMTS QoS	104
Creating a Class Map	105
Creating a Policy Map	105
Specify the Location of the Interface	106
Assigning a QoS Boilerplate to an Interface	109
Configuring UMTS Congestion Management Control	113
Configuring Satellite Support	116
Configuring Graceful Degradation	117
Saving Configuration Changes	119
Example Configurations	119
BTS/Node-B Configuration	119
BSC/RNC Configuration	123
Monitoring and Managing the Cisco 3825 Router	127
Enabling the Cisco 3825 Router for Remote Network Management	127
Show Commands for Monitoring the Cisco 3825 Router	129
Where to Go Next	131
Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference	133
Configuration Examples	269
Overview	269
Asymmetric PWE3 Configuration	270
Ethernet over MPLS-VLAN and Port Mode Configuration	283
PWE3 over MLPPP Configuration	289
PWE3 Redundancy Configuration	298
TDM over MPLS Configuration	304
ATM over MPLS Configurations	309
ATM over L2TPv3 Configuration	316
GSM Only Configuration	323
UMTS Only Configuration without IMA	327
Combined GSM and UMTS Configuration	331
GSM and UMTS with IMA Configuration	336
GSM and UMTS with IMA and PVC Routing (HSDPA Offload) Configuration	342
GSM Only Configuration via Satellite	348
GSM Congestion Management	351
UMTS Congestion Management	352

Match case Limit results 1 per page

A-42

Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide

OL-15667-03

Appendix A

Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference

ip rtp header-compression

The passive Keyword

By default, the

rtp header-compression

command compresses outgoing RTP traffic. If you specify

the

passive

keyword, outgoing RTP traffic is compressed only if

incoming

RTP traffic on the

same

interface is compressed. If you do not specify the

passive

keyword,

all

outgoing RTP traffic is

compressed.

The

passive

keyword is ignored on PPP interfaces. PPP interfaces negotiate the use of

header-compression, regardless of whether the

passive

keyword is specified. Therefore, on PPP

interfaces, the

passive

keyword is replaced by the IPHC format, the default format for PPP interfaces.

The iphc-format Keyword

The

iphc-format

keyword indicates that the IPHC format of header compression that will be used. For

PPP and HDLC interfaces, when the

iphc-format

keyword is specified, TCP header compression is also

enabled. For this reason, the

ip tcp header-compression

command appears in the output of the

show

running-config

command. Since both RTP header compression and TCP header compression are

enabled, both UDP packets and TCP packets are compressed.

The

iphc-format

keyword includes checking whether the destination port number is even and is in the

ranges of 16,385 to 32,767 (for Cisco audio) or 49,152 to 65,535 (for Cisco video). Valid RTP packets

that meet the criteria (that is, the port number is even and is within the specified range) are compressed

using the compressed RTP packet format. Otherwise, packets are compressed using the less-efficient

compressed non-TCP packet format.

The

iphc-format

keyword is not available for interfaces that use Frame Relay encapsulation.

Note

The header compression format (in this case, IPHC) must be the same at

both

ends of the network. That

is, if you specify the

iphc-format

keyword on the local router, you must also specify the

iphc-format

keyword on the remote router.

The ietf-format Keyword

The

ietf-format

keyword indicates that the IETF format of header compression will be used. For HDLC

interfaces, the

ietf-format

keyword compresses only UDP packets. For PPP interfaces, when the

ietf-format

keyword is specified, TCP header compression is also enabled. For this reason, the

ip tcp

header-compression

command appears in the output of the

show running-config

command. Since both

RTP header compression and TCP header compression are enabled, both UDP packets and TCP packets

are compressed.

With the

ietf-format

keyword, any even destination port number higher than 1024 can be used. Valid

RTP packets that meet the criteria (that is, the port number is even and is higher than 1024) are

compressed using the compressed RTP packet format. Otherwise, packets are compressed using the

less-efficient compressed non-TCP packet format.

The

ietf-format

keyword is not available for interfaces that use Frame Relay encapsulation.

Note

The header compression format (in this case, IETF) must be the same at

both

ends of the network. That

is, if you specify the

ietf-format

keyword on the local router, you must also specify the

ietf-format

keyword on the remote router.

Support for Serial Lines

RTP header compression is supported on serial lines using Frame Relay, HDLC, or PPP encapsulation.

You must enable compression on both ends of a serial connection.