Configuring the SAPphone Server

Configuring the SAPphone Server

Use

You must enter the settings which are required before the SAPphone server can be used.

Activities

General settings

Select Configuration ® General

Area	Field	Description
Mode of operation	Desktop	Select this option if the SAPphone server is installed locally on your computer.
	Server	Select this option if the SAPphone server is installed centrally on the telephony server.
Connection to R/3	Enable incoming calls	Specify the functions which are to be supported by the SAPphone server and enter the settings for the selected functions. Do not select these fields if you are testing the compatibility between the SAPphone server and your service provider without a connection to the R/3 System.
	Enable outgoing calls
	R/3 Release	Enter the release number of the R/3 system to which the SAPphone server is to be connected.
TAPI problem analysis only	Request additional TAPI messages	If you select this option, various TAPI messages are displayed.
Program startup options	Start TAPI client module on program start	If you do not select this option, you must call and close the TAPI client module manually via File ® Start TAPI client module or File ® Stop TAPI client module
	Start RFC server on program start	If you do not select this option, you must call and close the RFC server manually via File ® Start RFC Server or File ® Stop RFC Server

Settings for supporting incoming calls

Select Configuration ® Incoming calls

Area	Field	Description
Logon mode	Group logon	Select this option if automatic load distribution is to be used, and enter the system, group and message server.
	Server logon	Select this option if the server should always log on to the same application server.
User logon information		If the telephony server is installed locally on the computer, enter the logon data for the user.
Only for R/3 releases 3.1x	Start R/3 GUI on incoming call	Select this option if the SAPphone server has been activated in start mode and the system is to display an R/3 dialog box containing the relevant caller data whenever an incoming call is received. The prefix for the telephony server must be entered if the telephone itself does not transfer the complete number (including local area code, connection and extension).
Corresponding R/3 telephony server id	Server id	Server name (ID) of the telephony server from which the SAPphone sever reads the list of work centers which can receive incoming calls via this server. The server ID is entered automatically from Release 4.0A onwards if you execute the Connection test function when creating the SAPphone telephony server.
List of telephone extensions for incoming calls	Synchronize list of extensions for incoming calls with R/3	Select this option if the telephony server supports a large number of connections.
	Do not synchronize list of extensions for inbound calls with R/3	In all other cases, select this option.

To test the settings, select Test logon

Settings for outgoing calls

Select Configuration ® Outbound calls

Area	Field	Description
RFC activation type	Register	Select this option if the SAPphone server is installed on a central telephony server or on a local computer with its own RFC destination. Enter the program ID, the SAP gateway and the service. These entries must correspond to the entries for the RFC destination.
	Start program	At present, only registration mode is supported for outgoing calls.

Settings for log files

Select Configuration ® Customizing

Area	Field	Description
Log file expiration	Do not delete log files	The log files are not deleted automatically.
	Delete log files	When the SAPphone server is started, all log files which are older than the specified value are deleted.
Select logging category	Information Warning TAPI messages	Select the messages to be included (apart from the error messages and system messages).

Select Trace if the RFC commands for incoming and/or outgoing calls are to be logged in a trace file.

You can also create your own trace file which logs all actions by the SAPphone server at runtime and is subsequently deleted.