Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide
Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide 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+.
DEFINITY ECS Release 8.2
Administrator’s Guide 555-233-506 Issue 1
April 2000
Features and technical reference
1337 Facility and Non-Facility Associated Signaling
20
The following 2 communications-interface forms must be completed for the
ISDN-PRI interface on G3si configurations if the D-channel is switched through
the TN765 Processor Interface (PI) circuit pack:
nInterface Links screen — Used to create an association between the
D-channel on a DSI circuit pack and the port on a TN765 Processor
Interface circuit pack used for this link.
nProcessor Channels screen — Used to assign processor channels to the link
administered on the Interface Links screen.
Finally, trunk ports are added to the ISDN-PRI trunk group and to Signaling
Groups.
.
ISDN-PRI Trunk Group screen — Trunk Members with Required Signaling
Group
The Sig Grp column on the above trunk group screen is completed as follows:
nIf a DS1 interface appears in one and only one Signaling Group, then Sig
Grp may be left blank because the system automatically populates the field
with the correct Signaling Group.
nIf a DS1 circuit pack appears in more than one Signaling Group, then the
Signaling Group numbers must be entered in the appropriate fields before
submitting the screen.
Related topics
Refer to ‘‘
ISDN service’’ on page 1394 for an overview of ISDN capabilities.
Page Y of X
TRUNK GROUP
Administered Members (min/max): xxx/yyy
Total Administered Members: xxx
GROUP MEMBER ASSIGNMENTS
Port Code Sfx Name Night Sig Grp
1: 1B1501___ ___________ _________ _
2: 1B1523___ ___________ _________ _
3: 1B1601___ ___________ _________ _
4: 1B1623___ ___________ _________ _
5: 1B1701___ ___________ _________ 1
6: 1B1709___ ___________ _________ 1
7: 1B1716___ ___________ _________ 2
8: 1B1724___ ___________ _________ 2
9: 1B1801___ ___________ _________ _
10: 1B1823___ ___________ _________ _
11: 1B1901___ ___________ _________ _
12: 1B1923___ ___________ _________ _
13: _________ ___________ _________ _
14: _________ ___________ _________ _
15: _________ ___________ _________ _
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1338 Facility restriction levels and traveling class marks 20 Facility restriction levels and traveling class marks Facility Restriction Levels (FRL) and Travelling Class Marks (TCM) allow certain calls to specific users, and deny the same calls to other users. For example, you can give certain users access to central office (CO) trunks to other corporate locations, and you can restrict other users to less expensive, private-network lines. Detailed Description FRL The switch compares the FRL of the outgoing phone to the FRL of either the terminating trunk group or, for AAR and ARS, the routing preference specified on the Routing Pattern Table. If the FRL of the originator is equal to or greater than the terminating or route pattern FRL, the call continues. Otherwise, the call is blocked. TCM If an intertandem tie-trunk group is used for a call, then a TCM is outpulsed as the last digit. If the intertandem tie-trunk FRL is equal to or greater than the terminating FRL, the call continues. If the originating FRL is less than the terminating FRL, the TCM is compared with the tie-trunk’s FRL. If the TCM is greater than or equal to the FRL, the call continues. Call-originating facilities Any of the following can originate an AAR or ARS call. Each is assigned an FRL via an associated Class of Restriction (COR). nattendant ndata terminal capable of keyboard dialing nincoming tie-trunk group from a subtending location nincoming intertandem tie-trunk group (at a tandem switch) nincoming access tie-trunk group (links a remote main switch to a tandem switch) nphone nremote access user Phones and all incoming tie-trunk groups use the FRL of their COR. On attendant-extended calls, the attendant-group FRL is used. If Individual Attendant
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1339 Facility restriction levels and traveling class marks 20 Access assigned, the individual attendant’s COR FRL is used. Data terminals use the FRL of the COR assigned to the associated data module. A remote access call uses the FRL of the COR assigned to the dialed barrier code. If a barrier code is not required on remote access calls, there is no FRL Call terminating facilities Any of the following trunk types can serve as the termination point for an AAR or ARS call: nTie trunk — excluding Release Link Trunks (RLT), but including Common Control Switching Arrangement (CCSA) and Enhanced Private Switched Communications Services (EPSCS) access trunks nWide Area Telecommunications Service (WATS) nCentral Office (CO) nForeign exchange (FX) nIntegrated Services Digital Network - Primary Rate Interface (ISDN-PRI) Each of these outgoing trunk groups has an assigned COR that contains an FRL. However, this FRL is never used in an AAR or ARS call. A terminating-side FRL for AAR/ARS calls is assigned in the route pattern, not to the outgoing trunk group. FRL guidelines You assign the FRL to the trunk group within the route pattern. You can use the same trunk group in more than one route pattern, and the same trunk group can have a different FRL in a different pattern. You can assign the same FRL to more than one trunk group. Be consistent in FRL assignments. For ease of assignments, always use FRL 0 or 1 for a trunk group that everyone can access. If you use a range of 0–5 in one pattern, use the same range in another pattern if all users can access the first-choice route. Assign a COR with an FRL of 0 to a group of users to restrict them from making outgoing calls. Use any other number for the FRL on your first choice route pattern. This denies access to any trunk group for the users, because all trunk-group FRLs are greater than 0. You assign FRLs for remote access users through the remote-access barrier codes. You can assign up to 10 barrier codes, each with its own COR and FRL. The simplest way to assign these FRLs is to duplicate the on-premises FRLs, then relate the appropriate barrier code to users who need remote access.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1340 Generalized route selection 20 Example The following is an example of how FRLs can be assigned in a COR: nFRL0 — 911 access only nFRL1 — Local calls only nFRL2 — FRL1 plus home area-code calls using WATS nFRL3 — FRL2 plus use of local lines for all calls in the home area code nFRL4 — FRL3 plus calls to all the USA, using WATS only nFRL5 — FRL4 plus calls to all the USA, using local lines nFRL6 — FRL5 plus international calls nFRL7 — Reserved Interactions nCall Detail Recording If 15-digit CDR account codes are used, the FRL field in the CDR record is overwritten with the account code. Related topics Refer to ‘‘ Class of Restriction’’ on page 1304 for more information the types of restrictions you can assign. Refer to ‘‘ Route Pattern’’ on page 865 to find more information on fields on the route pattern screen. Generalized route selection Generalized Route Selection (GRS) is built into Automatic Alternate Routing (AAR) and Automatic Route Selection (ARS). This switch uses GRS to look at various route patterns and preferences and decide which preference is most appropriate at the time. With GRS, voice and data calls can be sent along separate routes or be integrated on the same trunk group. If the type of transmission is incompatible with the endpoint (for example, a digital data call is sent to an analog phone), GRS provides a conversion resource such as a modem from a modem pool to complete the call.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1341 Generalized route selection 20 Detailed description GRS recognizes one or more Bearer Capability Class (BCC) for each trunk group preference in the route pattern. BCC defines the type of information being sent as voice or data. The switch checks the BCC for all trunk groups to see if the route selected and type of call are compatible. The BCC is assigned to the route preference on the Route Pattern screen. GRS chooses a preference with BCC set to yes in this order: BCC 2, BCC 1, BCC 3, BCC 4. When an exact match is not found in any route-pattern preference, calls with originating BCCs listed are treated as follows: nBCC of 0 (such as voice or analog modem) GRS routes a BCC 0-originated call with no match. This allows voice transfer to data when making a data call. Since BCC 0 (voice) has no Information Transfer Capability (ITC), the switch selects an ITC from the route pattern when a BCC 0 call is routed as a data call. Table 50 shows how the ITC codepoint in the Bearer Capability IE is determined. nBCC 2 If there is no preference with BCC 2 yes, GRS chooses a preference with BCC 0 yes. If BCC 0 yes does not exist, the call is blocked. nBCC 1, 3, or 4 BCC 4 (DCP/DMI Mode 0), BCC 1 (Mode 1), and BCC 3 (Mode 3) calls requires an exact match in order for the call to complete. ITCs must also match. Table 50. Determination of ITC Codepoint Originating Endpoint’s ITCRouting Preference’s ITC ITC codepoint in BC IE restrictedun- restrictedboth endpointboth un- restricted voice x restricted voice x unrestricted voice x unrestricted voice x unrestricted
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1342 Generalized route selection 20 Example Assume a route pattern is set up with BCC 0 and BCC 2 set to yes in preference 1, and BCC 1, BCC 3, and BCC 4 set to yes in preference 2. A voice or Mode 2 data call accessing this pattern uses preference 1. A Mode 1, Mode 3, or Mode 0 data call uses preference 2, regardless of what trunks are available in the first preference. Data modules and GRS For all endpoints, the switch automatically determines its current operating mode when a data module begins operations. The default is Mode 2. Because call origination from a data module determines the mode used on the call, you should press the Originate/Disconnect button if you change data options. This way, the right mode is assigned to the next call. Table 51 lists the BCC for different types of information and endpoints. Table 51. BCC Assignment Endpoint Voice/Data Mode BCC Phone Voice 0 Data Line Circuit Pack 2 2 Voice Data Set 2 2 Modular Processor Data Module 0,1,2 1,2,4 Modular Processor Data Module-M1 (For ACCUNET Switched 56 kbps Service)11 Modular Trunk /Data Module 2 2 Digital Terminal/ Data Module 2 2 510D Personal Terminal 2 2 Digital Communications Protocol Interface 0,2,3 2,3,4 7400A Data Module 2 2 3270T Data Module 3 3 3270C Data Module 3 3 3270A Data Module 2,3 2,3
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1343 Group paging 20 Related topics Refer to ‘‘ Route Pattern’’ on page 865 for information on how to set up route patterns. Group paging Group paging allows users to make an announcement over a group of digital speakerphones. nYou can create up to 32 paging groups on one DEFINITY ECS. nEach group can have up to 32 extensions in it. nIt’s OK to assign the same extension to different groups. Brief description You, the switch administrator, create paging groups and assign extensions as members to the appropriate groups. Each group is assigned its own identifying extension, and users page the group by dialing this extension. When a user dials the group’s extension, the switch activates the speakers on all the phones in the group. Speakerphone paging is one-way communication: group members hear the person placing the page but cannot respond directly. Restrictions Pages aren’t always heard on every phone in a group. An extension does not transmit a group page if it has an active or ringing call or if it is off-hook. Listeners may drop a page by disconnecting. Refer to ‘‘ Interactions’’ on page 1344 for features that block group pages. Legend BCC TypeDCP/DM I Mode 0 Voice-Grade Data and Voice None 1 56 kbps Data (Mode 1) 1 2 64 kbps Data (Mode 2) 2 3 64 kbps Data (Mode 3) 3 4 64 kbps Data (Mode 0) 0
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1344 Group paging 20 Controlling access to paging groups Each paging group is assigned a class of restriction, so you can provide or deny access to different classes of users by setting calling permissions appropriately. Note that you can administer classes of restriction so remote callers can make speakerphone pages. If you don’t want to allow remote users to page, you may want to set calling permissions (on the Class of Restriction screen) for VDNs and trunk groups so that neither can initiate pages. Interactions nAttendant Intrusion Attendants cannot intrude on group pages. If the attendant tries to intrude on the paging originator, the intrusion attempt succeeds. However, all group page members are able to hear both the paging originator and the attendant. nAuto Exclusion and Manual Exclusion Bridged appearances are not allowed on the page. Therefore, the Auto Exclusion and Manual Exclusion features are disabled. Auto Exclusion is not activated because there are no bridged appearances to alert when the page terminates. nAuto Hold Auto Hold does not put a group page on hold.The page is dropped and the incoming call is answered. nAutomatic Callback Automatic Callback is disabled when calling an active page group. nBridging Bridging is disabled on this feature. A bridged appearance of a group member does not receive any indication of a call when the page arrives. The bridged appearance cannot bridge onto the page. nCall Coverage Pages do not follow group members’ coverage paths. A page group cannot be a coverage point. nCall Park Group members who receive a page cannot park the call. nCall Pickup/Direct Call Pickup Other extensions cannot pick up a group page.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1345 Group paging 20 nCall Forwarding Group pages cannot be forwarded. nConference Neither group members receiving a page nor the originator of the page can conference the page to other extensions. nDistributed Communications System (DCS) Page groups cannot be administered across DCS switches. DCS is not supported. nDo Not Disturb If a member of a page group activates Do Not Disturb, that member does not receive pages. nGo to Cover The Go to Cover feature is ignored because group pages do not follow coverage. nHold The originator of a group page can put the page on hold, but group members cannot. nLeave Word Calling Leave Word Calling (LWC) is disabled. A page group cannot receive messages. nManual Signaling The Manual Signaling feature cannot be assigned to a page group. nSend All Calls If a member of a page group activates Send All Calls (SAC), that member does not receive pages. nService Observing Group page members and page originators cannot be observed while active on a page. nTransfer Group members cannot transfer a page. nTrunks Trunks cannot be added to a page group. nVe c t o r i n g Paging groups cannot be explicitly added to a vector path.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1346 Hospitality features 20 NOTE: If a vector has a collect digits step and a route-to digits step, a person who uses the vector can enter a page group extension. Ensure that the COR of the vector restricts the vector from calling the page group if this action is not desired. Related topics Refer to ‘‘ Paging over speakerphones’’ on page 381 to administer group paging. Hospitality features This section describes the following DEFINITY ECS features that are tailored to hospitality applications: n‘‘Attendant Room Status’’ on page 1346 n‘‘Automatic Selection of DID Numbers to Guest Rooms’’ on page 1347 n‘‘Automatic Wakeup’’ on page 1348 n‘‘Do Not Disturb’’ on page 1354 n‘‘Names Registration’’ on page 1357 n‘‘Property Management System Interface’’ on page 1359 n‘‘Suite Check-in’’ on page 1367 Each feature indicates how to administer the Attendant Console screen and Hospitality screen to enable the hospitality features. Attendant Room Status Attendant Room Status allows the attendant to see whether a room is occupied and each room’s housekeeping status. NOTE: This feature is available only if you have Enhanced Hospitality enabled on the System-Parameters Customer-Options screen and you have the DXS lamp field on the console. (Contact your Lucent Technologies account representative for information.) Check In/Check Out Status You can allow the attendant to review the check-in/check-out status by assigning an occ-rooms (occupied rooms) button on the Attendant Console screen.