Procedure 14.20: UPDATE SAS CUSTOM ANNOUNCEMENTS
ASP (PVN) AND AIN
ONLY
OVERVIEW
This document gives the instructions for updating or changing an existing Service Announcement System (SAS)
custom announcement data base. This document is not for growth: refer to
235-105-231
for growth.
NOTE:
This update is Software Release sensitive and not office dependent. Insure that the office and the update
are the same software release.
It is assumed that those who are using this document are experienced in the use of recent change, Office
Dependent Data (ODD) activities, trunk line work station, and Master Control Center (MCC) activities or have
access to technical support in these areas. It is also assumed that the telephone company/switch owner engineering
group has provided completed Growth Recent Change and Verify (GRCV) forms that are applicable to this update
process.
General Description
This procedure installs new SAS custom announcements for ASP (PVN), and AIN application only in an office with
an existing operational SAS environment.
NOTE 1:
The noted applications are Advanced Service Platform (ASP) which was previously known as
Private Virtual Network (PVN), and Advanced Intelligent Network (AIN).
NOTE 2:
The ASP application might apply to only a few new phrases (less than eight) and these would be updated
manually with recent change rather than with magnetic tape script. This information should be provided by
the telephone company/switch owner engineering group.
If this update is for another application other than those mentioned above then refer to Procedure
14.19
, "Update
SAS Custom Announcements
BRCS."
There are three possible office configurations:
(a)
Install new SAS memory board and flash memory cards.
(b)
Install new flash memory cards in an existing memory board.
(c)
Replace existing flash memory card in an existing memory board.
Hardware Description
The SAS unit can be located in either a DSU2 (digital services unit 2) or a CSU
(combined service unit). The DSU2-SAS unit consists of a maximum of four service groups numbered 0, 2, 1, 3
from left to right as viewed from the front of the unit. Refer to
Figure 14.20-1
. There is no redundancy in the
configuration, although service interruption can be minimized if replacement/update is performed in segmented
service groups, i.e. 0,2 and 1,3.
Service is distributed equally among the service groups. When a service group is removed from service then the
traffic is routed to the remaining operational service groups. During heavy traffic periods service could be effected
due to reduced service groups.
The TN1842 SYSTEM boards provide the SAS announcement storage memory. A minimum of one and a maximum
of four SASMEM boads are allowed. The SASMEM boards must be contiguous from board 1 to board 4. Each
SASMEM board can accommodate up to 8 flash cards. These cards do not have to be in any order and board 1
235-105-210
October 1999
Copyright © 1999
Page 1
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...