SIP Voicemail Manual Deployment
These steps apply to release 8.1.1.
Manual Deployment Task Summary Table
Complete the following steps to deploy Genesys SIP Voicemail manually.
Objective
|
Related procedures and actions
|
- Ensure that your system meets the deployment prerequisites.
|
See Deployment Prerequisites.
|
- Install SIP Voicemail Server.
|
Complete one of the following procedures, as per your operating system:
Installing SIP Voicemail Server (on Linux)
Installing SIP Voicemail Server (on Windows)
|
- Configure the SIP Voicemail Server Application.
|
Complete the following procedure:
Configuring the SIP Voicemail Server Application object
|
- Configure the Agent SIP Server Application.
|
On the Options tab, in the TServer section, configure the following options to activate the Message Waiting Indication (MWI) functionality:
- mwi-implicit-notify=true
- subscription-event-allowed=*
- dial-plan=<voicemail DN>
To use the No-Answer-Supervision feature, configure related configuration options, which could be set at an Application- or at DN-level. See the Framework 8.1 SIP Server Deployment Guide for details
|
- Configure DNs for the Agent SIP Server Application.
|
Complete the following procedure:
Configuring DNs for the Agent SIP Server Application
|
- Configure the GSVM SIP Server Application.
|
On the Options tab, in the TServer section, configure the following options, configure the following options to activate the MWI functionality:
- mwi-implicit-notify=""
- subscription-event-allowed=*
|
- Configure DNs for the SIP Server Application dedicated to GSVM.
|
Complete the following procedure:
Configuring DNs for the GSVM SIP Server Application
|
- Configure the GVP Resource Manager Application.
|
Reorganized this section to separate mandatory step from single-site-only steps.
Configure the following (mandatory):
- Indicate that the DNIS for the IVR Profile is fetched from the Request-URI message:
[rm].sip-header-for-dnis = request-uri
Configure the following only if SIP-Server and Resource Manager are deployed on the same host:
- On the Options tab, in the proxy section, modify the following options by entering new port numbers. For example:
- sip.localport = 5260
- sip.localsecureport = 5261
- sip.transport.0 = transport0 udp:any:5260
- sip.transport.1 =transport1 tcp:any:5260
- sip.transport.2 = transport2 tls:any:5261 cert=$InstallationRoot$/config/x509_certificate.pem key=$InstallationRoot$/config/x509_private_key.pem
|
- Configure GVP resources.
|
Complete the following procedure:
Configuring GVP Resources
|
- Configure A GVP IVR Profile to point to SIP Voicemail Server.
|
On the Options tab, specify these parameters in their respective sections:
- [gvp.general]service-type = voicexml
- [gvp.service-prerequisite]initial-page-url = http://<Voicemail Server IP>:<8080>/voicemail-web
Note: For HA deployments, use the Virtual IP address for the GSVM Server HA pair.
|
- Configure a GVP DID Group.
|
- On the Options tab, specify this parameter in its respective section:
[gvp.dn-groups]<name of the group> = <DNs in the group> where <DNs in the group> are configured DNs under a Switch with which the voicemail SIP Server Application is associated.
- Associate the IVR Profile with the DID Group, by specifying the following parameter in its respective section:
[gvp.dn-group-assignments]voicemail=<DBID of the Voicemail IVR Profile>
|
- Configure a GVP MCP object.
|
- On the Options tab, in the gvp.rm section, configure the following parameter:
aor=sip:<MCP_IP_Address:MCP_Port>
- Make sure the Squid is disabled by specifying the following parameter:
fm.http_proxy=""
- On the Connections tab, add the TTS Application object
- On the Advanced tab, in theApplication Parameters dialog box, specify the following parameter:
provisiontype=primary
|