Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Customer Voice Portal Installation

 

 

 

 

Prerequesites

 

  • The CVP server hostname should not contain any hyphen
  • Arrange for CVP license
  • Regional and language options should be set to English

 

Pict1.gif

 

  • Text services and input languags options should be set to English (United States) - US

 

Pict2.gif

 

  • Only one Ethernet connection should be active on the CVP machine

 

Pict3.gif

 

  • Install Network Monitor Tools, Simple Network Management Protocol, WMI SNMP Probe Provider, and WMI Windows Installer Provider

 

CVP Call Server, Operation Console and Media Server Installation

 

In our laboratory deployment, CVP Call Server, Operation Console and Media Server are collocated on the same machine.

 

Follow the screen shots below to complete the installation

 

  • Select the options that you want to install

 

Pict4.gif

 


  • Add the name and other related information

Pict5.gif

 

 

  • Enable the services automatically after the installation is done

 

Pict6.gif

 

  • For this lab installation support tools are disabled but in production deployment, they are highly recommended and desired

 

Pict7.gif

 

CVP Component Configuration

 

There are several components that needs to be configured before CVP can operate properly. They are

 

  • CVP Medial Server Configuration
  • CVP Call Server Configuration

 

This document is not including CUPS (For SIP Proxy functionality), TTS and VXML Server.

 

CVP Media Server Configuration

 

This setup used Microsoft IIS as the web server to host the media files.

 

  1. Enable read permission to the directory where .wav files are saved.
  2. Make sure anynymous access is enabled and the built-in IIS User is assigned.

 

CVP Call Server Configuration

 

Before configuring CVP call server, it should be important to know little bit about the setup and SIP call flows. In this setup since we are not using CUPS, we will use Call Flow Model#1. Notice that these call flows are valid for Type 10 VRU only. Also notice that cid is actually correlation id that is a numerical value.

 

Call Flow Model#1 without CUPS

 

 

 

PSTN Originated Calls

 

CUCCE Pilot Number Caller dials 541-764-1400 from PSTN

 

Processing at Ingress GW Ingress gateway sends this call to CVP Call Server

 

Processing at CVP CVP will send the call to CUICM via a static SIP route as a new route request

 

Routing Client CVP is the routing client

 

Label Returned to CVP by CUICM 541-764-1401+cid

 

Processing at CVP CVP Call Server sends this label 541-764-1401+cid to VXML-GW

 


Processing at VXML-GW VXML-GW has an incoming dial-peer configured that invokes the bootstrap tcl service. Now a sequence of VXML communications happen between the VXML GW and CVP IVR Service
This communication happens via MicroAppas.

 


Processing at CVP At this point CVP sends the same label 541-764-1401+cid to CUICM

 


Processing at CUICM If agent is available then CUICM sends a new label which is basically the Agent’s IP Phone extension to CVP to informs thatVXML-GW resources are engaged

 


Processing at CVP CVP has a static SIP route configured that would send call to agent’s ip phone

 

CUCM Originated Calls

 

CUCCE Pilot Number IP Phone caller dials CTI route point number 541-764-3000
Routing Client CUCM is the routing client
Label Returned to CUCM by CUICM 541-764-1402+cid

 


Processing at CUCM CUCM receives ths label and send the call to CVP Call Server
Processing at CVP CVP receives this label and send it to CUICM as a new route-request.

 


Routing Client Notice that now CVP is the routing-client and controls the Call States. CUCM is out from the picture.

 


Processing at CUICM CUICM receives its own generated label again and knows that loop is complete. And then generates a new label 541-764-1401+cid and sends to CVP

 

 

 

Processing at CVP Call Server send this label 541-764-1401+cid to VXML-GW

 

Processing at VXML-GW VXML-GW has an incoming dial-peer configured that basically invokes the bootstrap tcl service
Now a sequence of VXML communications happen between the VXML GW and CVP IVR Service.
This communication is called MicroAppas.

 

Processing at CVP At this point CVP sends the same label 541-764-1401+cid to CUICM to inform thatVXML-GW resources are engaged

 


So once you understand the high level overview of the call flow, it will be easy to understand the static routes that needs to be added to CVP Call Server.

 

Local SIP Static Routes in CVP

 

5417641400
CUICM: 192.168.93.130
Route request to CUICM

 


91919191
VXML-GW:192.168.93.1
To play ringtone

 


92929292
VXML-GW:192.168.93.1
To play error tone

 

5417641401
VXML-GW:192.168.93.1
Label+cid sent to VXML-GW to invoke bootstrap service

 


5417644…
CUCM:192.168.93.100
For CVP to dial agent ip phone extension

 

CVP Operation Console Server

 

CVP Operation Console Server provides web based front end to configure different components in CVP environment.

 

CVP Call Server General Settings

 

Pict8.jpg

 

 

Pict9.jpg

CVP Call Server ICM Configuration

 

Pict10.jpg

 

CVP Call Server SIP Configuration

 

Default information was used and no fields were modified in the following picture

 

Pict11.jpg

 

CVP Call Server Local SIP Static Routes

 

Pict12.jpg

 

VXML and Ingress Gateway Configuration

 

In this setup, same router is used as an ingress as well as VXML gateway. Notice that due to VXML compatibility issues, all Cisco IOS versions are not approved. In this lab setup c3725-adventerprisek9-mz.124-15.T1.bin is used.

 

Copy following files to VXML Gateway flash memory

 

bootstrap.tcl
bootstrap.vxml
cvperror.tcl
CVPSelfService.tcl
CVPSelfServiceBootstrap.vxml
survivability.tcl
handoff.tcl
ringtone.tcl
recovery.vxml
holdmusic.wav
ringback.wav
pleasewait.wav
critical_error.wav
en_0.wav

 

Configuration

 

cvp-vxml-gw#sh run
!
hostname cvp-vxml-gw
boot system flash flash:c3725-adventerprisek9-mz.124-15.T1.bin
enable password lab
ip cef
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
signaling forward unconditional
h323
emptycapability
h225 id-passthru
h245 passthru tcsnonstd-passthru
sip
bind control source-interface FastEthernet0/0.93
bind media source-interface FastEthernet0/0.93
rel1xx disable
min-se 360
header-passing
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
!
voice class h323 1
h225 timeout setup 3
!
application
service new-call flash:/bootstrap.vxml
paramspace english language en
paramspace english index 0
paramspace english location flash:
paramspace english prefix en
!
service cvp-survivability flash:survivability.tcl
paramspace english index 0
paramspace english language en
param alert-timeout 20
paramspace english location flash
paramspace callfeature med-inact-det enable
param setup-timeout 7
paramspace english prefix en
!
service ringtone flash:ringtone.tcl
paramspace english index 0
paramspace english language en
paramspace english location flash
paramspace english prefix en
!
service recovery flash:/recovery.vxml
paramspace english language en
paramspace english index 0
paramspace english location flash:
paramspace english prefix en
!
service cvperror flash:cvperror.tcl
paramspace english language en
paramspace english index 0
paramspace english location flash
paramspace english prefix en
!
service takeback flash:survivability.tcl
paramspace english language en
paramspace english index 0
paramspace english location flash
paramspace english prefix en
!
service bootstrap flash:/bootstrap.tcl
param gtd_format1 ascii
param gtd-field0 noa
paramspace english language en
param gtd-attribute0 rgn
paramspace english index 0
param gtd-field1 dat
paramspace english location flash
param gtp-instance0 1
param gtd-attribute1 fdc
paramspace english prefix en
!
!
vxml version 2.0
!
controller T1 ½
description Incoming and outgoing T1 PRI Trunk
framing esf
linecode b8zs
pri-group timeslots 1-24
!
interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/0.1
description Admin VLAN
encapsulation dot1Q 1 native
ip address 36.36.36.1 255.255.255.0
!
interface FastEthernet0/0.93
description Voice, Data and Server VLAN
encapsulation dot1Q 93
ip address 192.168.93.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.93.1
!
interface Serial1/2:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
no cdp enable
!
router ospf 7
log-adjacency-changes
network 36.36.36.0 0.0.0.255 area 0
network 192.168.93.0 0.0.0.255 area 0
!
ip http server
no ip http secure-server
!
voice-port 1/2:23
!
dial-peer voice 1400 voip
description TO CVP CALLSERVER
preference 1
max-conn 2
destination-pattern 5417641400
session protocol sipv2
session target ipv4:192.168.93.3
dtmf-relay rtp-nte
codec g711ulaw
ip qos dscp cs3 signaling
no vad
!
dial-peer voice 1401 voip
description From CVP Call Server. To match label generated for CVP RC
service bootstrap
session protocol sipv2
incoming called-number 5417641401T
dtmf-relay rtp-nte
codec g711ulaw
ip qos dscp cs3 signaling
no vad
!
dial-peer voice 1 pots
incoming called-number .
direct-inward-dial
!
dial-peer voice 3000 voip
description PSTN->CCM
destination-pattern 5417644...
session protocol sipv2
session target ipv4:192.168.93.100
dtmf-relay rtp-nte h245-signal h245-alphanumeric
codec g711ulaw
ip qos dscp cs3 signaling
no vad
!
dial-peer voice 2 pots
description calls from PSTN to CUCCE pilot number will match this first
service cvp-survivability
incoming called-number 5417641400
direct-inward-dial
!
dial-peer voice 9292 voip
service cvperror
session protocol sipv2
incoming called-number 9292T
dtmf-relay rtp-nte h245-signal h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 9191 voip
service ringtone
session protocol sipv2
incoming called-number 9191T
dtmf-relay rtp-nte h245-signal h245-alphanumeric
codec g711ulaw
no vad
!
line vty 0 4
password lab
login
!
cvp-vxml-gw#

 

CVP VXML Server

 

Untill this point we have configured CUICM and CVP in generatl. There is another component called VXML Server that play vital role in the solution, although not required.

 

Few things to remember

 

 

 

  • Voice Browser is also called VXML browser
  • VXML browser is basically the Cisco IOS VXML Gateway
  • VXML gateway browser pages from CVP VXML server (Like FireFox browser browse web pages from an Apache web server)
  • Every communication process between the VXML browser and Voice Application has to be initiated by the VXML browser as a request to the VXML server.

 





Comments
New Member

First of all Thanks for publishing the contact center configuration in such details.

I am looking to use either a Cisco 3825 or a Cisco 2801 as an ingress/VXMML gateway. Is there any criteria for minumum requirements for a router to be used as an ingress and VXML gateway?

Hi Rashid,


Thanks a lot or your comments, rating the doc and appreciating the efforts here.

Coming back to your question, the criteria is mentioned in the CVP SRND

In table 7-2 for example in the third column, you will see the sessions it can support while co-residing the VXML and ingress gateway functionalities on the same router/gateway.

Please let me know if it doesn't answer your question.


Thanks,
Shahzad

New Member

Thanks for your answer. Should have found the answer myself, but next time I will try to do my homework before asking a question.

Rashid

This is an excellent guide, but noticed that a few pictures aren't showing up.  Can you guys confirm that all the picture locations are correct please?

Thank you.

New Member

Hello,

the PDF version doesn't work...

The following message appears:

"System Error
We're sorry but a serious error has occurred in the system".

Regards.

Cisco Employee

I agree - I am able to reproduce this issue with PDF conversion.

I think this error has something to do with the content - other documents are converting to PDF just fine.

I created a copy of the file and ran it through html tidy, but that mangled it.   I managed to recreate the formatting, and the images.  You can find the alternate document here -

https://supportforums.cisco.com/docs/DOC-21986.  It does convert to PDF at least....and now this one does too....

New Member

Anton,

I think that the correct link for Pict4.gif is:

http://cisco-support.hosted.jivesoftware.com/servlet/JiveServlet/downloadImage/1455/Pict4.gif

Could you correct the issue, please?

Thanks and regards.

Sorry folks for the inconvenience. The document was originally published on supportwiki.cisco.com site and since then it has moved to two different publishing systems. The migration team did fantastic job in moving large number of documents but still there are issues left here and there.

I am going to fix the images in this document. Thanks for your feedback and pointers.

Regards,

Shahzad

15977
Views
24
Helpful
8
Comments