Scenario: LA, NYC and SF will have 256K PVC frame-relay circuits to the customer's HQ in Upstate, NY (768K PVC.) They want to do data and voice over each PVC. Each branch office will have a new 1760 router, and there will be a 2600 at HQ. Occasionally, the branch offices will want to call each other, although most of the calling will be between HQ and the branch offices. We tried to sell the customer an IP telephony solution (Call Manager and IP phones), but they have opted instead for small Nortel keysets at the branch offices and a PBX and HQ. The PBXs at each office will connect to E&M cards in the routers, for tie-line functionality.
Question: should I use a Vo/FR or Vo/IP over Frame solution?
I think that in the above case, Vo/IP over Frame is the way to go, but I don't have a strong argument one way or the other. Can you make a suggestion?
I agree with the VoIP over Frame for it's relative simplicity and resource conservation. You're citing smaller routers, and most likely, they're running with baseline DRAM. Remember that all these queueing strategies and other such processes (on top of "basic" routing) all require DRAM and processor resources--in these smaller implementations, those items tend to be less abundant than in a 3660 or other higher end router. I'd imagine that a simple policy route raising IP precedence to 5 on the VOIP traffic, or even better (from a Keep It Simple and Small perspective) would be to include the IP precedence 5 line in your voice-port config so the precedence is set at the time the packet is created. In most cases, that's all it takes. Don't go for a 20-pound sledge when a simple claw hammer will do the job.
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...