Subject: Time: 8:57 AM

OFFICE MEMO DMS-250 answers Date: 2/26/97

Local Number Portability is part of DMS-250's Software Product line:

NetworkBuilder.

First release is in UCS07

VO September 1997

GA October 1997

NetworkBuilder's LNP on the DMS-250 supports the AIN LRN approach

utilizing the new LNP trigger: OfficeCode. The DMS-250's LNP product

is based on the Illinios Commerce Commission (ICC) April 3, 1996

requirements.

The DMS 250 LNP "office code" trigger is a PODP-like trigger at the

Info_Analyzed PIC.

The OfficeCode Trigger table is checked after the existing triggers at

the PIC. Only "offnet" 10-digit national addresses trigger in this

table.

The LNP specific office code trigger uses a subset of AIN 0.1 per the

ICC spec so it can interwork with a variety of platforms. Feature

interworking issues are avoided due to the limited LNP functions of

these queries; value-added services are not supported on the OfficeCode

trigger. Routing numbers returned for an IN/1 N00 or Carrier SCP can

trigger at the LNP trigger. NetworkBuilder's LNP also supports Non-LNP

carrier AIN queries by allowing return LNP data (GAP/FCI) in a single

dip as part of a value-added AIN service.

Agents supported: DALs, FGD (PTS & SS7), PRI, IMT (SS7) and Axxess

(FlexDial).

NetworkBuilder LNP Operational Impacts:

Billing Changes: The DMS-250 utilizes CDRs (Call Detail Records) not

AMA

Field TERMLRN holds LRN used to route the call

Field ORIGLRN holds LRN from originator's JIP parm (if present)

Field LNPCHECK shows LNP work done on call

Table Changes:

New trigger table: OFFCCODE for LNP (incl. QoR)

Table TRKGRP has new option SIGPTDNO for ISUP trunks

Additional CAINPARMs for selecting trigger criteria, QoR cause value

Tables C7GTTYPE/C7GTT have new LNP Global Title Type

Operational Measurement Changes:

New group CAINLNP created to track usage per-trunk group

Existing CAIN OM groups updated as required.

LOGs:

No new logs; existing CAIN logs updated as required

HMI:

CAINTEST includes support for LNP