For example, the following line, for an event handler definition, associates the event handler with an event response:. Any lines preceded by a semicolon ; are not in effect and might contain explanatory comments. Do not remove these lines from your export files. See also Importing Communications Configuration Data. If you have to manually prepare a file for import, then you can export a file of the same type containing preconfigured data, then check that your file to be imported uses the correct format.
Previous Next JavaScript must be enabled to correctly display this content. Creating or Modifying a Communications Configuration This topic describes how to create or modify a communications configuration. It contains the following information: Copying or Deleting a Communications Configuration Viewing All Communications Configuration Data Specifying Parameters for a Communications Configuration Parameters for Communications Configurations In the Administration - Communications screen, use the All Configurations view to create or modify a communications configuration.
Tip: Rather than using the Administration - Communications screen to create or modify communications configuration data directly, you can export some of the data to files and modify or extend it using a text editor. Then you can import the data into the test or production Siebel database when you are ready to test, deploy, or update the communications configuration.
Creating a Communications Configuration Use the following procedure to create a communications configuration.
To create a communications configuration Navigate to the Administration - Communications screen, then the All Configurations view. The All Configurations view appears. In the Name field, enter the name of the configuration. Add any comments. Modify an Existing Communications Configuration Use the following procedure to modify an existing communications configuration.
To modify an existing communications configuration Navigate to the Administration - Communications screen, then the All Configurations view. In the Configurations list, select the record for the configuration to edit. Make your changes. Copying or Deleting a Communications Configuration You can copy or delete an existing communications configuration record.
Copying a Communications Configuration You can copy an existing communications configuration record by using the available menu commands. Note: When you copy a record for a communications configuration, associated configuration parameters, profiles, agents, commands commands and command data , and events event handlers, event responses, and event logs are not copied. Deleting a Communications Configuration You can delete an existing communications configuration by using the available menu commands.
Viewing All Communications Configuration Data Use the Configuration Explorer view to view information about all the elements of your communications configuration. To view communications configuration data Navigate to the Administration - Communications screen, then the Configuration Explorer view. Specifying Parameters for a Communications Configuration Use the All Configurations view to specify parameter values for a communications configuration.
To specify configuration parameters Navigate to the Administration - Communications screen, then the All Configurations view. In the Parameters list: If the configuration does not include all of the supported parameters that you require, then add a record for each such parameter, specifying the parameter name and parameter value.
Verify or edit values for all the parameters in your configuration. Parameters for Communications Configurations This topic describes the configuration parameters for communications configurations and displays applicable default values.
The following are the parameters for communications configurations: AutoLoadDriver. Note: For a communications configuration in which you set AutoLoadDriver to False, associate only the agents to which the preceding conditions apply. Otherwise, other agents are unnecessarily prompted to specify the computer host name. Note: It is recommended to define the ChannelCleanupTimer parameter if you use the Push Keep Alive driver with your communications configuration. In this case, the EnterpriseServer and GatewayAddress parameters are optional.
To support Siebel Server load balancing you generally run Communications Session Manager on all of the load-balanced computers where Application Object Manager is running. If Communications Session Manager is disabled on any of these computers, then you must run it on another computer and specify its location using the parameters described here.
If you are also running a backup Communications Session Manager, then see also the descriptions for the BackupCommConfigMgr parameter and related parameters. For more information, see Administering Communications Session Manager. Specifying Agents This topic describes how to specify agents. Relationship of Agents and Telesets for Siebel CTI If you are using Siebel CTI, then you must associate agents with communications configurations, specify telesets for your call center, and associate the agents with any telesets they use.
Note: If you are not defining ACD queues, then this topic does not apply. Specifying Agents for Communications Configurations This topic provides instructions for adding agents to a communications configuration.
To add agents to a communications configuration Navigate to the Administration - Communications screen, then the All Configurations view. Click the Agents view tab. The Add Agents dialog box appears: Scroll to display any additional records that are not shown, or use Query or Find to locate records matching certain criteria.
Click OK to add all selected employees to the Agents list. Alternatively, in the Agents list, click Add by Responsibilities or choose it from the menu to add to the configuration all agents with the specified responsibilities: Scroll to display any additional records that are not shown, or use Query or Find to locate records matching certain criteria.
Click OK to add all selected responsibilities to the Agents list. Configuring Agents This topic provides instructions for configuring an agent after the agent has been added to at least one communications configuration. Note: The Agent General Profile view lists only those agents who have been associated with one or more configurations. For more information, see Creating or Modifying a Communications Configuration. Note: For an Aspect switch, Agent Login also represents the number that other call-center agents dial to reach the agent.
Specifying Telesets This topic describes how to specify telesets. Teleset Naming and Hoteling Considerations You can provide any sort of unique name or number for a teleset.
Specifying Telesets, Agents, and Extensions This topic provides instructions for specifying telesets and specifying agents and extensions for telesets. To specify telesets Navigate to the Administration - Communications screen, then the All Telesets view.
In the Telesets list, add a new record. In the Teleset field, enter the name of the teleset. The host name that you enter is stored using all uppercase letters. Enter any optional comments for the teleset. Specifying Agents for Telesets This topic provides instructions for specifying agents for telesets.
To specify agents for a teleset In the All Telesets view, select the record for the teleset to which you add agents who are authorized users of the teleset. The Add Agents dialog box appears, displaying employees who have been added as agents to one or more configurations: Scroll to display any additional records that are not shown, or use Query or Find to locate records matching certain criteria.
Click OK to add all selected agents to the Agents list. If no Agent Login and Password values exist for a given agent, then you can add this data, as necessary: Click the hyperlink in the Agent field to drill down to the Agent General Profile view.
Specifying Extensions for Telesets This topic describes how to specify extensions for telesets. Note: Extensions are not required for all environments. S Nortel Meridian Specify two extensions for each teleset: one of each type.
Viewing Extension Data Use the All Extensions view to view information about the extensions for your telesets or to locate records for particular extensions. To view extension data Navigate to the Administration - Communications screen, then the All Extensions view. Defining Communications Events This topic describes how to define communication events. Siebel Communications Server supports three event types: Event handlers Event responses Event logs In general, you create event logs first, then create event responses and associate event logs with them, then create event handlers and associate event responses with them.
Note: If you are implementing a custom communications driver, then see also Configuring Communications List of Values Types. Specifying Event Log Parameters This topic describes how to add parameters for an event log. To add parameters for an event log Navigate to the Administration - Communications screen, then the All Event Logs view. In the Event Logs list, select the event log for which you want to add parameters.
Click the Event Log Parameters view tab. In the Event Log Parameters list, add a new record. In the Name field, specify the name of the parameter. In the Value field, enter the value for the parameter. Specifying Event Response Parameters This topic describes how to add parameters for an event response. To add parameters for an event response Navigate to the Administration - Communications screen, then the All Event Responses view.
Click the Event Response Parameters view tab. In the Event Response Parameters list, add a new record. Associating Event Logs with an Event Response This topic describes how to associate an event log with an event response. To associate an event log with an event response Navigate to the Administration - Communications screen, then the All Event Responses view. Click the Associated Event Logs view tab. In the Associated Event Logs list, add a new record.
Specify the event log to associate with this event response: In the Name field, click the select button. Select an event log with which to associate the event response, then click OK.
In the Log Type field, specify the type for this log. Specifying Event Handler Parameters This topic describes how to add parameters for an event handler. To add parameters for an event handler Navigate to the Administration - Communications screen, then the All Event Handlers view. Click the Event Handler Parameters view tab. In the Event Handler Parameters list, add a new record. Specifying Parameters for the Event Response Associated with an Event Handler This topic describes how to add parameters for the event response associated with an event handler.
To add parameters for the event response associated with an event handler Navigate to the Administration - Communications screen, then the All Event Handlers view. Defining Communications Commands This topic describes how to define communication commands.
Siebel Communications Server supports two command types: Commands Command data definitions In general, you create command data definitions first, then create commands and associate command data definitions with them.
For more information, see the following: For more information about the role of commands within a communications configuration, see About Communications Configuration Data. Specifying Command Data Parameters This topic describes how to add parameters for a command data definition. To add parameters for a command data definition Click the Command Data Parameters view tab. In the Command Data Parameters list, add a new record.
Creating Commands This topic describes how to create commands, using the All Commands view. Specifying Subcommands for a Group Command This topic describes how to specify subcommands for a group command.
Note: When you specify subcommands for a group command, do not specify invalid recursive relationships between subcommands and group commands.
For example, do not specify a subcommand that is itself a group command for which the current group command is specified as a subcommand. Specifying Command Parameters This topic describes how to add parameters for a command. To add parameters for a command Navigate to the Administration - Communications screen, then the All Commands view.
In the Commands list, select a command to which you add parameters. Click the Command Parameters view tab. In the Command Parameters list, add a new record. Specifying Parameters for the Command Data Definition Associated with a Command This topic describes how to add parameters for the command data definition associated with a command. To add parameters for the command data definition associated with a command Navigate to the Administration - Communications screen, then the All Commands view.
Click the Command Data Parameters view tab. Exporting and Importing Communications Configuration Data This topic describes how to export and import configuration data. You can use these mechanisms to: Move configuration data between databases or between communications configurations within the same database Move configuration data and custom communications drivers obtained from another source such as a third-party vendor into Siebel Communications Server Edit or enter data in text files rather than directly within the Administration - Communications screen For more information about adding custom communications drivers, see Configuring Communications Drivers and Profiles.
The basic options for exporting and importing are as follows: Export communications configuration data from the database to a DEF file Import communications configuration data into the database from a DEF file or from an INI file exported from a previous release The following table describes how driver and profile parameters are handled by the import process from a DEF file to the database.
For example Does not exist in the database, then the import process adds it. Note: Using the Export Configuration and Import Configuration features, you can transfer all types of communications configuration data from one configuration to another except data for agents and ACD queues and telesets and extensions. Exporting Communications Configuration Data Exporting communications configuration data from the database into a file can make it easier to review your configuration settings.
To export communications configuration data Navigate to the Administration - Communications screen, then the All Configurations view. In the Configurations list, select the configuration record for which to export data.
Click Export Configuration, located at the start of the view. A dialog box appears that contains four export options: Configuration Parameters. Click OK. You are prompted whether to open or save this file. Specify whether to open or save the file, then click OK: If you choose to open the file, then the DEF file is opened in your default text editor.
Note: When you export a configuration, the prompted filename has the extension. However, files when exported might be appended by. TXT or another extension, depending on your computing environment. Importing Communications Configuration Data You might have to import communications configuration data from a file into the database for several reasons.
For any communications configuration file that you import that does not contain an entry as shown, upgrade steps are performed on the file. Do not manually add such an entry to a configuration file unless the file is known to be valid and does not have to be upgraded. Caution: When you import communications configuration data, all existing data of the same type is first deleted from the database for the current configuration. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox.
Newsletter Topics Select minimum 1 topic. Enterprise Software. Any comment is deeply appreciated. Thanks in advance! Camilla Tai Camilla. Tai advantech. Anonymous Posted April 9, 0 Comments. Did u contact Siebel? They might be having some Standard drivers.
Danj Posted April 9, 0 Comments. Camilla Tai. We need to develop CTI derver for Siebel 7. See also the description for the parameter Service:ServiceLogFile. If the specified limit is reached, another instance of the driver handle is created. For more information about the driver handle, see Developing a Communications Driver.
For any users running the Communications Simulator, this parameter specifies a number representing a simulated port number, so that users can simulate an "inside call" to another teleset. Network communications protocol as configured in the Call Processing Server.
Possible values include:. This parameter need not be explicitly set in order to use the Communications Simulator. The type of switch for your call center. Values include:. Determines whether to automatically log the agent out of the ACD queue when the communications session has ended:. This setting applies whether the agent specifically exited the Siebel application or the browser, or if the agent's application session times out.
Settings that, when set to TRUE, specify whether the connected switch provides programmatic support for the indicated functionality. You can also disable a feature that is supported by the switch but that you do not want your agents to use. Data for Siebel Communications Server and Intel NetMerge activity is logged, including device events and event data fields. Log files are created by default in the log subdirectory of the Siebel Server or Siebel Dedicated Web Client installation directory, depending on the client type and on your communications deployment.
A complete path can be specified along with the filename in order to write the file to a nondefault location. Optionally, if you want to use a single log file in a multichannel environment, you can specify the same log file name for all interactive drivers you are using. In each log file, log records referring to the same call would contain the same value for the refId event data field. See also the description for the parameter Service:ServiceLogFile.
If the specified limit is reached, another instance of the driver handle is created. For more information about the driver handle, see Developing a Communications Driver. For any users running the Communications Simulator, this parameter specifies a number representing a simulated port number, so that users can simulate an "inside call" to another teleset.
Network communications protocol as configured in the Call Processing Server. Possible values include:. This parameter need not be explicitly set in order to use the Communications Simulator.
0コメント