As a very new person to the Cisco VOIP world, I am looking to educate myself. It's not so much of what I need, but what people's experiences are so I can determine if there is more that I can do to achieve more and give my end users a better solution to their needs.
Does this make sense to you?
Therefore, I am looking for real experiences and the pros and cons of H.323 vs. MGCP.
Donna as java said, the need will dictate the solution. With MGCP, your dialplan is on the Call Manager. I prefer to build MGCP gateways, however certain features are not always available and h323 becomes a requirement. With H323, your reliance will be on the gateway. Your dialplan will and your codec definition reside on your gateway. If you have multiple h323 gateways, dialplan management can be troublesome. As an example, caller-id on an fxo line would require H323.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...