Parlay X Call Notification over Parlay uses the Usage Record component Web service to record events in a application that sends Web service requests to the network mapper for the creating, registering, and reporting of network related events.
For accounting and billing purposes, each TWSS Web service implementation generates a service usage record that describes how the service was used. 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.
Parlay X Call Notification over Parlay creates a service record by calling the Usage Record component Web service.
The following table lists part names and service attributes used by startCallNotification and startCallDirectionNotification:
Attribute | Description |
---|---|
REQUESTER | The requester that invokes the operation |
SERVICE | The name of the service registering the notification |
TARGET | The target string after the validation is processed |
START_TIME | The start time of the notification |
RESPONSE_TIME | The time it takes to process the response, in milliseconds |
NOTIFICATION_ENDPOINT | The endpoint which attempts the notification delivery |
NOTIFICATION_CRITERIA | The notificationCriteria value which determines the status of the notification delivery attempt, should a network attempt occur |
ASSIGNMENT_ID | The returned Parlay gateway assignment ID |
CORRELATOR | The correlator used to identify the notification with the requester and service |
The following table lists part names and service attributes used by stopCallNotification and stopCallDirectionNotification:
Attribute | Description |
---|---|
REQUESTER | The requester invoking the operation |
SERVICE | The name of the service which registers the notification |
START_TIME | The start time |
RESPONSE_TIME | The time it takes to process the response, in milliseconds |
ASSIGNMENT_ID | The returned Parlay gateway assignment ID |
CORRELATOR | The correlator used to identify the notification with the requester and service |
The following table lists part names and service attributes used by Error attributes:
Attribute | Description |
---|---|
FAILURE_DETAIL | Detailed error message |
FAILURE_REASON | Message which indicates the type of error that occurred. Has to be one of the following: SVC xxxx |