on 06-09-2009 02:33 AM
A: CVP 7.0 with SIP does not support post call survey feature, but it is something we are looking to add for the future release.
A: No. Since OAMP Server component does not involve in any call processing so it should not affect call processing.
A: No. Each CVP Server can only be managed or controlled by single OAMP Server.
A: Unfortunately the Cisco Voice Browsers (IOS VXML Gateways) do not render TDD to VoiceXML. Therefore CVP relies on sending a call to a partner when TDD is selected (usually the TDD tone is played as a wave file).
A: At the time of writing of this document, (June 25, 2008) CVP 7.x is supported in labs for VMWare. For production systems, we are evaluating VMWare, but it is premature to say if - and when it would be supported.
A: Communication between CVP Voice Browser (VXML GW) and VXML Server can be made secure (HTTPS) to enhance the security. However you have to understand and consider its sizing impact as well
A: Unified CVP supports upgrade of its product components from CVP 3.1 SR2, CVP 4.0(X) and CVP 4.1 to Unified CVP 7.0. But when planning upgrade, it is not enough to consider only upgrading the CVP components. There are dependencies all across the solution thay you must be aware of too.
A: The CVP 7.0.2 release should have these UUI enhancements.
A: All VRU types that existed before Type 10 will continue to work. Type 10 was created as a convenience to configure CVP in ICM. You can change them at a later date.
Keep in mind, if you are changing to Type 10, all your CVP Network VRUs must be Type 10, including the one assigned to your ICM instance. And your Communication Manager (Call Manager) Network VRU should not be assigned a type.
A: Currently (August 29th 2008) the CVP Studio 7.x is not capable of doing so. But in future release you would be able to play video IVR menus from VXML script without going to ICM script and calling ICM microapps. In a future version of Studio it will be easier to make ICM scripting and VXML Server work together to create video IVR and other types of complex scripts across platforms.
A: On the AS5400XM, you do not need to specifically buy any VoiceXML licenses. They come bundled with IOS. However, on the ISRs (2800s and 3800s) you would still need to buy VoiceXML port licenses.
A: Although CVP is a B2BUA, currently G.722 and iLBC codes are not supported by CVP.
A: Lets take an example here. If CUBE is to be used as an SBC on Cisco 3845 to handle flow-thru or flow-around calls only (no vxml), then it can support upto 750 sessions.
(This number increased to 3000 for AS5350XM/AS5450XM in flow-around mode).
If CUBE is to be used as an SBC for flow-thru or flow-around calls AND is to handle vxml sessions for CVP, one must use the same sizing
information in the current CVP SRND that is available for regular voice gateways.
CUBE will be limited to the maximum number of simultaneous vxml sessions/calls as outlined in the CVP SRND for the particular situation and
hardware platform.
For Cisco 3845 the maximum number of SBC calls and VXML sessions it can support in co-resident fashion is 230.
A: Yes it is correct. If a customer configure CVP to dial agent with only 3 digit extension, call will fails and he might see following error:
user.microapp.input_type=D >>STATE: isTabular=false isWriteable=true cursor=-1 dnis=8761 version=CVP_7_0
labeltype=1 label=232 calllegid= >>STATE: isTabular=false isWriteable=false cursor=-1
366: 10.20.20.60: May 15 2009 13:07:34.557 +0300: %CVP_7_0_IVR-3-UNKNOWN_EXCEPTION:
CALLGUID=4D1C19283D4B11DE85EE0022915807EC Processing exception: java.lang.StringIndexOutOfBoundsException:
String index out of range: 4 (ConnectTask.runTask)
java.lang.StringIndexOutOfBoundsException: String index out of range: 4
at java.lang.String.substring(String.java:1765)
at com.cisco.cvp.ivr.ConnectTask.generateResponse(ConnectTask.java:129)
at com.cisco.cvp.ivr.CallTask.runTask(CallTask.java:263)
at com.cisco.cvp.ivr.CallTask.run(CallTask.java:313)
at com.cisco.ccbu.infra.threads.CCBURunnable.run(CCBURunnable.java:35)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Agent might go in to reserved state but the call will not be delivered.
A: The answer is Yes. Although the filed on the CVP Call Server says put the max agent DN lenght, you have to put the exact length of the agent otherwise you might receive following error message
335: 192.168.45.131: Oct 21 2009 16:00:12.540 -0700: %CVP_7_0_SIP-3-SIP_CALL_ERROR: CALLGUID = 7954366D100001242B74447E3F57D27D LEGID = 7b872b80-adf1927c-24-b62da8c0 - [INBOUND] - DIALOGUE_FAILURE from ICM Router sends 500 rejection to call. [id:5004]
A: CVP has always been designed to be OS independent, thus not testing with any specific operating system features. As such, we cannot state AD is supported, as we have never tested in an AD environment, and do not have any guidelines regarding deployment models or what to expect.
A: OAMP does not restrict the number of call servers that can be connected to one reporting server. It depends on the amount of load (aka number of messages at any give time) that is going to be pumped in a reporting server. Typically most customer deployments limit the amount to about 4 callservers per one reporting server.
A: Estimated wait time (EWT) is being calculated on the time that callers spend in queue awaiting an available agent. Based on history of Calls in queue and how quickly agents are answering calls determines the EWT value. The call never leaves the queue, so the position in queue remains the same. We are using the EWT to determine if it is time to re-establish the caller leg of the call.
A: In Courtesy Callback, the call is being maintained in the ICM queue and is still using license ports. It is just as if the customer were waiting in queue and listening to queue music, only we have disconnected the caller leg and will re-establish the customer leg when their time in queue comes about. The call remains in the same position of the ICM queue. That said the call could potentially be disrupted by failures of the ICM, gateway and VXML Servers just as it could if it were a live call in queue.
A: http://docwiki.cisco.com/wiki/Unified_CCE_Software_Compatibility_Matrix_for_9.0(x)
hello
I have one question regarding Agent Extension Length . You have mentioned that " If a customer configure CVP to dial agent with only 3 digit extension, call will fails and he might see error ( mentione above)
But in reality we have tested in our LAB & we faced no issue , secondly one of my customer is also using Agent Legth 3 and its working fine .
CVP version 7.x
ICM 7.5
Please reply
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: