The SIS uses the following ten profile specifications, and root configuration schema, to store its configuration and subscription data.
IN = SIS feature for IN only
Profile specifications
Profile specification | What it does |
---|---|
root configuration |
Defines basic service-interaction configuration information, and includes the names of other profile tables the SIS needs (see the root configuration schema). |
macros |
Allows common expressions to be reused multiple times in triggers, compositions or other macros. |
triggers |
Specifies how the SIS deals with initial events it gets from the network. Includes an expression that the SIS can evaluate against the initial event, composition-selection criteria and failure-handling instructions. |
compositions |
Prompts the SIS to process an ordered set of services, according to various details, when triggered. |
interceptors |
Provides custom logic to manipulate the signaling parameters of protocol messages. |
extension references |
Identifies extension components that can be used in compositions. |
service references |
Identifies services that can be used in compositions. |
interceptor references |
Identifies interceptors that can be invoked by SLEE applications or other interceptors. |
external platforms |
Describes the location of services that are external to the SIS. |
network interface definitions |
Describes SIS network interfaces and their associated configuration properties. |
network routes |
Specifies how the SIS selects a network interface for outgoing traffic. |
address subscriptions |
Defines subscription to compositions using an address. (Address lookup may be based on various addresses present in the initial event.) |
service key subscription |
Defines subscription to compositions using the mandatory service key parameter of IN initial events. |
trigger address tracing |
Lets you associate a tracing-debug level with any arbitrary address, so you can enable debug logging for a dialog with a specific address string in one of the initial event’s parameters. |
experimental features |
Identifies incomplete or untested features that may be enabled in the SIS. |
Schema of root configuration profile
The SIS configuration profile specification defines the schema of the root configuration profile for the SIS, as follows:
Attribute |
Type |
---|---|
Description |
|
Description |
java.lang.String |
An optional arbitrary descriptive name for the configuration. |
|
Macro profile table name |
java.lang.String |
Name of the profile table used to store macro expressions. This profile table must have been created from the SIS macro profile specification. |
|
Trigger profile table name |
java.lang.String |
Name of the profile table used to store triggers. This profile table must have been created from the SIS trigger profile specification. |
|
Service composition profile table name |
java.lang.String |
Name of the profile table used to store compositions. This profile table must have been created from the SIS composition profile specification. |
|
Interceptor profile table name |
java.lang.String |
Name of the profile table used to store interceptors. This profile table must have been created from the SIS interceptor profile specification. |
|
Extension reference profile table name |
java.lang.String |
Name of the profile table used to store extension references. This profile table must have been created from the SIS extension reference profile specification. |
|
Service reference profile table name |
java.lang.String |
Name of the profile table used to store service references. This profile table must have been created from the SIS service reference profile specification. |
|
Interceptor reference profile table name |
java.lang.String |
Name of the profile table used to store interceptor references. This profile table must have been created from the SIS interceptor reference profile specification. |
|
Address subscription profile table name |
java.lang.String |
Name of the profile table used to store composition provisioning information for triggerable addresses. This profile table must have been created from the SIS address subscription profile specification. |
|
Service key subscription profile table name |
java.lang.String |
Name of the profile table used to store composition provisioning information for triggerable service keys. This profile table must have been created from the SIS service key subscription profile specification. |
|
External platform profile table name |
java.lang.String |
Name of the profile table used to store the definitions of external service platforms. This profile table must have been created from the SIS external platform profile specification. |
|
Network interface definitions profile table name |
java.lang.String |
Name of the profile table used to store the definitions of network interfaces. This profile table must have been created from the SIS network interface definitions profile specification. |
|
Network routes profile table name |
java.lang.String |
Name of the profile table used to store network routes. This profile table must have been created from the SIS network routes profile specification. |
|
Experimental features profile table name |
java.lang.String |
Name of the profile table used to store the experimental feature configuration information. This profile table must have been created from the SIS experimental features profile specification. |
|
Trigger address tracing profile table name |
java.lang.String |
Name of the profile table used to store fine-grained tracing information for arbitrary addresses that may appear in trigger events. This profile table must have been created from the SIS trigger address tracing profile specification. |
|
Originating trigger address tracing selection |
com.opencloud.slee.resources.sipsis.management.SipTriggerAddressTracingSelector[] or com.opencloud.slee.resources.insis.management.INTriggerAddressTracingSelector[] |
An array of trigger-address-tracing selectors (which specify the initial event parameters to examine for initial events from the originating call state model), to look for a profile in the trigger-address-tracing profile table when fine-grained tracing is enabled. You can select the following parameters: Calling Party Number, Called Party Number, Called Party BCD Number, Redirecting Party ID, Location Number, Original Called Party ID, Additional Calling Party Number, Destination Subscriber Number, SmscAddress, Request-URI, From, To, P-Asserted-Identity, P-Called-Party-ID, and P-Served-User. You can specify zero or more selectors. The SIS searches for profiles in the trigger-address-tracing profile table using the unmodified address from each selected trigger event parameter. |
|
Terminating trigger-address-tracing selection |
com.opencloud.slee.resources.sipsis.management.SipTriggerAddressTracingSelector[] or com.opencloud.slee.resources.insis.management.INTriggerAddressTracingSelector[] |
Same as the originating trigger-address-tracing selection, except that it applies to initial events from the terminating call state model. |
|
Third-party trigger-address-tracing selection |
com.opencloud.slee.resources.insis.management.INTriggerAddressTracingSelector[] |
Same as the originating trigger-address-tracing selection, except that it applies to initial events for third-party (network-initiated) calls. |
|
Concatenated FCI interaction mode delimiter |
byte[] |
Byte array of length zero or more, used as a delimiter between multiple furnish charging information (FCI) requests sent during a particular instance of service interaction. Used only if the concatenated FCI interaction mode has been specified for a service composition. |
|
Fine-grained tracing enabled |
boolean |
Boolean flag that indicates whether the fine-grained tracing facilities on the SIS are enabled (true) or disabled (false). Checking fine-grained tracing options for an initial event, such as looking up the trigger address tracing profile table, incurs a small additional overhead — so this option lets an administrator eliminate that performance penalty if not needing fine-grained tracing. |
|
Default service timeout |
long |
The default timeout period, measured in milliseconds, that the SIS uses when waiting for a response to an event from a composition service or an extension component. If it gets no response within the timeout period, the SIS assumes the service or extension component is non-responsive, and if it is a composition service, removes the service from further interaction with the network dialog. The default timeout period is 2s, and the minimum permitted timeout is 100ms. |
|
Audit level |
com.opencloud.slee.resources.sis.management.AuditLevel |
The SIS audit logging level. |