m essw switch selective call forwarding local...

LT PRACTICESLT 231-390-236, Issue 8

Lucent TechnologiesoBellLabs Innovation .

M ESSw Switch

Selective Call Forwarding

Local Area Signaling Services

Feature Document

Contents Page

1. Introduction 1

Economic Worth 1

Availabil’ky 2

Feature Groups 2

Feature Assignment 2

2. User Perspective 2

User Profile 2

Customer Premises Equipment 3

Feature Description 3

A. Selective Call FomardingScreen List Editing 3

B. Terminations to SelectiveCall Forwarding Lines 5

Special Planning Considerations 5

Activation 6

A. Screen List Editing 6

B. Selective Call ForwardingTerminations 7

Deactivation 8

Abnormal Operations 8

Interactions 10Restriction Capability 10

3. Engineering 11

Hardware 11 ,

Software 11

A. Base Generic Program 11

B. Optionally Loaded FeatureGroups 11

C. Parameters/Call Store Areas 11

D. Translations 13

Real Time 14

4. Implementation 14

Assignment Restriction 14

Set Cards 15

A. INS Feature Groups 15

B. General LASS Set Cards 15

hcerd Technologies InG - hpli~~This document contains proprietary information of

Lucent Twhnoiogiea Inc. and is not to be disclosed or usedexcept in accordance with applicable agreements

Copyright e 19% Lucent Technologies Inc.Unpublished and Not for Publication

AH Rights ReservedPrinted in L!.SA.

August 1996

L 2 3 1 - 3

L i bS u b s1T r a n sF o1 A S pD iC hfR e cC h aM e s1 R eD iN

V e r i f i1 E d2

A

M e a s u1A u t oM e sA c c o1

6 S I

R e f e r1A L P r a c1B O tD o c u m1

A

1 S i nA c t iS e l eC aF o r wT e r mT r e a2

S e l eC aF o r w( lG e nP r oT e r m iT r e a

E nR e mD i r eN uf S i nA c t iS e lC aF o r w2

S c rL iE d iA c t iS e q u

S c rL iE d iD e a c tS e q u2

●

A 1

,,.

LT Practices LT 231-390-236, Issue 8

1. Introduction

1.01 The Selective Call Forwarding (SCF)feature is a Local Area Signaling

Services (LASS) feature that allows a customerto preselect calls that should be forwardedbased on the identity attribute of the callingparty. An identity attribute maybe the callingline directory number (CLDN) or the centrexextension of the calling line. The customercreates a screening list that contains theidentity attribute for each calling party whosecalls are to be forwarded. A call from a stationthat has its identity attribute on the customer’sscreening list is forwarded. All other callsreceive standard terminating treatment.

1.02 This practice is being reissued toinclude information for the Advanced

Intelligent Network (AIN) Release 0.1Termination Attempt Trigger (TAT)featuresimpacting Selective Call Forwarding.

1.03 Lucent Technologies welcomes yourcomments on this practice. Your

comments aid us in improving the quality andusefulness of Lucent Technologiesdocumentation. Please use the FeedbackForm provided in this practice or call theLucent Technologies DocumentationPreparation Group at 708-224-7053.

1.04 Additional copies of this practice,associated appendixes, and all

referenced practices may be ordered from theLucent Technologies Customer InformationCenter. One of the following methods shouldbe used:

(a) Lucent Technologies Employees:Lucent Technologies employeesshould mail Form IND 1-80.80,available from the Lucent TechnologiesCustomer Information Center, to:

Lucent Technologies Inc.Customer Information CenterAttention: Order Entry Department2855 N. Frankfin RoadP. O. Box 19901Indianapolis, Indiana 46219-19!39

or

Call 800-43245600

(b)

(c)

(d)

‘> NOTE:When orderingdocumentation from theLucent TechnologiesCustomer Information Center,each Lucent TechnologiesBusiness Unit/Division mustbe identified and all requiredbilling information must beprovided.

Local Exchange Carrier (LEC):Orders should be processed throughyour Technical Information ResourceManagement (TIRM) coordinator. Ifyou are unsure who your TIRMcoordinator is, call 800-432-6600.

Federal Government: These ordersshould be processed through:

Lucent Technologies Inc.P. O. Box 20046Greensboro, NC 27420

or

call 919-279-7424

All Others: Call 8004324%00.

1.o5 Every effort has been made to ensurethat the information in this practice is

complete and accurate at the time of printing.However, information is subject to change.

1.06 This practice is issued by

Document Preparation Groupc/o M. W. AuterLucent Technologies Inc.Network Software Center2600 Warrenville RoadLisle, IL 60532

Economic Worth

1.07 With the Call Forwarding Variable (CFV)or Call Fomvarding Usage Sensittie

(CFUP) POTS feature, the forwarding of allcalls to the remote station can bedisadvantageous. The SCF feature avoids this.Terminating calls are screened based on acustomer’s preselected list of identityattributes. The identity attributes on thescreening list determine which calls are

August 1996 Page 1

LT 231-390-236, Issue 8

forwarded.

1.08 The Single Activation SCF feature allowsthe customer to activate SCF with one

activation request. Before the Single ActivationSCF feature, the customer had to activateCFV/CFUP and then activate SCF. Thisenhancement allows the customer to avoid the2-step activation procedure. Further, with theSingle Activation enhancement, the customerdoes not have to subscribe to CFV and theoff ice does not require CFUP.

Availability

1.09 The SCF feature is a IASS feature and isgenerally available with the 1AE9

generic program.

1.10 The Single Activation SCF feature isavailable in the 1AE1Ogeneric program.

It is the standard version of SCF.

1.11 The Total Separation of SCF (TSCF)optional feature is available in the 1AE1O

generic program. The Single Activation SCFfeature does not allow CFV and SCF to beactive at the same time. The TSCF featureoffers complete separation of CFV and SCF,thus, allowing the two features to be activeconcurrently. Refer to Part 6 A(l 2).

1.12 The Inter-Local Access and TransportArea (IATA) Calling Party Number/

Billing Number Delivery and Related Services(CPNBND) feature is available with thelAE11and later generic programs.

1.13 The Shared/Split N)(X (S/SNXX)enhancement is available with the

1AE1Oand later generic programs.

1.14 The LASS Office Option Feature(LOOF) is available with the 1AE1Oand

later generic programs.

1.15 Please contact your LucentTechnologies representative for feature

licensing information.

Feature Groups

1.16 The SCF feature requires MSS optionalfeature groups 9SCF or 9SIASA for

intraoffice only applications. For interofficeapplications, 9SCF [which requires commonchannel signaling (CCS) for interoffice

applications] or 9SLASS is required. Refer toPart 6 A(8) for a general description of thel&S features.

1.17 The 9SBNI feature group is required todeliver the Calling Party Number (CPN)

across IATA boundaries. The NeWorkInterconnect (Nl) feature provides the 1A ESSswitch system with the ability to interface withInterexchange Carriers using the CCS7Integrated Services User Part Protocol. Refer toPart 6 A(l O)for NI information.

Feature Assignment

1.18 The SCF feature is provided on a singleoffice (intraoffice) basis or on a multiple

office (interoffice) basis. When applied on aninteroffice basis, the end offices must bewithin the LASS boundary area.

1.19 The LASS boundary area is ageographical area within which the

telephone company offices are connected bya Common Channel Signaling System 7 ●

(CCS7) network. Refer to Part 6A(7).

120 For inter-MTA delivery of the CPN, thesignaling network must be a CCS7

network. If the LASS boundary area extendsbeyond a LATA,NI protocol is required in alloff ices within the network. Refer to Part 6A(10).

121 The SCF feature maybe usage sensitiveand available to all lines in a IASS

off ice/boundary area that have a unique lineequipment number (LEN). The SCF feature canalso be provided on a subscription basis.

2. User Perspective

User Profde

2.01 The SCF feature is provided to POTSusers and, in the 1AEI Oand later

generic programs, to centrex groups on ausage-sensitive or subscription basis. In the1AE9 generic program, the SCF is provided tocentrex groups on a subscription basis only. Inthe 1AE9 generic program, the SCF featureapplies only to users that have access to eitherCFV or CFUP.

Page 2 August 1996


Customer Premises Equipment

2.o2 The SCF feature requires only atelephone station set at the customer

premises. Either dial pulse (DP) or dual tonemultifrequency (DTMF) telephones may beused. The SCF feature is optimized for DTMFcustomers; extensive use is made of the star(*) and number sign (#). Refer to paragraph2.39. A DP customer must dial 11 for* and 12for #. (A DTMF customer may also dial 11 and12 instead of* and #.)

Feature Description

A. Selective Call Forwarding Screen ListEditing

2.03 When a user dials the SCF access code,a check is made to determine if the line

is restricted from using LASS or SCF. Theaccess code is translated via the prefixedaccess code translator (PACT) for POTS linesor via the centrex translator (digit interpretertables) for centrex lines. If the access code isunassigned for the office or centrex group, theline receives reorder treatment. Thistranslation also checks the line prohibitindicators. The line prohibfi indicators arelocated in the line equipment number class 2(LENC12) word. The LENCL2 word containseither the access code restriction group(ACRG) field (POTS lines) or the centrexaccess treatment (CAT)code field (centrexlines). These fields can be used to deny a lineservices that are associated with an accesscode. If access is not allowed, the line receivesreorder treatment.

2.04 If the access code is assigned, therestriction field (RESTR)of the primary

translation word (PTW) from the PACT or thedata word from the centrex digit interpretertable is used to evaluate the ACRG or CATcode for the requesting line.

2.05 If the ACRG/CAT evaluation indicatesthat the customer is allowed access, the

class of service prohibn indicators in the PTWof the class of sewice information (CLSI)translator are checked. This check determineswhether the line should be denied access tothe SCF feature because of its setvice class.The classes of service which should be deniedaccess are listed in paragraph 4.02.

2.06 If the class of service of the user isallowed access to SCF, option word L of

the LEN supplementary auxiliary block ischecked. If this word is not assigned and theLASS Office Option Feature (LOOF) is notloaded, no restrictions apply, and the user isallowed access. If this word is not assignedand LOOF is loaded, word 19 of the officeoptions table is used as the default option wordL. If the LEN option word L exists or the defaultoption word L is used, it is checked to see ifthe user is denied access to SCF. If SCF is notdenied, processing continues. If access to SCFis not allowed, the line receives IASS denialannouncements.

2.07 Further checking is done for restrictionsthat apply specifically to the LASS

screening features. In particular, certainmultiline group (MLG) members are restrictedfrom using SCF (paragraph 4.03).

2.o?3 For offices with Single Activation SCF, acheck is made to verify that the

customer does not have CFV active. Foroffices without Single Activation SCF, a check “is made to ensure that the line has CFV orCFUP.

2.09 If the line is denied access to SCF forfailure to satisfy the preceding

conditions, the call is routed to announcement.For the 1AE9 generic program, if the line isallowed access to SCF, control is passed tothe screen list editing (SLE) primitive. ForSingle Activation SCF, the customer isprompted for the remote directory number(RDN) before control is passed to the SLEprimitiie. Refer to Part 6A(8) for further detailsconcerning the LASS primitives. The LASSprimitives include: SLE, retrieval of distant linestatus (RDLS), retrieval of calling line DN(RCLDN), and line history (LH).

2.10 If resources are available, an ATI(announcement sewice circuit [ASC]

trunk interface) is seized and replaces thecustomer digit receiver (CDR). A SLE register(SLR) replaces the originating register (OR). ASLE buffer (SLEB) is initialized with the currentcopy of the screening list. At the end of theediting session, the contents of the SLEB areused to update the screening list.

2.11 If the Single Activation SCF feature is inthe office, the RDN editing routine edits

and validates (paragraph 4.06) the RDN beforebeginning the screening list editing session. Ifthe RDN is valid, a confirmation

August 1996 Page 3

LT 231-390-236, Issue 8

announcement is played,

2.12 When RDN editing is done, if noprevious RDN exists, a temporary

recent change (TRC) register for SCF is seized.If an existing RDN is changed, the existing TRCis deleted and a new TRC is seized. If anexisting RDN is just confirmed (that is, notchanged), the existing TRC remainsunchanged. If the new or changed RDN is inanother off ice (interoffice), a 2- or 3-wordcustomer originated recent change (CORC)block is seized. if the office has the CLOGfeature package, the CORC02 message isoutput on the maintenance TTY.

2.13 Refer to paragraphs 2.51 through 2.53for system response when the recent

change (RC) area is full or the office is in theinhibit RC/CFV mode.

2.14 The SLE primitive returns control to SCFto verify the validity of an identity

attribute which is to be added to the SCFscreening list. The SCF feature uses the RDLSprimitive to verify an identity attribute. TheRDLS primitive requires as input the identityattribute to be verified, the client ID, a returnaddress, and the call register address (CRA).The SCF client ID indicates to RDLSthatoriginating characteristics are requested. If theattribute is a centrex extension, the extensionis converted to a 10digit DN.

2.15 The CPNBND feature provides an inter-LATASLE blocking option to block the

sending of Transaction CapabWy ApplicationPart (TCAP) query messages for statusinformation of inter-LATA numbers. The RDLSprimitive determines if the DN to be added tothe screening list is intraoffice, interoffice,intra-LATA, or inter-lATA. If RDLS identifies thenumber as inter-iATA, and the CPNBNDfeature group is loaded, control returns to SCFand the SLE blocking option is checked.

2.16 The inter-lATA SLE blocking option isan office option that blocks or allows a

TCAP query message for originatinginformation of an inter-UTA number. Thisoffice option is implemented as a bit in theoff ice options table translator (refer toparagraph 3.39). The option, when set to“blocK’, prevents the inter-lATA DN from beingplaced on the end user’s screening list. If theSLE blocking option is set to “blocK, no returnis made to RDLS to send the TCAP query.Instead, SCF returns long-term denialindication to the SLE primitive. If the blocking

Page 4

option is set to “allow, control returns to RDLSto send a TCAP query message.

2.17 If the CPNBND feature group is notloaded, control does not return to SCF

from the RDLS primitive. Instead, the TCAPque~ message is sent. Refer to paragraph2.27 for additional information.

2.18 The S/SNXX enhancement optionallyallows a TCAP query message to be

sent for a number that has a shared or splitNXX. A shared NXX is when all ten thousandDNs for that NXX are shared between switches.A split NXX is when thousand’s blocks ofnumbers are assigned to different switches.Without this option, a 1A ESS Switch can notadd a DN having a shared or split NXX to ascreening list. The RDLS primitive identifiesthese numbers as intraoffice, and terminatingDN translations used to get the statusinformation for intraoffice DNs, indicate thatthese numbers point to a route index. As aresult, the customer receives long-term denialtreatment. With the S/SNXX option active, ifterminating DN translations indicate an ●

outpulsing trunk with a terminating major classof trunk group without ringing, the DN istreated as interoff ice and a TCAP querymessage is sent to the distant switch to retrieveline status information. This off ice option isimplemented as a bn in the office options tabletranslator (refer to paragraph 3.4o).

2.19 If RDLS is successful, the followingstatus information is returned to SCF:

(a) Valid DN (that is, assigned).

(b) Input DN matches calling line DN.

(c) Originating major class code.

(d) Multistatus indicator (1AE9 genericprogram).

(e) Temporarily-out-of-service indicator(1AE1Oand later generic programs).

If the number is added to the list, anannouncement is played.

220 A failure to verify the identity attribute isreturned to SLE by SCF if any of the

following conditions exist:

(a)

(b)

(c)

Resources required by RDLS areunavailable.

RDLS request times out.

DN or centrex extension input by userdoes not match the DN or centrex

August 1996

..”


(d)

(e)

(f)

extension that would be retrieved byRCLDN.

DN is a multiparty line (1AE9 genericprogram only).

DN or centrex extension (centrex only)is denied origination.

DN is temporarily out-of-service - thisinformation is available only for a DN inanother off ice that is not a 1A ESSSwitch.

If the number cannot be validated, anannouncement is played.

221 When SLE processing is done, SLEreturns control to the SCF feature. The

SLR contains required automatic messageaccounting (AMA) data. The AMA routineprocesses the data and writes an AMA record.A new and modified list indicator is added tothe AMA record. The following SLRinformation is formatted and passed to theAMA routine:

(a)

(b)

(c)

Start and end times of the editingsession

Number of entries on the screening list

Status of the screening list

(d) Customer billing DN

(e) Client ID.

After the necessary information is copied fromthe SLR, the register is released and return ismade to the main program.

B. Terminations to Selective CalfForwarding Lines

222 Initially, on any call terminating in anoffice with the LASS SCF feature, the

identity attribute of the calling party is receivedfrom the originating office. As mentionedpreviously, the identity attribute may be theCLDN or centrex extension. Call processingproceeds in one of two directions dependingupon whether the switch has Single ActivationSCF or not.

223 The criieria for forwarding callsterminating to Single Activation SCF

(1AE1Oand later) lines follow. (Refer toFigure 1.)

(a) The terminating line has the SCFfeature.

(b)

(c)

(d)

The SCF feature is active.

The calling party identity is obtainable(that is, there is CCS connectivitybetween the originating andterminating off ices).

A match exists between the callingparty identity attributes on the SCFscreening list.

Calls that meet all of the preceding conditionsare forwarded to the RDN. Calls that are notforwarded receive standard terminatingtreatment.

224 In case of SCF without single activation(1AE9 generic program), it is

determined whether CFV is active. Refer toFigure 2. If CFV is not active, standardtermination continues. If CIW is active, a checkis made to determine if SCF is also active. IfSCF is not active, the call forwardsunconditionally. If SCF is active, the identityattribute of the calling party is compared to thescreening list. If the identity attribute of thecalling party is specified on the list, the call is ●

forwarded to the remote station specified forCFV. If not, standard termination is continued(that is, termination to the called base station).

225 For forwarded calls (with or withoutSingle Activation), ring reminder

(RNGR) maybe provided at the base stationdepending on the RNGR option of the basestation.

2Q6 The remote station may also have aLASS screening feature active. If so, the

CLDN of the originating party, not the CLDN ofthe base station, is used for screening at theremote station.

Special Planning Considerations

227 Currently, there are no specificationsavailable which provide instructions on

how to route inter-LATATCAP messages forLASS (neither the query messages nor theresponse messages). If CPNBND is not loadedor if CPNBND is loaded with the blockingoption set to “allov/’, a TCAP message is sentfrom the originating end office but it may notbe possible to deliver it to its destination; or forthe destination to correctly deliver theresponse back to the originating office. The

August 1996 Page 5

LT 231-390-236, Issue 8

inter-lATA application of the TCAP issuecurrently has not been resolved. Therefore, ifthe SLE blocking option is not set to “block’, itis the responsibility of the operating telephonecompanies to make the necessary routingtranslations in their signal transfer points(STPS). These translation changes shouldallow TCAP messages to be routed acrossLATAboundaries to assure that TCAPmessages are appropriately delivered.

Activation

A. Screen List Editing

228 The SCF activation includes thefollowing two processes:

(a)

(b)

Defining/modifying the RDN. [Refer toFigure 3 for lAE1 Oand later genericprograms; refer to Part 6 A(I ) and A(6)for prior generic programs.]

Creating/editing the SCF screening list(Figure 4),

Edit the Remote Directory Number

2Z9 The SCF feature is activated by dialingthe SCF activation code. Single

Activation SCF allows a customer to specifythe DN to which calls are forwarded during theSLE process. Without the Single Activationenhancement, the CFV or CFUP feature mustbe activated prior to SLE.

230 With Single Activation SCF, the usergoes off-hook and dials the SCF

activation code. If the RDN exists, it is voicedback to the user. The user may retain orchange the RDN. If Single Activation is not yetactive, and no RDN exists, the user must enterthe RDN before proceeding with the SLEprocess.

231 The RDN can be in any of the followingformats:

(a)

(b)

(c)

Page 6

[1OXXX] + [1] + 7/10digit DN [#].(The base station is not carrierrestricted.)

[1OXXX] + l/2digit speed call (SC)access code + [#] (end of dialingsign). (The SC access code must bedefined previously with a valid DN.)

[101XXXX] + [1] + 7/10 digit DN [#].(The base station is not carrierrestricted. 4digit carrier access code

(d)

(e)

(9

(9)

dialing allowed in lAE12 and later.)

[101XXXX] + 1/2digit speed call (SC)access code + [#] (end of dialingsign). (The SC access code must bedefined previously with a valid DN. 4-digit carrier access code dialingallowed in 1AE12 and later.

Centrex extension (centrex intragroupforwarding).

Centrex Extension Trigger (data type 8,subtype 1 or 2). Refer to Part 6 A(9)for information about the ASP/SSPFeature.

Centrex extension (data type 2),Centrex attendant (data ~pe 6) orCentrex Extension Trigger (data type 8,subtype 1 or 2) when the line isassigned the ASP/SSP Off-Hook Delay(OHD) capability. For informationabout the ASP/SSP Feature, refer toPart 6 A(9).

Brackets symbolize optional information within.●

232 If an RDN is entered, it is validated andvoiced back to the user for

confirmation. In the case of an invalid RDN(paragraph 4.06), the user is informed andgiven three additional chances to reenter theDN. The RDN is stored in the switch as long asSingle Activation SCF is active.

233 The POTS user can use specialcharacters “*” and “#” during the LASS

SCF RDN entering sequence. These charactersmay be used when entering an RDN (to nullifythe timing interval) as in the SLE session(paragraph 2.39). The centrex common blocktranslations have been modified to allowcentrex customers to use the “*” and “#”during an RDN entering sequence. Refer toparagraph 3.31. This modification is requiredbecause these characters are already used insome centrex dialing patterns (for example,*9).

Edit the SCF Screening List

234 After diafing the access code (or in thecase of SCF Single Activation, after

entering/modifying the RDN), the user is toldthat the SCF service is on and informed of thenumber of entries on the SCF screening list.This includes the number of private entries.

235 An SCF screening list is activated whenit is initially created during SCF

August 1996


activation. In 1AE9, a deactivated SCFscreening list is also activated by dialing theSCF activation cede. For Single ActivationSCF, the user must also specify an RDN inorder to activate a deactivated screening list.When the screening list is active and has atleast one identity attribute on it, the SCFfeature is ON.

236 The SLE primitive allows SCF users tobuild and manipulate a list of numbers

(VPi@y DNs) that SCF utilizes during callprocessing. The user is guided by SLE. TheSLE interactive procedure allows users to tailora screening list to their satisfaction. Refer toPart 6 A(8) for more information concerning theSLE primitive.

237 Although the SLE primitive interfaceswith individual users, it is transparent to

the user who perceives only the interactionwith the SCF feature. When editing a screeninglist (Figure 4), SLE allows a user to accomplishthe following:

(a) Create a list.

(b) Add entries.

(c) Delete entries.

(d) Hear the list.

(e) Obtain instructions.

238 The SLE primitive is activated when auser dials the SCF activation code. The

user also controls SLE operation by dialingvalid digit strings. A DP or DTMF telephonemay be used, however, a DTMF telephone ismore efficient. The following defines validtypes of character strings that maybe dialed(input) for use with SLE.

(a)

(b)

(c)

A command is an input string thatcauses immediate system action (thatis, play instructions, read list, deleteentry, add entry, delete list).

A subcode is a 2digit string thatimplies further input is required (forexample, subcode 02 is used to prefixcentrex extensions).

An identity attribute is an entry on thescreening list (that is, DN, centrexextension). An identity attribute maybe added from the incoming linehistory block (ILHB) by dialing 01.

239 When collecting digits in a LASS SLEsession, a timing interval is def ined to

determine the amount of time that shouldelapse between the collection of digits. If thistiming interval is exceeded, time-out occursand digit collection ceases. Also, whenentering a DN, the user waits for the timinginterval to elapse before the DN can beprocessed. To nullify this timing interval, thespecial character # can be used to indicateend-ofdialing, and an entered DN will beprocessed immediately. In case of misdialing aDN, the special character ● nullifies the timinginterval and cancels the processing of theentered digits; at this point, the user may redialthe desired DN.

2.40 The user can terminate the activationsession at any time by simply going

back on-hook. In 1AE9, a SCF activationsession is considered successful if thescreening list contains at least one identityattribute. For 1AE1Oand later, a SCFactivation session is considered successful ifthe RDN exists and the screening list contains #at least one identity attribute.

B. Selective Call Fomvarding Terminations

2.41 The SCF feature, in the 1AE9 genericprogram, is an enhancement of the CFV

feature. The CFV feature functionsindependently of SCF, however, CfW must beactive if the SCF screening list is to be used(Figure 2).

2.42 In reference to the preceding, the user isresponsible for ensuring that the CFV

and SCF configuration is correct to obtain thedesired terminating treatment. (Anannouncement is provided during SLE initialannouncements to inform the user of the CFVdependency.) For example, if a user has SCFand CFV active and deactivates CFV, the SCFlist will remain active but will not be applied toterminating calls. Unless the user specificallydeletes or deactivates the screening list,subsequent activation of CFV results in theselective fomvarding of calls from the parties onthe screening list. When call fomvarding andSCF are active, only those calls that originatefrom a party specified on the screening list arefo~arded.

2.43 Wth Single Activation SCF, callforwarding is activated when the RDN is

entered prior to editing the SCF screening list.Subsequent calls terminating to the line whenSCF is active are forwarded if the calling party

August 1996 Page 7

LT 231-390-236, Issue 8

number is specified on the SCF screening list.Forwarding will terminate to the destinationdictated by the RDN unless the remote numberis treated as an ASP/SSP trigger, in whichcase the Service Control Point (SCP) is queriedfor routing instructions. For information aboutASP/SSP, refer to Part 6 A(9).

2.44 For all generic programs, on forwardedcalls, RNGR is provided at the base

station if the line has the RNGR option; the callproceeds with the call forwarding function. Forcalls that are not forwarded, standardterminating treatment is provided (that is,termination to the base station).

Deactivation

2.45 When the user deactivates the SCFfeature (Figure 5), the screening list can

be saved or removed. To deactivate SCF, theuser goes off-hook and dials a uniquedeactivation code for SCF. The user is told thenumber of entries, including private entries, onthe screening list. The customer may terminatethe deactivation session by going back on-hook.

2.46 During the deactivation session, theuser may choose one of the following

actions:

● Delete all entries on the list.

. Delete only the private entries.

if the user simply goes back on-hook, theexisting screening list entries are saved and putin an inactive mode.

2.47 With the Single Activation SCF feature,the RDN is deleted upon termination of

the deactivation session.

Abnormal Operations

2.48 If the activation or deactivation accesscode dialed is unassigned, standard

error treatment is provided. If the user is notpermitted access to the SCF feature,reorder/’’denied IASS” 13A/14A recordedannouncement is provided when the accesscode is dialed.

2.49 If after dialing theactivation/deactivation access code,

there is a lack of system resources before an

ASC is connected, reorder is returned (forexample, no ASC circuits available or a SLR isnot available).

2.50 If the connection to the ASC has beenestablished, but a SLEB is unavailable,

the customer receives a denial announcementvia the ASC and dial tone is returned. If a SCFactivation is attempted, a “no resources”announcement is provided. If a SCFdeactivation (1AE9 generic program) isattempted, a “no resources” announcement isprovided. For 1AE1Oand later, if a SCFdeactivation is attempted, the user is told thattheir SCF sewice is now off, then a “noresources” announcement is provided.

2.51 The following occurs during an SCFact”wationattempt when the office is in

the CFV/SLE INH:RCSOURCE mode. In the1AE9 generic program, a two-stepactivation/deactivation process is required; theSCF and CFV features must beactivated/deactivated separately.

(a)

(b)

When an office is in the inhibit CFVmode, CFV cannot be activated (that ●

is, the RDN cannot be added orchanged). However, CFV may bedeactivated (the RDN mayberemoved). Activation/deactivation ofSCF is not affected.

When the office is in the inhibit SLEmode, SCF cannot be activated ordeactivated. Activation/deactivation ofCFV is not affected.

2.52 For lAE1 Oand later, the followingoccurs during an SCF activation attempt

when the office is in the CtW/SLEINH:RCSOURCE mode. If both CFV and SLEare inhibited, the results are the same as whenonly CFV is inhibited.

(a) When the office is in the inhibit CFVmode, reorder/’’denied IASS”13A/1 4A recorded announcement isprovided and dial tone is returned.

(b) When the office is in the inhibit SLEmode, a “no resources” denialannouncement is provided via the ASCand dial tone is returned.

For each of these cases, the resultingtreatment is the same whether the screeninglist exists or not. If a screening list exists, itsstatus remains unchanged. ...

Page 8 August 1996

LT Practices LT231-390-236,Issue 8

2.53 The following occurs during an SCFdeactivation attempt when the off ice is

in the CFV/SLE INH:RCSOURCEmode. Ifboth CFV and SLE are inhibited, the results arethe same as when only SLE is inhibited.

(a)

(b)

(c)

(d)

If the office is in the inhibit CFV modeand a screening list does not exist onthis line, a “no list” error announcementis provided via the ASC and dial tone isreturned.

If the office is in the inhibit CFV modeand a screening list does exist on thisline, the deactivation is allowed. TheSCF RDNTRC is also removed if oneexists.

If the office is in the inhibit SLE modeon the 1AE9generic program, a “noresources”denial announcement isprovided via the ASC and dial tone isreturned.

If the office is in the inhibit SLE modewith IAE1O or later, the user is told thattheir SCF service is now off, then a “noresources”denial announcement isprovided via the ASC and dial tone isreturned.

For cases (c) and (d), the resulting treatment isthe same whether or not a screening list existsfor the line at the time of the deactivationattempt. If an SCF RDNTRC exists, it isremoved.

2.54 For system failures not related to theASC, the “no resources”announcement

is played via the ASC before ending the editingsession. If the ASC is unavailable, thescreening list editing session is terminated.

2.55 Incorrect dialing by the user results inerror announcements. Generally,after

dialing incorrectly, a user may continue withthe SLE procedure; the call is not terminated.The system responds with an errorannouncement when either of the followingoccurs:

(a) Invalid subcode/command

(b) Incomplete dialing (not enough digits)

(c) Entry of extra digits.

256 There are two cases when time-outoccurs during SLE: interdigital time-out

and time-out between user actions. The systemresponds with an error announcement

indicating a dialing error in the case ofinterdigital time-out. In the case of time-outbetween user actions, the user is prompted formore input. This occurs whether the action issuccessful or unsuccessful. If the user doesnot dial within a specified timing interval afterthe prompt, the instructions are played. If theuser fails to dial after four consecutiveprompts, the call is dropped.

2.57 For Single Activation SCF, if an invalidRDN is entered, an error announcement

is returned through the ASC. If the maximumerror count is not exceeded, the user isprompted to reenter the RDN. After enteringfour consecutive invalid RDNs,the userreceivesan error announcement and isdisconnected.

2.58 Abandon can bean abnormaltermination of SLE. If abandon occurs

before actions requested by the user areexecuted, the last action requested by the useris ignored and the SLE procedure isterminated. All previous successful actions arepreserved (successful actions are indicated via “announcements). If a user goes on-hookbefore an entered identity attribute is verifid (areal-time break is taken to verify an interofficeidentity attribute), SLE treats the call asabandoned. Note that the time delay involvedin the real-time break is office settable, 1 to 6seconds (paragraph 3.37). An announcementis provided to indicate success or failure of theverification attempt.

239 If a user attempts to add the last callingline directory number (CLDN)from the

ILHB to the SCF screening list, and the CLDNis not available, an announcement is given.The CLDN may not be available if, for example,the last incoming call originated outside theLASSarea. Since line histo~ blocks (LHBs)are not maintained in duplicated call store onthe 1AE12and later generics, the CLDN maybe temporarily unavailablewhen switchresource limitations prevent retrieval of theILHB. An announcement is also given for thissituation. Referto Part 6 A(8) for details aboutLHB structures available on each generic.

2.60 An abnormality related to SCF occurswhen the identity of a calling party,

previously specified on the screening list, isnot available. This may be caused by lack ofCCS7 connectiv’~ for the interoff ice call, CCS7failure or major far-end overload/outage.When this happens, determination of whetherthe call should be forwarded cannot be made.

August 1996 Page 9

LT 231-390-236, Issue 8

As a result, the calls are not forwardedregardless of the specification of the callingparty identity in the SCF screening list.

Interactions

2.61 The SCF feature (1AE9 genericprogram) screening list is applicable

only to the existing CFV features which allow acustomer to change the RDN without a serviceorder (that is, WV and CFUP). Refer to Part 6A(l) and A(6), respectively, for informationconcerning the CFV and the CFUP features.

2.62 For 1AE1Oand later only, customersmay subscribe to Single Activation SCF

and/or CFV. However, these two features maynot be active at the same time.

2.63 In a centrex environment, centrex callforwarding outside (CTX-CFO) must be

allowed in order to designate an RDN that isoutside the centrex group.

2.64 The ASP/SSP feature impacts SCF asfollows (refer to Part 6 A(9) for detailed

information about the ASP/SSP feature):

(a)

(b)

(c)

For a POTS or Centrex line, callfomvarding processing of the RDN maydetect a Dialed Number Trigger. Whenthis happens, an ASP/SSP querymessage will be sent to the SCPdatabase and the call will fomvardusing the routing information returnedfrom the SCP. Dialed Number Triggerprocessing is provided in the 9FASP2feature package.

For a Centrex line, the RDN could bean extension built as a CentrexExtension Trigger. If this is the case,an ASP/SSP query message will besent to the SCP database during callfomvarding processing and the call willfotward using the routing informationreturned from the SCP. CentrexExtension Trigger processing isprovided in the 9FASP1 featurepackage.

If the POTS or Centrex line is assignedthe OHD capabiiitv, an ASP/SSPquery will always be sent to’the SCPdatabase during call forwardingprocessing unless “No Que@indication is specified for the RDNdigits. If “NO Query” is indicated, then

(d)

(e)

an ASP/SSP query will be sent to theSCP only if a Dialed Number orCentrex Extension Trigger is detectedfor the RDN digits. If the SCP is notqueried, then forwarding will be to thedestination dictated by switch-basedtranslations of the RDN. OHD triggerprocessing is provided in the 9FASP3feature package.

When a Centrex customer enters aCentrex extension as the RDN, thedialed digits (1 to 7 digits) are stored inthe CORC block if the extension is builtas a Centrex Extension Trigger. If theCentrex customer’s line is assignedOHD, then an extension entered forthe RDN is always stored in its dialedformat in the CORC block regardlessof whether the extension is a CentrexExtension Trigger. Note that storingthe RDN in its dialed digits formatdiffers from storage of an extensionwhen neither OHD nor CentrexExtension Triggers apply. In this case,the extension is stored as its ●

corresponding 7digit number with anindicator set to inform SCF to voiceback only the extension digits duringsubsequent activations.

When the RDN is a Centrex extensionand an OHD or Centrex ExtensionTrigger ASP/SSP query is sent to theSCP database, forwarding isconsidered intragroup even if therouting information fotwards the calloutside the Centrex group (that is,CTX-CFO is not applicable).

2.65 AIN Release 0.1 triggers that result interminations to SCF subscribers may

have received new Calling Party ID informationfrom the SCP. SCF screening is performed onthe latest Calling Party ID information. If theinformation has not been changed, the latestpre-quey Calling Party ID is used whenavailable. For more information about AINRelease 0.1 Protocol and Capabilities, refer toPart 6A(n).

Restriction Capability

2.66 Each of the IASS features can bedenied to certain classes of lines

(paragraph 4.02). The telephone company

Page 10 August 1996


determines the features that are included ineach service class. On a class of service basis,the RC:CCOL recent change message can beused to restrict access to ail SLE features.

2.67 The USS features can also be deniedto a specific line. On a per line basis,

the ACRG/CAT code f ield in the LENCL2 wordis used to determine if a IASS feature can beaccessed. The RC:LINE recent changemessage is used to change the ACRG/CATcode to allow or deny access to SCF for aspecific line. Refer to Patt 6 A(2) and A(3) forthe keywords associated with RC:CCOL andRC:LINE.

2.68 In addition to the ACRG/CAT codemechanism of feature denial, each line

has an option word L in the LENsupplementary auxiliary block to deny SCF ona per line basis. This allows for greaterflexibility than can be achieved via theACRG/CAT code mechanism. The wordcontains an indicator for each feature that isused to allow/disallow access to a requestedfeature. If allowed, this indicator also specifieswhether the customer is subscription or usagesensitive. Refer to Part 6 A(3).

2.69 An alternative mechanism to restrictingall lines access to LASSfeatures is to

implement the LASS Office Option Feature(LOOF). LOOF eliminates the need forACRG/CAT codes in offices implementing theIASS features on a subscription only basis byallowing all lines to dial the LASSfeatureaccess codes. After the access code is dialed,normal ACRG/CAT screening still applies but isnot required. The second level of screening isperformed on a class of service basis. The finallevel of restriction is the option word L check.LOOF, if loaded, will provide all lines without anoption word L a default option word L fromword 19 of the office options table. Word 19 ofthe off ice options table is the recent changedefault and, if LOOF is loaded, will also be thecall processing default for all lines without anoption word L. If a line has been assignedLASS features and has an LEN option word L,then the individual LEN option word L is usedinstead of the office default option word L.LOOF is controlled by fast feature 069.

3. Engineering

3.01 These guidelines are for planningpurposes only. The Central Office

Equipment Engineering System (COEES)Information System Document, Index 38,should be used to manually order and engineerthe 1A ESS Switch. The standardrecommended automated procedure isCOEES-Mechanized Ordering (MO).

Hardware

3.02 The SCF feature requires the followinghardware:

● CDR

● Tone or recorded announcement circuit(SD-1A218-01)

. ASC (SD-6AO03-01) and ATI ~M 504).

3.03 For interoffice applications, the SCF ‘feature requires the hardware necessary

to allow the switch to communicate over aCCS7 network. Refer to Part 6 A(7).

Software

A. BaseGeneric Program

3.04 The SCF feature uses some baseprogram store memory. For further

information concerning memory usage, refer toPart 6 B(l).

3.05 The Single Activation SCF feature isavailable in the 1AE1Oand later generic

programs.

B. Optionally Loaded Feature Groups

3.06 The SCF feature code is provided in theoptionally loaded LASSfeature package

required by the LASS or LASA feature group.Refer to Part 6 B(l ) for information about otherfeature packages needed for SCF. Refer toPart 6 B(4) for feature package word sizeinformation.

C. Parameters/CaIi Store Areas

3.07 Refer to Part 6 B(3) and B(4) forcomprehensive parameter information.

August 1996 Page 11

LT 231-390-236, Issue 8

Parameters

3.08 Parameter L9SCF SIZE (set cardIASCFE) is requir-d specifically for

SCF. It defines the size of the SCF list (that is,the maximum number of entries) per customerin an office.

3.09 The following parameters are related tothe SCF feature:

(a)

(b)

(c)

(d)

Parameter L9EDIT BUF ADMINcontains the startitig address of theSLEB busy/idle head cell.

Parameter L9EDIT BUF NSIZEcontains the numb~r of ~LEBsprovided and the size of an SLEB.

Parameter L9EDIT BUF PTR containsthe starting address of the SLEB block.

Parameter R2SLEDB contains theaddress and length of the call storetable (RSLEKMDB) used by SLE tobuild keyword message data block(KMDB) information.

3.10 Parameter B6LASS is the Compooldefined address and size of the LASS

traffic count block. The lASS traffic countblock is 50 words in length.

3.11 Parameter B6SLE contains the Compooldefined address and size of the SLE

traffic count block. The SLE traffic count blockis six words in length.

3.12 Parameter C7BATBTAcontains thestarting address of the buffer

administration timing block (BATB) table. Thisgroup of call store blocks provides the meansfor applications to store data over the real-timebreaks involved in interoff ice informationexchange. The BATBtable is allocated inunprotected variable DCS. Parameter wordC7BATBTA + 1 contains the number of 6-wordBATBs in the table. Parameter C7BATBTA + 2contains two parameter values. The MAXTIMEfield contains the maximum timer value that aBATB may have. The MAXNOTIFY fieldcontains the maximum number of clients thatmay be notified of time-out in a real-timesegment.

3.13 The SCF feature requires ILHBs to storethe last CLDN. Refer to Part 6 A(8) for

the parameters needed on each generic toimplement LHBs.

Call Store

3.14 Refer to Part 6 B(2) for call store datalayout information.

3.15 If CCS7 is used, the BATBtable isrequired to provide timing on interoffice

RDLS TCAP queries. If the Message InterfaceProcessor (MIP) is loaded, and set card BATBS(paragraph 4.17) is nonzero, the size of theBATBtable is equal to six times set cardBATBS plus six. Otherwise, no BATBtable isbuilt.

3.16 The SCF feature requires ILHBs to storethe last CLDN. Refer to Part 6 A(8) for

LHB call store options on each generic.

3.17 The SLEB table (set card LASLEB) inUDCS is a contiguous block of memo~

allocated for the total number of SLEBS.WhenSLE changes screen list information for a line,it seizes an SLEB. The SLE links the SLEB to aTRC register and loads new screen list data inthe SLEB. Upon termination of the editingsession, a request is queued to the RC systemto process the change. After processing, the ,TRC register is removed and the SLEB isrestored to the idle link list. Administration(seize and release) of the SLEBSuses abusy/idle head cell with one bit allocated perSLEB.

3.18 Table RSLEKMDB (SLE service orderkeyword message data block), located

in UDCS, is required for SLE customer-originated messages.

3.19 The size of the Originating Registers(&OR), Cathode Ray Tube Originating

Register (&CRTOR) and SXS ForeignExchange SR Registers (&SOR) is defined inthe Parameter Guide PG-IA.

320 The SLR is a senior call register inrestricted duplicated call store (RDCS)

used for storing screen list editor information.The length of the SLR is 28 words. The numberof SLRSis equal to set card NSLR.

321 The SLE requires the use of TRCregisters (set card TRCR) to process

changes to the screening lists, A TRC registeris required for linking the SLEBSfor theduration of an editing session. The number ofadditional TRC registers required is equal tothe number of SLEBS(set card LASLEB).

322 Two types of AMA records are writtenfor SCF. These are event records and

continuation records. An event record is

Page 12 August 1996


generated whenever a customer accesses oredits the SCF screening list. A continuationrecord is written on a daily basis for eachcustomer that has an SCF list active. In manycases, existing AMA registers will suflice.

Additional System Resources for SingleActivation SCF

323 System resources related to callfowarding must be engineered to

handle the SCF usage. Such system resourcesinclude CORC blocks, TRC registers, andtemporary transfer ~PT) registers.

3Q4 Two-word CORC blocks (set cardCORC02) are used to specify the RDN

when no 10XXX/101XXX)(access code isdialed. The additional 2-word blocks requiredare only for those SCF lines that will not haveCiW active at any time.

325 Three-word CORC blocks (set cardCORC03) are used to specify the RDN

when a 10XXX/10IXXXX access code is dialed.The additional 3-word blocks are only requiredfor those SCF lines that will not have CFVactive at any time.

326 Additional TRC registers are required forSingle Activation SCF lines that will not

have CFV activated at any time.

327 Additional TPT call forwarding registersare required for Single Activation SCF

lines that do not use CFV but will use SCF.

D. ‘Ikanslations

3.28 The following translations are requiredor are affected by the SCF feature. Refer

to Part 6 A(3) for further details concerningSCF translations. Refer to Part 6 B(5) and B(6)for comprehensive translation information.

329 The ASC trunk translations include thefollowing:

(a)

(b)

(c)

(d)

August

One 9-word trunk network number toperipheral equipment number (TNN-PEN) miscellaneous trunk frame circuitauxiliary block per ATI circuit.

One 3-word TNN-PEN supplementaryauxiliary block per ATI circuit.

A 4-word trunk class code (TCC)expansion block for the ATI circuit.

One word per ATI circuit trunk groupfor the trunk group number (TGN)

1996

translator.

330 The following translations are affectedby the ATI circuits:

(a)

(b)

(c)

(d)

Pseudo route index (PRI)

Route index (Rl)

Master scanner number to trunknetwork number (MSN-TNN)

Trunk network number to trunk groupnumber (TNN-TGN).

331 A 2-bit field is defined in the centrexcommon block. This 2-bit field in word

23, bits 9 and 10, allows the centrex customerfour possible options for using specialcharacters (that is, # and *) when entering anRDN. Refer to Table A.

332 Each LEN supplementary auxiliary blockrequires an option word L that contains

two bits indicating the ind”widualline accessmode: usage sensitiie, subscription, or deniedaccess. This word is required only if the ●

customer chooses to subscribe to or be deniedaccess to one or more of the IASS features.

333 Each LEN supplementary auxiliary blockrequires an option word F that contains

the address of the screen list head table(SLHT) when a line has a screening list.

334 The SLHT is required for each customerwith one or more screen lists. Each

SLHT requires one word for each screen listthat is built plus one word. The SLHT containsthe addresses of the screen list auxiliary blocks(SLABS).

335 A SIAB is required for each SCF screenlist in the office. The SIAB may be built

in higher unduplicated call store (HUCS) orlower unduplicated call store (LUCS).

336 A 3-word or 4-word CLSI auxiliary blockis required for every class of sewice that

is denied one or more of the usage-sensitiveIJ4SSfeatures.

337 With the lAE1 Oand later genericprograms, the office options table

translator defines the timing interval in theoriginating switch to wait for the response tothe query message in word O,bms7 through 9.The range of value in this bit field is 1 to 6. Ifset to all O’s,the timing interval is 3-seconds. [fset to all 1‘s, the timing interval is 6-seconds.

Page 13

.LT 231-390-236, Issue 8

3.38 Interoffice RDLSTCAP signalingrequires word 1, bit 17 in the office

options table be set to 1. If TCAP is loaded,and bit 17 is set to O,the office will not sendinteroffice RDLS TCAP signaling messages.

339 Word 10, bit 8, of the office optionstable translator defines the inter-lATA

SLE blocking option. The blocking optionallows a 1A ESS Switch to prevent sending theTCAP query message for status information ofinter-lATA numbers. The default is “O”whichblocks the TCAP query message.

3.40 Word 10, bit 10, of the office optionstable translator defines the shared/spiit

NXX office option. This office option allows a1A ESS Switch to send a TCAP query messagefor status information of a number having ashared/split NXX.The default is “O”whichprevents the TCAP query message.

3.41 Word 18 in the office options tabletranslator contains the office AMA mode

indicators for the SCF feature. The indicator isused to specify when AMA records should bewritten. The options per feature are:

(a) Never write AMA records.

(b) Always write AMA records.

(c) Wriie AMA records for usage-sensitiiecustomers only.

3.42 Word 19 of the office options tablecontains the off ice default option word

L This value represents the office defaulthandling for the type of access this feature isgiven (that is, usage sensitiie, subscription,denied access, or unused). The default optionword L is consulted by RC when building acustomer’s LEN supplementary auxiliary blockoption word L for the first time. When a LASSfeature is added to a line for the first time, thedefault option word L is used by RC to buildout the remaining fields of the customer’soption word L If the default option word L isset to deny all IASS features, RC builds allunspecified feature fields the same as thedefault option word L which, in this case, isdenied access. if the USS Office OptionFeature (LOOF) is loaded, word 19 of theoffice options table is used as the defaultoption word L by call processing if the LENsupplementary auxiliary block option word Ldoes not exist.

3.43 The SCF access codes are assigned inthe PACT and the centrex translator

_.

(centrex common block and centrex digitinterpreter tables). Adding the assignments inthe PACTand centrex translators is done bythe standard RC procedure for thosetranslators.

Real Time

3.44 For the real-time penalty due to LASS,refer to COEES Information System

Document, Indexes 38 (lASS), 60 (lAE1 OCCS7), and 47 (1AE9 base), For the impact ofthe Intelligent Simplex Peripheral Interface(ISPI) feature, refer to COEES InformationSystem Document, Index 43.

3.45 During call processing, resources areconsumed when comparing a calling

party identity attribute to the screening list.This has minimal impact on resources used bystandard CFV treatment. In many cases, whencalls are not fomvarded, there is a savings ofresources.

●

4. Implementation

. .

4.01 The SCF feature is installed with orwithout other LASS features. For

detailed L4SS installation procedures, refer toPart 6A(3).

Assignment Restriction

4.02 Customers with the following types oflines are denied access to the SCF

feature:

(a)

(b)

(c)

(d)

(e)

Two-party/multipan-y.

Manual (POTS and centrex). Theselines may be allowed access via recentchange message RC:SLE.

Private branch exchange (PBX).

Remote Switching System (RSS).

Centrex attendant with console.

Customers with the following types of linesshould be denied access to the SCF feature:

(a) Coin lines.

(b) Coinless public lines.

Page 14 August 1996


(c) Denied terminating treatment lines.

(d) Hotel/Motel lines.

4.03 One SCF screening list is allowed permultiline hunt group (MLHG) and is built

and controlled by terminal 1 [the listed DN(LDN)] of the MLHG. Calls terminating to theLDN or to any hunting DN within the MLHG arescreened against the screening list for terminal1. Calls to any non-hunt DN within the MLHGare not screened. In addition, a non-hunt DNwithin the MLHG cannot have its ownscreening list. If terminal 1 of the MLHG is anESS Switch line and the MLHG contains bothESS Switch and RSS lines, these types of lines(ESS switch and RSS) are provided SCFtreatment. An RSS line cannot have screeninglists. If terminal 1 is an RSS line, SCF treatmentis denied to the group.

4.04 In a MLG with no hunting members,every member of the MLG can have a

screening list. In this case, calls to a member ofthe MLG will only be screened against themember’s own screening list.

4.05 Additionally, there are restrictions on thetypes of lines that can be specified on

an SCF screening list. A line is invalid if:

(a) The line is unassigned.

(b) The line cannot originate a call to theowner of the SCF list.

(c) The line is not associated with aunique identity attribute.

4.06 The Single Activation SCF RDN mustconform to the formats in paragraph

2.31. Additionally, the RDN is invalid if it is:

(a) A free number

(b) Unassigned

(c) An intercept number

(d) The base station DN

(e) A 950-l XXX number.

If the call type of the RDN indicates interoff ice,the TROK item in the RI expansion table ischecked to determine if call forwarding isallowed over the outgoing trunk.

Set Cards

4.o7 The following set cards are required byor affect the SCF feature. Refer to Part 6

A(3) and A(8) for additional SCF and LASS setcard information. Refer to Part 6 B(3) and B(4)for comprehensive set card information.

A. LASS Feature Groups

4.08 The following feature group set cards

9

●

●

apply to LASS.

9SLASA defines the intraoffice only featuregroup for LASS. Feature groups 9SDRNGand 9SSLE and feature packages 9FACRBand 9FLASS are required for 9SIASA.

9SLASS def ines the intra/interoff icefeature group for LASS. In 1AE9, 9SLASSrequires feature groups 9SCILC (or FF024),9SDRNG, and 9SSLE and feature packages9FACRB and 9FLASS. In 1AEI Oand later,9SLASS requires feature groups 9STCAPand 9SISUP for CCS7 signaling in place of ●

9SCILC (or FF024).

9SSLE defines the feature group for SLE.Feature groups 9SISPI and 9SVM11andfeature package 9FSLE are required for9SSLE.

4.09 If all the LASS features are loaded,9SIASS (interoffice) or 9SLASA

(intraoffice) is set to 1. If only some of thefeatures are to be provided, LASS Unbundlingis required. The SCF feature is loaded bysetting 9SCF to 1 and setting 9SIASS and9SlASA to O.Feature group 9SCF requires9SSLE and feature package 9FIASS.

4.10 Set card 9SCNBN provides the SLEfeatures, including SCF, with the ability

to block inter-LATATCAP query messages.9SCNBN contains feature package 9FCNBNand requires that 9STCAP and 9SSLE beloaded for the inter-LATA SLE blocking option.It is recommended that 9SCNBN be loaded inmultiswitch SLE configurations. Refer toparagraph 2.27.

B. General LASS Set Cards

4.11 The following feature package set cardsapply to IASS:

● 9FlASS defines the feature package forM3s.

August 1996 Page 15

LT 231-390-236, Issue 8

●

●

●

9FISPI defines the feature package forISPI,

9FSLE defines the feature package forSLE.

9FCNBN defines the feature package forCPNBND.

4.12 The LH primitive requires the presenceof certain set cards. Refer to Part 6 A(8)

for specific information.

4.13 Set card FF050 defines the SLE Privacy(SLEPR) optional feature (lAEIO and

later). If FF050 is set to 1, an identity attribute(DN) on a customer’s screening list from anILHB is marked as private only if the privacy bitfor the entry is set in the ILHB. If the privacy bitis not set, the entry is public. If FF050 is set toO,all entries from the ILHB are marked asprivate, Set card 9SSLE must be set to 1 forSLEPR.

4.14 Set card FF069 defines the LOOFoptional feature available in 1AE1Oand

later generic programs. If FF069 is set to 1,then all lines without an individual option wordL in the supplemental auxiliary block will usethe off ice default option word L The officeoptions table word 19 def ines the callprocessing/recent change default option wordL. LOOF eliminates the need to restrictnonsubscribers access to IASS features byusing the ACRG/CAT codes in thePACT/CTXDIT translators thus simplifyingrecent change procedures required toimplement the IASS features. If set cardFF069 is set to O,IASS feature access defaultsto usage sensitive access if no option word Lexists in the LEN supplementary auxiliaryblock.

4.15 The SLE primitiie requires the followingset cards:

● IASCFE specifies the maximum number ofentries a customer can have on an SCF

●

9

screen list, The default value is 3.

IASLEB specifies the number of SLEBS.The value of this set card is equal to NSLR+ NRCSBQ.

NSLR defines the number of SLRS.Thevalue of NSLR in 1AE9 is equal to thenumber of ATI circuits dedicated for IASSplus 1. For 1AE1Oand later genericprograms, the value of NSLR is calculated

●

●

based on office traff ic. Refer to Part 6 B(l).

NRCSBQ defines the number of RC batchqueue entries required for SLE customeroriginated RC messages. The value of thisset card is equal to NSLR.

NRCBQ is an existina set card whichdefines the number ;f RC batch queueentries.

4.16 The following set cards must be

●

9

●

modified for_SingIeActivation SCF:

CORC02 and CORC03 define the numberof 2- and 3-word CORC blocks.

NTR def ines the number of TPT callforwarding registers.

TRCR defines the number of TRC registers.

4.17 The following set cards are required bySCF for RDLS CCS7 TCAP signaling

messages. (Refer to COEES InformationSystem Document, Index 60 for all the setcards required by CCS7 and to Part 6 A(7) for a .general description of CCS7.)

●

9SMIP defines the feature group for theCCS7 Message Interface Processor (MIP).

9STCAP defines the feature group forTransaction CapabiMy Application Part(TCAP). The CCS7 feature requires TCAPprotocol for interoffice LASS; 9SMIP isrequired for 9STCAP.

SNLASS defines the Signaling ConnectionControl Part (SCCP) SSN (subsystemnumber) used for LASS features whenCCS7 signaling is used.

STIASS defines the global title translationtype value to be used by the LASS featureswhen using global title routing to sendmessages.

BATBS defines the number of bufferadministration timing blocks (BATBs) (usedwith 9STCAP). The minimum value is Oandthe maximum value is 150.

9SBNI defines the feature group for the NIfeature. The NI feature allows the use of aninter-LATA CCS7 network.

Page 16 August 1996


Library Subsystem 5. Administration

4.18 Library package APT47 (List 47) mayberequired to update from 1AE9to lAE1 O.

Library package APT51 (List 51) mayberequired to update from 1AE1Oto lAE11. SeeJ6AO02AC-1for further information.

Translation Forms

4.19 The following translation forms, detailedin Part 6 B(5), are applicable to the SCF

feature:

●

●

●

●

●

●

●

ESS 1101- Directo~ Number Record

ESS 1107A/B-Supplementary InformationRecord/Centrex Group SupplementaryInformation Record

ESS 1109- Centrex Group Record

ESS 1115- Multiline Group Record

ESS 1303-Trunk and Service Circuit RouteIndex Record

ESS 1304-Rate and Route Chart

ESS 1500E- Recent Change Limits Record.

Recent Change Messages

420 Refer to Part 6 A(3) for comprehensiveinformation concerning installation of all

LASS features (including SCF).

Veritlcation

421 The TRCID item in the messageprovided by the Customer Originated

Recent Change Log (CLOG) feature indicateswhether the CORC is for SCF or CFV. If themessage includes the keyword “EXlG”, thenthe RDN digits for the ’70” keyword are thestored dialed extension digits for a potentialOHD or Centrex Extension Trigger (seeparagraph 2.64).

Measurements

5.o1 The following type measurement code(TMC) 148 traff ic counts apply

specifically to the SCF feature:

EGO Definition

26 SCF Screen List Access PegCount

27 SCF Calls Forwarded Peg Count.

5.02 The following TMC 149 traff ic countsapply to the SLE primitive:

EGO Definition

o Screen List Edit Buffer Peg Count

1 Screen List Edit Buffer OverflowCount

2 Screen List Edit Buffer Usage ‘Count

3 Screen List Edit Call RegisterUsage Count.

Automatic Message Accounting

5.03 Refer to Part 6 A(8) for further SCF AMAinformation. Refer to Part 6 A(5) and

B(7) for comprehensive AMA information.

5.04 Two types of records can be generatedfor the SCF feature based on the office

AMA options and the individual line billingoptions.

(a)

(b)

An event record can be made eachtime the SCF access code is enteredby a customer to access/edit thescreening list. Charges can be madebased on activities and/or resourcesused during the editing session or as asingle event.

A daily record can be generated foreach customer who has an SCF listwhether currently active or not. Thisallows billina for use of memorv tostore the lis~

August 1996 Page 17

LT 231-390-236, Issue 8

5.05 For POTS and centrex (lAE1 Oand1AE11 generic programs), billing is

based on the use of the SLE functions and theexistence of an SCF screening list. In the 1AE9generic program, centrex customers are billedon a subscription basis. Centrex and POTSAMA records are generated similarly.

5.06 The AMA record for LASS has a uniqueservice feature code for the Single

Activation SCF feature. The feature status codefield in the AMA record is updated accordingly.Refer to Part 6 A(5) and B(7). All forwardedcalls are billed as in the CFV feature.

6. Supplementary Information

References

A. LT Practices

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(lo)

(11)

231-090-074- Call Fomarding VariableFeature

231-318-325 -ACZ CW, DNRNGE,LINE, MLHG, MOVE,SCLIS~ SLE,TWOPN, VENDLine Recent ChangeFormat

231-318-340 -Local Area SignalingSewices (L&33) Recent ChangeImplementation Procedures

231-365-005- Intelligent SimplexPeripheral Interface Description,Implementation, and Maintenance

231-390463 -Automatic MessageAccounting Feature

231-390-292- Call Forwarding UsageSensitive Feature

231-390-500- Common ChannelSignaling System 7 Feature GeneraiDescription

231-390-515-Local Area SignalingServices (LASS) CCS7 Feature

231-3!30-519-Advanced SewicesPlatform/Setvice Switching Point(ASP/SSP) Feature Document

231-390-521 – Network Interconnect

231-390-522 -Advanced Intelligent

(12) 231-390-523- Total Separation ofSelective Call Forwarding Feature

B. Other Documentation

(1)

(2)

(3)

(4)

(5)

(6)

(7)

COEESInformation SystemEngineering Document Index 38

Data Layout Document PK-6AO06

Office Parameter SpecificationPA-8AO01

Parameter Guide PG-1A

Translation Guide TG-1A

Translation Output ConfigurationPA-6.4002.

TR-TSY-000508LSS-GR-AMA Section8.1.

.

.-

Network (AIN) Release 0.1 Protocoland Capabilities Feature Document

Page 18

--

August 1996


7. Abbreviations and Acronyms

A

ACRGAccess Code Restriction Group

AINAdvanced Intelligent Network

AMAAutomatic Message Accounting

ASCAnnouncement Service Circuit

ASPAdvanced Services Platform

ATIASC Trunk Interface

B

BATBBuffer Administration Timing Block

cCAT

Centrex Access Treatment

CcsCommon Channel Signaling

CCS7Common Channel Signaling System 7

CDRCustomer Digit Receiver

CFUPCall Forwarding Usage Sensitiie

CFVCall Forwarding Variable

CICECarrier Identification Code Expansion

CLDNCalling Line Directory Number

CLOGCustomer Originated Recent Change Log

CLSIClass Of Service Information

COEESCentral Office Equipment EngineeringSystem

CORCCustomer Originated Recent Change

CPNCalling Party Number

CPNBNDinter-lATA Calling Party Number/BillingNumber Delivery and Related Services

CRACall Register Address

D

DNDirectory Number

DPDial Pulse

DTMFDual Tone Multifrequency

H

HUCSHigher Unduplicated Call Store

I

ILHBIncoming LHB

ISPIIntelligent Simplex Peripheral Interface

●

August 1996 Page 19

LT 231-390-236, Issue 8

K

KMDBKeyword Message Data Block

L

IAssLocal Area Signaling Services

IATALocal Access and Transport Area

LDNListed DN

LECLocal Exchange Carrier

LENLine Equipment Number

LHLine History

LHBLine History Block

LOOFIASS Office Option Feature

LUCSLower Unduplicated Call Store

M

MIPMessage Interface Processor

MLGMultiline Group

MLHGMultiline Hunt Group

MSN-TNNMaster Scanner Number to Trunk NetworkNumber

N

NINetwork Interconnect

oOHD

Off-Hook Delay

OROriginating Register

P

PACTPrefixed Access Code Translator

PBXPriiate branch exchange

POTSPlain Old Telephone Service

PPUPeriodic Partial Update

PTWPrimary Translation Word

R

RCRecent Change

RCLDNRetrieval of Calling Line DN

RDLSRetrieval of Distant Line Status

RDNRemote Directory Number

RESTRRestriction Field

RIRoute index

RNGRRing Reminder

Page 20 August 1996


RSSRemote Switching System

sS/SNXX

Shared/Split N)(X

ScSpeed Call

SCCPSignaling Connection Control Part

SCFSelective Call Forwarding

SCPService Control Point

SIABScreen List Auxiliary Block

SLEScreen List Editing

SLEBSLE Buffer

SLHTScreen List Head Table

SLRSLE Register

SSNSubsystem Number

SSPService Switching Point

STPSignal Transfer Point

T

TATTermination Attempt Trigger

TCAPTransaction Capability Application Part

TIRMTechnical Information ResourceManagement

TMCType Measurement Code

TNN-TGNTrunk Network Number to Trunk GroupNumber

TPTTemporary Transfer

TRCTemporary Recent Change

TSCFTotal Separation of SCF

uUDCS

Unrestricted Duplicated call Store●

August 1996 Page 21

LT 231-390-236, Issue 8

~INCOMING CALL

PROCESSING ~

/ SCF ACTIVE

/ AND CALLING 1) NO

\ PARTY IDENTITY

\\ EXISTS,/’/

j YES

,/ATTRIBUTE

-J

‘\NO STANDARD ~

ON SCREENING TERMINATION i

\ LIST ,/ AT BASEI

Iv

I

PROCEED

WITH CALL

FORWARDING

Figure I. Single Activation Selective CallFonvarding Termination ’lkeatment●

~ INCOMING CALL

I PROCESSING II

JYES

\NO

SCF ACTIVE

>

J YES

7PROCEED YES ATTRIBUTE NO r STANDARD

‘H. ‘::cREENING/=Figure2. Sekctive Call Forwarding (lAE9 Generic Program) Termination lkeatment

August 1996


I CUSTOMER GOES

I OFF-HOOK AND DIALS THE

] SCF ACTIVATION CODE

“ SCF ALLOWED ‘\ No \

(, $l;;VNOT )7I

DENY ACCESS

I

\

~ YES

,//

(REMOTE

DN \

EXISTS >NO dENTER REMOTE DN ~

\ \

VOICE BACK AND FAIL CONFIRMATIONCONFIRM THE

REMOTE DN

CONFIRMATION

1 1

NOTE: All announcements during remote DN

editing session are interruptible.

Figure 3. Enter Remote Directory NumberforSin@e ActivationSelectiveCaU Forwarding

*

August1996

LT 231-390-236, Issue 8

// CONTROL RECEIVED ‘\

(\

FROM CLIENT ;)\

vIINTERRUPTIBLE ANNOUNCEMENTS ~

1FEATURE IDENTITY

-.--.-jNUMBER OF ENTRIES

I DIALING INSTRUCTIONSIi

1 JREADY ‘

TONE f

I II

$,‘! , I

~~q m *’~DELETE

“3

TIME-OUT

OR

END BY

e

DIALING

#OR*

DIGIT

PROCESSING

DIAL “1” ~

TO READ

THE ENTIRE ,LIST FIFO I!

6J

‘Es INTERRUPT?

I NO I

1 II

I

r~CONFIRMATION 1VALID YES

i)

>

y

ANNOUNCEMENT: ‘

ENTRY? “THE NUMBER

DELETEDI

NO ADDED 1S..”

ERROR

MESSAGE

LEGEND :

FIFO - FIRST IN, FIRST-OUT

●

Figure4.Screen List Editing Activation Sequence

August 1996

LT PracticesLT 231-390-236, Issue 8

/’ CONTROL RECEIVED ‘,

( FROM CLIENT)

\I

/

1

I INTERRUPTIBLE ANNOUNCEMENTS ~I

I

I FEATURE IDENTITYI L III

NUMBER OF ENTRIES II

~1 , I!! DIALING INSTRUCTIONS

I I

IJ

4,r 41 READY )

II

L---J

TONE

I IIf

I ,

+ ~ DIALO,TODELETE

I77

DELETE ALLALL LIST I ‘PRIVATE LISTENTRIES ENTRIES

I

I I

bCONFIRMATIONANNOUNCEMENT

J------

v1

HANG UP TO ;SAVE THE ~

LIST UNCHANGED I

BUT DEACTIVATED I

I

/cJ----nACTIVATION

SCF

JYES

DELETE THE

REMOTE DN

J-%

( END-— 1

Figure5. Screen List Editing Deactivation Sequence

b

August1996 Page 25

LT 231-390-236, Issue 8

Table A. Special Dialing Characters for Remote Directory Number Editing

Bits 9and 10

00

01

10

11

SpecialChars(Notes)

* And #

* Only

# Only

* And #

Definition

Not treated as specialcharacters during the remoteDN entering sequence(Default). In this case, time-out occurs even when an * or# is entered.

Treated as special charactersduring the remote DNentering sequence. In thiscase, delayed time-out doesnot occur after the ● isentered.

Treated as special charactersduring the remote DNentering sequence. In thiscase, delayed time-out doesnot occur after the # isentered<

Both treated as specialcharacters during the remoteDN entering sequence. In thiscase, delayed time-out doesnot occur atter the * or # isentered.

Notes:

1. These options do not affect how the # and * are currently used in SCF screen list editing.

2. If the * and # are used as LASS remote DN editing characters, they cannot be pati of theremote DN entering process (for example, *9 for outside dialing).

Page 26 August 1996

FEEDBACK

Document Title:

Document Number:

Issue Number: 8

FORM

1A ESSWSwitchSelective Call ForwardingLocal Area Signaling ServicesFeature Document

231-390-236

Issue Date: August 1996

Lucent Technologies welcomes your feedback on this document. When commenting on specificitems within this document, please include the section/chapter, paragraph, and page numbers inquestion. If you choose to complete the “Submitted by” information at the bottom of this form, aLucent Technologies representative will respond to your comments.

Comments:

●

Submitted by (optional):

Name:

Company/Organizations:

Address:

Telephone Number:

Date:

Return to:

Document Preparation Groupc/o M. W. AuterLucent Technologies Inc.Network Software Center2600 Warrenville RoadLisle, IL 60532or FAX 708-224-7180

m essw switch selective call forwarding local...

Documents