Home > GTE > Communications System > GTE Omni Si Database Technical Practices Manual

GTE Omni Si Database Technical Practices Manual

    Download as PDF Print this page Share this page

    Have a look at the manual GTE Omni Si Database Technical Practices Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 950
    							TL-130400-I 001
    This diagram represents an application of MERS Off-Network using an access
    code defined with the MERS Off-Network code type to initiate the feature.
    Dialed Access Code
    AC (Code Type 48)
    1
    Dialed Service Code or NPA or IDDD Code/Country Code
    (or Undialed Home NPA)
    I,Dialed
    ABC Code
    ISending Instruction
    List Number
    4
    SI
    Li
    Routine List
    Number
    4Dest.
    Type =COT
    LDN
    Prefix
    IndexPrefixMEW
    lndexSCC IDDest.
    Type =DGT
    Dest.
    Type =INTDest.
    Type =
    LOCTIE
    see
    WTS
    Figure 11.1 COff-Network MERS Record Code AssociationSVR 5210
    D-223 
    						
    							TL-130400-1001
    This diagram represents an application of MERS On-Net using an access code defined with
    the MERS On-Net code type to initiate the feature.
    Dialed Access Code
    AC (Code Type 105)
    Dialed On-Network ABC Code
    or Authorization Prefix Digits+
    /TR.
     .4
    OF
    7Authorization
    Code
    4
    vRouting List
    NumberAU
    7(switches to MERS Off-Net
    process 
    - See code type 48)
    I11RP
    t
    I
    t
    I
    +4+++4
    MERSOther
    DigitsPrefix
    LDNSCC IDDest.Dest.Dest.Dest.Dest.
    DeletedIndexPrefix
    1
    Type =Type =Type =
    Type =Types1
    p&&$-&&&&,,-
    JOTES:Translation type must never specify MRN or MRS.
    *The MERS SCC ID and the other destination types (COT, FXT, SCC, WTS) may be
    specified for On-Net MERS but the DDD network will be used to complete On-Net
    MERS calls.
    Figure 11 .l DOn-Net MERS Record Code Association
    8187SVR 5210 
    						
    							TL-130400-1001
    This diagram represents an application of MERS On-Net and/or MERS Off-Net.
    An access code defined with the IDDD variable numbering plan, the flexible numbering plan, or
    the 7-l 0 digit called number can initiate the feature. The 1 st digit of either the flexible
    numbering plan or the 7-10 digit called number can also initiate the feature.
    Dialed Access CodeDialed 1st Diqit ofNetwork Numberinq Plan
    AC (code types 96, 126)
    IDialed 1st 3 Digits of Network Dialing Plan or
    IDDD Code/Country Code
    /Trans. 
    T;pe= MER ++
    On-Net/NPA Code
    Sendinq Inst./Routing
    SpecifiedPattern Specified
    ITrans. Type = DGT
    Dialed 
    Dl/D2 Diqits
    t
    I -l-D I
    I -
    I
    Trans. Type = MRN
    I
    Trans. Type = MRS
    IDialed on-net ABC code
    I
    TR
    IDialed Service Code Or NPA
    IOr Undialed Home NPA)
    I
    STMR
    I
    1 NR
    Dialed ABC Code
    ITR
    IContinued on the Next Page
    Figure ll.lEOn/Off-Net MERS Record Code Association
    SVR 5210
    8187
    D-225 
    						
    							TL-130400-1001
    Sending Inst.
    List NumberRoutinq
    List NumberLDN
    Prefix
    IndexMERSDest.
    Type =DGT
    Dest.
    Type =INTDest.
    Type =
    LOCDest.
    Type =TIEOtherDest.
    types
    NOTES:cTranslation type must never specify MRN or MRS.
    teThe MERS SCC ID and the other destination types (COT, FXT, SCC, WTS) may be
    specified for On-Net MERS but the DDD network will be used to complete On-Net
    MERS calls.
    ltldRecord Code MO is only applicable to On-Net MERS.
    Figure 11.1 EOn/Off-Net MERS Record Code Association (Continued)
    8187SVR 5210 
    						
    							TL-130400-1001Record Code RP:11.2 Record Code RP, Figure 11.2, defines the routing list data,
    MERS Routing Listincluding the trunks to be used by the MERS feature. Any trunks
    not listed on this record code cannot be accessed by calls using
    the MERS feature. In addition to listing all trunks to be used for
    MERS, this record code also lists the trunk order in which calls
    will go out. The routing list(s) is defined here and assigned to the
    variqus NPAs/ABCs on Record Codes TR and NR.
    ;I; I ;T,NI NOTT! TIIIDI g I:I 651 6I
    IEI,341 3I
    IXI xI‘:,081 ‘: I1111I. IIII ’ I
    -.).--$.-T-r-t-t-r-t-r-r-t-r-t-t-t-r-r-r-r-r-r-r-r-r-r-r-r-r-r-r-r-r-r-~1 I1 I1 I1 11 11 11 11 11 II 1212121212121212121213131313131313131313l417!8!9,Oll 12131415161718191011 12,3i41516,718191011 121314151617181910,-+-+-u--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-~C-216lOlRI PtI I Il-Ad-l--L- -L,d,1,,,1I I I I I I I I I I I I I I I III I III,I-*-~-*-*-*-~-~-~-i-*-~-*-~-*-~-~-~-~-~-~-~-~-~------
    I
    I
    I1
    I
    I
    I
    :
    I
    1
    Figure 11.2Record Code RP: Most Economical Route Selection Routing List Data SheetSVR 5210
    8187D-227 
    						
    							TL-130400-1001Table 11.2
    Entry Fields for Record Code RP
    COL.COL.VALID
    NO.
    NAME
    ENTRIESCOMMENTS
    12MERS RoutingO-7 = numberThis field defines the identification number
    List Number
    given to a route.
    __-For most applications, only one routing
    pattern list number is required.
    -If only one routing pattern is used, enter 0
    down the row 12 times in column 12.
    -The 12 entries coincide with the 12 possible
    sending instructions found on Record Code SI,
    columns 12-l 3.
    - All 12 entries must be made whether used
    or not used. If they are not used, they will be
    sent to intercept.
    -When off-network MERS is used, it is
    normally recommended to use a separate
    routing pattern list number.
    -A separate routing pattern list number can
    be used for local calls.
    -This number is referred on the following
    record codes:
    TR, columns 23, 26, 29 and/or 32
    NR, columns 20, 23, 26 and/or 29
    ST, column 19
    NT, column 30
    13-14Select Order1-12 = numberThis field identifies the trunks that can be used
    and the order of these trunks for calls placed
    using this route.
    -Each routing list/select order combination
    must be unique across this record code.
    -The select order must be continuous with no
    gaps for each routing list.
    8187SVR 5210 
    						
    							TL-130400-1001COL.NO.
    Table 11.2Entry Fields for Record Code RP (Continued)
    COL.VALID
    NAME
    ENTRIESCOMMENTS
    15-17
    . . . .Destination
    COT = CO trunksThis field determines how the trunk group is
    TypeFXT = FX trunkstreated (see columns 17-18).
    3-TIE = Tie trunks-LOC (Local Termination) is used in a
    WTS = WATSnetwork environment when the system is only
    trunksto look at the last four digits dialed. Since the
    INT = interceptfirst three digits (leading network digits) are all
    LOC = local_the same, the last four digits dialed determine
    terminationthe network switch to which the call is routed.
    DGT = Dl /D2 digit-If an SCC is used, access to more than one
    SCC = specializedlocal trunk group can be allowed. By allowing
    common carrieraccess to more than one local trunk group,
    the probability of accessing the SCC is
    greater.
    -If COT, FXT, WTS, or SCC is entered in this
    field, then Record Code T2, columns 32, 33
    and 34, cannot be dashed. It is
    recommended to set these fields at the lowest
    possible value.
    18-19Destination00-63 = trunkThis field determines the trunk group number,
    Identifier
    group numberfor the trunk type defined in columns 14-l 6.
    00-l 5 = intercept-If columns 14-16 are marked LOC or DGT,
    routing numberthis field must be dashed.
    -- = N/A or local
    -If columns 14-l 6 are marked INT, this field
    termination ormust be marked 
    00-15.
    Dl /D2 digit-If columns 14-16 are marked COT, FXT,
    translationSCC, TIE, or WTS, this field must be marked
    00-63.-Trunk group numbers must be defined on
    Record Code 
    Tl, columns 12-l 3.
    -The destination identifier can also be an
    intercept routing number. This must be
    defined on Record Code IR, columns 12-13.
    20MERS SCC
    Identification
    NumberO-7 = number
    - = not selectedIf an SCC is included in this route, this field
    determines which SCC is to be used.
    -SCCs are identified on Record Code MS,
    column 12.
    SVR 5210
    8187D-229 
    						
    							TL-130400-1001Table 11.2Entry Fields for Record Code RP (Continued)Expensive
    Route
    s-
    . .
    _VALID
    ENTRIES
    I= tone
    U = not selectedCOMMENTS
    Mark this field Y if a burst tone is to be heard
    when the call goes out over this route.
    -A burst tone is normally used to notify a
    caller that the call is going out over the most
    expensive route.
    -The most expensive route should be the last
    trunk group of the route.
    -With this feature, the caller has the option of
    hanging up and trying later or continuing the
    call over the most expensive route.
    -A tone can be assigned to as many trunk
    groups within a route as wanted.
    8187SVR 5210 
    						
    							TL-130400-1001Record Code SI:11.3 Record Code SI, Figure 11.3, defines the special handling
    MEW Sendingrequirements for a trunk group and the trunk group’s assigned
    Instructiondestination number. Record Code RP defines the routes for
    MERS usage. Record Code 
    SI determines what facilities, within
    a route, can be accessed by a specific 
    NPAIABC. The sending
    instructions are defined on this record code and assigned to the
    various 
    NPAs/ABCs on Record Codes TR and NR.
    3-r------iL-r-------r-----------------------~-----~---------------------------~IIII_ IIIIT
    I
    I
    I
    f!
    T ;
    5:dII ! t
    I
    II-
    I
    III;I ‘; II
    I
    III
    I
    III ,
    1718191011 1213141516171819101112131415161718191011 
    1213141516171819l011 I21IO Ic-+-+-u-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-~C-4l2171Olsl~l I I I l I l l 1 l 1 l I I 1 l  1 I 1 I I I I I I I I  1 I I 1 I I  ILLL--L-L-~-~-~-~-*-~-~-~-~-~-~-*-~-~-*-*-~-~-~-*-~-~-~-~-~-~-~-u-u
    Figure 11.3Record Code SI: Most Economical Route Selection
    Sending Instruction Data Sheet
    SVR 52108187D-231 
    						
    							TL-130400-1001
    Table 11.3Entry Fields for Record Code StCOMMENTS
    00-31 = number
    Ion purposes.
    -This number is referred to on the following
    Record Codes:
    TR, columns 21-22, 24-25, 27-28, and
    NR, columns 18-l 9, 21-22, 24-25, and
    NT, columns 28-29
    ST, columns 17-18
    -The sending instruction/select order
    combination must be unique across all
    NOTE: Sending instruction list number 00 is a
    valid CPG entry; however, 00 should never be
    used on this record code.
    number that is used for this s
    instruction. The routing patte
    for this sending instruction is chosen from the
    list of routing patterns on Record Code RP,
    column 12.
    -This field must be continuous with no gaps
    for each sending instruction list.
    16-17Skip/RouteAL = allowedThis field determines whether or not this
    Usage AllowedSK = skippedsending instruction is allowed access to this
    trunk group.
    -The trunk groups are defined for each route
    on Record Code RP, and must be listed in the
    order in which they appear on that record
    code.
    18Pause AfterT = requiredEnter T if a pause is required after a trunk is
    Trunk Seizure
    -=N/Aseized.
    -See Record Code T2, column 32, for the
    timing value required for this field.
    -This field is normally used for older 
    COs.
    19Pause AfterE = equippedEnter E if a pause is required after an escape
    Escape Digit
    -=N/Adigit (trunk group access code) is sent.
    Sent-See Record Code T2, columns 31 and 33,
    for the timing value required for this field.
    D-2328187SVR 5210 
    						
    All GTE manuals Comments (0)

    Related Manuals for GTE Omni Si Database Technical Practices Manual