Hiya, I have installed the SIP CS and linked it to router in a lab enviornment. Overall the documentation for the product is pretty good, so by all means read the manual.
SIP CS acts like a TServer and switch combined in a Pure Voip environment, but if you want to bring analog voice into the platform you will need hardware to do the compression/decompression.
SIP CS will act like a normal TServer, excect it interfaces with the proxy instead of a switch. The SIP CS will create TEvents for the activity in the proxy and pass them to softphones, router and statserver and pass handle requests back to the proxy.
Stream Manager is another product that is used to bridge the caller with IVR applications and voice treatments. I wasn’t able to install this product or play around with it much, but it’s part of the solution of interfacing SIP CS with GVP.
There is the document “SIP Server 7.5.0 - GVP Integration - Behind Mode” describing integration of GVP with SIP Server 7.5 available on Genesys Technical Support website (Knowledge Base / IP TServers).
to Rakesh: I have experience with such integration - GVP 7.2 with CCM 4.x via H.323.
We already did the installation GVP Core components and H.323 Session Manager. We configured the settings related to GVP with Cisco IP Media Gateway and CCM in GVP. But we need help to configure in Cisco IP Media gateway and Cisco Call Manager side.
The only supported variant of integration between GVP and Cisco CallManager (CCM) is when GVP is configured in “In-Front” mode. In that variant the calls are routed to GVP by CCM and not by media gateway (MG). Sample call flow of an incoming call is following:
Call comes to MG
MG sends the information about the call to CCM
CCM send a response to MG where the call has to be routed e.g. to GVP
On CCM side you have to define GVP as H.323 gateway and create a route pattern to route inbound calls from selected numbers to GVP directly. GVP doesn’t support the feature “Inbound fast start” so you have to disable in the definition of H.323 gateway. And that’s all.
Of course, there are several other requirements (GVP has to use the same codec as used in Cisco environment, network connectivity between MG, GVP and agent’s phones etc.) but I consider these as “basic” ones if we’re talking about VoIP.
The last note - please check the release notes of H.323 Session Manager for required version of GVP Core component because the support of integration with CCM via H.323 protocol wasn’t available in the first releases. And I have experience that it really didn’t work…
Route patterns are “Cisco things” and I don’t consider myself to be the right person to teach someone how to configure CCM… I would suggest you to ask someone responsible for your CCM to help you with creating the route patterns. It could be risky to create a new route pattern without having the knowledge of existing patterns and numbering plan because it could affect existing call routing…
You can find more information about the route patterns in “Cisco CallManager Administration Guide” which is download-able from Cisco website.