Home > Lucent Technologies > Communications System > Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual

Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions 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+.

    Page
    of 1718
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1307 Call-by-Call Service Selection 
    20
    Using Country Protocol 1, you integrate services and features such as 
    MEGACOM, ACCUNET, and INWATS onto a single ISDN-PRI trunk group 
    with flexible assignment of trunks to each service or feature. Calls such as an 
    incoming 800 Service call that requires through-switching as an Outgoing WATS 
    call can be routed via the same facility. See the ISDN trunk group screen on page 
    ‘‘
    ISDN trunk group’’ on page 750 for a listing of available services. 
    NOTE:
    When the DEFINITY ECS is connected to 5ESS, all of the services 
    supported under the Lucent Technologies and NI-2 country options are 
    available.
    Screens used to administer Call-by-Call Service 
    Selection
    You administer Call-by-Call Service Selection on a per trunk group basis. The 
    following list shows the required screens and the fields you must use on each 
    screen:
    nSystem Parameters Customer-Options
    — Version
    — ISDN-PRI
    — ISDN-BRI Trunks
    — Usage Allocation Enhancements
    nISDN trunk group
    —Service Type
    — Usage Alloc
    — all fields on the Incoming Call Handling Treatment (ICHT) Table
    nRoute Pattern
    —IXC
    — Service/Feature
    —Band 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1308 Call-by-Call Service Selection 
    20
    You can administer trunk Usage Allocation for multiple called numbers within a 
    given Service/Feature, or you can administer trunk Usage Allocation for incoming 
    or outgoing calls independent of Service/Feature.
    nSystem Parameters Customer-Options
    — Version
    — ISDN-PRI Trunks
    — ISDN-BRI Trunks
    — Usage Allocation Enhancements
    n Network-Facilities (Refer to the DEFINTY services documentation for 
    information about the Network Facilities screen.)
    —All
    ISDN messages and information elements for 
    usage allocation 
    Understanding the technical details of ISDN messages and information elements 
    may help you implement ISDN.
    Call-by-Call Service Selection allows the system to specify one of the preceding 
    service types on a call-by-call basis. You can specify service types by classifying 
    incoming calls to an ISDN Call-By-Call trunk group using the called-party’s 
    number. 
    You can also specify service types with a SETUP message that indicates the intent 
    of the originating system to initiate a call using the specified service or facility. 
    The SETUP message may contain units called information elements (IE) that 
    specify call-related information. The IE used with Call-by-Call Service Selection 
    are:
    nNetwork-Specific Facility (NSF)
     — Indicates which facilities or services 
    are to be used to complete the call (typically not used outside the US and 
    Canada).
    The system also checks all incoming ISDN trunk calls for the presence of 
    an NSF IE. If an NSF IE is present, the system makes sure that the 
    requested service is compatible with the trunk administration before it 
    accepts a call.
    For an outgoing call on a Call-By-Call trunk group, the NSF IE is 
    constructed using the Service/Feature specified on the routing-pattern 
    preference selected for the call. 
    If the Service/Feature specified does not have an associated NSF, an NSF 
    IE is not sent. For example, SETUP messages for incoming and outgoing 
    calls classified only by a called-party number do not contain an NSF IE. 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1309 Call-by-Call Service Selection 
    20
    nTransit Network Selection
     — Indicates which interexchange carrier is to be 
    used on an inter-LATA call.
    If a call requires both the Service/Feature and the interexchange carrier to 
    be specified, the interexchange carrier information is sent in the NSF IE 
    rather than the Transit Network Selection IE.
    Usage allocation plans
    Optional Usage Allocation Plans (UAP) may be assigned to provide more control 
    over a Call-by-Call Service Selection trunk group. You can allocate a minimum 
    and maximum number of channels for incoming and outgoing called numbers, 
    privileged users, and voice and data calls.
    A UAP allows the customer to set the following options:
    nMaximum number of trunks that each service can use at any given 
    time.The sum for all services may exceed the total number of trunk-group 
    members. For example, for a15-member trunk group, you could administer 
    a maximum of seven MEGACOM service calls, six MEGACOM 800 
    service calls, and eight SDN calls. This ensures that all trunk-group 
    members are not dominated by a specific service, yet allows for 
    fluctuations in demand.
    nMinimum number of trunks that always must be available for each service. 
    The sum for all services may not exceed the total number of trunk-group 
    members. For example, for a 10-member trunk group that provides access 
    to MEGACOM service, MEGACOM 800 service, and SDN, the minimum 
    number of trunks to be used for each of these services cannot add up to 
    more than 10.
    When these UAP limits are exceeded, the system rejects the call, even if a trunk is 
    available. On outgoing calls, the calling party receives a reorder tone unless other 
    preferences are available.
    You can assign either fixed or scheduled UAP for each Call-by-Call Service 
    Selection trunk group.
    nWith a fixed UAP, one plan applies at all times.
    nWith a scheduled UAP, different plans can be administered to apply at 
    different times of day and different days of the week. As many as 6 
    activation times and associated plans can be assigned for each day of the 
    week.
    You can have anything from a simple fixed UAP to a very flexible UAP with 
    many scheduling options. You can even start out with no UAP and build one as 
    the need arises. 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1310 Call-by-Call Service Selection 
    20
    Incoming call-handling treatment
    Call-by-Call Service Selection provides special incoming call-handling treatment 
    for ISDN trunk groups. An incoming call on an ISDN trunk is handled according 
    to a treatment table administered for the trunk group. Depending on the platform 
    you use, the table allows for a different number of combinations of call 
    treatments. 
    The treatment for an incoming call is selected based on the first 3 columns in the 
    ICHT table on the ISDN Trunk Group screen. When the attributes of an incoming 
    call match these specifications, the call is treated according to the corresponding 
    following 4 columns. If an incoming call matches more than one set of 
    specifications, the most restrictive case applies. The following table lists the 
    possible cases from most restrictive to least restrictive.
    Call detail recording
    On successful call attempts using ISDN Call-By-Call trunk groups, CDR records 
    the NSF specified by the call’s NSF IE. CDR refers to this information as the 
    ISDN Network Service (INS). The value passed to CDR is the 3-digit equivalent 
    of NSF IE. NSF information for Facility Type 2 calls (used with ISDN-Pri 
    Call-by-Call trunk groups) also is recorded if the NSF is available in the incoming 
    SETUP message.
    If an outgoing Call-by-Call Service Selection call uses an interexchange carrier 
    other than the presubscribed common carrier, CDR records the 3-digit or 4-digit 
    Interexchange Carrier Code (IXC). CDR may not record the IXC properly if the 
    dialed-code format differs from the US IXC formats.
    Service / 
    Feature Called Len Called Number
    Most 
    restrictiveSpecified Specified x leading digits specified
    Specified Specified y leading digits specified, where y < 
    x 
    Specified Specified not specified
    Specified Not specified not specified
    “other” Specified x leading digits specified
    “other” Specified y leading digits specified, where y < 
    x
    “other” Specified Not specified
    Least 
    restrictive“other” Not specified Not specified 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1311 Calling Party/Billing Number 
    20
    When a Call-by-Call Service Selection call is rejected because of a UAP, CDR 
    records the cause as an ineffective call attempt. The NSF recording takes place 
    also for the user-defined Facility Type 2. However, the NSF recording takes place 
    only if the NSF is available in the incoming SETUP message.
    Interactions
    nMultiquest Flexible Billing
    Do not use a Service/Facility with the Facility Type field set to 2 or 3. NSF 
    processing is not performed for Facility Type 2. An NSF is not included in 
    the outgoing SETUP message for Facility Type 3.
    nTime-of-Day Routing
    Any Time-of-Day Routing administration that affects routing preference 
    also affects Call-by-Call Service Selection. Use Time-of-Day Routing to 
    vary the IXC based on the time of day and day of the week.
    Calling Party/Billing Number
    Calling Party Number/Billing Number (CPN/BN) allows the system to transmit 
    CPN/BN information to an ISDN-PRI trunk group. The CPN is the calling party’s 
    telephone number. BN is the calling party’s billing number. The CPN/BN may 
    contain international country codes. CPN/BN is used with an adjunct application.
    Brief Description
    The following list shows the screens used to administer CPN/BN and the fields 
    you must use on each screen:
    nISDN trunk group
    — All fields including Per Call CPN/BN
    nISDN Numbering — Public/ Unknown or ISDN Numbering — Private
    —All
    nProcessor Channel Assignment (Refer to the DEFINTY services 
    documentation for information about this screen.)
    —All
    On the ISDN Trunk Group screen, assign all fields needed to provide an 
    ISDN-PRI link between the system and the adjunct. Set the Per Call CPN/BN 
    field to 
    can-only, can-pref, bn-only, or bn-pref as required to make sure that 
    CPN/BN information is sent with a call-offered event report to the adjunct.
    On the Processor Channel screen, assign all fields for one data link. The system 
    can support only one interface. 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1312 Calling Party Number Restriction 
    20
    Related topics
    Refer to ‘‘
    ISDN service’’ on page 1404 for an overview of ISDN capabilities.
    Refer to the DEFINITY ECS Guide to ACD Call Centers for information on using 
    Calling Party Number and Billing Number with Automatic Call Distribution 
    (ACD) and Inbound Call Management. Complete all screens required to 
    administer ACD.
    Refer to the DEFINTY services documentation for information about the 
    Multifrequency-Signaling-Related System parameters screen.
    Calling Party Number Restriction
    With Calling Party Number (CPN) Restriction, you can administer individual 
    phones to restrict sending CPN information on outgoing calls (per call restriction). 
    Also, phone users can use a phone button or a feature access code (FAC) to restrict 
    CPN information on individual outgoing calls (per line restriction). CPN 
    Restriction works on any trunk that supports MFC signaling.
    Per Line CPN Restriction overrides any outgoing trunk group CPN 
    administration. Per Call CPN Restriction overrides any Per Line CPN Restriction 
    for the phone, and it also overrides any Trunk Group administration for sending 
    the calling number. For a tandemed ISDN call, only the Tandem Trunk Group’s 
    “sending calling number” administration applies.
    Interactions
    CPN Restriction is not supported on:
    nlocal switch station-to-station calls
    ncalls originated from attendant console or data module
    nDCS calls (DCS CPN information is not affected by CPN Restriction)
    nUniform Dial Plan (UDP) calls
    nTrunk Access Code (TAC) calls where the Per Line CPN Restriction field 
    on the * screen is 
    y or r, or when the Per Call CPN Restriction FAC is 
    dialed before the TAC
    nnon-ISDN calls that must be tandemed
    nPer Call CPN Restriction over Adjunct Switch Application Interface 
    (ASAI) and CTI interfaces 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1313 Class of Restriction 
    20
    Class of Restriction
    You use Class of Restriction (COR) to define the types of calls your users can 
    place and receive. Your system may have only a single COR, a COR with no 
    restrictions, or as many CORs as necessary to effect the desired restrictions. 
    You will see the COR field in many different places throughout the DEFINITY 
    System - when administering phones, trunks, agent logins, and data modules, to 
    name a few. You must enter a COR on these screens, although you control the 
    level of restriction the COR provides. You must administer a COR for the 
    following objects:
    nAgent LoginID
    nAccess Endpoint
    nAnnouncements/Audio Sources
    nAttendant Console
    nAuthorization Code — COR Mapping
    nConsole-Parameters
    nHunt Groups
    nLoudspeaker Paging
    nData Modules
    nRemote Access (each barrier code has a COR)
    nStation
    nTerminating Extension Group
    nTrunk Groups
    nVector Directory Number
    Called-party and calling-party restrictions
    Called-party and calling-party restrictions are the basis for all CORs. When no 
    restrictions are needed, assign a single COR with called-party and calling-party 
    restrictions set to none. You can use this COR for unrestricted telephones, trunk 
    groups, terminating extension groups, Uniform Call Distribution (UCD) groups, 
    Direct Department Calling (DDC) groups, data modules, attendant groups, and 
    individual attendant extensions.
    The called-party restriction is checked only at the called terminal, module, 
    attendant console, zone, or group, even if a call redirects from one telephone to 
    another. For example, if a called terminal (with no terminal restrictions) has Call 
    Forwarding active to a restricted terminal, the call still completes. 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1314 Class of Restriction 
    20
    Inward restrictions
    You can use inward restrictions to permit users to receive only internal calls. 
    Inward restrictions prohibit users at assigned telephones from receiving 
    public-network, attendant-originated, and attendant-extended calls.
    The COR of the originally-called extension is the only one checked unless you 
    administer 3-way COR check on conference and transfer calls. Denied calls are 
    routed to intercept tone, a recorded announcement, or the attendant for Direct 
    Inward Dialing (DID) calls.
    Manual terminating line restrictions
    You can use manual terminating line restrictions to allow users to receive calls 
    only from an attendant or that were extended by an attendant. Calls can redirect to 
    a manual terminating line-restricted telephone. The COR of the originally-called 
    extension is the only one checked.
    Local CO, foreign exchange (FX), and Wide Area Telecommunications Service 
    (WATS) calls are routed to the attendant. DID calls are routed to an announcement 
    or the attendant. Telephone calls are routed to intercept treatment.
    Origination restrictions
    You can use origination restrictions to prohibit users from originating calls. These 
    users can still receive calls.
    Outward restrictions
    You can use outward restrictions to prevent users from placing calls to the public 
    network. These users can still place calls to other telephone users, to the attendant, 
    and over tie trunks. If necessary, an attendant or an unrestricted telephone user can 
    extend a call to an outside number for an outward-restricted telephone user.
    When outward restriction is applied to the Calling Party Restriction field on the 
    Class of Restriction form, calls coming into a trunk with that COR will be denied 
    if they make use of the AAR/ARS feature.
    Public restrictions
    Public restrictions prohibit users from receiving public-network calls. Denied 
    calls are routed to an intercept tone, a recorded announcement, or the attendant. 
    Public restrictions still allow users to receive internal calls from other telephones 
    or calls that were extended from the attendant. 
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1315 Class of Restriction 
    20
    Termination restrictions
    You can use termination restrictions to prohibit users from receiving any calls. 
    These users can still originate calls. DID or Advanced Private-Line Termination 
    calls route to a recorded announcement or the attendant.
    Fully restricted service 
    Fully restricted service prevents specific users from making or receiving 
    public-network calls. Fully-restricted users cannot use authorization codes to 
    deactivate this feature.
    Calls from the public network to a fully-restricted extension redirect to intercept 
    treatment or to the attendant. If the call redirects to the attendant, the attendant’s 
    display indicates the call was redirected because of fully restricted service 
    (FULL).
    There are circumstances where an extension with fully restricted service can 
    access or be accessed by the public network. 
    Miscellaneous terminal restrictions
    You can use miscellaneous terminal restrictions to prohibit users from accessing 
    other specific terminals. Restricted calls are routed to intercept tone. 
    Miscellaneous restriction groups apply on a per-COR basis. However, you can 
    assign the same COR to more than one facility. Facilities with the same COR may 
    be like facilities (such as two telephones) or different facilities (such as a 
    telephone and a trunk group)
    Miscellaneous trunk restrictions
    You can use miscellaneous trunk restrictions to prohibit users from accessing 
    specific trunk groups, such as WATS or CO trunk groups. Any or all trunk groups 
    can be in a miscellaneous-trunk-restriction group. Restricted calls are routed to 
    intercept tone.
    Toll and TAC-Toll restrictions
    Toll restrictions prevent users from placing public-network calls to certain 
    toll-call numbers. Toll restriction is not a COR; you assign Toll restrictions to 
    outgoing trunk groups on the Trunk Group form. You disable TAC-toll restrictions 
    for specific outgoing trunk groups on the Trunk Group form.  
    						
    							DEFINITY ECS Release 8.2
    Administrator’s Guide  555-233-506  Issue 1.1
    June 2000
    Features and technical reference 
    1316 Class of Restriction 
    20
    Interactions
    nAAR/ARS
    Originating FRLs are assigned via a COR. Termination and Miscellaneous 
    Restrictions do not apply to ARS/AAR calls.
    nAAR/ARS Partitioning
    Partition Group Numbers are assigned via a COR.
    nBridged Call Appearance
    The COR assigned to a telephone’s primary extension also applies to calls 
    originated from a bridged call appearance of that extension on another 
    terminal.
    nCall Coverage
    Users who normally are restricted from calls can still receive calls directed 
    to them via Call Coverage. When a call goes to coverage, the called party’s 
    (not the covering party’s) restrictions are used.
    nCall Forwarding All Calls
    If a call is restricted between the forwarding and forwarded-to extensions, 
    Call Forwarding is denied. Restrictions are always checked when Call 
    Forwarding is activated, but not when a call is forwarded.
    nCall Vectoring
    When a call is directed to a VDN extension, the COR of the caller and the 
    VDN are compared to determine if the caller can access the associated call 
    vector.
    nClass of Service
    In some cases, the COR can be overridden by the COS. See the Trk-to-Trk 
    Restriction Override field documented with the ‘‘
    Class of Service’’ on 
    page 545.
    nControlled Restriction
    Restrictions assigned via Controlled Restriction override COR restriction.
    nEmergency Access to Attendant
    Emergency Access to Attendant calls are not restricted by COR. 
    						
    All Lucent Technologies manuals Comments (0)

    Related Manuals for Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual