Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies Whats New In DEFINITY Enterprise Communications Server Release 8.2 Manual
Lucent Technologies Whats New In DEFINITY Enterprise Communications Server Release 8.2 Manual
Have a look at the manual Lucent Technologies Whats New In DEFINITY Enterprise Communications Server Release 8.2 Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 155 Networking - ISDN Public 2 Networking - ISDN Public BellCore Calling Name ID Bellcore Format with V.23 FSK nThe 24-Por t Analog Line with CID feature supports the option to send Bellcore specification messages using V.23 modem protocol. nBellcore Format with V.23 FSK differs from the standard Bellcore format only in the frequencies used for the FSK signaling in the Physical Layer. nEncompasses some Middle East countries such as Bahrain. It is necessary to set the US NI Calling Name for outgoing Calls? field to y/n on page 6 of the change system-parameters features form, as shown below. Screen 1. Feature-Related System Parameters screen change system-parameters features Page 6 of 10 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS Send Non-ISDN Trunk Goup Name as Connected Name? _ Display Connected Name/Number for ISDN DCS Calls? _ Send ISDN Trunk Group Name on Tandem Calls? n CPN Replacement for Restricted Calls: _____ CPN Replacement for Unavailable Calls: _____ QSIG TSC Extension: ___ Path Replacement with Measurements? n MWI - Number of Digits Per AUDIX Subscriber: _ Feature Plus Ext: ___ National CPN Prefix: _____ International CPN Prefix: _____ Pass Prefixed CPN to ASAI? n Unknown Numbers Considered Internal for AUDIX ? n Maximum Length: 5 US NI Calling Name for Outgoing Calls? n
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 156 Networking - ISDN Public 2 US NI Calling Name for Outgoing Calls? Bellcore National ISDN Calling Name Supplementary Service for PRI nProvides the user with the capability on incoming calls, to receive Network provided Calling Name information, along with name presentation indication. nProvides the user with the capability on outgoing calls, based on trunk group administration, for DEFINITY to provide the calling name and its presentation status to the network. nEnables DEFINITY to provide users the same Calling Name capability provided by Central Office to residential customers. NOTE: DEFINITY only supports the Bellcore National ISDN Calling Name feature for PRI, and does not support the Bellcore National Calling Name feature for BRI. There is no support for original called name information when a call has been forwarded or redirected. Bellcore Calling Name is a public network feature and its feature operation is very much dependent on how the National ISDN trunk interfaces are provisioned at the CO switch (whether to accept CPE originated Calling name, how to deliver Calling Name with or without Privacy Override). Valid entries Usage y/n Enter y to send a name on outgoing calls over NI PRI trunks. Important: Be sure you have validated that your service provider’s central office is capable of accepting calling name information from DEFINITY in this way. For example, if the central office switch is a 5ESS, it must be a generic 5EXX or later. Failure to validate the central office capability may cause the central office to drop outgoing calls from your switch. In this case, change the value in this field to n. Enter n to prevent sending calling name information with outgoing calls over NI PRI trunks. n is this field overrides a y in the Send Name field of the outgoing trunk group screen.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 157 Networking - ISDN Public 2 Capacity Constraints and Feature Limitations nDEFINITY will be capable of receiving up to 50 characters of Bellcore National ISDN Calling Name information but display a maximum of 15 characters. — Truncation behaviors will truncate names longer than 15 characters to the first 15 characters to be displayed. NOTE: DEFINITY does not support optional capabilities to interpret/display the original called name information when a call has been forwarded or redirected. nIf the Bellcore Calling Name information is received during Call Setup time, this feature presents the same end user interface when displaying calling name information. nBased on user administration for this feature, if Calling Name is received later in a FACILITY message, there may be a display update to include Calling Name in the “calling” part of an incoming call display. — This display update may erase any Call Center collected/prompted/ CINFO/II digits being displayed on agent CallMaster sets but agents can redisplay the digits via a feature button. Feature Administration nAvailable if “ISDN-PRI” is administered on the system-parameters customer option form. nFollowing theDEFINITY administration scheme, the Bellcore Calling Name feature for PRI is selected for ISDN PRI or ATM trunk groups as follows: — The DS-1 interface for PRI or the signaling group for ATM Trunk is administered with country protocol “1b” for Bellcore. — The ISDN Trunk Group SS option (Supplementary Service option) is administered “A” for National Supplementary Service protocol . — The ISDN Trunk Group “Send Name:” field is administered to either “y” or “n” in order to originate Calling Name information for outgoing calls. Calling Name Display Update nBefore DEFINITY release 8.1 calling number and/or calling name display to the called station was provided when the SETUP message was received, except in the case of Call-by-Call subscription of ANI delivery by the AT&T PRI network.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 158 Networking - ISDN Public 2 nThe 5ESS network database query timer is set to one to six seconds (three seconds is the default). — The aim of DEFINITY support of the Bellcore Calling Name is to present as similar a user interface as the LEC Caller-ID service. Caller-ID usually delivers the Caller ID information on the 2nd ring cycle with each ring-silence cycle defined as 6 seconds. nGiven the Caller-ID information delivery timing, the LEC network switch should be delivering the Calling name information to DEFINITY within 2 rings as the call is being alerted and therefore there is no need to delay any call alerting on DEFINITY. — Customers can select whether to get a display update with name information if name was not initially displayed when the call was first alerting at the Called station. Bellcore National ISDN Calling Name Update nA new administration parameter added to the ISDN Trunk Group form if the “SS option” field is set to “A: nThe new field “US NI Delayed Calling Name Update? ” is a “y/n” field and defaults to “n”(o). — If it is set to “n” and Calling Name information is received after the incoming call has been delivered to the Called station, there will be no display update to the terminating station with the Calling name information. — If the field is set to “y” and Calling Name information is received after the incoming call has been delivered to the terminating station, there will a display update with the Calling Name information in the “calling” portion of the display. — This field can only be set to “y” for ISDN PRI or ATM trunk group types with corresponding trunk interface that selected “1b” as the Country Protocol (on DS-1 form for PRI trunk or on signaling group form for ATM trunk). — If this field is set to “y” for other ISDN trunk group types, at form submission time the SAT cursor will placed on this field and the following error message displays “BRI trunks do not support this value”. Option A Change nWith the support of Bellcore Calling Name under SS Protocol “A” (National SS), the “r” choice is allowed. nDEFINITY Call Processing code enforce a check if “Send Name: r” is administered for an SS Option A trunk group not associated with a Country Protocol “1b” PRI interface results in no Calling name being sent (as if the “Send Name:” field is set to “n”).
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 159 Networking - ISDN Public 2 SS Option A Choices nThe “Send Name:” field on page 2 of ISDN Trunk Group form allows the “r”(estricted) choice when the “Supplementary Service Protocol” is set to “A” (National SS protocol). Standard error and help messages apply. NOTE: For the Bellcore National ISDN Calling Name feature for PRI, DEFINITY supports the callingName, NAME, NamePresentationAllowed, NamePresentationRestricted, NameNotAvailable, NameData, NameSet, and CharacterSet. Interworking nDEFINITY supports Calling Name for the following types of ISDN networks: — QSIG private network (multi-vendor networks) — DCS/DCS+ private network (DEFINITY only networks) — AT&T Custom PRI private network (DEFINITY only networks) — AT&T Custom PRI public network (4ESS networks) nCalling Name information interworking is supported between any two of these networks —QSIG — DCS/DCS+ — AT&T Custom PRI private or public network. Trunk Group Page 2 screen with the new field choice and new field. change trunk-group 1 Page 2 of 10 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support: n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: r Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Numbering Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Send UCID? n Send Codeset 6/7 LAI IE? y US NI Delayed Calling Name Update? n
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 160 Networking - ISDN Public 2 nWith the addition of Bellcore National ISDN Calling Name feature, interworking of Calling Name in the Bellcore National ISDN network will also be fully supported if the Bellcore Calling Name information is available in the SETUP message. — There is no interworking of the Bellcore Calling Name with other PRI networks if the Bellcore Calling Name is not in the SETUP message. Feature Plus – Non-DID Calling via UDP ISDN Feature Plus Phase 2 nProvides users without Direct Inward Dialing (DID) the capability of direct dialing (via the public network) users on a remote PBX. nAvailable according to the following parameters: — ISDN Feature Plus is a set of features using non-standard ISDN signaling to give users feature transparency over public networks. — A non-blank subaddress entry on the route pattern form causes routing digits to be sent to the terminating end. nWhen these digits are received, the call will route based on the received routing digits. nMust only be used for route preferences destined for public LDNs. — For networks supporting less than the standard 23 octet Subaddress IE, either calling name or Pseudo DID information can be transported, but not both. nRecommended to turn off calling name since it will be truncated to only 6 characters. — For users without DID, remote extensions can only be reached over public networks by dialing the Listed Directory Number (LDN) of the remote location and having the remote attendant redirect the call to the appropriate extension. nUsing the Feature Plus platform to provide Pseudo DID, a remote users extension is transported across a public network in a Subaddress IE. nThe remote user is accessed by their assigned extension and any other routing digits required, such as an AAR access code. nUtilizing existing DEFINITY® system digit manipulation, the remote users extension is converted to the correct public LDN.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 161 Networking - ISDN Public 2 nWhen a LDN call is received, the incoming SETUP message is checked for a Calling Party Subaddress IE containing a DID extension. nIf the extension is present, the call will not be sent to the attendant, as is currently the case. The call will, instead, be routed to the indicated extension. nFeature Plus Pseudo DID will only work over trunk groups assigned Supplementary Service Protocol Option f. nRequires the originating and terminating nodes in a network to be DEFINITY® ECS release 8 or later. nTandem nodes in the network may be other vendors so long as they support transmitting the Calling Party Subaddress IE in SETUP. nA pre-release 8 DEFINITY® ECS can also be included in the network as a tandem node. nApplicable offer category is B. Administration nThe number of digits to send in the Calling Party Subaddress IE must be administered. nIn order to allow the most flexibility for routing alternatives, the administration was added to the route pattern form. nNew field only administered if the software is version 8 or above and ISDN Feature Plus is enabled. nSending Feature Plus information is only valid on trunk groups administered with Supplementary Service Protocol. nA new numeric field No. Dgts Subaddress added to the Route Pattern form. — Default is blank. — Field can not be administered unless the switch is administered as version 8 or later. — Field can not be administered unless ISDN Feature Plus is enabled. — Field can not be administered unless the trunk group is ISDN. — Field is only valid for ISDN trunk groups.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 162 Networking - ISDN Public 2 Example nLeased line from DEFINITY® system A to DEFINITY® system B. nThe first routing preference can be assigned to the leased line so User B1 can be dialed directly without sending Pseudo DID subaddress information. nIf preference 1 is not available, preference 2 can be assigned to the LDN on DEFINITY® system B, and the dialed Pseudo DID extension can be sent as the subaddress. nThe 4000 block of extensions was not purchased from the public network and extension 4010 in the public network. nWith Feature Plus, User A can reach User B1 directly by dialing 94010. Digit manipulation must be administered (AAR digit analysis and route pattern) to delete the dialed extension (4010) and insert the LDN (303 XXX XXXX). nThe LDN is sent in the Called Party IE as the destination address and the DID extension is sent in the Calling Par ty Subaddress IE. nUsing the DID extension received in the Subaddress IE at DEFINITY® system B, the call terminates to User B1 rather than to the attendant. If User A wants to reach the attendant, the full ARS number must be dialed (for example, 8 303 XXX XXXX).Route Pattern Form Page 1 of 3 change route-pattern 1 Pattern Number: 1 0 Grp. FRL NPA Pfx Hop Toll No. Del Inserted IXC No. Mrk Lmt List Digits Digits 1: ___ _ ___ _ __ __ __ ____________________________________ user 2: ___ _ ___ _ __ __ __ ____________________________________ user 3: ___ _ ___ _ __ __ __ ____________________________________ user 4: ___ _ ___ _ __ __ __ ____________________________________ user 5: ___ _ ___ _ __ __ __ ____________________________________ user 6: ___ _ ___ _ __ __ __ ____________________________________ user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR 0 1 2 3 4 W Request Dgts Format Subaddress 1: y y y y y n y none___both ept outwats-bnd____ __ _ _____ none 2: y y y y y n n rest _______________ _ ________ next 3: y y y y y n n rest _______________ _ ________ rehu 4: y y y y y n n rest _______________ _ ________ none 5: y y y y y n n rest _______________ _ ________ none 6: y y y y y n n rest _______________ _ ________ none
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 163 Networking - ISDN Public 2 Alerting Ring Pattern nIf the incoming trunk group, which terminates to the LDN, is administered as tie, the ring pattern administered on the trunk for incoming calls apply. — If Internal Alert? is yes, the system ring pattern administered for internal calls apply. — If Internal Alert? is no, the system ring pattern for external calls apply. — If the trunk group is not tie, the system ring pattern administered for external calls applies. nWhen calls are received for LDNs and the switch is in night service, the calls are redirected to the administered night service extension. — The night service extension are ignored for Pseudo-DID calls and routed to the received extension regardless of night service status. Shared Calling Party Subaddress IE Contents nWhen a Pseudo DID extension is assigned in conjunction with calling name (trunk group Send Name? y), both the calling users name and the DID extension are transported in the Calling Par ty Subaddress IE. nBy default, for networks supporting less than the standard 23 octet IE, calling name information is discarded. Terminating DID Subaddress nWhen a call is received over an SSF interface for an LDN extension, the Calling Party Subaddress IE is checked for a DID extension. nIf present, the call is routed to the DID extension rather than the attendant. nOnce the call has been routed to the DID extension, all procedures for a direct incoming call apply. nSince a DID extension received as a subaddress can be the result of AAR, ARS or UDP dialing on the originating side, ringing applies based on the administered ring pattern for external calls unless the trunk group is administered with Internal Alert? yes (applies only to tie trunks). Multiple Pubnet Calling/Connect Numbers/ System (Italy) This feature provides multiple public-network calling/connected numbers per system. It provides the user with the capability to send out different “main” numbers for trunks associated with different network providers. nIn Tenant Partitioning where each tenant is using specific trunks, this can ensure that proper calling/connected numbers are sent out based on the trunks used.
What’s New in DEFINITY ECS Release 8.2 Job Aid 555-233-754 Issue 1 April 2000 Networking Enhancements 164 Networking - ISDN Public 2 nPublic networks may check the accuracy of the Calling Line Identification number information sent by a CPE. nThe number is checked to make sure it is within a provisioned range. nIf the number is not accurate based on the trunk group used, the DEFINITY®-provided Calling Number would be deleted and a network- provided “main billing” number would be used instead. nThis creates a situation in which the callers extension information is lost, adversely impacting the caller identification in both emergency and normal situations. nIn outbound call management applications for third party companies, multiple trunks and numbers would be used and accurate Calling Number information is provided by DEFINITY ® system on call originations. It also passes network Advice of Charge (AOC) information to all protocol WCBRI endpoints provides the user with the capability to tandem transparently network provided AOC information to all WCBRI endpoints. The AOC information can be used by WCBRI stations for local station display purposes. Network AOC information to be passed include: ETSI, CEPT Italy, and NTT INS-NET 1500 Japan. Capacity Constraints and Feature Limitations nWhen a switch is administered for the multiple public network numbering enhancement, the number of administered entries in the ISDN public- unknown number form could increase by n fold with “n” being the number of distinct main numbers that the switch needs to originate for outgoing calls. — The maximum form entries (8 pages of 30 entries each) was considered sufficient, and therefore not increased. nMaximum number of number digits displayed including any national/ international prefix remains at 15 digits. — Numbers longer than 15 digits will be truncated to the first 15 digits of number information (this is consistent with the current DEFINITY ® system number/name truncation behaviors. nMaximum national or international prefix length is 5 digits. nNetwork provided AOC information is tandemed transparently to WCBRI endpoints. nDisplay of the AOC information at end user stations is dependent on the station capability. nDEFINITY® system does not control WCBRI station display functions. nThere is no mapping or conversion of Network side (PRI) AOC protocol to Line side (WCBRI) AOC protocol.