TER

TERMINAL NUMBER - MULTILINE GROUP

INDICATES:

Terminal numbers in stored program control switches Multiline Hunt (HML), and Non-hunt (MLG) groups in 1AESS, 2ESS, 3ESS and 5ESS only.

DATE:

10/31/2014

BILLING:

CRIS and CABS

APPLICATIONS:

1AESS, 2ESS, 3ESS, 5ESS, Access Service, Access Service Request (ASR), AXE, DMS-100, EWSD, FETEX-150, GTD-5 EAX, Hunting, ISDN BRI, Local Competition, Local Service Request (LSR), STROM-DCO, TL1

SECTION - POSITION

EXAMPLES

S&E - FL

G1   HML 532/TLI 732 555-1234
I1   @@4/TER 1/TN 732 555-1234/LHT 7
I5   @@4/TER 2, 3, 5-7
I1   @@4/TER 4/TN 732 555-2345/HPF
     TER 2, 1, 3/LHT 7

ASGM - FL

Floated TER Entry
IOE  11-100-200/TER 1/TN 732 555-1234

Grouping TER Entry
G1   TER 1/HML 5

FID RULES/CONSTRAINTS:

1. For mechanized processing by Telcordia and/or Ericsson Operations Support Systems (OSSs), the number of TERs in a hunt group cannot exceed 200.  For additional information, see SOAC/NSDB, SOAC/TIRKS, or SOAC/WFA/DO Interface Specifications Document.
2. The Telcordia and/or Ericsson Operations Support Systems (OSSs) do not support a TER value greater than four characters.
3. A terminal number must be assigned to each hunting or non-hunting (e.g., outdial) line in each multiline hunt (HML) group and to each non-hunting line in each multiline non-hunt (MLG) group.
4. The terminal number is used as the Primary Line Identifier (PLID) for each line in a multiline hunt group, but not in a multiline non-hunt group.
5. TER is associated with each USOC for each line in a multiline hunt or non-hunt group.  TER is entered associated with each USOC for items of service and equipment associated with the line whether or not there is a telephone number associated with the line.
6. The quantity entered following an action code preceding an assignment affecting USOC, must equal the quantity of terminal numbers entered on the USOC action line.
7. In multiline hunt groups, one or two telephone numbers may be associated with each line to which a terminal number is assigned.  Also a line may be associated with a terminal number not assigned a telephone number. In multiline non-hunt groups, one telephone number must be associated with each line to which a terminal number is assigned.  The telephone number is used as the Primary Line Identifier for each line in  a multiline non-hunt group.
8. All terminal numbers assigned in each multiline hunt or non-hunt group must be in ascending and consecutive order.
9. 1AESS
   The first terminal number must be 1 and must always have a Telephone Number (TN) (or Line Designation Number (LD), if TN is not preassigned).
10. 2ESS and 3ESS
    The first terminal number must be 0 and must have a telephone number (or LD, if TN is not preassigned).
11. The TER FID is required with all USOCs that reference a line in a multiline group even when TER is not the Primary Line Identifier (PLID). When the TER FID  is not the PLID, Terminal Line Identifier (TLI) must be explicitly entered with each USOC.
12. EWSD
    Terminals may be assigned a TN to provide additional start hunt arrangement if the directory number is different from the TLI directory number.  A TN is not required to be assigned to any TER, including TER 1.  This rule applies to Regular, Circular or Uniform Call Distribution (UCD) hunting.
13. EWSD - Integrated Services Digital Network (ISDN )
    A TN must be assigned to TER 1 and it must be the pilot TN for the hunt group.  TER 1 may also have an optional non-hunt TN identified with the Non-Hunting Number (NHN) FID.  For other than TER 1, a TN may be assigned (but is not required) and can be either a hunt TN or a non-hunt TN identified with the NHN FID.  TN and NHN are mutually exclusive for other than TER 1.  For Electronic Key Telephone System (EKTS) Call Appearance Hunting, all TNs are hunt TNs and the NHN is prohibited.
14. Section:  ASGM      Position:  FL
    This FID is entered in the Miscellaneous Subset, Central Office Facilities Subset and Outside Plant Facilities Subset.
15. TN and/or LD entries in a range and/or series are ordered according to the sequence of terminal numbers specified (i.e., the first TER entry is associated with the first LD or TN entry, the second TER with the second LD or TN entry).
    TER 1 is associated with LD 1
    TER 2 is associated with LD 2
    TER 3 is associated with LD 3
    TER 4 is associated with LD 4
    TER 5 is associated with LD 5
16. T, F, and X order types prohibited for Access Service application.
17. X action code prohibited on Access Service orders.
18. SERIES AND RANGE ENTRIES - PROCESSING
    Service Order Analysis and Control System (SOAC) should process series and range data entries using the DISTRIBUTE algorithm.

REFERENCES:

1. For use of this FID and its data as a Primary Line Identifier see Common Language Service Information Universal Service Order (USO) Requirements, (BR 751-000-151), Section 7.
2. 5ESS
   Lucent technologies, 235-118-257, Views 1.6 and 23.2, Keywords CKTTERM and TERM
3. EWSD
   Siemens 0625-00070, Multiline Hunt Service; Siemens 0770-00010, LNO
4. EWSD - Release 17.0
   Siemens Telecom Networks Requirement Specification, TL1 for MLHGs, P30310-A2445-A016-02-7626, CUG, DC, DNCT, and OEDN Views, Keywords MLHG and MLTERM
5. TL1
   TR-NWT-000199, Subscriber Lines, OE, DNCT, MLHG and MLTERM Views, Keyword MLTERM
6. AXE
   Ericsson Translations Guide, Keyword HNB
7. GTD-5 EAX
   AG Communication Systems, DNCT View, Keyword MLTERM
8. ATIS/OBF-ASR-009, TER field
9. ATIS/OBF-LSR-072, 073, 076, 077, 080, 081, 083, 099 AND 122, TERS field

SECTION - POSITION

APPEARANCE

MODE

MIN

MAX

Required

Numeric

1

5

Element: 1

Terminal Number - Multiline Group

Appearance

Mode

Min

Max

Series

Range

Required

Numeric

1

5

Yes

Yes

Data Parameters:

SECTION - POSITION

APPEARANCE

MODE

MIN

MAX

Required

Numeric

1

5

Element: 1

Terminal Number - Multiline Group

Appearance

Mode

Min

Max

Series

Range

Required

Numeric

1

5

No

No

Data Parameters:

ORDER TYPE/ACTION CODE/FID RELATIONSHIPS

Order Type

N

T

F

D

C

R

X

P

A

Presence

O

O

O

O

O

O

O

P

P

Action Codes

I,E

I,E

O,D

O,D

I,O, C,T, M,X, D,E, R

I,O, C,T, M,X, D,E, R

C,T, R

-

-

CRIS

CABS

Data Retention

Yes

Yes

Printed on CSR

Yes

Yes

Order Type

N

T

F

D

C

R

X

P

A

Presence

O

O

O

O

O

P

O

P

P

Action Codes

I,O

I,O

O

O

I,O

-

I,O

-

-

CRIS

CABS

Data Retention

No

No

Printed on CSR

No

No

Note: Please refer to BR-751-000-150 for a complete description of a FID specification and its structure.

iconectiv Confidential - Restricted Access

This document and the confidential information it contains shall not be distributed, routed or made available to any third party, except with written permission of iconectiv.

Licensed Material - Property of iconectiv

Possession and/or use of this material is subject to the provisions of a written license agreement with iconectiv.