CHAPTER: Chapter 4: Supported Call Flow Scenarios
SECTION: Time-Division Multiplexing PBX
MODIFY two paragraphs on pages 53-54:
In the first method, the PBX sends the call for the DID number through the media gateway to the SIP switch. Upon receiving the call, SIP Server directs the call to the MCP, which then launches the self-service application. The application can transfer the call to an agent RP at SIPServer by invoking a blind transfer with REFER on the MCP, at which point the MCP also attaches application data to the REFER request.
The URS strategy can then use Play Application treatments to launch further prompts, or it can transfer the call to the routing point on the PBX—the premise T-Server performs an Inter Server Call Control (ISCC) transfer from the SIP Server to an available agent and completes the call.
23 March 2015
The Media Server function Call Progress Detection (CPD) now performs voice print analysis and beep analysis to identify the specific preconnect tones that occur in different countries. Other detectable preconnect possibilities include answering machine (AM) and voice.
Media Server's configurable database of preconnect tones is initiated during installation and loaded when Media Server starts. You can update the database with different tones at any time, without stopping Media Control Platform.
When the caller's nature is determined (preconnect tone | AM | voice), the appropriate recording is played in response.
Other features include the ability to leave postconnection messages such as voicemail.
You can read about additional CPD functionality in "Appendix C: Tuning Call Progress Detection" of the
GVP 8.5 User's Guide.
The Reporting Server (RS) adds support for Windows 2012 64-bit and MS SQL Server 2012, in native 64-bit mode using the 64-bit version of the Java Virtual Machine. RS also adds support for Standard and Enterprise editions of the SQL Server 2012 database.
Resource Manager can now be configured to reject a call request if the geo-location of the targeted Logical Resource Group (LRG) does not match the geo-location attribute of the call request. This extends to all calls, a behavior that previously applied only to recording solution calls. Read about this behavior and the option that controls it, reject-on-geo-location-nomatch (new in release 8.5.1), in Locating Resources Using Geo-Location.
18 December 2014
GVP added support for Genesys Interactive Recording (GIR):
Media Control Platform added two new mp3 encoding compressions—16kbps (new default) and 24kbps—to the existing configuration option [mpc]mp3.bitrate.
VP Reporting Plugin for GAX added new support and compatibility requirements:
Added support for Management Framework 8.5 and Genesys Administrator Extension 8.5.
Added support for Windows Server 2012 R2 64-bit.
The plugin now requires GAX 8.5.0; support for GAX 8.1.4 is discontinued.
Warning: The Verbose level of debug tracing affects GVP production environment performance.
This warning applies to all mentions of the debug tracing setting verbose:
Warning: Debug tracing has a significant impact on GVP performance under load, especially the verbose setting. Genesys recommends that you enable debug tracing in GVP production systems only when recommended by Customer Care or Engineering.
Trace or tracing is mentioned in the context of debugging or a logging in several places, in the documentation listed below. In each instance, readers should be aware of its performance impact:
Appendix A: Deploying the T-Server-CUCM to Media Server Connector
Section: Deploying the Connector
Procedure: Integrating the Connector with Resource Manager and Cisco T-Server, page 141
Appendix A: Deploying the T-Server-CUCM to Media Server Connector
Section: Customizing the Configuration
Table 23: Selected T-Server-CUCM to Media Server Connector Options, page 144
Appendix A: Deploying the T-Server-CUCM to Media Server Connector
Section: Customizing the Configuration
Task Summary: Configuring the Connector Common Features, page 154
Chapter 5: Configuring Policy Server Important Policy Server
Section: Configuration Options
Table 15: Selected Policy Server Configuration Options, pages 100-101
