CVP: using the Gatekeeper and the SIP Proxy, why? VXML gateway and the ingress gateway communication?
I am actually keep asking with my self, why to use gatekeeper or SIP proxy when deploying the CVP solution, why not to use the Call Manager? Is it because that the concept built on SIP and H323 so call manager can not handle these kind of operations as call manager is supporting MGCP?
From the other side, what kind of trunk or protocol of communication method is used between the ingress gateway and the VXML browser?
Re: CVP: using the Gatekeeper and the SIP Proxy, why? VXML gatew
The main reason is not all who deployed ISN/CVP in the past use Call Manager as the PBX.
CVP is a powerful solution that covers many deployment scenarios. Its ability to integrate with legacy switches has been very important in the past, and although as we move forward, these types of deployments will probably become fewer, the independence of CVP on Call Manager remains a cornerstone of the design.
I'm glad it was built that way. Look at some of the other deployment models (like Call Director) in the CVP Guide.
It's not because Call Manager supports MGCP - you don't need to have any MGCP gateways in your Call Manager deployment. You could have all H.323 gateways and manage the dial plan on the gateways with a gatekeeper. Or use SIP.
The ingress gateway does not talk to the VXML server - the VXML gateway does.
In a branch office design, these are one and the same; but that's not the fundamental architecture. The IOS on the VXML gateway runs a voice browser (I guess you could call this a VXML browser). It uses HTTP to send and receive information (VXML documents) from the VXML server - whether this be the CVP Call Server or an external VXML server (like what was brought in-house with the Audium acqusition - the Cisco CVP VXML Server).
You can theoretically deploy SIP solution without SIP Proxy, CVP SRND guide is saying SIP Proxy is optional. But I think everyone is using SIP Proxy as it provides additional features that CM does not.
2. Gatekeeper is a required component for H.323 deployment, that's how CVP was designed.
You can read in more detail in the CVP SRND guide, section Typical H.323 Unified CVP Call Flow
I also advise you to read the complete CVP SRND guide. All your answers are in there.
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...