Preface Document Conventions
•
Chapter 9, “T-Server Fundamentals,” on page 255 , describes T-Server, its
place in the Framework 7 architecture, T-Server redundancy, and multi-site issues. It does not, however, provide configuration and installation information.
•
Chapter 10, “Multi-Site Support,” on page 267
, describes the variations available for T-Server implementations across geographical locations.
•
Chapter 11, “Common Configuration Options,” on page 321
, describes log configuration options common to all Genesys server applications.
•
Chapter 12, “T-Server Common Configuration Options,” on page 343
, describes configuration options common to all T-Server types including options for multi-site configuration.
Part Three—DMX Reference Information
Part Three of this SIP Server document, “DMX Reference Information,”
consists of Chapters 13 and
14 . These chapters contain reference information
specific to DMX.
•
Chapter 13, “DMX Deployment,” on page 369
, describes how to configure, install, and start DMX.
•
Chapter 14, “DMX Reference,” on page 393 , provides detailed information
about DMX.
Appendix
•
The appendix “Session Initiation Protocol (SIP) Overview” on page 401 ,
provides basic information about the SIP protocol.
Document Conventions
This document uses certain stylistic and typographical conventions— introduced here—that serve as shorthands for particular kinds of information.
Document Version Number
A version number appears at the bottom of the inside front cover of this document. Version numbers change as new information is added to this document. Here is a sample version number:
76fr_sip_06-2008_v7.6.001.00
You will need this number when you are talking with Genesys Technical
Support about this product.
16 Framework 7.6
Preface Document Conventions
Type Styles
Examples:
Italic
In this document, italic is used for emphasis, for documents’ titles, for definitions of (or first references to) unfamiliar terms, and for mathematical variables.
•
Please consult the Genesys Migration Guide for more information.
•
A customary and usual practice is one that is widely accepted and used within a particular industry or profession.
•
Do not use this value for this option.
•
The formula, x +1 = 7 where x stands for . . .
Examples:
Example:
Monospace Font
A monospace font, which looks like teletype or typewriter text
, is used for all programming identifiers and GUI elements.
This convention includes the names of directories, files, folders, configuration objects, paths, scripts, dialog boxes, options, fields, text and list boxes, operational modes, all buttons (including radio buttons), check boxes, commands, tabs, CTI events, and error messages; the values of options; logical arguments and command syntax; and code samples.
•
Select the
Show variables on screen
check box.
•
Click the
Summation
button.
•
In the
Properties
dialog box, enter the value for the host server in your environment.
•
In the
Operand
text box, enter your formula.
•
Click
OK
to exit the
Properties
dialog box.
•
The following table presents the complete set of error messages T-Server distributes in EventError events.
•
If you select true for the inbound-bsns-calls option, all established inbound calls on a local agent are considered business calls.
Monospace is also used for any text that users must manually enter during a configuration or installation procedure, or on a command line:
•
Enter exit
on the command line.
Screen Captures Used in This Document
Screen captures from the product GUI (graphical user interface), as used in this document, may sometimes contain a minor spelling, capitalization, or grammatical error. The text accompanying and explaining the screen captures corrects such errors except when such a correction prevents you from
SIP Server—Deployment Guide 17
