8         Notifications

false

The notification feature is disabled completely; neither SNMP traps nor e-mails will be sent. This is the default setting.

traps

Notifications will only be sent through SNMP traps if proper receivers are defined in the corresponding xml file (TrapReceivers.xml).

email

Notifications will only be sent through e-mail if proper receivers are defined in the corresponding xml file (EmailConfigurations.xml).

all

Notifications will be sent through both SNMP traps and e-mails, if proper receivers are defined in the corresponding xml files (TrapReceivers.xml and EmailConfigurations.xml)

trapReceivers

Root tag.

trapReceiver

Block to define a connection to a SNMP receiver.

trapReceiver/id

Unique ID to identify this SNMP receiver.

trapReceiver/categories

Specifies that SNMP traps should be sent via this connection if the notification matches one of the defined categories. Allowed values are ERROR, WARN, INFO. To specify more than one category, a comma-separated list can be defined. In addition also custom categories might be added. Examples:

·          categories=”WARN”
Only includes notifications of category WARN

·          categories=”CUSTOM1”
Only contains notifications of category CUSTOM1

·          categories=”INFO,WARN,ERROR”
Includes all notifications of categories INFO, WARN, and ERROR

trapReceiver/version

Defines the SNMP version to be used for this connection. Allowed values are v2, v2c and v3.

trapReceiver/protocol

Optional attribute to define the protocol to be used for sending out SNMP traps. Allowed values are udp (the default) and tcp.

trapReceiver/enabled

Optional setting to disable the corresponding trap receiver. Allowed values are true (the default) and false.

hostIP

IP address of the machine running the SNMP receiver.

port

Port number on which the SNMP receiver is listening (typically the default SNMP port 162 is used here).

community

Authentication parameter (only used for SNMP receivers of version 2c).

locale

Defines the locale to be used for the messages of the SNMP traps sent out for this receiver. Allowed values are either en (the default) or de.

userName

Authentication parameter (only used for SNMP receivers of version 3).

maxCountPerNotification

Optional setting to define a maximum number of same SNMP traps that will be sent out for the same notification. If the maximum number is exceeded, for instance when running out of licenses, no further SNMP traps will be sent out for this notification.

resetTimeInterval

Defines the time interval in minutes after which the limit defined in the attribute maxCountPerNotification is reset, if not defined a default value of 60 (1 hour) is used.

notificationEmailReceivers

Root tag.

emailReceiver

Block to define a connection to an e-mail receiver.

emailReceiver/id

Unique ID for identifying this e-mail receiver.

emailReceiver/categories

Specifies that e-mails should be sent via this connection if the occurring notification matches one of the defined categories. Allowed values are ERROR, WARN, INFO. To specify more than one category, a comma-separated list can be defined. In addition also custom categories might be added. Examples:

·          categories=”WARN”
Only includes notifications of category WARN

·          categories=”CUSTOM1”
Only contains notifications of category CUSTOM1

·          categories=”INFO,WARN,ERROR”
Includes all notifications of categories INFO, WARN, and ERROR

emailReceiver/enabled

Optional setting to disable the corresponding e-mail receiver. Allowed values are true (the default) and false.

from

Defines the From field of the sent e-mail. Has to be a valid e-mail address. As an alternative to providing an e-mail address the placeholder @INSTANCE_NAME@ can be used. In this case VoiceObjects Server will automatically fill the From field with: instanceName@logical_Server, where instanceName identifies the corresponding server instance and logical_Server is the reference ID of the used Server object.

8Caution: Some SMTP servers require a valid domain to be used in the from e-mail field. In these cases the placeholder can not be used.

to

Defines the To field: e-mail is sent to all e-mail addresses defined in a comma-separated list. This setting is optional, but at least one valid e-mail address has to be defined for at least one of the settings to, cc or bcc in order to define a valid e-mail receiver.

cc

Defines the CC field: e-mail is sent to all e-mail addresses defined in a comma-separated list. This setting is optional, but at least one valid e-mail address has to be defined for at least one of the settings to, cc or bcc in order to define a valid e-mail receiver.

bcc

Defines the BCC field: e-mail is sent to all e-mail addresses defined in a comma-separated list. This setting is optional, but at least one valid e-mail address has to be defined for at least one of the settings to, cc or bcc in order to define a valid e-mail receiver.

priority

Optionally sets the priority for the e-mail; can either be low, normal (the default) or high.

smtpServer

Defines the address of the SMTP server used for sending out e-mails. This can either be an open SMTP server or one that requires authentication. Note that in the latter case the settings for user and password are mandatory.

smtpPort

Optional setting to define the port number of the SMTP server. If not specified the default SMTP port 25 is used.

user

Defines the user to be used for a SMTP server that requires authentication. Optional.

password

Defines the password to be used for a SMTP server that requires authentication. Optional.

locale

Defines the locale to be used for the messages of the e-mails sent out for this receiver. Allowed values are en (the default) or de.

maxCountPerNotification

Optional setting to define a maximum number of same e-mails that will be sent out for the same notification. If the maximum number is exceeded, for instance when running out of licenses, no further e-mails will be sent out for this notification.

resetTimeInterval

Defines the time interval in minutes after which the limit defined in the attribute maxCountPerNotification is reset, if not defined a default value of 60 (1 hour) is used.

messagesPerConnection

Specifies the number of e-mails which are sent via a single SMTP connection. After this number of e-mails the connection will be closed. For the next e-mail a new connection will be created. By default messagesPerConnection is set to 1.
8Caution: It is recommended not to change this value (i.e. set it to something greater than 1), as otherwise some e-mails might get lost depending on the SMTP server used (e.g. Microsoft Exchange).

notifications

Root tag.

group

Defines a group of notifications; currently there are five groups (server, service, unsolicited, sla and others) available.

group/name

Unique name to identify the group.

group/categories

Defines a comma-separated list of categories for this group of notifications. Possible values are INFO, WARN, ERROR plus any custom categories. If this attribute is set it will be inherited by all notifications within this group.

notification

Element for defining a notification.

notification/id

Unique name to identify the notification.

notification/locale

Defines the localization key that is internally used by VoiceObjects Server for localizing the message of this notification. This message is then used within both the SNMP trap and/or the e-mail that is sent to the corresponding receivers.
8Caution: Do not change this value, as otherwise the notification will no longer have a localized message.

notification/masterOnly

Defines if the notification has to be sent via the master server instance or from the server instance on which the event occurred, which is the default behavior. Allowed values are either false (the default) or true.

notification/categories

Defines a comma-separated list of categories this notification belongs to. Possible values are INFO, WARN, ERROR plus any custom categories. If this definition is in conflict with a setting on the group level, the local category assignment will overwrite the category assignment made on the group level for this notification. If any custom category (see code example above) has been added do not forget to add this category to a corresponding SNMP trap and/or e-mail receiver as well. Otherwise this custom category assignment will not have any effect.

Server %1 is starting.

4.13

Start (or Resume) command has been invoked for this server.

Server %1 has started successfully.

4.14

Server %1 is idling.

4.15

Idle command has been invoked for this server.

Server %1 has idled successfully.

4.16

Server %1 is stopping.

4.17

Stop command has been invoked for this server.

Server %1 has stopped successfully.

4.18

Server %1 is resetting.

4.1

Reset command has been invoked for this server.

Server %1 has reset successfully.

4.3

Server %1 is shutting down.

4.2

Shutdown command has been invoked for this server.

Server %1 has shut down successfully.

4.4

Server %1 is reloading the service list.

4.11

Reload Service List command has been invoked for this server.

Server %1 has reloaded the service list successfully.

4.12

Server instance %1 is starting.

4.5

Start (or Resume) command has been invoked for this server instance.

Server instance %1 has started successfully.

4.6

Server instance %1 is idling.

4.9

Idle command has been invoked for this server instance.

Server instance %1 has idled successfully.

4.10

Server instance %1 is stopping.

4.7

Stop command has been invoked for this server instance.

Server instance %1 has stopped successfully.

4.8

Service %1 is starting on server %2.

5.1

Start (or Resume) command has been invoked for this service.

Service %1 has started successfully on server %2.

5.5

Service %1 is idling on server %2.

5.3

Idle command has been invoked for this service.

Service %1 has idled successfully on server %2.

5.7

Service %1 is stopping on server %2.

5.2

Stop command has been invoked for this service.

Service %1 has stopped successfully on server %2.

5.6

Service %1 is redeploying on server %2.

5.4

Redeploy command has been invoked for this service.

Service %1 has redeployed successfully on server %2.

5.8

Service %1 is restoring on server %2.

5.9

Restore command has been invoked for this service.

Service %1 has restored successfully on server %2.

5.10

No license available for server %1 and service %2. Contact VoiceObjects Technical Support to get a valid license key.

6.2

While starting VoiceObjects Server no valid license key could be found in the Metadata Repository. Contact VoiceObjects to get a proper license key. Refer to Chapter 4 - Managing Licenses in the Administration Guide for further information.

The notification feature is not available as it is not included in the VoiceObjects Server license.

6.3

Your current VoiceObjects Server license does not include the additional notification feature. Contact VoiceObjects to get a new license key including the notification feature. Refer to Chapter 4 - Managing Licenses in the Administration Guide for further information.

The license key will expire within the next %1 days. Contact VoiceObjects Technical Support to get a valid key.

6.14

Your current license key is about to run out. Take care to contact VoiceObjects early enough to secure that you receive an updated license key in time. Refer to Chapter 4 - Managing Licenses in the Administration Guide for further information.

The license key for VoiceObjects Server is not valid anymore. Contact VoiceObjects Technical Support to get a valid key.

6.15

Your license key has already been expired. Contact VoiceObjects as soon as possible to get a new license key, as your current VoiceObjects installation will become unmanageable and your applications may also stop answering calls soon. Refer to Chapter 4 - Managing Licenses in the Administration Guide for further information.

Server instance %1 is now running in master mode.

6.4

A new master server instance has been selected in your VoiceObjects cluster. A typical reason for this might be that the current master server instance has been shutdown due to maintenance situations. Refer to Chapter 1 - Deployment Architecture in the Deployment Guide for further information.

Requested service not available (VSN=%1, DNIS=%2).

6.5

The service that has been requested by the media platform is not available. This might have several reasons like e.g.:

·          The service is not started

·          The used VSN does not match the VSN of the corresponding Service object

Rejected URL due to inactive server/service (VSN=%1).

6.6

VoiceObjects Server rejects the URL since the server or service that has been intended to handle the dialog is not available. Make sure that the service or server is started in the Control Center.

Connection to Infostore Repository not available. Possible reason: %1

6.7

The database connection to your Infostore Repository is not available. Check the message of the notification for hints on the possible reason.

Connection to Infostore Repository is available again.

6.16

The database connection to your Infostore Repository has been re-established.

Connection to Custom DB logging database is not available. Possible reason: %1

6.8

The database connection to your Custom DB logging repository is not available. Check the message of the notification for hints on the possible reason.

Connection to Metadata Repository is not available. Possible reason: %1

6.9

The database connection to your Metadata Repository is not available. Check the message of the notification for hints on the possible reason.

Connection to Metadata Repository is available again.

6.10

The database connection to your Metadata Repository has been re-established.

Timeout: Dialog %1 called by ANI %2 has expired.

6.11

The dialog timeout defined for this service has been reached. Due to this the dialog has expired, based on inactivity, either on the caller or on the system side.

Request redirected to target %1.

6.12

The request sent from the media platform has been redirected to another target server instance since the original one is currently not available. Typical reason for this is that the original server instance has been stopped or idled.

Call rejected due to unlicensed channel or partner (VSN=%1).

6.13

VoiceObjects Server has rejected to answer a call since the used channel or partner is not included in the current license key. Contact your VoiceObjects sales representative to get an extended license key, which enables you to support all phone channels with your VoiceObjects installation.

Infostore queue is full. Due to this logging information '%1' is dropped.

6.17

If the connection to your Infostore Repository has not been available for a while, the queue for storing the logging information might be full. In this case no further logging information is transferred into the queue but gets lost. To inform you about this possible logging data loss, this notification is sent from VoiceObjects Server.

Last operation %1 failed. Possible reason: %2

6.18

The latest command for changing the status of a server, server instance or service (e.g. start service) failed. Check the message of the notification for hints on the possible reason.

No license could be found in the Metadata Repository. Contact VoiceObjects Technical Support to get a valid key.

6.19

While starting VoiceObjects Server no valid license key could be found in the Metadata Repository. Contact VoiceObjects to get a proper license key. Refer to Chapter 4 - Managing Licenses in the Administration Guide for further information.

The setting <maxCountPerNotification> has been reset for this notification. Summary of all blocked messages: %1

6.20

The defined time interval in <resetTimeInterval> has been reached, enabling the sending of further notifications of this kind until the setting <maxCountPerNotification> is reached again.

No license available for dialog %1 (Server %2, VSN %3, Site %4): Server limit of %5 reached.

7.1

VoiceObjects Server has rejected to answer any additional calls as the session limit (granted sessions - limit) defined for this server has been reached. Refer to Chapter 9 - Service Level Agreements (SLA) in the Deployment Guide for further information.

No license available for dialog %1 (Server %2, VSN %3, Site %4): Service limit of %5 reached.

7.2

VoiceObjects Server has rejected to answer any additional calls as the session limit (granted sessions - limit) defined for this service has been reached. Refer to Chapter 9 - Service Level Agreements (SLA) in the Deployment Guide for further information.

No license available for dialog %1 (Server %2, VSN %3, Site %4): Site limit of %5 reached.

7.3

VoiceObjects Server has rejected to answer any additional calls as the session limit (granted sessions - limit) defined for this site has been reached. Refer to Chapter 9 - Service Level Agreements (SLA) in the Deployment Guide for further information.

Overdraft license returned: %1 (licensed: %2, total: %3).

7.4

An overdraft license has been issued.
This indicates that the session limit defined in the license key for the installation is reached. Contact your VoiceObjects sales representative for a larger license key.

License Manager not available, returning failover license. %1 of the grace period remaining, %2 sessions left.

7.5

A failover license has been issued.
This indicates that a temporary problem has occurred in the VoiceObjects cluster. If this only happens in isolated cases and corrects itself after a short period of time, it does not constitute an issue.
If, however, this message persists for longer periods of time or occurs frequently, contact VoiceObjects Technical Support for assistance.

Maximum limit of concurrent dialogs reached. %1

7.6

VoiceObjects Server has stopped accepting any additional concurrent dialogs as the session limit (= concurrent dialogs) has been exceeded. This already includes the overdraft of 20%, which VoiceObjects grants to guarantee full availability during peek times.

Object %1 triggered error. %2.

8.1

An error occurred during the call. Check the error message mentioned in the notification and refer to the listed object for further investigation.

VoiceObjects session %1 is already in use!

8.2

VoiceObjects Server rejected to answer a request from the media platform since it has already been processing a request with the same ID.

Initial request held parameter dialogID (dialogID=%1).

8.3

The initial request sent from the media platform to VoiceObjects Server already contains the parameter dialogID. As this parameter is generated by VoiceObjects Server based on the first request, this is a conflict and leads to an aborted call. Check if the media platform has cached some VXML pages, which might be a typical reason for this issue.

Invalid assignment of parameter in initial URL (Parameter=%1, Value=%2).

8.4

The initial request sent from the media platform contains an invalid parameter assignment; check and correct the syntax.

Invalid assignment of parameter in request URL (Parameter=%1, Value=%2).

8.5

The request sent from the media platform contains an invalid parameter assignment; check and correct the syntax.

Could not store utterance recording of dialog object %1 in service %2 on server instance %3:%4.

8.6

Utterances recorded during the call could not be stored. Check if the file system for storing the utterance recordings is available and is also still accepting new files.

%1

8.7

An Expression object with function NOTIFICATION has been processed in the current dialog. The parameter %1 will be replaced by the message defined in the first argument of the corresponding Expression object.