Alcatel-Lucent OmniPCX Office Manual
  1. Manuals
  2. Brands
  3. Alcatel-Lucent Manuals
  4. IP Phone
  5. OmniPCX Office
  6. Manual

Alcatel-Lucent OmniPCX Office Manual

Hide thumbs Also See for OmniPCX Office:
Table of Contents

Advertisement

Quick Links

Advertisement

Table of Contents
loading

Related Manuals for Alcatel-Lucent OmniPCX Office

Summary of Contents for Alcatel-Lucent OmniPCX Office

  • Page 2 Legal notice: The information presented is subject to change without notice. ALE International assumes no responsibility for inaccuracies contained herein. Copyright © ALE International, 2016 Disclaimer: While efforts were made to verify the completeness and accuracy of the information contained in this documentation, this document is provided “as is”.

  • Page 3: Table Of Contents

    Chapter 1 Expert Documentation structure Chapter 2 Problem-Solving Methodology Maintenance ....................Maintenance ....................Troubleshooting Procedure ................Extent of Failure ..................... Deliberate Reproduction of Defaults ............... Locating Errors ....................Element Substitution ..................Chapter 3 Board Management Maintenance ....................Generalities ....................3/62...
  • Page 4 System with a Software Version older than R2.0 ........... System with a Software Version from R2.0 ............ Assigning Directory Numbers ................. Initializing Sets ....................Chapter 4 Replacing / Relocating Sets Maintenance ....................Replacing a Set ....................Relocating a Set ..................... Adding Sets ....................
  • Page 5 Information displayed ................Types of board (INFO 0 of messages 100, 101, and 244) ......Types of terminal (INFO 0 of messages 111 and 112) ........Reasons for board refusal (INFO 1 of message 106) ........Reasons for terminal refusal (INFO 1 of message 111) ......... Additional information contained in message 112 (INFO 1: type of error) ..
  • Page 6 Maintenance ....................Chapter 10 SNMP Overview ..................... Protocol ...................... Topology ......................Security ......................SNMP Trap ..................... MIB ......................... Configuration .................... Configuring the SNMP Service ............... Notification Filtering ..................Supervision ....................6/62...
  • Page 7 As of R10.1, the OmniPCX Office Expert Documentation has been split into fifteen separated documents, each corresponding to a chapter of the previous version of this documentation. These documents are: table 1.1: Expert Documentation structure Documentation title Part number OmniPCX Office Expert Documentation: General Presentation...
  • Page 8 OmniPCX Office Expert Documentation: System services 8AL91213xxAC Summary: this document gives information about software keys, including their complete list. The document also describes opera- tion of the OmniPCX Office with NTP (as client or server) and the configuration of the embedded DHCP server. 8/62...
  • Page 9 Documentation title Part number [15] OmniPCX Office Glossary 8AL91214xxAC Summary: this document contains a glossary of general telecom- munications terms as well as specific terms related to OmniPCX Office. In the present document, cross-references are identified by the number in the first column of the above table.

  • Page 10: Maintenance

    Maintenance 2.1.1 Maintenance This section does not deal with failures caused by configuration errors nor with those caused by errors in the telephone features. In either of these cases, refer to the sections on MMC-Station and Telephone Features. In all cases, a thorough knowledge of the system (architecture, distribution of function processing, etc.) and of its telephone features is essential, and in particular the limits of these features.

  • Page 11: Deliberate Reproduction Of Defaults

    • In this case, the fault can only be located in the module • The failure is most likely to come from the power supply or from the CPU (control unit); the next most likely cause is a set or network interface board interfering with the CPU. Total failure of a group of sets: •...
  • Page 12 Chapter 2.1.6.2 Powering up/down the System Press the ON/OFF button. Wait for the LED to go to steady red (about 30 seconds): system powered down Press ON/OFF to power up again after intervening (with the boards plugged back in). Wait 3 to 4 minutes for the system to initialize completely.

  • Page 13: Maintenance

    Maintenance 3.1.1 Generalities The following conditions require maintenance to handle boards after these are accepted: First appearance in the system: • System configuration aspect when a new board is detected • Initialization and start-up of the corresponding hardware Dynamic appearance or disappearance due to physical causes: •...

  • Page 14: System With A Software Version From R2.0

    Chapter When a board is plugged, the system assigns numbers to the board equipment (user directory numbers or line numbers); these numbers are assigned in ascending order of free system numbers. The board equipment is initialized with the corresponding default configuration. When a board is plugged into a slot previously taken up by another board, this board is managed in the following way: if the new board is of the same type (same scan point) as the board previously plugged,...

  • Page 15: Assigning Directory Numbers

    processing is the same for a board in a "present but refused" state, but that board will not be deactivated. Note: In case of a "gentle" plugging-in, it is possible that the plugged board may not be detected by the CPU board or detected with the wrong slot number.

  • Page 16: Initializing Sets

    Chapter Example: We have an XS-N with an AMIX board, a PowerCPU EE with a Mini-MIX daughter board. For sets, the numbering order is: UA of AMIX. Z of AMIX. Z of Mini-MIX. VMU ports, RA. For trunks, the numbering order is: Trunks of AMIX.

  • Page 17: Maintenance

    The replacement set keeps its own default functions (customized settings are not transferred). The data not transferred are stored in the OmniPCX Office Rich Communication Edition system until a set of the same type as the initial one is connected.

  • Page 18: Relocating A Set

    The add-on modules are always transferred provided the substitution set supports these modules. Note 2: It is possible to replace a Reflexes set with an Alcatel-Lucent 9 series set. It is not possible to replace an Alcatel-Lucent 9 series set with a Reflexes set.

  • Page 19: Adding Sets

    4.1.3 Adding Sets When adding sets, attention must be paid to the limits on the number of sets and the features offered by the system software key. The set is recognized as soon as it has been plugged into the socket. 4.1.4 IP Phones When an IP phone is connected to the network, default parameters are configured on the...
  • Page 20 Chapter On dialing the ASR-Replace code in the new IP Phone, it requests the EDN and then password of the existing IP Phone. On successful replacement: The New IP Phone is assigned with the existing sets EDN and other properties The previous IP Phone with default configuration is deleted The OMC must be configured to enable the Noteworthy addressASRRep_IP.

  • Page 21: Maintenance

    Maintenance 5.1.1 Overview Configuration backup The backup operation concerns all the parameters not reinitialized during a warm reset: global data (software version, backup time and date, etc.) configuration data (types of boards and terminals, characteristics of terminals and groups, keys and directory settings, numbering plans, directory, Class of Service restrictions tables) data recorded by users (mail, appointment reminders, forwarding) call details counters...
  • Page 22 Chapter Manual backup: • by OMC (Expert View): Data Saving & Swapping -> Commands -> check Backup • by MMC-Station: DatSav -> ManBkp Automatic backup: • by OMC (Expert View): Data Saving & Swapping -> Data Saving -> Enter date, time and periodicity •...

  • Page 23: Interface Markers

    The system messages are divided into 2 tables: the hardware message table the history message table Interface markers XX # 1 for the first half-board of slot XX, XX # 2 for the second half-board, XX - YY for the YY access of slot XX, ***** concerning the system messages.
  • Page 24 Chapter Type Message Location Additional Information Action KEY REDUCED CPU (80) INFO 0 = reduced feature set index The features normally asso- 01 : VMU storage capacity dimin- ciated with the active key ished have been reduced due to a 02 : number of VMU and Auto- hardware problem (CPU mated Attendant ports diminished...
  • Page 25 Type Message Location Additional Information Action CLOCK PROBLEM Board location. INFO 0 = type of interface: T0, T2, Check there Clock synchronization prob- Access marker DASS2, etc. is no syn- lem detected on an add-on chronizing ac- module interface cess in the add-on mod- ules SPECIFIC ACCESS PROB-...
  • Page 26 Chapter Type Message Location Additional Information Action INTERNAL FAULT ON S0 Board location. If the fault Internal problem detected Access marker keeps recur- on an S0 access following ring, check release message giving the bus wir- cause as "deactivation of ing.
  • Page 27 Type Message Location Additional Information Action 4070 IO/EO BASE: ER- Board location. RORS DETECTED DUR- Interface mark- ING INITIALIZATION PHASE OF BOOT PRO- GRAM (RESET) 4070 IO/EO BASE: ER- Board location. RORS DETECTED DUR- Interface mark- ING SOFTWARE DOWN- LOAD PHASE 4070 IO/EO BASE: TRANS- Board location.

  • Page 28: History Messages

    Chapter Type Message Location Additional Information Action STORAGE MEMORY CPU (80) INFO 0 = type of error CHANGED OR LOST 0 : medium KO 1 : medium full 2 : checksum error 3 : system file control error INFO 1 = type of medium 0 : NAND FLASH CPU 2 : HARD DISK INFO 2 = type of initial medium...
  • Page 29 Type Message Location Additional Information Action SYSTEM RESTART INFO 0 = reason to restart 1 : MMC reset command 2 : reset due to hardware fault 3 : mail notify queue is full 4 to 5: reset following software problem 6: reset due to an external applica- tion to take into account new config- uration...
  • Page 30 Chapter Type Message Location Additional Information Action AUTOMATIC DATA SAVING CPU (80) End the MMC BACKUP REFUSED session. Save MMC session was active manually or wait for the next automat- ic save. LAUNCH OF DATA RESTORE CPU (80) Data Saving DATA RESTORE OK CPU (80) Check if the...
  • Page 31 Type Message Location Additional Information Action PS-BOOST BOARD FAULT CPU (80) INFO 0 = type of error (1 = more A PS-BOOST board problem than one boost present or boost in has been detected a small rack; 2 = no boost nor ex- ternal feeding;...
  • Page 32 Chapter Type Message Location Additional Information Action R_TERM_REBOOT_OR_RESE Board loca- INFO 0 = Reset (01) or Reboot (02) T_OF_USER_DATA tion INFO 1 = -- Reboot of IP terminal or reset of INFO 2 = First byte of EDN user data. INFO 3 = Second byte of EDN R_PUBLIC_DDI_REGISTRATI Board loca-...
  • Page 33 Type Message Location Additional Information Action PRINTER THRESHOLD O.K. Message emitted by the spooler when the array where the tick- ets are stored is less than 70% full again R_DHCP_SERVER_EXITED Board loca- INFO 0 = Bad configuration DHCP server exited due to bad tion INFO 1 = Option definition error configuration or option definition...
  • Page 34 Chapter Type Message Location Additional Information Action PERMANENT BOARD RESET Board loca- INFO 0 =1: hardware fault; 2: no re- Disconnect tion. sponse from board; 3: fan failure; 4: and reconnect running on battery; 5: license prob- the board. If lem;...
  • Page 35 Type Message Location Additional Information Action APPEARANCE OF A TERMIN- Board loca- INFO 0 = type of terminal tion. INFO 1 = reason for restarting A terminal has been recognized Interface by the system. This terminal is marker now operational NB: this message will only be sent if the NMC is present and active...
  • Page 36 Chapter Type Message Location Additional Information Action FAN STATUS CPU (80) or INFO 0 = fan identity (0 = fan 1; 1 = Controller fan 2) Board (81) INFO 1 = fan status (True = OK; or (82) False = KO) POWER SAVING INFO 0 = module (0 = basic mod- Check rota-...
  • Page 37 Type Message Location Additional Information Action REGISTER 500 CPU (80) INFO 0 = octet 1 of the IP address SIP registration failure (500: of the remote registry Server error) INFO 1 = octet 2 of the IP address of the remote registry INFO 2 = octet 3 of the IP address of the remote registry INFO 3 = octet 4 of the IP address...
  • Page 38 Chapter Type Message Location Additional Information Action REGISTER FAILED CPU (80) INFO 0 = octet 1 of the IP address SIP registration failure of the remote registry INFO 1 = octet 2 of the IP address of the remote registry INFO 2 = octet 3 of the IP address of the remote registry INFO 3 = octet 4 of the IP address...
  • Page 39 Type Message Location Additional Information Action THRESHOLD METERING TA- CPU (80) The critical threshold (80 % by default) of the data metering buffer has been reached THRESHOLD URGENT TABLE CPU (80) The critical threshold (80 % by default) of the urgent alarms ta- ble has been reached HARDWARE TABLE FULL CPU (80)
  • Page 40 Chapter Type Message Location Additional Information Action NMC WAIT ACK TIMEOUT CPU (80) The PCX received no acknow- ledgement for the establishment request sent to the NMC NMC PHONE NB MISSING CPU (80) The PCX attempted to call the NMC to send urgent alarms, but the NMC number was not spe- cified ADDRESS NOT REGISTERED...
  • Page 41 Type Message Location Additional Information Action GATEWAY TRAFFIC CPU (80) INFO 0 to INFO 3: bytes corres- If this alarm Too much traffic to the remote ponding to the IP address Network keeps recur- gateway xxxxx format ring, increase the bandwidth associated with the gate- way in the...
  • Page 42 Linux startup script occurs. INFO 2 = Critical error INFO 3 = Status R_NOE_DLD_SUCCESS CPU (80) INFO 0 = Device type Alcatel-Lucent 9 series down- INFO 1 = Files downloaded: one bit loading successful. for each kind of file. R_ANO_NOE_DLD_FAIL Board loca-...
  • Page 43 6.5.1 Types of board (INFO 0 of messages 100, 101, and 244) Boards R1.0 and R1.1 82H : integrated voice server 9EH : SLI board A0H : UAI board A1H : PRA board = E1 A2H : PRA board = DLE1 A3H : PRA board = T1 A4H : PRA board = DASS2 A7H : virtual XRA board...
  • Page 44 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 0EH 4070 IO base 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH 1FH station Alcatel-Lucent N/A 24H 24H 24H 24H 24H 24H 24H 24H 24H 24H 24H 24H IP Touch 4018 Phone set...
  • Page 45 R3.1 R4.0 R5.0 R5.1 R6.0 R8.1 R8.2 R9.0 R9.1 R9.2 R9.2 fore R4.1 R3.1 R7.1 External alpha- 26H 2FH 2FH 30H 31H 32H 34H 34H 34H 34H 34H 34H 38H numeric key- board for Re- flexes set DECT option 2AH 33H 33H 34H 35H 36H 37H 38H 38H 38H 38H 38H 3CH (Reflexes 3G set) Z standard...
  • Page 46 Chapter R3.1 R4.0 R5.0 R5.1 R6.0 R8.1 R8.2 R9.0 R9.1 R9.2 R9.2 fore R4.1 R3.1 R7.1 IP-DECT: 500 N/A N/A N/A N/A N/A N/A N/A N/A N/A 52H 52H 52H 56H DECT IP-DECT: 8232 N/A N/A N/A N/A N/A N/A N/A N/A N/A 53H 53H 53H 57H DECT IP-DECT GAP...
  • Page 47 13H : number of DLT2 accesses exceeded 19H : max. number of DECT base stations exceeded 21h : B channel init failed 22h : max. number of analog trunks reached for a cabinet 23h : max. number of analog trunks reached for the system 24h : maximum of resources reached 1CH : exceeded equipment level in module in terms of available energy 1DH : exceeded max.
  • Page 48 Chapter 28h : TSC IP set 2Ah : PCM digital network interface 2Bh : PCM analog network interface 2Dh : T1-CAS digital network interface 2Eh : T1-CAS analog network interface 2Fh, 30h, 31h, 32h : MSG1 to MSG4 interfaces 34h : Audio In interface 35h : Audio Out interface 36h : General bell interface 3Ah to 3Dh : MSG5 to MSG8 interfaces...
  • Page 49 Reject reasons for interfaces Meaning 25: REJ_MAX_IBS Maximum of IBS reached for a reached 26: REJ_MAX_WIRED_MAIN_DEV_PER_S Maximum of wired main devices reached 27: REJ_NIL_DYN_PROT Default allocated protocol is not NIL_PROT 28: REJ_MAX_POWER_BUDGET Maximum of power budget reached for a cab- inet 29: REJ_MAX_HSL_LINK_TS Maximum of hsl resources reached for a cab-...
  • Page 50 Chapter 21 : the key entered does not correspond to the system: the services are open for a limited time. 24 : the software key entered does not correspond to system software version (invalid serial number): the services are open for a limited time. 26 : a software key with too old an edition has been entered: the services are open for a limited time.
  • Page 51 NAND Flash memory (CPU ) or hard disk not detected (message 239) Urgent alarms OmniPCX Office Rich Communication Edition will generate a call to the network management center (NMC) if any of the following alarms is detected: the system reboots (message 0)
  • Page 52 (message 242) an error occurred at the reading of the voice prompt file (message 244) an error occurred at the writing of the voice prompt file (message 245) the downloading of an Alcatel-Lucent 9 series terminal has failed (message 252) 52/62...
  • Page 53 Maintenance 7.1.1 PowerCPU board used When maintaining and exchanging a PowerCPU board, the data stored in the SD card and/or in the Hard Disk will be restored by applying the following procedures. 7.1.1.1 Procedure to Exchange a PowerCPU 7.1.1.1.1 PowerCPU with SD Card (without Hard Disk) The SD Card Is not Faulty and Does not Have to Be Exchanged Insert the SD card in the new PowerCPU board.
  • Page 54 Chapter 7.1.2 PowerCPU EE board used When maintaining and exchanging a PowerCPU EE board, the data stored in the MSDB (Mass Storage Daughter Board) 8 GB equipped with eMMC (embedded Multi-Media Card) will be restored by applying the following procedures. 7.1.2.1 Procedure to Exchange a PowerCPU EE 7.1.2.1.1 The MSDB 8 GB equipped with eMMC is not faulty and does not have to be...
  • Page 55 Maintenance 8.1.1 Start Monitoring It is possible to follow the progress of the start in 2 ways: On the display of the dedicated stations Using the Web-Based Tool 8.1.1.1 On Station The display on the dedicated set indicates the different steps for starting the system with following elements: Start x.y (x is the step and y the sequence) 8.1.1.1.1 Detail: Start 2-6: detection of the cards of the main cabinet...
  • Page 56 Maintenance This paragraph applies only when the CPU is the PowerCPU board Some services of the OmniPCX Office Rich Communication Edition require a hard disk: Voice mail with a recording capacity of 200 hours ACD statistics In case of hard disk crash, these services are no more available:...
  • Page 57 OmniPCX Office nodes supervised by OmniVista 8770 is limited. SNMP is a protocol commonly used for data network supervision. Historic, hardware anomalies and urgent alarms of the OmniPCX Office are got via the SNMP service. Through the SNMP, an alarm report mechanism with traps (SNMP Trap V2C mechanism) allows to report the urgent alarms of the system on the fly.
  • Page 58 Only UDP protocol is used for SNMP. Ports used by SNMP are the default ones: Port 161 (GET mode): used by the OmniPCX Office, open only when the SNMP is activated in the OmniPCX Office Port 162 (TRAP mode): used by the supervisor to receive the traps The OmniPCX Office uses only SNMP V2c security.
  • Page 59 SNMP Trap Type SNMP Trap Name Trap defined in MIB ochmSystemRestart ochmSystemRestarted ochmCabinetUnplugged ochmCabinetOperational ochmBoardFailure ochmBoardCleared ochmBoardOperational ochmPowerSupplyFailure ochmPowerSupplyOperational ochmFanFailure ochmFanOperational ochmIsdnFailure ochmIsdnOperational ochmVoipLinkDown ochmVoipLinkUp ochmIbsSynchroDown ochmIbsSynchroUp ochmAnoRegisterReject ochmRemoteAccessMbxLocked ochmRemoteAccessMbxUnlocked ochmRemoteAccessWsapiLocked ochmRemoteAccessWsapiUnlocked ochmArpSpoofInfo ochmDefaultPasswordFound ochmEasyPasswordFound ochmDhcpServerExited ochmDhcpServerStatus ochmAnoQuarantineAlert ochmMgtsrvLock ochmMgtsrvUnlock ochmUnsupportedRamSize ochmMsdbHealthStatus ochmAnoPrinterFault ochmAnoMemoryAvail...
  • Page 60 Transmission: SNMP global statistics • SNMP: SNMP detail statistics Proprietary MIBs, containing: • A hardware MIB available to give a view of what OmniPCX Office system is made of • A specific MIB dedicated to the call handling 10.2.4.1 Hardware MIB The Hardware description gives information about the board itself.
  • Page 61 The historic event and hardware anomaly tables allow reading the recent problems that have occurred. Some of these problems correspond to the traps sent by OmniPCX Office, but most of them only describe less important troubles that the system has encountered.
  • Page 62 [9]. It is a free downloadable access, even when SNMP is not activated. The alarm supervision is done exclusively either through the SNMP supervisor or the NMC. The two services are exclusive, but neither the OMC nor the OmniPCX Office check it. The installer must insure that both are not configured.

Table of Contents