Annex

Keyboard shortcuts on the phone

The following key combinations can be used on telephones that have been auto-provisioned via STARFACE to control various features and functions.

Keyboard shortcuts for general control

Keyboard shortcuts during an active call

Keyboard shortcuts for additional service features

Keyboard shortcuts for controlling conferences

Overview of country-specific emergency numbers and special numbers

Certain internal phone numbers cannot be assigned to users, groups, etc. Which internal numbers cannot be assigned depends on the configured country setting on the SIP trunk.

The wildcard * stands for none or several arbitrary digits. The information in square brackets indicates a number range.

Configure new SIP provider profile

This documentation describes which configuration options are available when creating a new SIP provider.

• Kopfleiste
• SIP-Konfiguration
• Kopfzeilen für SIP REGISTER
• Einstellungen für Wählformat und Rufnummernanzeige
• Erweiterte Einstellungen

Es wird empfohlen nur verifizierte Providerprofile zu nutzen, da diese automatische gegen verschiedene Versionen der STARFACE getestet werden. Nur die mit „Profil bereitgestellt von STARFACE GmbH“ gekennzeichneten Profile werden durch den Support der Firma Starface abgedeckt.

Header bar

Various functions can be selected directly using the buttons of the same name:

• Copy profile
• Show previous version
• Import TLS certificate

SIP configuration

Example screenshot of SIP configuration

The following configuration fields are available:

type

dtmfmode

auth mode

auth user

nat

allow

insecure

port

transport

defaultip

rtpholdtimeout

fromdomain

host

If there are zeros in the leading digits of one or more number blocks in a manually configured line (e.g. 002.007.165.006), these must be removed via the manual line configuration (pencil symbol next to the provider field). To do this, click on the pencil icon and remove the corresponding zeros in the host field. Click on "Save". This prevents outgoing calls from being cancelled with "404 Not Found".

permit

deny

canreinvite

disallow

outboundproxy

progressinband

qualify

encryption

rtptimeout

mask

fromuser

resolve host

Headers for SIP REGISTER

In the "Contact" drop-down menu, you must select which information is to be transferred to the provider in the SIP registration package. In the adjacent "Number format" drop-down menu, you can select the format in which the respective number is entered in the SIP registration package.

The number formats are structured as follows:

Settings for dialling format and call number display

In this area, the dialling format and the display of incoming and outgoing numbers can be configured via the respective drop-down menus. The necessary settings must match the format expected by the provider and must also be specified by the provider.

The display of the phone number is dealt with in various RFCs for the SIP protocol. In addition to these RFCs, there are other setting options in the STARFACE, some of which have been added specifically for providers who do not operate within these standards.

When using the respective type, the applicable data protection law must be observed. It is your own responsibility to check whether the data transferred to the provider fulfils the requirements of the data protection regulations.

Advanced settings

In this area, the "Cross-line number recognition" checkbox can be used to configure that the STARFACE checks whether an incoming call also fits into the line context of another line configuration.

Description of the XML-RPC interface of the queue

The "queue" ringing strategy (see also"Configuring the queue" and"Configuring the evaluation for the queue") provides external applications with access to live data and history data. XML-RPC technology is used for both interfaces. The live data of an waiting loop is called up via the XML-RPC function "Queue.getLiveData", which expects an input parameter:

<name>queueName</name> <string>…</string>

This function returns the following values:

callersLiveData (LIST) - This return value is a list, which in turn contains maps as elements. Each map contains information (key -> value) about exactly one caller who is in the queue at that time. The list is sorted according to the position of the caller in the queue. Each map contains the following keys:

agentsLiveData (MAP) - This return parameter is a map, which in turn contains maps as elements. The key of the map is the login ID of the agent. Each element map contains information (key -> value) about an agent:

History interface

The historical data of a queue is called up via the XML-RPC function "Queue.getHistoryData". The input parameter for this is a "struct" with three values:

This function has a return value:

queueHistoryData (LIST) - The elements of the list are maps and each map contains information about exactly one call. The list is sorted according to the timestamp of the calls. Each element in the list contains the following keys:

Example

By post method:

http://IP-ADRESSE/xml-rpc?de.vertico.starface.auth=$LoginID:SHA512($LoginID*SHA512($Passwort))

The password is hashed with SHA512 in the first step. This hash is then hashed again with the LoginID as a prefix and the separator *. For a user with the following key data:

LoginID = 0001
Passwort = starface
IP-Adresse der STARFACE = 192.168.0.100

is the call URL for XML-RPC:

http://192.168.0.100/xml-rpc?de.vertico.starface.auth=0001:5273503e607e5b24eeb48a3f71c53eb50df6b6622839ecd7149e248893f627d05d8d4af88cf36b3d7d5cd5d1d559dfa1c10404067d8c0f37a138c6546dad7ef7

The body would then look like this, for example:

Description of the CSV file for "Export line utilisation data"