RTP/TCP header compression

From: Brown, Patrick (NSOC-OCF} (PBrown4@chartercom.com)
Date: Mon Aug 04 2003 - 21:34:24 GMT-3


While putting tcp header compression in PASSIVE mode on BOTH sides of the
Frame Relay interface, compression was still occuring. I was under the
impression that one side had to be active and on had to be passive. If both
sides are waiting for an compress packet in passive mode, they will never
receive one. But the output shows different. If anyone can provide some
insight on this I will be greatful.

Topology:
(r4)---------------(r1)

r4
interface Serial0/0
 ip address 132.15.74.4 255.255.255.224
 encapsulation frame-relay
 frame-relay map ip 132.15.74.1 401 broadcast tcp header-compression passive
 no frame-relay inverse-arp
 frame-relay lmi-type cisco
 
r4#sh ip tcp header-compression
TCP/IP header compression statistics:
 DLCI 401 Link/Destination info: ip 132.15.74.1
  Interface Serial0/0: (passive, compression on)
    Rcvd: 82 total, 71 compressed, 0 errors
             0 dropped, 0 buffer copies, 0 buffer failures
    Sent: 87 total, 74 compressed,

r1
interface Serial0/0
 ip address 132.15.74.1 255.255.255.224
 encapsulation frame-relay
 frame-relay map ip 132.15.74.4 104 broadcast tcp header-compression passive
 no frame-relay inverse-arp

R1#sh ip tcp header-compression
TCP/IP header compression statistics:
 DLCI 104 Link/Destination info: ip 132.15.74.4
  Interface Serial0/0: (passive, compression on)
    Rcvd: 87 total, 74 compressed, 0 errors
             0 dropped, 0 buffer copies, 0 buffer failures
    Sent: 82 total, 71 compressed,
             2485 bytes saved, 2616 bytes sent
             1.94 efficiency improvement factor

Thanks,

Patrickb



This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:52 GMT-3