Metaswitch Service Assurance Server (SAS) is a platform for analyzing call processing data and diagnosing call processing issues in both fixed line and mobile networks. It offers a web-based user interface (UI) in which the detailed call processing information it received from other network elements is displayed. Through the UI, you can examine the detailed history of how each call was processed.
Rhino SAS API is an API that Rhino TAS provides. With the API, you can send data to SAS servers from within your Rhino application, such as a service or a resource adaptor. An application with SAS tracing capability allows support personnel to use SAS to analyze the calls that it processed and investigate the cause of any issue.
In terms of the API architecture, Rhino TAS provides a SAS facility, with which applications can send diagnostic data to configured SAS servers. From the SAS facility, you can create a trail, which is the primary interface for reporting data to SAS. Multiple related trails form a trace, which reflects a distinct occurrence of subscriber activity. The most common trace type is a call. Trails are composed of two message types: events and markers. An event is a structure for capturing call processing data to be sent, while a marker is a tag for identifying or associating trails.
For example, in an application you can define an event that captures certain processing data of a call.
In your processing logic, you can assign a marker such as CALLING_DN_MARKER to a trail
or use a marker such as IMS_CHARGING_ID_MARKER to associate multiple trails.
Markers that identify a call enable SAS users to search for the call.
Markers that associate trails enable the users to view the full call flow.
