Siebel Communications Server Administration Guide > Advanced Communications Configuration > Configuring Remote Transfers and Conferences >

Using Macros to Identify Remote Call Centers


This section describes how you can use parameters to obtain a call center configuration name.

In the communications configurations for San Mateo and Emeryville, you would add a command parameter like one of the examples below to the command data definition for any applicable commands—such as commands used for initiating a call transfer or conference call to another call center.

The command data parameter Param.RemoteConnectStr can include one of two related macros in its parameter value in order to obtain the desired configuration name. For more information, see Macros for Parameter Values.

Example Command Using $RemoteConnectStr

The example command and command data definitions shown in Table 33 and Table 34, using the $RemoteConnectStr macro, use the Owner Phone field in the Service Request business component to determine which call center has the phone number.

In this example, the Param.RemoteConnectStr command parameter gets the extension number for the call recipient by macro-expanding Owner Phone:Lookup. The Siebel application looks up which configuration has this extension and returns the name of the call center with this extension.

Table 33.  Command: BlindTransferToSROwner
Parameter Name
Parameter Value
Description
Blind Transfer to Service Request Owner
DeviceCommand
TransferMute
Hidden
TRUE

Table 34.  Command Data: BlindTransferToSROwner
Parameter Name
Parameter Value
BusComp
Service Request
RequiredField.'Owner Phone'
?*
Param.PhoneNumber
{Owner Phone:Lookup}
AttachContext
TRUE
Param.CallNotifyText
Blind transfer from {@UserName} about SR {Id}...
Param.RemoteConnectStr
{$RemoteConnectStr(Owner Phone:Lookup)}
(In this example, Owner Phone is a field from the Service Request business component.)


 Siebel Communications Server Administration Guide 
 Published: 23 June 2003