WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Usage records for Parlay X Call Notification over SIP/IMS

Parlay X Call Notification over SIP/IMS uses the service usage record to store network events, caller information, and called party information.

Each Telecom Web Services Server Web service implementation generates a service usage record that describes how the service was used for accounting and billing purposes. Service usage records are stored in relational table format. Each service usage record contains common event data that can be used to unique identify the service record, and that references a properties table containing application-specific attributes. This provides a uniform infrastructure for creating and storing service usage records.

Service usage records consist of general service usage information that may be generated at multiple points during service execution. An event type field is used to differentiate the different recording points. Each service implementation defines the event types (generation points), status codes, and service data attributes that are generated for storage in the service usage table. The Parlay X Call Notification over SIP/IMS creates a service record by calling the Usage Record component Web service.

Service data for CallNotificationManager operation

The following table lists part names and service attributes used by the CallNotificationManager.
Table 1. startCallNotification and stopCallNotification service attributes and descriptions
Attribute Description
SERVICE Identifies the service implementation that is writing the usage record
EVENTTYPE Identifies the place in the service implementation where the service record is recorded
CODE One of the following:

0 = Operation successful
1 = General failure

REQUESTER Name requesting the operation
METHOD Identifies the method writing the usage record. If there is an error, a brief failure reason will be attached to the operation and separated by ":" (for example; setAddressBean:RemoteException)
CORRELATOR Correlator value sent with the request
CALLED_PARTY Not available for: stopCallNotification
CALL_EVENTS A string of combination network events from:

called_number
busy
no_answer
not_reachable

Service data for CallNotification operation

The following table lists part names and service attributes used by CallNotification operation.
Table 2. CallNotification service attributes and descriptions
Attribute Description
SERVICE Identifies the service implementation that is writing the usage record
EVENTTYPE Identifies the place in the service implementation where the service record is recorded
CODE One of the following:

0 = Operation successful
1 = General failure

CALL_NOTIFICATION One of the following:

Sending = Ready to call PX Notification Delivery Web service
Error = Invoking PX Notification Delivery Web service error

CORRELATOR The correlator value is sent with the entity bean
CALLER Converted to a string
CALLED_PARTY Converted to a string
NETWORK_EVENT The network event that triggered the notification. The event can be any one of the following:

NotifyCalledNumber
NotifyBusy
NotifyNotReachable
NotifyNoAnswer




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.