Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity 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+.
QSIG 381 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 B Private Networking •Data-Call Setup A data call is denied ANF-PR. •Data Privacy If Data Privacy is active, ANF-PR is denied. •Data Restriction If Data Restriction is active, ANF-PR is denied. •Malicious Call Trace If MCT is active, ANF-PR is denied. •Recorded Announcement A call that is receiving a recorded announcement cannot have its path replaced. •Trunk Access Code The paths of outgoing calls made using a TAC are not replaced. •Voice Terminals Voice terminal displays that show trunk group name should update with new trunk group information after ANF-PR occurs. Calling and connected party displays are not disturbed when ANF-PR takes place if the original display shows the connected party name, number, or both. Transit Counter •Call Forwarding (Diversion) When call forwarding (Diversion) occurs and the ANF-TC feature is enabled, the transit counter is set to zero. •ISDN Trunk Group Administration If all of the conditions are satisfied for both the Tandem Hop Limitation and ANF-TC, ANF-TC takes precedence. In situations where DEFINITY ECS is an Incoming or Outgoing Gateway, either makes use of the hop count/transit count information provided by the other. •Trunk Access Code ANF-TC does not apply to TAC calls. Call Completion •Adjunct Switch Applications Interface (ASAI) ASAI cannot invoke/initiate QSIG-CC. •Attendant Calling Waiting and Call Waiting Termination If you activate QSIG SS-CC to a single line voice terminal, the Attendant Call Waiting and Call Waiting Termination features are denied. •Attendant Console Group You cannot activate QSIG SS-CC toward the attendant console group or towards the individual attendant.
QSIG B Private Networking Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 382 •Attendant Control of Trunk Group Access You cannot activate QSIG SS-CC if the call uses a controlled trunk group. •AUDIX You cannot activate QSIG SS-CC towards AUDIX. SS-CC to any transferred-to station is not allowed. •Automatic Call Distribution (ACD) You cannot activate QSIG SS-CC towards a voice terminal after dialing the ACD group extension. It is possible to invoke SS-CC towards a station when dialing the individual’s extension number. You can activate SS-CC from any ACD agent. •Bridged Call Appearance You cannot activate QSIG SS-CC from a bridged call appearance. When a call originates from a primary extension number, the return call notification rings at all bridged call appearances. •Busy Verification After the called party in a QSIG SS-CC call hags up, neither extension number can be busy-verified until both the calling and called parties are connected or the callback attempt is canceled (by the activating party or by time-out of the callback interval). •Call Coverage QSIG SS-CC requests are always activated at the principal user and not coverage points. Similar to ACB, QSIG SS-CC Call Completion calls to the called user can redirect to coverage. •Call Forwarding You cannot activate SS-CCBS or SS-CCNR towards a called station that has Call Forwarding enabled. •Call Pickup On recall at the originating side, a group member cannot answer a QSIG SS-CC call for another group member. •Call Waiting Call Waiting is denied when QSIG SS-CC is activated to the single-line voice terminal. •Conference and Transfer You cannot activate QSIG SS-CC towards a transferred-to party. •Hold A single-line voice terminal cannot receive a QSIG SS-CC call while it has a call on hold. •Hotline Service A hotline service cannot request SS-CC.
QSIG 383 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 B Private Networking •Internal Automatic Answer (IAA) If the IAA feature is enabled, QSIG SS-CC calls are not answered automatically. •Manual Originating Line Service A manual originating service cannot request QSIG SS-CC. •Multimedia Endpoints You cannot activate QSIG-CC towards multimedia data endpoints. •Restriction Features ~Class of restriction (COR): Any terminal that is Origination-restricted cannot activate SS-CC. Any terminal that is Termination-restricted cannot have SS-CC activated towards it. ~Class of Service (COS): To invoke SS-CC, the ACB field on the Class of Service screen of the calling terminal must be set to yes. •Ringback Queuing Ringback Queueing and ACB share the same button to indicate that they are active. If the user has only one ACB button, then both features cannot be active at the same time. •Outgoing Trunk Queuing Outgoing Trunk Queueing cannot be invoked after the calling party answers the priority call back call and no trunks are available. The SS-CCBS and SS-CCNR request cancels at both PBXs. •Termination Extension Group (TEG) You cannot activate QSIG SS-CC towards a TEG extension, but QSIG-CC requests can be activated towards a single member in the group. •Uniform Call Distribution and Direct Department Calling You cannot activate QSIG SS-CC towards a uniform call distribution group or a direct department calling group extension, but you can activate towards a single member in the group. •Vector Directory Number (VDN) You cannot activate SS-CC towards a VDN extension. Message Waiting Indications•AAR/ARS Partitioning All QSIG MWI messages use Partition Group 1 for routing. •Alternate Facilities Restriction Levels QSIG MWI messages have unrestricted COR. •DCP and Mode Code links to AUDIX QSIG MWI does not work with the DEFINITY AUDIX that emulates a DCP phone. A Prologix that communicates with AUDIX by using mode codes cannot be a QSIG message center switch complex.
QSIG B Private Networking Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 384 •Authorization Codes The authorization codes do not block routing because the routing of TSCs used for QSIG MWI uses FRL 7. •Automatic Alternate Routing (AAR) AAR may be used to route the QSIG TSCs. •Automatic Route Selection (ARS) ARS may be used to route the QSIG TSCs. •Call Coverage Features The served user switch uses call coverage paths to route calls to users in the served user switch to the AUDIX hunt group on the Message Center switch. •Class of Restriction QSIG MWI messages use the default COR of unrestricted. •Class of Service QSIG MWI messages use the default COS of unrestricted. •Facility Restriction Levels and Traveling Class Marks A QSIG MWI TSC always uses FRL 7 (unrestricted). •Generalized Route Selection GRS uses the “TSC” column on the Route Pattern form to select a preference for carrying QSIG MWI TSCs. •ISDN - QSIG - BRI QSIG MWI is dependent on QSIG TSCs. QSIG MWI is possible over QSIG BRI lines. •Message Sequence Tracer MST traces QSIG MWI messages. •Off-Premises Station If a DS1 is used to implement an off-premises station, QSIG MWI does not work with the off-premises station. DS1 off-premise stations do not receive system message waiting indicators. •Uniform Dial Plan (UDP) It is possible to route QSIG MWI messages by using UDP.
QSIG 385 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 B Private Networking Called/Busy Name•Adjunct Switch Applications Interface (ASAI) A Connected Number is sent in the Connected Event to ASAI adjuncts. Therefore, upon receipt of a Called/Busy Number, it is stored in such a way that it is not be sent accidentally as a Connected Number if no actual Connected Number is received in the CONNECT message when the call is answered. •ISDN - QSIG Call Diversion (including Reroute) Both the Called Name and Called Number are sent to the ringing/busy extension. Call Transfer As is done for the Called Name, the Called Number of a ringing party is sent to the transferred-to party in the QSIG “Call Transfer Complete” message. •Message Sequence Tracer (MST) MST records facility IEs containing Manufacturer Specific Information (MSI), but is not yet able to decode this information. VALU Call CoverageThe interactions that apply to DCS call coverage apply to VALU call coverage, with the exceptions listed below. See Call Coverage (page 326) •Call Coverage Off Premises Unlike DCS, QSIG-VALU can handle non-UDP numbers in the remote call coverage table. It is not limited to route only on UDP numbers. •Coverage Answer Groups Same as DCS Call Coverage (i.e. Coverage Answer Groups across nodes (on a remote system) are not supported). •Consult Consult from the remote covering user to principal user is not supported. •Displays When a Principal user bridges on the call, its display is updated with “CONFERENCE” and counted for the number of parties on the call. The remote covering user and calling user (local and remote) display is not updated with the word “CONFERENCE”. •Leave Word Calling back to Principal from Covering User Same as DCS Call Coverage — not supported. •Go to Cover Same as DCS Call Coverage — not supported. •Queuing (UDC/DDC/ACD/VDN) Same as DCS Call Coverage. •QSIG Call Forwarding/Diversion Same as DCS Call Coverage — call forwarding has a higher priority than Call Coverage with QSIG-VALU.
QSIG B Private Networking Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 386 •QSIG Centralized Attendant Service (CAS) The calls that cover from a QSIG CAS branch to main are not treated as QSIG-VALU Coverage calls. This is because calls covered to “attd” (administered as a coverage point on a Coverage Path form) do not utilize Remote Call Coverage table and QSIG-VALU Call Coverage is supported only for coverage points associated with Remote Call Coverage table. The implication of this is that the attendant on the main will lose QSIG-VALU Call Coverage display information and QSIG Path Replacement will not be invoked after the call is answered by the covering attendant. • Coverage of Calls Redirected Off-Net (CCRON) If both QSIG-VALU coverage is enabled and CCRON is enable, the QSIG-VALU coverage will have a higher precedence then CCRON. • Privacy - Manual Exclusion With Call Coverage feature, when the principal user bridges onto a call that went to coverage and has been answered at the coverage point, the user is not dropped when Privacy - Manual Exclusion is activated by the Covering user. With QSIG-VALU Coverage, if the Principal bridges on the call after the remote covering user has answered the call. then the remote coverage user stays bridged until the call clears or the covering user goes on-hook. • Simulated Bridge Appearance (SBA) With QSIG-VALU, maintaining SBA for Principal user will be based on the administration of the field “Maintain SBA at Principal” on the System Parameters - Call Coverage / Call Forwarding form. • Temporary Bridge Appearance (TBA) Same interaction as Simulated Bridge Appearance. • AUDIX / Centralized AUDIX AUDIX is usually specified as the last coverage point. When a call is routed to AUDIX (local or remote centralized place), the TBA (Temporary Bridge Appearance) is not maintained for the Principal user (i.e. the Principal user can not bridge on to the call after it routes to AUDIX). For the last coverage point, which do not require control at the Principal user’s PBX, the QSIG-VALU Coverage shall route the call as QSIG Diversion by Rerouting instead of QSIG Diversion by forward-switching and let the remote calling user’s PBX route the call directly to the remote covering number. If the Rerouting PBX indicates failure, then the Principal user’s PBX (i.e. Served User’s PBX in terms of QSIG Diversion) shall revert to the normal QSIG-VALU Coverage handling. The advantage of this approach is that it saves the trunk resources and provide path optimization without QSIG Path Replacement.
QSIG 387 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 B Private Networking •QSIG Call Transfer If a call that is transferred using QSIG Call Transfer transfer-by-join to a secondary user (i.e. Principal user for QSIG VALU Call Coverage) and the call is routed to a covering user by QSIG VALU Call Coverage and if the Principal user has a Simulated Bridge Appearance (SBA) and if a call goes through a QSIG Path Replacement successfully, the Principal user will loose the SBA. •Integrated IP Trunking An incoming call over an IP trunk that goes through more than 2 tandem nodes, and is compressed and decompressed at each entry and exit point on the trunk, may suffer voice-quality degradation. Centralized Attendant Service (CAS)•Abbreviated Dialing The main attendant can use abbreviated dialing buttons to extend QSIG-CAS calls. •Administration without Hardware Administration without hardware for attendant consoles for QSIG-CAS functions as for RLT-CAS. •Attendant Auto-manual Splitting The attendant can split away from a call to privately call another party by pressing the START button. •Attendant Auto Start and Dont Split Attendant Auto Start and Don’t Split functions as for RLT-CAS. The attendant can initiate a call while on an active call by pressing any button, without pressing the START button first. The system automatically splits the call and dials the next call. To deactivate Auto Start, press the Don’t Split button. •Attendant Backup Alerting Attendant Backup Alerting for QSIG-CAS functions as for RLT-CAS. If attendant backup alerting is turned on, other users on the main PBX may have the ability to answer attendant seeking calls. •Attendant Call Waiting Attendant call waiting is available for calls that originate on the main. •Attendant Calling of Inward Restricted Stations Attendant calling of inward restricted stations for QSIG-CAS functions as for RLT-CAS. That is, a user who is inward restricted cannot receive an attendant originated or extended call unless that user has field Restriction Override on the COR form set to “attd.” •Attendant Conference By using the attendant split/swap feature, it is possible for the attendant to conference join the attendant, calling party, and extended party together in conference. If the attendant drops out of the conference, leaving just the calling party and extended party, path replacement is not attempted.
QSIG B Private Networking Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 388 •Attendant Control of Trunk Group Access Attendant control of trunk group access for QSIG-CAS functions as for RLT-CAS. •Attendant Crisis Alert Attendant crisis alert for QSIG-CAS functions as for RLT-CAS. •Attendant Direct Extension Selection With Busy Lamp (standard and enhanced) For QSIG-CAS the DXS allows attendants to use the DXS for monitoring and placing calls to users on the main PBX and for placing calls to users on a branch PBX only when UDP is used. •Attendant Group and Tenant Partitioning Attendant Group and Tenant Partitioning are local features that do not require QSIG signaling on the main. Attendant Group and Tenant Partitioning do not function on a CAS branch. You can administer tenant partitioning and multiple attendant groups on a branch PBX. However, all attendant-seeking calls at the branch PBX are directed to the QSIG-CAS number, as administered on the console-parameters form, regardless of any tenant partition. If the QSIG-CAS number corresponds to the Dial Access to Attendant number at the main or to a VDN that eventually routes to the Dial Access to Attendant number at the main, the call is directed to the attendant group assigned to the tenant partition of the incoming trunk to the main. •Attendant Interposition Calling and Transfer Attendant Interposition calling and transfer is a local feature that remains unchanged by QSIG-CAS. Attendants on the main still have the ability to call and transfer to each other using Individual Attendant Extensions. •Attendant Intrusion As with RLT-CAS, Intrusion is not be available in QSIG-CAS to calls that are incoming from a branch. •Attendant Misoperation Misoperation is used only in France and Italy. It is a local feature and functions as for RLT-CAS. If the system goes into Night Service while an attendant has a call on hold, the call realerts at the attendant console. If it is unanswered after an administrable amount of time, the call begins alerting at the night service destination. •Attendant Override of Diversion As with RLT-CAS, Override of Diversion is not available in QSIG-CAS for calls incoming from a branch. • Attendant Recall As with RLT-CAS, Attendant Recall is not available in QSIG-CAS to calls incoming from the branch.
QSIG 389 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 B Private Networking •Attendant Release Loop Operation Attendant Release Loop Operation is a local switch feature. It allows an unanswered extended call on the main to return to the attendant after an administrable amount of time. The call first tries to return to the same attendant that originally answered the call and, if that attendant is not available, the call goes to the next available attendant (waiting in the Attendant Queue if necessary). •Attendant Return Call Attendant Return Call functions in the following manner: Suppose a call comes into the attendant from a branch PBX. If the attendant extends the call and it is unanswered after an administrable amount of time the call returns to the attendant. Initially, the call attempts to return to the same attendant that originally handled the call. If that attendant is unavailable, then the call goes to the next available attendant (waiting in the Attendant Queue if necessary). •Attendant Serial Calling As with RLT-CAS, Attendant Serial Calling is not available in QSIG-CAS to calls incoming from the branch. •Attendant Tones Call identification tones are not heard by attendants answering calls from a QSIG-CAS branch. •Attendant Trunk Group Busy/Warning Indicators As with RLT-CAS, the attendant can only receive busy/warning indicators for trunks at the main PBX. The attendant cannot receive information about branch PBX trunks. •Attendant Vectoring The attendant vectoring feature is available to QSIG-CAS at the branch and the main. An attendant-seeking call terminating at the main PBX follows any vector steps that are defined at the main. The QSIG-CAS Number should not contain the number of a remote VDN. Note that there is no admin check to block such administration, but QSIG CAS may not function correctly. •Automatic Circuit Assurance As for RLT-CAS, the CAS attendant cannot receive ACA referral calls from a branch because any administered ACA referral extension must be on the local PBX.
QSIG B Private Networking Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 390 •Call coverage The attendant group is allowed to be a coverage point. If the call covers from the branch to the main over a non-QSIG ISDN trunk, then the call is treated as a forwarded call. That is, Call Coverage Off Net (CCRON) procedures do not apply and the call is not brought back to the branch PBX. Note:In order to obtain the full functionality of QSIG CAS, it is recommended that routing patterns are set up so that a QSIG trunk is used when sending a call from the branch to the main. If the call covers from the branch to the main over a QSIG trunk (not QSIG VALU), then QSIG Diversion procedures apply. If the call covers from the branch to the main over a QSIG VALU trunk, then QSIG VALU Call Coverage procedures apply. • Call forwarding Forwarding calls to the QSIG-CAS number is allowed. •Call park If a call is parked and the Call Park Timeout Interval (as set on the Feature Related System Parameters screen) expires, the call is sent to the attendant. This works the same as for RLT-CAS. •Call Detail Recording (CDR) CDR functions with QSIG-CAS as for RLT-CAS. •Call Record Handling Option Calls are sent to the attendant as non-CDR calls if the following conditions all hold: ~the call is subject to CDR, and ~the CDR buffer is full, and ~the attendant is administered as the Call Record Handling Option on the CDR system parameters form. •CDR Reports The format of the CDR data report is an administrable option on the CDR systems parameters form. Customers can select from a list of pre-defined formats or create their own. The content of the CDR records is unchanged by QSIG-CAS. CDR records generated at the main are covered by existing procedures. Calls incoming to the attendant look like incoming trunk calls. Calls originated or extended by the attendant look like outgoing calls. •CAS Back-Up Extension The CAS Back-Up Extension is used in an RLT-CAS environment but has no benefit in QSIG-CAS.