We have some customers that wish to start using IP telephony over GRE tunnels. We are currently baselining some plans to implement a network wide QoS. However, the use of GRE is going to mask the true nature of a packet as it passes over intermediate routers. This will present a problem in setting up the QoS.
Has anyone tackled a similar problem? What QoS have you used?
You can permit GRE packets in the access-lists but the problem is that you can't recursively look into the GRE packets to see if they are UDP voice streams, or telnet, or whatever.
However, if you have customers build 2 or more GRE tunnels, one of them specifically for voice traffic only, then you can permit GRE packets coming from and going to the network numbers they defined for that tunnel, and give it strict priority.
Note that if the links are relatively small (less than 768k) then you may also need to fragment the large data packets using FRF.12 if frame relay, or LFI if PPP on leased lines.
Thanks for the information. I've actually just found out that IP Precedence will automatically be re-created in a GRE header. If that is correct, then we should still be able to provide QoS mechanisms using that setting, thereby allowing us to use a single GRE tunnel.
If the IP packet's ToS is set in the GRE header ToS, then you would also have to beware of other data applications setting the ToS field. Many Windows-based applications now set the IP ToS field to nonzero values, some of them 5. This happens in both Microsoft applications and OS's such as IE 5.0 and higher, and Windows 2000. Evidence of this can be found by doing a Net search.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...