Call Detail Recording (CDR)

CDR functionality records the calling and the called number information, and the start and end times of each measured call. You administer this CDR functionality on a trunk-group basis within Communication Manager. At the end of a call, the information is made available to an adjunct server for functions such as costing, reports, and traffic analysis.

In the case of an SBS call, the data that is gathered and made available to the adjunct server does not change. However, since each trunk group that is involved in an SBS call can be administered to generate CDR reports, the system can generate two CDR records for each SBS call. The system generates one record for the SBS signaling call, and one record for the SBS bearer call.You cannot link the separate SBS signaling and bearer CDR records.

Since the signaling and bearer CDR records cannot be linked, you might prefer to measure only the bearer calls. The service provider is more likely to bill for the bearer calls. However, note that the SBS bearer call is always answered by the SBS extension, even though the actual called party does not answer the SBS call. The parties on the SBS bearer call are not the actual originating and terminating parties. The parties on the SBS bearer calls are dummy users, who are internal to Communication Manager for the sole purpose of originating and terminating the bearer call.

Call Management System (CMS) and Basic Call Management System (BCMS)

You can administer the following entities to be measured for CMS or BCMS:

• A trunk group

• A Vector Directory Number (VDN)

• A hunt group

An SBS call can generate two separate CMS or BCMS records. The system can generate one record for the SBS signaling call, and one record for the SBS bearer call.

CMS and BCMS measure the SBS bearer call only if the bearer trunk group is administered to be measured. CMS and BCMS measure only the trunk bearer seize events and idle events.

The SBS signaling call is measured if the SBS signaling group is administered to be measured, or an endpoint on the SBS call is a measured object. A measured object can be an agent in a hunt group that is administered to be measured. The measured events on the SBS signaling call include not only the trunk signaling seize events and idled events, but also any endpoint events, such as agent hold.

The SBS signaling and bearer calls generate separate CMS or BCMS records with different Universal Call IDs (UCIDs). You cannot link these separate records.

Calling Party—Delay in Call Setup Time

When originating an SBS call, the calling party might perceive a delay in call setup time compared to non-separated calls. This delay is caused by several factors. First, the SBS bearer call cannot be initiated until after the SBS signaling call initiates and a number to route the SBS bearer call to is received from the SBS Terminating Node. Then, the establishment of this SBS bearer call may be noticeably delayed relative to a non-SBS call, depending upon the type of bearer trunk selected and its trunk signaling protocol. Finally, DTMF digits must be sent over the SBS bearer call, so that the SBS Terminating Node can identify the correct bearer call, which also adds delay.

The exact amount of these delays depends upon several variables such as the amount of congestion in the IP network used for the SBS signaling call and the type of bearer trunk used for the SBS bearer call.

Given a fairly un-congested data network, SBS calls add approximately 1.5 seconds to the call setup time as perceived by the originating user. The SBS delay of approximately does not affect the originating user in any profound way. This delay is relative to a non-separated call over the same type of trunk as used for the SBS bearer call.

The time before the originator hears audible ringback may approach 10 seconds for a bearer trunk that is slow to outpulse digits (rotary). However, a non-separated call using the same bearer trunk would result in a delay of approximately 8.5 seconds before audible ringback is heard. Some bearer trunks can outpulse digits quickly. An example of message oriented signaling trunks is ISDN. For these types of bearers, the SBS induced delay is a majority of the overall delay until the originator hears audible ringback.

The called party will perceive no delays relative to non-separated calls. All setup, validation, and association of SBS signaling and bearer calls occur before alerting of the called party.

Feature Information Displays

SBS call display feature information such as Name and Number, call transfer or forward indication and transfer-to or forward-to party information is the same as QSIG calls. SBS call displays are driven exclusively by translations and signaling on the SBS trunk, and not by translations/signaling on the associated bearer trunk.