Home > Lucent Technologies > Communications System > Lucent Technologies DEFINITY Enterprise Communications Server Release 8, Issue 2.0 (02.0.034.2) Description Manual

Lucent Technologies DEFINITY Enterprise Communications Server Release 8, Issue 2.0 (02.0.034.2) Description Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8, Issue 2.0 (02.0.034.2) Description 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+.

    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Highlights 
    7  
    In Release 4.0 of the OMD Serenade Voicemail system, the connection between 
    the Serenade and the PBX will be a QSIG ISDN link.  The Serenade will be able 
    to interpret the QSIG MSI message and subsequent QSIG transfer information 
    sent to it by DEFINITY, thus enabling QSIG Transfer to QSIG Voicemail to function 
    between Serenade and DEFINITY, connected via QSIG ISDN.
    In order to enable QSIG Transfer to QSIG Voicemail, the following options must 
    also be enabled:
    nISDN-PRI or ISDN-BRI
    nQSIG Basic Supplementary Services
    nTransfer into Lucent QSIG Voicemail
    VALU: Call Coverage and CAS
    On a trunk which has both CAS and VALU Call Coverage activated, coverage 
    display information is provided on calls that cover from a branch to the main. Also, 
    path replacement occurs after coverage.
    Calls Covering Over QSIG VALU
    QSIG VALU coverage calls time out based on the local coverage “doesn’t answer” 
    interval and all coverage points after a QSIG diversion call can be reached.
    Class of Restrictions (COR) Value of Customer or Attendant Console
    The COR value associated with a traditional user or attendant console can be 
    changed by a DEFINITY customer (who has console permissions) via a feature 
    access code.
    Networking
    Administrable Loss Plan
    DEFINITY customers can now administer the loss or gain applied on calls.  
    DEFINITY ECS endpoints are classified into 17 endpoint types.  The loss plan 
    port type is administrable per trunk and Personal Cental Office Line (PCOL) 
    group, and per station.  The 2-party loss plan and the digital tone plan are 
    administrable per system, by assigning losses to be applied per endpoint types.  
    Administered loss values are in the range from 15 dB of loss to 3 dB of gain.  The 
    2-par ty and Digital Tone Plans are easily defaulted to fixed values specified by a 
    country code.   The 3 to 6 party loss plans are derived from the administered 
    2-par ty data and additional losses administered according to the number of 
    parties in the conference.
    This feature is available only if the new Digital Loss Plan 
    Modifications? field on the customer options form is set to y. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Highlights 
    8  
    Networking — ATM
    Asynchronous Transfer Mode (ATM) PNC Reliability
    A DEFINITY system without duplicated Switch Processing Elements (SPEs) 
    equipped for ATM Port Network Connectivity (PNC) is supported with duplicated 
    Expansion Port Network (EPN) connectivity to different points on an ATM network.  
    These points may be on separate ATM switches, the same ATM switch, or may be 
    directly connected to an ATM wide area network.  Existing levels of reliability for 
    DEFINITY are standard, high, and critical.  ATM PNC Reliability (formerly called 
    Hybrid Reliability) provides yet another level of reliability.  ATM PNC reliability 
    configurations are equipped with a simplex Switch Processing Element (SPE) 
    complex in the Processor Port Network (PPN), duplicate connectivity over ATM to 
    all Port Networks (PNs) and duplicate ATM interfaces in each PN.  The EPN 
    configuration for ATM PNC reliability is the same as that for an EPN equipped for 
    ATM critical reliability.
    The ATM PNC Reliability configuration may be the result of a new installation or 
    an upgrade from a previously standard reliability system.  ATM PNC Reliability is 
    cost-effective for customers who require redundancy and the resulting level of 
    reliability in their R8r ATM Wide Area Newtork () configuration to provide for 
    potential network and ATM switch outages. 
    Interworking with Bandwidth Constricted ATM Networks
    Administrators of DEFINITY R8r systems using ATM Port Network Connectivity 
    can fine-tune the operation when bandwidth is at a premium.  DEFINITY monitors 
    performance in the network, and alarms out-of-specification conditions.  During 
    out-of-specification conditions, calls between the affected Port Networks may 
    optionally be denied.  The alarm details identify those pairs of Port Networks that 
    are experiencing the congestion.  The congestion alarm indicates if an 
    unacceptable number of call set-ups have suffered excessive delay or have failed.  
    The alarm clears if set-ups begin to succeed at a defined rate.  The number of 
    calls and delay thresholds are provisionable.
    System Availability / Serviceability
    Incomplete Command Timeout
    An SAT user could enter a command through the SAT but then walk away without 
    ever canceling or otherwise completing the command. Certain commands (e.g. 
    add, change, remove, duplicate, set) if left in this incomplete state could actually 
    prevent the periodic save translations from executing which could lead to alarms 
    and possibly loss of newly translated data. If one of these commands is left in an 
    incomplete state for the duration of the 2-hour (default) timer, then the command 
    is canceled and the login session terminates.
    Display of Hardware and Firmware Vintages 
    When executing the “list configuration” command, the hardware (HW) and 
    firmware (FW) vintages display separately for applications of the TN802B. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Highlights 
    9  
    Trouble Isolation: List Trace Command
    Two new options for the list trace command allow customers and technicians to 
    troubleshoot misdirected calls, trunking/routing problems, and call denials.
    nlist trace station nnnnn (where nnnnn is the number of the station you 
    want to troubleshoot)
    nlist trace tac xxxx (where xxxx is the identifier of the trunk you want to 
    troubleshoot)
    Execute the list trace command with the relevant option word.
    nTo see all the list trace options, execute list trace at the command line.
    nTo redisplay the most-recently done trace, execute list trace previous at 
    the command line. 
    nTo cancel a trace in progress, press F7. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Highlights 
    10   
    						
    							Change Descriptions 
    11  
    DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions
    The following problems have been addressed and corrected in DEFINITY Enterprise 
    Communications Server (ECS), Release 8, Issue 2.0 (02.0.034.2).
    1. User defined data associated with the auto-selection of DIDs displayed as 
    asterisks in the Property Management System (PMS).
    2. If the Survivable Remote Processor was not in contact with the Survival 
    Remote Expansion Port Network (EPN), MAJOR EXP-LINK alarm and 
    MINOR EXP-INTF alarms were raised. Now, when the Survivable Remote 
    Processor is not in contact with the Survival Remote EPN, EXP-LINK and 
    EXP-INTF alarms are warnings.  A MAJOR SPR-EPN alarm is raised only 
    if the link between the SRP and SREPN is active.
    3. The Class of Restrictions (COR) value associated with a traditional user or 
    attendant console could only be changed by an administrator via the 
    System Access Terminal (SAT). Now, the COR value associated with a 
    traditional user or attendant console can be changed by a user (who has 
    console permissions) via a feature access code.
    4. Coverage following QSIG diversion did not properly alert all points in the 
    coverage path when the first was remote and the second was local. Now, 
    all available points in a principal’s coverage path after a QSIG diversion will 
    alert.
    5. An H.323 native endpoint drops its existing call (from Caller1) when an 
    incoming call from Caller 2 is received. Now, Caller2 receives a busy tone.  
    6. Users did not see the Maximum Number of External Calls Logged Per 
    Station and Message Waiting Indication for External Calls field on the 
    System Parameters form. They also did not see the Leave Word Calling 
    (LWC) Log External Calls field on the station form, nor on the Agent 
    Login-ID form. Now, users see these fields and are able to administer 
    values in them. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions 
    12  
    7. Processor channels could remain down after reset system 2 in some 
    cases. Now, processor channels come back up in these cases. 
    8.A rotary station user can now simulate flash hook by dialing the digit that’s 
    specified in the new feature parameters field, if this functionality has been 
    enabled by setting the new Recall Rotary Digit field on the station form to 
    yes.
    9. When making an Internet Protocol (IP) trunk call, if the originator drops the 
    call before the party answers, the call will still ring on the receiver side. 
    Now, the call will be dropped on the receiver side as well. 
    10. Third party merge acknowledge did not contain trunk group information 
    even if there were trunks on the call.  
    11. It was possible to administer a station with IP SoftPhone set to “y” and 
    Multimedia Mode set to “basic”. Now, if the user attempts to add such a 
    station, they will receive the error: “Mode must be ‘enhanced’ when IP 
    SoftPhone is ‘y’”
    12. It was possible to administer a station with IP SoftPhone set to “y” and no 
    call appearance buttons. Now, if the user attempts to administer such a 
    station, they will receive the error: “At least 1 call-appearance is required 
    when IP SoftPhone is ‘y’”.
    13. Incoming trunk calls routed to a QSIG-Centralized Attendant Service (CAS) 
    branch switch that had an invalid destination number administered on the 
    console-parameters form caused a system reset. 
    14. Nippon Telephone and Telegraph (NTT) Japan Integrated Services Digital 
    Networking (ISDN) cellular handsets received two-way talk cut-off when 
    conversing with a DEFINITY endpoint and the DEFINITY endpoint pressed 
    “hold”.
    15. If no gateway IP address was specified (when not needed) for the TN802B 
    board, the ping test would abort and the signaling groups would not be 
    placed into service. 
    16. If traceroute command timed out when it encountered a page break. 
    17. For R8 software optioned as a V7 switch, the TN802B board would not 
    boot. Now, it will boot in any release.
    18. When many requests for VDN Origin of Announcements (VOA) and regular 
    announcements were queued, it was possible for a request for a VOA 
    announcement to be lost.  This left the call in a hung state where it could 
    not be answered. 
    19. TTC Japan calls could fail due to the presence of Sending Complete IEs in 
    SETUP messages and the sending of NOTIFY messages. Now, neither will 
    be sent by DEFINITY on TTC Japan peer interfaces.
    20. DEFINITY did not suppor t interoperability with the Ascend MAX box.
    21. The “Logged-in Automatic Call Distribution (ACD) Agents” field on the 
    “display capacities” form was missing. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions 
    13  
    22. Q.931 calls failed after a few dozen calls.
    23.After entering “busyout pnc-standby”, control was returned to the SAT 
    before the process was complete. If the SAT entered another command, 
    new inter-port calls could not be made for up to one minute. Now, the SAT 
    forces the user to wait for the entire board test/release to complete before 
    gaining control.
    24. After a failed Microsoft
    ® NetMeeting® registration, the status showed as 
    authenticated-not registered. Now, about 30 seconds after a failed 
    NetMeeting
    ® registration, the station’s status shows as unregistered.
    25. Performing the Personal Station Administration (PSA) function on a 
    registered IP Solutions endpoint from a DCP set failed to allow the 
    endpoint to re-register.
    26. When a Basic Rate Interface (BRI) trunk’s administration of “send calling 
    number” was set to ‘n’, intermittently the terminating user saw the calling 
    party number.
    27. SAT commands like change, add, duplicate, remove, and set, if left 
    incomplete, interfered with periodic save translations. There is now an 
    administrable timout period that terminates these commands and avoids 
    the interference.
    28. The status station command for a logged-in agent-ID displayed ‘18xxxx’ as 
    its destination, where xxxx is the extension number of the physical terminal. 
    Now, only xxxx is displayed.  
    29. Calls covering to a busy Distributed Communications System (DCS) or 
    QSIG VALU coverage point with no other coverage points available, and for 
    which the principal was SAC’d, returned busy treatment to the originator, 
    but were not dropped.
    30. When a room change was executed from the Property Management 
    System (PMS) simulator, the Direct Inward Dialing (DID) did not change to 
    the new room.  
    31. High traffic H.323 IP trunks were not being updated to the idle state for use.
    32. The link to the Call Management System (CMS) could enter a state in 
    which administration could not be performed from the CMS.
    33. Pulling the TN802B board with no ethernet port defined did not take the 
    signaling groups out of service. Now, if the TN802B board is pulled, the 
    signalling groups go out of service. Also, if there is no ethernet port defined 
    for the region of the TN802B, the signaling groups do not go into service.
    34. Pushing the reset button on the faceplate of the TN802B board left the port 
    in service.
    35. Changes to the IP address after a busyout of the C-LAN board leave 
    obsolete routes on the CLAN board.
    36. There was no command to determine the status of the PSA. Now, there is a 
    “status psa” command that maps to the “status tti” form, which informs the 
    user that TTI must be enabled for the PSA to work. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions 
    14  
    37. The IP Solutions endpoint did not have the current button and lamp status 
    upon registration.
    38. Attempting to register an IP Solutions endpoint from an extension with a 
    data module corrupted the extension’s translation. Now, the registration is 
    denied.
    39. An extension with a large number of autodial buttons could not register as a 
    DoLAN endpoint. 
    40. If more than 16 node names were added on page two of the “node-names” 
    form, entries for the first field of the IP address in column two were also 
    displayed on page three. 
    41. System reset occurred if DCS+ was administered over H.323 IP trunks.
    42. If a station had coverage with “coverage all” and “hunt after coverage” 
    enabled, with only one coverage point in the coverage path, calls would not 
    follow the hunt to coverage.  
    43. When IP stations were registered and/or IP trunks were administered, 
    executing the “list usage extension” command would lock up the SAT.
    44. In Adjunct Switch Applications Interface (ASAI) messages, trunk group 
    number and member number were not provided for DCS calls. Now, they 
    are provided for the following:  
    Alerting Event Report
    Connected Event Report
    Call Offered Event Report
    Conference Event Report
    Transfer Event Report
    Adjunct Route Request
    3rd Party Merge Acknowledge
    45. In a QSIG CAS scenario when user A calls user B, both on the branch 
    switch, covers to the attendant on the main, the display on the console 
    shows “ to OPERATOR s”, which is wrong. Now, the display 
    correctly shows “ to  s”.
    46. Coverage calls to attendant on QSIG CAS branch were not working with 
    Trunk Access Codes (TAC) administered on the console.
    47. If the TN802B board was busied out, a DCP call to the Road Warrior 
    application received ring back. Now, a DCP receives busy. 
    48. DCS coverage calls that were answered did not invoke DCS re-routing.
    49. An incoming H.323 IP trunk call to a vector with a collect digit step did not 
    collect any digits. Now, the digits are collected and the vector is processed 
    correctly.
    50. Account codes did not show on CDR report if the account code button was 
    used. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions 
    15  
    51. The wakeup display mode did not timeout. Now, the wakeup mode 
    undergoes timeout after 1 minute.
    52. Abandoned calls to telecommuter application endpoints left the associated 
    endpoint ringing.
    53. If the system is optioned as V7, and the CLAN board is pulled, the trunk 
    groups remained in service. Now, the trunk groups are taken out-of-service 
    when the CLAN is pulled, if the trunk groups are part of an H.323 IP 
    signaling group.
    54.Procedure errors were generated when submitting the “data-module” form 
    of a PDM type with a blank Port field.
    55. The Access Security Gateway (ASG) could be turned on for a login, even if 
    the login was VOID.
    56. Translation corruption occurred on some Release 6 and ealier G3 si 
    systems, when the TN790 processor board was replaced with a new board 
    that contained Release 7.1 or later software. Now, when replacing a TN790 
    processor board on a pre R7.1 si system, a Major alarm is raised, and 
    translations are blocked from being saved.  A warning message is printed 
    on the copyright screen indicating an incompatibility between software and 
    hardware.
    57. The sum of the hardware (HW) and firmware (FW) vintages are now 
    displayed separately.
    58. In a telecommuter application, if the voice path is through a CO loop start 
    trunk, when the associated telephone drops the call, no disconnect 
    supervision is sent to DEFINITY, thus the service link is not dropped. If 
    another call is made within 10 seconds, the call is dropped. Now, when the 
    service link is up, the user can dial the Feature Access Codes (FAC) of the 
    multi-media enhanced mode to drop the service link.
    59. External unanswered calls were not logged. Now, the new feature “Log 
    External Calls” has been implemented to log external unanswered calls. 
    60. When a call covered to a Uniform Dial Plan (UDP) number over a non-DCS 
    trunk with Coverage of Calls Redirected Off-Net (CCRON) not enabled, the 
    call would at some point stop ringing at the coverage point.
    61. There were resource limits enforced for Station Busy Indicators (SBIs) of 
    100 on gaz and 500 on mips. Now, these resource limits for SBIs have 
    been eliminated.
    62. Traffic measurements in the “list measurements load-balance” reports were 
    often incorrect.
    63. When an endpoint attempts to register while an IP TTI port for the 
    extension already exists, the endpoint can not register. Now, the endpoint 
    successfully registers. 
    						
    							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
    Change Description  555-233-411  Issue 1
    April 2000
    Change Descriptions 
    16  
    64. When a telecommuter application attempted to use Trunk Access Code 
    (TAC) dialing to establish the service link audio call, the attempt failed if 
    more than 8 digits were needed after the TAC. Now, all digits after the TAC 
    are sent correctly.
    65. During the PMS database swap routine, the switch was performing resets.
    66. The Leave Word Calling (LWC) Log External Calls field appeared on the 
    station form for every software version.  It also appeared on the MASI 
    terminal form. Now, the field appears on the station form only when the 
    version is R8 or higher.  It does not appear on the MASI terminal form at all. 
    67. When a member was added to an in-service H.323 IP trunk group the new 
    member always stayed out-of-service. Now, if the trunk group is 
    out-of-service, the new member is out-of-service; if the trunk group is 
    in-service, the new member is in-service.
    68. A called failure occurred if a station had a higher Facility Restriction Level 
    (FRL) than the authorization code FRL.
    69. IP trunk calls sometimes did not clear properly.
    70. TN465 ports in CO, FX or WATS trunk groups did not receive the Incoming 
    Disconnect and Outgoing Disconnect timers. A new field has been added 
    to those trunk group types, on the Administrable Timer page; it is called 
    “Send Incoming/Outgoing Disconnect Timers to TN465 Ports?”.  If set to 
    y(es), the timers are sent to TN465B and later ports.
    71. If a # is used to dial an FP DID remote user, it was routed to the attendant 
    at the remote PBX. Now, it is terminated at the dialed extension.
    72. Calls redirected to a display set had too many spaces before the “to” on the 
    display, causing Audix failure.
    73. A telecommuter or road warrior application could have their service link 
    connected to an in-bound call that had not been answered by the IP 
    softphone. 
    74. A system could restart if a periodic or scheduled maintenance test did not 
    receive time to execute due to a system running under high load.
    75. When TTI was enabled on the ‘system parameters features’ form, the 
    ‘COR for PSA Dissociated Sets’ and ‘CPN, ANI for PSA Dissociated Sets’ 
    did not display properly.
    76. When Test #1382 passed, the TN802B port remained alarmed.
    77. Non-guest rooms showed as occupied when the attendant checked for 
    occupied rooms via Direct Extension Selection (DXS).
    78. The second channel on a world class BRI endpoint occasionally failed to 
    come up. 
    						
    All Lucent Technologies manuals Comments (0)

    Related Manuals for Lucent Technologies DEFINITY Enterprise Communications Server Release 8, Issue 2.0 (02.0.034.2) Description Manual