Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trafic Shapping for VOFR

Status
Not open for further replies.

leprikon

IS-IT--Management
Jan 29, 2003
20
US
I have a hub and spoke setup with a few agents in remote branches (no more than 4). Each branch has a 128k Port with a 64K cir.

We are testing SIP phones at one of the branches. I am getting a second PVC for that remote site (64k) and bumping the port up to 192k. How do i tell both routers that SIP traffic should go over the new PVC but data should go over the old one. Is it only by host/phone or by protocol (5060) ??
 
Hi Leprikon, the way to do this is via a route map on the router, apply it to the Ethernet interface. The route map selection criteria could be made on source IP address (the phone) or on destination port. The route map can be configured to set the destination by either next hop IP or by sending the selected traffic out a specific interface.

You then need to apply suitable traffic shaping as you would normally with a frame-relay network.

Lot of words, here's one I prepared earlier.

interface FastEthernet0/0
ip address 10.5.0.2 255.255.255.0
no ip redirects
ip policy route-map PBX

interface Serial1/0.123 point-to-point
description *** PVC to London
bandwidth 1024
ip address 172.16.36.13 255.255.255.252
traffic-shape rate 2048000 256000 0 1000
traffic-shape adaptive 1024000
traffic-shape fecn-adapt
frame-relay interface-dlci 123


interface Serial1/0.159 point-to-point
description Voice PVC to London
bandwidth 2048
ip address 172.16.36.5 255.255.255.252
traffic-shape rate 2048000 256000 0 1000
traffic-shape adaptive 1024000
traffic-shape fecn-adapt
frame-relay interface-dlci 159

route-map PBX permit 10
match ip address PBX
set interface Serial1/0.159

ip access-list standard PBX
permit 10.5.0.5
permit 10.5.130.99

In this example the IP addresses in the ACL PBX are the Ip addresses of the local phones. The policy map splits these out and send them over the specified interface.

Inorder to stop routing sending data over that link I made the voice PVC passive under the routing process.



 
hrm, looks easy enough. what does the London side show ? Any chance you can shoot me over your configs so i can compare them to mine (which currently has 3 lines per interface and not utilizing any ACL) ?

:)
 
The configuration for the remote site is pretty much a mirror of that above. All its doing is looking for packets from the (local) source address specified in the ACL PBX, and directing them out of the specified interface.
 
Qwest is telling me i don't need a seperate DLCI on the host side .. just the Leg. How would this work if i want to send all voice over a seperate pvc ?
 
I dont understand what you mean.

The config example I posted has 2 PVC's, one data, one voic. You could do it using one PVC with suitable QoS, although I've never done that. I suppose it depends on the cost of the PVC versus the set up costs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top