The document is the Administrator Guide for Avaya Communication Manager, issue 4.0, release 5.0 from January 2008. It provides guidance for administrators on tasks such as logging in, managing telephones, setting up features, handling calls, and routing calls. The guide includes conventions, legal information, and how to get support.
This document provides guidelines for antenna system planning for GSM and UMTS radio networks. It summarizes key aspects of antenna selection, feeder length planning, tilt planning, diversity planning and installation. Rules are presented for choosing antenna types, using transmultiplexers, height planning, azimuth planning and ensuring compatibility for site sharing. Mounting guidelines are also covered for mast, tower, roof and wall installations. The document is intended as a reference for radio network engineers on the essential issues to consider for effective antenna system planning.
ell Allocation (CA) is the subset of the total frequency band that is available for one BTS. It can be viewed as the total transport resource available for traffic between the BTS and its attached MSs. One Radio Frequency CHannel (RFCH) of the CA is used to carry synchronization information and the Broadcast Control CHannel (BCCH). This can be any of the carriers in the cell and it is known as the BCCH carrier or the c
carrier. Strong efficiency and quality requirements have resulted in a
0
rather complex way of utilizing the frequency resource. This chapter describes the basic principles of how to use this resource from the physical resource itself to the information transport service offered by the BTS.
Carrier separation is 200 kHz, which provides: • 124 pairs of carriers in the GSM 900 band • 374 pairs of carriers in the GSM 1800 band • 299 pairs of carriers in the GSM 1900 band
Using Time Division Multiple Access (TDMA) each of these carriers is divided into eight Time Slots (TS). One TS on a TDMA frame is called a physical channel, i.e. on each duplex pair of carriers there are eight physical channels.
A variety of information is transmitted between the BTS and thMS. The information is grouped into different logical channelsEach logical channel is used for a specific purpose such as paging, call set-up and speech. For example, speech is sent on the logical channel Traffic CHannel (TCH). The logical channels are mapped onto the physical channels.
The information in this chapter does not include channels specific for GPRS (General Packet Radio Service). For basic information on GPRS see chapter 14 of this documentation.
This document provides an overview of GSM principles and network structure. It discusses key aspects of the GSM system including frequency reuse, multiple access techniques, network components, numbering plans and identifiers. The objectives are to understand the GSM system, its structure, protocols, channel combinations, radio techniques and the introduction of GPRS and EDGE. It contains detailed descriptions and illustrations of concepts such as cells, frequency division duplexing, time division multiple access, frequency planning and network interfaces.
This document describes the X2 application protocol (X2AP) which is used for communication between two eNodeBs in an Evolved Universal Terrestrial Radio Access Network. It defines procedures for basic mobility management, including handover preparation and UE context release, as well as global procedures like load indication and error reporting. The document also outlines the services, functions and specifications of X2AP.
This document discusses BTS hotels, which are a concept that aggregates multiple base transceiver stations (BTSs) into a single location to help provide connectivity where towers are not permitted. BTS hotels provide benefits like decreased costs for site leases, power, maintenance and backhaul by sharing resources. The global market for distributed antenna systems (DAS), which include BTS hotels, is growing significantly. Vendors are getting involved by offering BTS hotels as a managed service and leasing their networks. The document recommends developing BTS hotels as a managed service and implementing a neutral host solution to serve multiple operators.
Begin your evolution with Ericsson’s new small cell solutions.
There is need for the multi-operator dots, multi-dot enclosure, and strand -mounted bracket. The complicated arrangements are made easier with Ericsson small cell solutions.
The document discusses virtualization technologies including server, storage, and network virtualization. Server virtualization allows multiple virtual machines (VMs) to run on a single physical host, improving resource usage. Storage virtualization manages storage volumes and isolates servers from physical storage hardware. Network virtualization integrates physical networks into a virtual network to support VM migration and load balancing. The document also describes how the OSMU centrally manages VMs and backups VM data to improve high availability of the virtualization solution.
This document provides guidelines for antenna system planning for GSM and UMTS radio networks. It summarizes key aspects of antenna selection, feeder length planning, tilt planning, diversity planning and installation. Rules are presented for choosing antenna types, using transmultiplexers, height planning, azimuth planning and ensuring compatibility for site sharing. Mounting guidelines are also covered for mast, tower, roof and wall installations. The document is intended as a reference for radio network engineers on the essential issues to consider for effective antenna system planning.
ell Allocation (CA) is the subset of the total frequency band that is available for one BTS. It can be viewed as the total transport resource available for traffic between the BTS and its attached MSs. One Radio Frequency CHannel (RFCH) of the CA is used to carry synchronization information and the Broadcast Control CHannel (BCCH). This can be any of the carriers in the cell and it is known as the BCCH carrier or the c
carrier. Strong efficiency and quality requirements have resulted in a
0
rather complex way of utilizing the frequency resource. This chapter describes the basic principles of how to use this resource from the physical resource itself to the information transport service offered by the BTS.
Carrier separation is 200 kHz, which provides: • 124 pairs of carriers in the GSM 900 band • 374 pairs of carriers in the GSM 1800 band • 299 pairs of carriers in the GSM 1900 band
Using Time Division Multiple Access (TDMA) each of these carriers is divided into eight Time Slots (TS). One TS on a TDMA frame is called a physical channel, i.e. on each duplex pair of carriers there are eight physical channels.
A variety of information is transmitted between the BTS and thMS. The information is grouped into different logical channelsEach logical channel is used for a specific purpose such as paging, call set-up and speech. For example, speech is sent on the logical channel Traffic CHannel (TCH). The logical channels are mapped onto the physical channels.
The information in this chapter does not include channels specific for GPRS (General Packet Radio Service). For basic information on GPRS see chapter 14 of this documentation.
This document provides an overview of GSM principles and network structure. It discusses key aspects of the GSM system including frequency reuse, multiple access techniques, network components, numbering plans and identifiers. The objectives are to understand the GSM system, its structure, protocols, channel combinations, radio techniques and the introduction of GPRS and EDGE. It contains detailed descriptions and illustrations of concepts such as cells, frequency division duplexing, time division multiple access, frequency planning and network interfaces.
This document describes the X2 application protocol (X2AP) which is used for communication between two eNodeBs in an Evolved Universal Terrestrial Radio Access Network. It defines procedures for basic mobility management, including handover preparation and UE context release, as well as global procedures like load indication and error reporting. The document also outlines the services, functions and specifications of X2AP.
This document discusses BTS hotels, which are a concept that aggregates multiple base transceiver stations (BTSs) into a single location to help provide connectivity where towers are not permitted. BTS hotels provide benefits like decreased costs for site leases, power, maintenance and backhaul by sharing resources. The global market for distributed antenna systems (DAS), which include BTS hotels, is growing significantly. Vendors are getting involved by offering BTS hotels as a managed service and leasing their networks. The document recommends developing BTS hotels as a managed service and implementing a neutral host solution to serve multiple operators.
Begin your evolution with Ericsson’s new small cell solutions.
There is need for the multi-operator dots, multi-dot enclosure, and strand -mounted bracket. The complicated arrangements are made easier with Ericsson small cell solutions.
The document discusses virtualization technologies including server, storage, and network virtualization. Server virtualization allows multiple virtual machines (VMs) to run on a single physical host, improving resource usage. Storage virtualization manages storage volumes and isolates servers from physical storage hardware. Network virtualization integrates physical networks into a virtual network to support VM migration and load balancing. The document also describes how the OSMU centrally manages VMs and backups VM data to improve high availability of the virtualization solution.
The document describes various signaling messages used in different layers and interfaces of the GSM network, including:
1. Radio Resource (RR) messages for channel establishment, ciphering, handover, channel release, paging, and system information on the Um interface.
2. Messages for BTS Management (BTSM) on the Abis interface for radio link management, channel management, and TRX management.
3. Base Station System Application Part (BSSAP) messages on the A interface for resource management between the BSC and MSC.
4. Mobile Application Part (MAP) messages involving mobility services, call handling services, and short message services between entities in the core network.
* Analysis of all critical aspects (market, technical, economic and financial) ensuring the best possible alignment between business and technology strategies
* Integrated and iterative approach to carry out a sound and reliable business case
* Tailored for the specific needs of players in the 4G ecosystem (operators, vendors, analysts and consultants, investors, regulators)
* Compliant with WiMAX and LTE technical specifications
The document discusses 5G networks and Internet of Things (IoT) architecture. For 5G, it describes the key requirements of ultra-high radio speed, ultra-low latency, and massive connectivity. This will require redefining cloud-RAN/fronthaul architecture with distributed 5G cores and packet-based fronthaul to handle high traffic loads. For IoT, it discusses the growth of the market and challenges around standards, security and privacy, and monetization. It provides an overview of key platform architectures from Microsoft, AWS, and Google for IoT. The biggest challenge remains developing solutions that can scale to handle the massive number of IoT devices connecting to 5G networks.
5G – Enable, elevate, and emerge Digitalising us to infinity and beyondaakash malhotra
5G networks have been launched in over 95 countries around the world. Global 5G adoption is growing rapidly, with Asia-Pacific expected to become the largest 5G market by 2025. 5G offers significantly higher speeds and lower latency compared to 4G, enabling new applications like augmented reality, virtual reality, smart cities, and industrial IoT. Many countries are strategizing phased 5G rollouts and establishing partnerships and committees to develop their 5G ecosystems. Successful 5G deployments will depend on investments in infrastructure, collaborations between stakeholders, and government initiatives to accelerate network buildouts.
The document discusses numerology and air interface resources in 5G New Radio (NR), including:
- NR supports multiple subcarrier spacings (SCS) to accommodate different services and bands. SCS determines symbol length and impacts coverage, latency, mobility, and phase noise.
- Time domain resources include slots, subframes, and frames which are configured similarly to LTE. Symbol length depends on SCS.
- Frequency domain resources include resource blocks and bandwidth parts. Space domain resources include antenna ports and quasi-co-location.
This document provides an operation and maintenance guide for the BSC6900 GSM system using the Web LMT. It describes the hardware requirements, Web LMT interface and functions, BSC maintenance tasks including device panel, transmission configuration, and software queries. It also covers BTS maintenance, alarms, performance, security, tracing, monitoring, and software management functions available through the Web LMT.
CCNA 1 Routing and Switching v5.0 Chapter 10Nil Menon
The document discusses the application layer of the OSI model and common application layer protocols. It describes how protocols like HTTP, SMTP, POP, FTP, and SMB allow end-user applications to transfer files, emails and web pages across the network. DNS and DHCP are also covered as they provide important network services like translating domain names to IP addresses and assigning IP configuration to devices.
This document provides an overview of analyzing and troubleshooting SDCCH drop rate issues. It describes the SDCCH channel and how it is used, defines the KPI formula for calculating SDCCH drop rate, lists the counters involved in the KPI, and presents a flow chart of the SDCCH assignment process. Tools that can be used for the analysis are also identified, including Business Objects, MCOM, ZXG10 OMCR, and TEMS Investigation.
UMTS system architecture, protocols & processesMuxi ESL
This document provides an overview of UMTS system architecture and protocols. It discusses:
- The logical architecture of UTRAN including RNC and Node-B elements.
- Interfaces between network elements are clearly specified to allow interoperability between equipment from different manufacturers.
- The main functions of the RNC include radio resource management, call management, and connection to the core network.
- Protocols in UTRAN include RRC for radio resource control, RLC for radio link control, and MAC for medium access control.
This document contains information about setting up and operating an Alcatel-Lucent 9500 MPR radio system, including:
- The CD contains manuals for operating and maintaining the 9500 MPR radio.
- Contact information is provided for technical assistance from Alcatel-Lucent, including phone support hours and emergency procedures.
- Instructions are included for initial turnup of the system, such as enabling modules, provisioning radios and protection schemes, and setting the network element time.
The document discusses using the Atoll radio planning software to design a UMTS mobile network to provide coverage for the town of Seville, Spain. Atoll allows modeling network traffic based on user profiles and services. It also incorporates detailed maps of Seville for terrain and land use data needed for radio propagation modeling and network optimization. The document defines user profiles for adolescents and young people with different expected usage patterns for voice, MMS, internet access, and video calling services.
This document is a technical specification from ETSI (European Telecommunications Standards Institute) that defines the mobile radio interface layer 3 specification for GSM (Global System for Mobile communications), specifically version 7.8.0 from 1998. It contains specifications for radio resource management procedures in both circuit-switched and packet-switched modes, including procedures for idle mode, dedicated mode, group receive/transmit modes, and changing between dedicated channels. It also references related documents and defines terms and abbreviations used.
This document provides an overview of Long Term Evolution (LTE) radio access network planning. It covers LTE fundamentals and key technologies including OFDM, SC-FDMA, frame structure and reference signals. Frequency and spectrum planning includes channel bandwidth, spacing and raster. Link budget and coverage planning outlines propagation parameters, equipment parameters and system reliability factors. Interference and guard band analysis examines interference between TDD systems and spectrum refarming. Network capacity planning defines capacity and limiting factors. The document also provides guidance on U-Net simulation and operation for LTE network planning.
This guide explains how to implement an Aruba 802.11n wireless network that must provide high-speed access to an auditorium-style room with 500 or more seats. Aruba Networks refers to such networks as high-density wireless LANs (HD WLANs). Lecture halls, hotel ballrooms, and convention centers are common examples of spaces with this requirement. Because the number of concurrent users on an AP is limited, to serve such a large number of devices requires access point (AP) densities well in excess of the usual AP per 2,500 – 5,000 ft2 (225 – 450 m2). Such coverage areas therefore have many special technical design challenges. This validated reference design provides the design principles, capacity planning methods, and physical installation knowledge needed to successfully deploy HD WLANs.
BTS Reserves for Installation, Preventative Maintenance and Acceptanceibrahimnabil17
1. Install the BTS cabinet and make sure bolts are fixed well to secure it to the shelter ground. Install L-angles to fix the cabinet to the wall.
2. Make sure proper cable installation including power, E1, fiber, alarm and jumper cables in good arrangement using clips and ties. Ensure spacing between cables and clips.
3. Configure the BTS and integrate it to ensure it is clear from alarms during performance and integration testing.
24x7 NOC services are setup to meet your infrastructure support requirements. NOC Services delivers the monitoring and management services includes network monitoring, server monitoring, application monitoring, website monitoring and US and Global 24x7.
This document provides an overview of optional features for UTRAN UR11.1, including wideband AMR speech support, PS signaling bearers for IMS, cell broadcast service, PS conversational bearers for VoIP, robust header compression, and PS conversational bearers for VoIP over HSDPA. It describes the benefits and technical details of each feature. The document also includes figures illustrating network architectures, protocols, and technical concepts related to the optional features.
This document provides an overview of techniques for troubleshooting LTE throughput problems. It discusses isolating throughput issues to the radio, transport, or end-to-end domains. The agenda includes initial checks of network changes, UE capabilities, and RBS parameters. Radio analysis examines the baseband scheduler traces and signal traces between blocks to identify issues. Transport analysis evaluates network infrastructure. End-to-end analysis looks at the entire path from UE to application server. The goal is to pinpoint the root cause of throughput degradation within each domain using theory, traces, and examples.
This document provides guidance on optimizing the success rate of uplink TBF establishments in GSM networks. It defines key terms related to uplink TBF establishment success rate and describes how to measure the number of successful, failed, and total attempted uplink TBF establishments. The document then details various factors that could affect uplink TBF establishment success rate and provides troubleshooting steps to check each factor. Finally, it presents three case studies where optimizations were made to improve low uplink TBF establishment success rates in actual networks.
Call pilot call center setup and operationkyawzay htet
This document provides instructions for setting up and operating a Nortel Networks call center using their Call Center and CallPilot software. It describes the different call center features, how to add agents and set up skillsets to route calls. The document also covers setting up and managing skillset mailboxes to handle calls not answered by agents.
Sonic os standard_3_9_administrators_guideAshwani Singh
This document is an administrator's guide for SonicOS Standard 3.9 that provides comprehensive internet security. It contains information about setting up and configuring SonicWALL security appliances, including collecting ISP information, running the setup wizard, registering the appliance, and viewing system status and settings. The guide is organized into sections covering introduction and setup, system configuration and management, and technical reference for features.
The document describes various signaling messages used in different layers and interfaces of the GSM network, including:
1. Radio Resource (RR) messages for channel establishment, ciphering, handover, channel release, paging, and system information on the Um interface.
2. Messages for BTS Management (BTSM) on the Abis interface for radio link management, channel management, and TRX management.
3. Base Station System Application Part (BSSAP) messages on the A interface for resource management between the BSC and MSC.
4. Mobile Application Part (MAP) messages involving mobility services, call handling services, and short message services between entities in the core network.
* Analysis of all critical aspects (market, technical, economic and financial) ensuring the best possible alignment between business and technology strategies
* Integrated and iterative approach to carry out a sound and reliable business case
* Tailored for the specific needs of players in the 4G ecosystem (operators, vendors, analysts and consultants, investors, regulators)
* Compliant with WiMAX and LTE technical specifications
The document discusses 5G networks and Internet of Things (IoT) architecture. For 5G, it describes the key requirements of ultra-high radio speed, ultra-low latency, and massive connectivity. This will require redefining cloud-RAN/fronthaul architecture with distributed 5G cores and packet-based fronthaul to handle high traffic loads. For IoT, it discusses the growth of the market and challenges around standards, security and privacy, and monetization. It provides an overview of key platform architectures from Microsoft, AWS, and Google for IoT. The biggest challenge remains developing solutions that can scale to handle the massive number of IoT devices connecting to 5G networks.
5G – Enable, elevate, and emerge Digitalising us to infinity and beyondaakash malhotra
5G networks have been launched in over 95 countries around the world. Global 5G adoption is growing rapidly, with Asia-Pacific expected to become the largest 5G market by 2025. 5G offers significantly higher speeds and lower latency compared to 4G, enabling new applications like augmented reality, virtual reality, smart cities, and industrial IoT. Many countries are strategizing phased 5G rollouts and establishing partnerships and committees to develop their 5G ecosystems. Successful 5G deployments will depend on investments in infrastructure, collaborations between stakeholders, and government initiatives to accelerate network buildouts.
The document discusses numerology and air interface resources in 5G New Radio (NR), including:
- NR supports multiple subcarrier spacings (SCS) to accommodate different services and bands. SCS determines symbol length and impacts coverage, latency, mobility, and phase noise.
- Time domain resources include slots, subframes, and frames which are configured similarly to LTE. Symbol length depends on SCS.
- Frequency domain resources include resource blocks and bandwidth parts. Space domain resources include antenna ports and quasi-co-location.
This document provides an operation and maintenance guide for the BSC6900 GSM system using the Web LMT. It describes the hardware requirements, Web LMT interface and functions, BSC maintenance tasks including device panel, transmission configuration, and software queries. It also covers BTS maintenance, alarms, performance, security, tracing, monitoring, and software management functions available through the Web LMT.
CCNA 1 Routing and Switching v5.0 Chapter 10Nil Menon
The document discusses the application layer of the OSI model and common application layer protocols. It describes how protocols like HTTP, SMTP, POP, FTP, and SMB allow end-user applications to transfer files, emails and web pages across the network. DNS and DHCP are also covered as they provide important network services like translating domain names to IP addresses and assigning IP configuration to devices.
This document provides an overview of analyzing and troubleshooting SDCCH drop rate issues. It describes the SDCCH channel and how it is used, defines the KPI formula for calculating SDCCH drop rate, lists the counters involved in the KPI, and presents a flow chart of the SDCCH assignment process. Tools that can be used for the analysis are also identified, including Business Objects, MCOM, ZXG10 OMCR, and TEMS Investigation.
UMTS system architecture, protocols & processesMuxi ESL
This document provides an overview of UMTS system architecture and protocols. It discusses:
- The logical architecture of UTRAN including RNC and Node-B elements.
- Interfaces between network elements are clearly specified to allow interoperability between equipment from different manufacturers.
- The main functions of the RNC include radio resource management, call management, and connection to the core network.
- Protocols in UTRAN include RRC for radio resource control, RLC for radio link control, and MAC for medium access control.
This document contains information about setting up and operating an Alcatel-Lucent 9500 MPR radio system, including:
- The CD contains manuals for operating and maintaining the 9500 MPR radio.
- Contact information is provided for technical assistance from Alcatel-Lucent, including phone support hours and emergency procedures.
- Instructions are included for initial turnup of the system, such as enabling modules, provisioning radios and protection schemes, and setting the network element time.
The document discusses using the Atoll radio planning software to design a UMTS mobile network to provide coverage for the town of Seville, Spain. Atoll allows modeling network traffic based on user profiles and services. It also incorporates detailed maps of Seville for terrain and land use data needed for radio propagation modeling and network optimization. The document defines user profiles for adolescents and young people with different expected usage patterns for voice, MMS, internet access, and video calling services.
This document is a technical specification from ETSI (European Telecommunications Standards Institute) that defines the mobile radio interface layer 3 specification for GSM (Global System for Mobile communications), specifically version 7.8.0 from 1998. It contains specifications for radio resource management procedures in both circuit-switched and packet-switched modes, including procedures for idle mode, dedicated mode, group receive/transmit modes, and changing between dedicated channels. It also references related documents and defines terms and abbreviations used.
This document provides an overview of Long Term Evolution (LTE) radio access network planning. It covers LTE fundamentals and key technologies including OFDM, SC-FDMA, frame structure and reference signals. Frequency and spectrum planning includes channel bandwidth, spacing and raster. Link budget and coverage planning outlines propagation parameters, equipment parameters and system reliability factors. Interference and guard band analysis examines interference between TDD systems and spectrum refarming. Network capacity planning defines capacity and limiting factors. The document also provides guidance on U-Net simulation and operation for LTE network planning.
This guide explains how to implement an Aruba 802.11n wireless network that must provide high-speed access to an auditorium-style room with 500 or more seats. Aruba Networks refers to such networks as high-density wireless LANs (HD WLANs). Lecture halls, hotel ballrooms, and convention centers are common examples of spaces with this requirement. Because the number of concurrent users on an AP is limited, to serve such a large number of devices requires access point (AP) densities well in excess of the usual AP per 2,500 – 5,000 ft2 (225 – 450 m2). Such coverage areas therefore have many special technical design challenges. This validated reference design provides the design principles, capacity planning methods, and physical installation knowledge needed to successfully deploy HD WLANs.
BTS Reserves for Installation, Preventative Maintenance and Acceptanceibrahimnabil17
1. Install the BTS cabinet and make sure bolts are fixed well to secure it to the shelter ground. Install L-angles to fix the cabinet to the wall.
2. Make sure proper cable installation including power, E1, fiber, alarm and jumper cables in good arrangement using clips and ties. Ensure spacing between cables and clips.
3. Configure the BTS and integrate it to ensure it is clear from alarms during performance and integration testing.
24x7 NOC services are setup to meet your infrastructure support requirements. NOC Services delivers the monitoring and management services includes network monitoring, server monitoring, application monitoring, website monitoring and US and Global 24x7.
This document provides an overview of optional features for UTRAN UR11.1, including wideband AMR speech support, PS signaling bearers for IMS, cell broadcast service, PS conversational bearers for VoIP, robust header compression, and PS conversational bearers for VoIP over HSDPA. It describes the benefits and technical details of each feature. The document also includes figures illustrating network architectures, protocols, and technical concepts related to the optional features.
This document provides an overview of techniques for troubleshooting LTE throughput problems. It discusses isolating throughput issues to the radio, transport, or end-to-end domains. The agenda includes initial checks of network changes, UE capabilities, and RBS parameters. Radio analysis examines the baseband scheduler traces and signal traces between blocks to identify issues. Transport analysis evaluates network infrastructure. End-to-end analysis looks at the entire path from UE to application server. The goal is to pinpoint the root cause of throughput degradation within each domain using theory, traces, and examples.
This document provides guidance on optimizing the success rate of uplink TBF establishments in GSM networks. It defines key terms related to uplink TBF establishment success rate and describes how to measure the number of successful, failed, and total attempted uplink TBF establishments. The document then details various factors that could affect uplink TBF establishment success rate and provides troubleshooting steps to check each factor. Finally, it presents three case studies where optimizations were made to improve low uplink TBF establishment success rates in actual networks.
Call pilot call center setup and operationkyawzay htet
This document provides instructions for setting up and operating a Nortel Networks call center using their Call Center and CallPilot software. It describes the different call center features, how to add agents and set up skillsets to route calls. The document also covers setting up and managing skillset mailboxes to handle calls not answered by agents.
Sonic os standard_3_9_administrators_guideAshwani Singh
This document is an administrator's guide for SonicOS Standard 3.9 that provides comprehensive internet security. It contains information about setting up and configuring SonicWALL security appliances, including collecting ISP information, running the setup wizard, registering the appliance, and viewing system status and settings. The guide is organized into sections covering introduction and setup, system configuration and management, and technical reference for features.
The document is a user guide for a ZTE Axon M phone. It provides instructions on basic phone set up and use, including installing SIM and memory cards, charging the battery, powering on/off, locking and unlocking the screen, using the touchscreen, understanding key functions, personalizing settings like ringtones and wallpapers, connecting to networks and devices via WiFi, Bluetooth, NFC, and USB. It also covers making phone calls, managing contacts, setting up email accounts, sending messages, and adjusting additional settings. The guide contains detailed explanations and steps for new users to get started with the essential functions of the phone.
This document provides a manual for the MaxCommunicator software. It begins with warnings about toll fraud and liability. It then covers installation, getting started with the main interface, handling calls, configuring settings, and other features like monitoring extensions and using voicemail. The manual provides step-by-step instructions for common phone system tasks in MaxCommunicator.
This document provides reference information for commands, programming, and connectivity in EViews 9. It includes sections on basic commands and objects, working with graphs, tables, and spool objects, strings and dates, EViews programming, and external connectivity options. The document is copyrighted by IHS Global Inc.
This document provides an abridged user guide for MapInfo Professional Version 9.0. It includes information about the software's features, instructions for installation and configuration, and contact details for technical support. New features in Version 9.0 include the ability to work with date/time data, use curved labels, directly access Universal Data formats, and employ templates for layouts. The guide also covers system requirements, licensing, installing related programs and data, and troubleshooting potential issues.
This document provides notes from a Linux system administration course. It covers topics like installing Red Hat Linux, configuring XFree86 for graphics, managing software packages, understanding the boot sequence, basic network concepts, kernel functions, configuring services, managing users and groups, working with filesystems, and basic security measures. The document contains detailed sections on partitioning and formatting disks, mounting filesystems, and using common Linux administration tools.
This document is a user guide for the Gigaset CL750A GO phone. It provides an overview of the phone and its components. The guide describes how to set up the phone for use over an analog landline or internet connection, and how to configure voip settings. It also explains the phone's basic functions such as making calls, using directories, messages lists, and settings menus.
This document provides an overview and instructions for using the Vivado IDE (Integrated Design Environment). It describes how to launch Vivado, create and manage projects, run synthesis and implementation, view and edit design files and properties, customize the Vivado environment, and use various windows like the sources window, device window, and Tcl console. The document contains revision notes and refers the reader to additional video tutorials for using Vivado.
This document is a user guide for the VideoJet 10 video encoding and transmission device. It provides information on installing and configuring the device, including connecting video and network cables, setting the date and time, configuring encoding settings, and establishing connections between senders and receivers. The guide also covers operating the device for live video streaming and playback of recorded video clips. Safety information is provided at the beginning, and maintenance procedures such as testing network connections and performing a device reset are discussed at the end.
The document provides instructions for installing the WATCHOUT software, connecting the necessary hardware components like display computers via an Ethernet network, and acquiring WATCHOUT license keys to allow the software to run on each computer in the system. It outlines the minimum requirements for a basic operational WATCHOUT system and where to go for additional information on setting up and configuring a full-scale presentation environment.
Faronics Deep Freeze Enterprise User GuideFaronics
This document is the user guide for Deep Freeze Enterprise, which allows administrators to centrally manage and deploy software configurations on multiple computers. It describes how to install and configure Deep Freeze Configuration Administrator and Enterprise Console to customize settings like frozen drives, ThawSpace locations, scheduled tasks and more. The Enterprise Console then enables monitoring and managing Deep Freeze across a network from a single interface.
Faronics Deep Freeze Server Enterprise User GuideFaronics
This document is the user guide for Deep Freeze Enterprise, software that protects computers from unwanted changes by restoring them to a known good state after each reboot or at scheduled times. The guide provides instructions on installing Deep Freeze, configuring settings using the Deep Freeze Configuration Administrator tool, and managing frozen computers and tasks using the Deep Freeze Enterprise Console.
This document provides technical information about the Harmony SCU HMI controller, including:
- An overview of the system architecture, package contents, and device functions.
- Requirements for installing the controller, including mechanical, electrical, and wiring guidelines.
- Descriptions of the controller modules and their input/output capabilities.
- Instructions for connecting devices, installing the controller, and connecting to a PC for configuration.
- Specifications for the controller's general operation, I/O, memory, and communication interfaces.
- Procedures for configuring, troubleshooting, and maintaining the controller system.
인터맥 PB22, PB32 및 PB50 모바일 프린터 제품군은 창고관리, 유통, 매장 및 기업 자산관리 분야에서 까다로운 애플리케이션을 보유한 고객에게 탁원한 선택이 될 것입니다.
인터맥 PB 프린터는 경쟁 제품보다 2~3배 빠른 인쇄속도로 작업자의 생산성과 정확성을 크게 향상시킵니다.
네트워크 연결은 유선 및 무선 인터페이스 (802.11 b / g, BT, 직렬, USB)를 선택하면 사용자 환경에 맞는 인터페이스를 선택할 수 있으며, 벨트 클립, 어깨 끈, 차량 마운트 등 다양한 운반 옵션을 사용할 수 있습니다.
또한 이 인터맥 PB 시리즈 프린터는 5 피트에서 다중 낙하 사양과 IP54 등급 및 지게차 강도의 충격 및 진동 사양을 갖추고 있습니다.
The industry’s fastest 2, 3, and 4 inch rugged mobile label printers
Built rugged to survive real-world industrial and retail environments
Two to three times faster time-tofirst- label than competitive products
Low cost of development, deployment and support
Seamless integration with Intermec mobile computers and other mobile devices
Secure wired and wireless communications options: Bluetooth®, 802.11 b/g, USB, Serial
Label sensors minimize printing errors and reduce waste
SmartSystems® remote device management reduces support needs
Optimized for Intermec media, including linerless label media options
PRINTER CHARACTERISTICS
Width : 160 mm (6.3 in)
Height : 174.5 mm (6.9 in)
Depth : 78.8 mm (3.1 in)
Weight (with battery) : 1189 g (42.0 oz)
ENVIRONMENT
Operating temperature : -15°C to 50°C (5°F to 122°F)
Storage temperature : -30°C to 70°C (-22°F to 158°F)
Humidity : 10 to 90% (non-condensing)
Sealing : IP54 (excludes paper path)
Drop spec : 1.5m (5 ft.) drops to concrete; 26 times including all corners and sides
PB22/32 : 2m (6.5 ft) multiple drops to concrete with optional protective case
POWER
PB50: 14.8V Li-Ion, 2.2 Ah, rechargeable battery
MEMORY
RAM: 16MB, Flash: 64MB
STANDARD COMMUNICATIONS
RS-232 Serial
USB v.2.0
OPTIONAL COMMUNICATIONS
Bluetooth® (v2.0, Class 1)
802.11b/g
WIRELESS SECURITY
Authentication & Encryption Options : WEP (64 and 128 bit) LEAP; WPA-PSK (TKIP / RC4); WPA2/802.11i- PSK (CCMP / AES);EAP-TLS, -TTLS, -PEAP, -FAST
PRINT SPEED AND RESOLUTION
4ips (101.6mm/sec), 203 dpi (8 dots/mm)
PRINT TECHNOLOGY
Printhead : Direct thermal
CARD READER (PB21/31 Option)
3 track magnetic stripe reader supports ANSI, ISO 7811, AAMVA, CA MVA, RAW formats
EMV-compatable smart card reader is EMV 2000, ISO 7816, CCID compliant
MEDIA (Type : Labels or receipt media)
Labels and Tags : Duratherm II, Duratherm III, Duratherm NIR, Duratherm III IR, Duratherm III Synthetic, Duratherm III Linerless, Duratherm II 5-mil Tag
Receipts : Duratherm Receipt II, Duratherm Receipt III
Media Width Ranges : PB50: 49mm to 111.5mm (2 to 4.39 in)
Core ID : 19mm (0.75 in) standard, 10.16 mm (0.4 in) supported
Max OD : PB50: 67.3mm (2.65 in)
SOFTWARE
Programming Language
IPL, Fingerprint, ZSim (ZPLII Simulation), ESC-P, DSim (DPL), CSim (CPCL)
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
인터맥 PB21, PB31 및 PB51은 감열타입, 견고한 모바일 프린터로 인보이스, 운송, 물류, 배달, 모바일 POS (point-of-sale) 도매, 소매 영수증, 창고관리, 재고관리 분야에 적합한 모바일 프린터 입니다.
PB21, PB31, PB51 모바일 프린터는 경쟁 모델보다 메모리가 2배 이상이며, 최적화된 인쇄 메커니즘을 채택하여 영수증과 인보이스를 20~30 % 더 빠르게 처리할 수 있으며 로고와 같은 복잡한 그래픽도 쉽게 처리 할 수 있습니다.
안정된 인쇄를 위해 Notch, Black Mark, End-of-Roll 및 도어 열림상태 (직관적인 LCD 디스플레이를 통해 모두 전달됨)를 감지하는 온보드 센서로 PB21, PB31, PB51 프린터는 작업자가 프린터의 상태를 항상 알 수 있도록 도와줍니다.
네트워크 연결은 유선 및 무선 인터페이스 (802.11 b / g, Bluetooth, 직렬, USB) 중 하나를 선택하면 환경에 맞는 인터페이스를 선택할 수 있습니다.
또한 프린터는 5 피트, 26회 낙하 사양과 (6.5 피트, 옵션 보호 케이스 포함); IP54 등급이 적용되었습니다.
The industry’s fastest 2,3 and 4 inch rugged mobile receipt printers
Built rugged to survive realworld mobility in field service, route accounting and pointof- service applications
20-30% faster time-to-receipt and -invoice printing than competitive products
Low cost of development and support
Paper sensors and standard LCD display minimize lost transactions and wasted time troubleshooting
Seamless integration with Intermec computers and other mobile devices
Secure wired and wireless communication options: Bluetooth®, 802.11 b/g, USB, Serial
Optional integrated card reader supports latest EMV and ISO payment standards
SmartSystems® remote device management reduces support needs
PRINTER CHARACTERISTICS
Width : 160 mm (6.3 in)
Height : 174.5 mm (6.9 in)
Depth : 78.8 mm (3.1 in)
Weight (with battery) : 1189 g (42.0 oz)
ENVIRONMENT
Operating temperature : -15°C to 50°C (5°F to 122°F)
Storage temperature : -30°C to 70°C (-22°F to 158°F)
Humidity : 10 to 90% (non-condensing)
Sealing : IP54 (excludes paper path)
Drop spec : 1.5m (5 ft.) drops to concrete; 26 times including all corners and sides (Mil Std 810F procedure)
PB21/31: 2m (6.5 ft) multiple drops to concrete with optional protective case
POWER
PB51: 14.8V Li-Ion, 2.2 Ah, rechargeable battery
MEMORY
RAM: 16MB, Flash: 64MB
STANDARD COMMUNICATIONS
RS-232 Serial
USB v.2.0
OPTIONAL COMMUNICATIONS
Bluetooth® (v2.0, Class 1)
802.11b/g (PB21/31 only)
WIRELESS SECURITY
Authentication & Encryption Options : WEP (64 and 128 bit) LEAP; WPA-PSK (TKIP / RC4); WPA2/802.11i- PSK (CCMP / AES);EAP-TLS, -TTLS, -PEAP, -FAST
PRINT SPEED AND RESOLUTION
4ips (101.6mm/sec) 203 dpi (8 dots/mm)
PRINT TECHNOLOGY
Printhead : Direct thermal
CARD READER (PB21/31 Option)
3 track magnetic stripe reader supports ANSI, ISO 7811, AAMVA, CA MVA, RAW formats
EMV-compatable smart card reader is EMV 2000, ISO 7816, CCID compliant
MEDIA (Type : Labels or receipt media)
Labels and Tags : Duratherm II, Duratherm III, Duratherm NIR, Duratherm III IR, Duratherm III Synthetic, Duratherm II, 5-mil Tag
Receipts : Duratherm Receipt II, Duratherm Receipt III
Media Width : 111.5 mm (4.39 in)
Core ID : 19mm (0.75 in) standard
Max OD : 67.3mm (2.65 in)
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
This document provides an overview of SAP Cloud Identity Services - Identity Provisioning. It discusses what identity provisioning is, how to set up tenants, recent releases and new features, concepts like systems and properties, operations that can be performed, supported systems, security considerations, monitoring and troubleshooting, and offboarding. It also references scenarios like real-time provisioning and hybrid identity management.
This document is the user guide for BMC Remedy ServiceDesk: Incident Management 7.0. It provides an overview of the product and its features. The guide is intended for various users, including requesters, support staff, and incident managers. It describes how to perform common functions in ITSM applications and how to work with the different console views to log, track, assign, resolve and close service requests and incidents.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Building RAG with self-deployed Milvus vector database and Snowpark Container...Zilliz
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
15. Overview
About this book
Overview
Avaya Communication Manager is the centerpiece of Avaya applications. Running on a variety
of Avaya S8XXX Servers and DEFINITY Servers, and providing control to Avaya Media
Gateways and Avaya communications devices, Communication Manager can be designed to
operate in either a distributed or networked call processing environment.
Communication Manager carries forward all of a customer’s current DEFINITY capabilities, plus
offers all the enhancements that enable them to take advantage of new distributed
technologies, increased scalability, and redundancy. Communication Manager evolved from
DEFINITY software and delivers no-compromise enterprise IP solutions.
Communication Manager is an open, scalable, highly reliable and secure telephony application.
The software provides user and system management functionality, intelligent call routing,
application integration and extensibility, and enterprise communications networking.
Purpose of this book
This book describes the procedures and screens used in administering the most recent release
of Communication Manager running on any of the following:
●
Avaya S8XXX Servers
- DEFINITY servers
- S8100, S8300, S8400, S8500, or S87XX Servers
●
Avaya S8XXX Servers configured as a Local Survivable Processor (LSP).
●
Avaya media gateways
- MCC1 or SCC1 Media Gateways
- G250, G350, G600, G650, or G700 Media Gateways
Newer releases of Communication Manager contain all the features of prior releases.
Intended audience
This document is intended for system administrators and managers, for users interested in
information about specific features, and Avaya personnel responsible for planning, designing,
configuring, selling, and supporting the system.
Issue 4.0 January 2008
15
16. About this book
Contents
This document includes the following chapters:
●
Chapter 1: System Basics tells you how to log in and log off, set permissions for others
who use the administration terminal, set daylight savings rules, set the system date and
time, post messages, and back up the information you administer.
●
Chapter 2: Planning the System provides information on system-wide functions. It explains
how to read, use, and make simple changes to your dial plan, and how to assign feature
access codes.
●
Chapter 3: Managing Telephones explains how to add, swap, and remove telephones, and
how to customize a telephone, for Communication Manager administrators.
●
Chapter 4: Managing Telephone Features explains how to administer feature buttons for
your users’ telephones.
●
Chapter 5: Managing Attendant Consoles explains attendant console feature buttons, and
tells you how to change, move, or add attendant consoles.
●
Chapter 6: Managing Displays provides information on the messages that appear on the
read-out screen on display telephones.
●
Chapter 7: Handling Incoming Calls shows you how to set up call coverage for incoming
calls to be sure that incoming calls are answered when the called party is unavailable.
●
Chapter 8: Routing Outgoing Calls explains how Avaya Communication Manager handles
outgoing calls and tells you how to modify call restrictions and your routing plan.
●
Chapter 9: Managing Multimedia Calling describes the Multimedia Applications Server
Interface (MASI), and provides instructions on administration, monitoring, and
troubleshooting. This section also provides information on Multimedia Call Handling
(MMCH), which enables users to control voice, video, and data transmissions using a
telephone and PC.
●
Chapter 10: Setting Up Telecommuting provides information on system-wide settings and
individual user administration for telecommuting.
●
Chapter 11: Enhancing System Security provides information on analyzing and setting up
basic system security, preventing toll fraud, using logins and permissions and passwords,
and dealing with security violations.
●
Chapter 12: Managing Trunks contains procedures for working with analog and digital
trunks. Specialized trunks such as APLT, tandem, release-link, DMI-BOS and ISDN trunk
groups are not covered in this manual.
●
Chapter 13: Managing Announcements tells you how to record, save, copy, restore and
delete announcements.
16 Administrator Guide for Avaya Communication Manager
17. Conventions used
●
Chapter 14: Managing Group Communications shows you how to administer your system
so users can page other users or use their telephones as intercoms. You can also give
specific users permission to monitor other users’ calls or to interrupt active calls with
important messages.
●
Chapter 15: Managing Data Calls describes the system features available to enable data
communications.
●
Chapter 16: Administering Avaya Servers describes how to administer an Avaya S87XX
Server and an Avaya G700 Media Gateway and the Avaya S8300 Server.
●
Chapter 17: Collecting Call Information provides information on account codes, and on
tracking and collecting billing information about calls.
●
Chapter 18: Telephone Reference describes many of the telephones that you can connect
to Communication Manager. It also describes the unique features and buttons for each
telephone series to help you administer your user telephones.
●
Chapter 19: Screen Reference provides a brief description and a graphic representation of
the Communication Manager screens used for administration. It also lists the valid values
for fields on the screens, and describes when and why to use each value.
Conventions used
Become familiar with the following terms and conventions. They help you use this book with
Communication Manager.
●
A “screen” is the display of fields and prompts that appear on a terminal monitor.
See the Screen Reference chapter for an example of a screen and how it is shown in this
book.
●
We use the term “telephone” in this book. Other Avaya books might refer to telephones as
phones, voice terminals, stations, or endpoints.
●
Keys and buttons are printed in a bold font: Key.
●
Titles of screens are printed in a bold font: Screen Name.
●
Names of fields are printed in a bold font: Field Name.
●
Text (other than commands) that you need to type into a field are printed in a bold font:
text.
●
Commands are printed in a bold constant width font: command.
●
Variables are printed in a bold constant width italic font: variable.
●
We show complete commands in this book, but you can always use an abbreviated
version of the command. For example, instead of typing list configuration
station, you can type list config sta.
Issue 4.0 January 2008
17
18. About this book
●
If you need help constructing a command or completing a field, remember to use Help.
- When you press Help at any point on the command line, the system displays a list of
available commands.
- When you press Help with your cursor in a field on a screen, the system displays a list of
valid entries for that field.
●
Messages that the system displays are printed in a constant width font: system message.
●
To move to a certain field on a screen, you can use the Tab key, directional arrows, or the
Enter key on your keyboard.
●
If you use terminal emulation software, you need to determine what keys correspond to
Enter, Return, Cancel, Help, and Next Page keys.
●
We show commands and screens from the newest release of Communication Manager. If
your system has an older version of Communication Manager installed, substitute the
appropriate commands for your system and see the manuals you have available.
●
The status line or message line can be found near the bottom of your monitor. This is
where the system displays messages for you. Check the message line to see how the
system responds to your input. Write down the message if you need to call the helpline.
●
When a procedure requires you to press Enter to save your changes, the screen clears.
The cursor returns to the command prompt. The message line shows “command
successfully completed” to indicate that the system accepted your changes.
Admonishments
Admonishments that might appear in this book have the following meanings:
Note:
Note:
Draws attention to information that you must heed.
Tip:
Draws attention to information that you might find helpful.
Tip:
! CAUTION:
Denotes possible harm to software, possible loss of data, or possible service
interruptions.
CAUTION:
!
WARNING:
WARNING:
Denotes possible harm to hardware or equipment.
! DANGER:
DANGER:
Denotes possible harm or injury to your body.
18 Administrator Guide for Avaya Communication Manager
19. Trademarks
!
SECURITY ALERT:
SECURITY ALERT:
Denotes when system administration might leave your system open to toll fraud.
Trademarks
All trademarks identified by ® or ™ are registered trademarks or trademarks, respectively, of
Avaya, Inc. All other trademarks are the property of their respective owners.
Related Resources
The following documents provide additional information.
Administration for Network Connectivity for Avaya Communication Manager, 555-233-504
ATM Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124
Avaya Application Solutions -- IP Telephony Deployment Guide, 555-245-600
Avaya Business Advocate User Guide, 07-300653
Avaya Call Center Release 4.0 Automatic Call Distribution (ACD) Guide, 07-600779
Avaya Call Center Release 4.0 Call Vectoring and Expert Agent Selection (EAS) Guide,
07-600780
Avaya Communication Manager Advanced Administration Quick Reference, 03-300364
Avaya Communication Manager Basic Administration Quick Reference, 03-300363
Avaya Communication Manager Basic Diagnostics Quick Reference, 03-300365
Avaya Remote Feature Activation (RFA) User Guide, 03-300149
Avaya Toll Fraud and Security Handbook, 555-025-600
Converged Communications Server Installation and Administration, 555-245-705
DEFINITY Communications Systems Generic 2.2 and Generic 3 Version 2 DS1/CEPT1/ISDN
PRI Reference, 555-025-107
DEFINITY Enterprise Communications Server Release 1.1 Getting Started with the Avaya R300
Remote Office Communicator, 555-233-769
Feature Description and Implementation for Avaya Communication Manager, 555-245-205
Hardware Description and Reference for Avaya Communication Manager, 555-245-207
Installation, Upgrades and Additions for Avaya CMC1 Media Gateways, 555-233-118
Issue 4.0 January 2008
19
20. About this book
Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers,
03-300430
Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers,
03-300431
Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers,
03-300432
Overview for Avaya Communication Manager, 03-300468
Reports for Avaya Communication Manager, 555-233-505
System Capacities Table for Avaya Communication Manager on Avaya Media Servers,
03-300511
Using the Avaya Enterprise Survivable Servers (ESS), 03-300428
What’s New in Avaya Communication Manager, 03-300682
For documents not listed here, go to http://www.avaya.com. Select Support and then Product
Documentation.
How to obtain Avaya books on the Web
If you have internet access, you can view and download the latest version of Avaya
documentation products. To view any book, you must have a copy of Adobe Acrobat Reader.
Note:
Note:
If you don’t have Acrobat Reader, you can get a free copy at
http://www.adobe.com.
For example, to access an electronic version of this book:
1. Access the Avaya Web site at http://www.avaya.com/support/.
2. Click Product Documentation.
3. To find a specific book, type the document number (for example, 03-300509 for this book) in
the Search Support text box, and then click GO.
4. In the resulting list, locate the latest version of the document, and then click the document
title to view the latest version of the book.
How to comment on this book
Avaya welcomes your feedback. Contact us through:
20 Administrator Guide for Avaya Communication Manager
21. How to get help
●
e-mail: document@avaya.com
●
fax: 1-303-538-1741
●
Contact your Avaya representative
Mention this document’s name and number, Administrator Guide for Avaya Communication
Manager, 03-300509.
Your comments are of great value and help improve our documentation.
How to get help
If you suspect that you are being victimized by toll fraud and you need technical assistance or
support in the United States and Canada, call the Technical Service Center's Toll Fraud
Intervention Hotline at 1-800-643-2353.
If you need additional help, the following resources are available. You might need to purchase
an extended service agreement to use some of these resources. See your Avaya
representative for more information.
Go to the Avaya Web site at http://www.avaya.com/support:
●
If you are within the United States, click the Escalation Management link. Then click the
appropriate link for the type of support you need.
●
If you are outside the United States, click the Escalation Management link. Then click
International Services, which includes telephone numbers for the international Centers of
Excellence. Or contact your local Avaya authorized dealer for any additional help and
questions.
Issue 4.0 January 2008
21
23. Chapter 1: System Basics
Logging into the System
You must log in before you can administer your system. If you are performing remote
administration, you must establish a remote administration link and possibly assign the remote
administration extension to a hunt group before you log in. The members of this hunt group are
the extensions of the data modules available to connect to the system administration terminal.
For information about setting up remote administration, contact your Avaya technical support
representative. When not using the system, log off for security purposes.
Logging in from a system terminal
This procedure provides instructions for logging in from a system terminal, not a remote
terminal.
To log into the system:
1. Enter your login name. Press Enter.
2. Enter your password. Press Enter.
For security, your password does not display as you type it.
3. Enter the kind of terminal you have or the type your system emulates. Press Enter.
The Command prompt displays.
Note:
Note:
If you enter the wrong terminal type, it can lock up your system. If the system is
not responding to keyboard commands, type newterm. Press Enter. Enter the
correct terminal type on the new screen. Press Enter. If this does not work, turn
the power off only on the terminal and then turn it back on. The terminal reboots
and you can log in again.
Issue 4.0 January 2008
23
24. System Basics
Logging in for remote administration
To log in for remote administration:
1. Dial the Uniform Call Distribution (UCD) group extension number.
Note:
The UCD group extension number is assigned when you set up remote
administration.
Note:
●
If you are off-premises, use the Direct Inward Dialing (DID) number, a Listed Directory
Number (LDN) (you must use a telephone), or the trunk number dedicated to remote
administration.
●
If you are on-premises, use an extension number.
If you dialed a DID number, dedicated trunk number, or extension, you receive data tone
or visually receive answer confirmation.
If an LDN was dialed, the attendant will answer.
a. Ask to be transferred to the UCD group extension number.
You receive data tone or visually receive answer confirmation.
b. Transfer the voice call to your data terminal.
The Login prompt displays.
2. Complete the steps for Logging into the System on page 23.
For information about setting up remote administration, contact your Avaya technical
support representative.
See also Chapter 11: Enhancing System Security. For a complete description of the Security
Violation Notification feature, see "Security Violation Notification" in Feature Description and
Implementation for Avaya Communication Manager, 555-245-205.
Accessing the Avaya S8XXX Server
To administer an Avaya S8XXX Server, you must be able to access it. Personal computers and
services laptop computers equipped with a network PCMCIA card, Avaya Site Administration
(ASA), and a Web browser are the primary support access for system initialization, aftermarket
additions, and continuing maintenance.
You can access an Avaya S8XXX Server in one of three ways:
●
directly
●
remotely over the customer’s local area network (LAN)
●
over a modem
24 Administrator Guide for Avaya Communication Manager
25. Logging into the System
A direct connection and over the customer’s LAN are the preferred methods. Remote access
over a modem is for Avaya maintenance access only.
Accessing the Avaya S8XXX Server Directly
You can access an Avaya S8XXX Server directly by plugging a computer into the services port
which defaults to port 2 (Eth1) on the back of the server. You must use a crossover cable with
an RJ45 connector on each end. Plug the other end into the network connector (NIC card) on
the your computer. You might need a NIC card adapter.
Once connected, you can administer the server using three tools:
●
Web interface for server-specific administration.
●
ASA for various features of Avaya Communication Manager
●
An SSH client, like PuTTY, and an IP address of 192.11.13.6.
Web Interface - You can access the server Web interface either by connecting directly to the
services port on the Avaya S8XXX Server, or by connecting over the customer network.
Connected to the services port - To use the server Web interface:
1. Open either the Netscape or MS Internet Explorer browser.
2. In the Location/Address field, type 192.11.13.6. Press Enter.
3. When prompted, log in to administer the Avaya S8XXX Server and the features of Avaya
Communication Manager.
Connected to the customer network - To use the server Web interface:
1. Open either the Netscape or MS Internet Explorer browser.
2. In the Location/Address field, type the active server name or IP address. Press Enter.
3. When prompted, log in to administer the Avaya S8XXX Server and the features of Avaya
Communication Manager.
You can also connect directly to an individual server using its name or IP address.
Accessing the Avaya S8XXX Server remotely over the network
You can access the Avaya S8XXX Server from any computer connected through the LAN. To
access either server, use the IP address assigned to the server you want to access. You can
also use the active server address to connect automatically to the server that is active. Once
connected, you can administer the server using three tools:
●
Web interface for server-specific administration and call processing features
●
Avaya Site Administration for Communication Manager (Only available on the active
Communication Manager server)
●
An SSH client, like PuTTY, and an IP address of 192.11.13.6.
Issue 4.0 January 2008
25
26. System Basics
Using Avaya Site Administration
Avaya Site Administration features a graphical user interface (GUI) that provides access to SAT
commands as well as wizard-like screens that provide simplified administration for frequently
used features. You can perform most of your day-to-day administration tasks from this interface
such as adding or removing users and telephony devices. You can also schedule tasks to run at
a non-peak usage time. ASA is available in several languages.
The S8300, S8400, or S87XX Server can be used to download Avaya Site Administration. A
downloadable version of this package can be accessed through the S8300, S8400, or S87XX
Server Web Interface. This software must be installed on a computer running a compatible
Microsoft Windows operating system such as Windows 95, 98, NT 4.0, Millennium Edition,
Windows 2000, or Windows XP. Once installed, it can be launched from a desktop icon, from
the P330 Device Manager, or through a link in the S8300 Server Web Interface.
Installing Avaya Site Administration
If you do not have ASA on your computer, make sure your personal computer (PC) or laptop
first meets the following minimum requirements:
Operating systems
Processor/RAM
Windows 2000
Windows XP
2003 (Standard and
Enterprise)
Pentium-class 300 MHz/64 MB
Pentium-class 300 MHz/64 MB
Pentium-class 300 MHz/64 MB
Graphics adapter
SVGA with minimum screen resolution of
800 x 600
Floppy disk drive
3-1/2 in. 1.44-MB floppy disk drive
CD-ROM
CD-ROM drive (required to install ASA
from CD)
Available hard disk space
A minimum of 100-MB free hard disk space
is required. The requirement for disk space
depends on the size and number of
configuration data sets.
Printer port
Standard PC or network printer port is
required for connecting to a printer to
produce station button labels.
26 Administrator Guide for Avaya Communication Manager
27. Logging into the System
Operating systems
Processor/RAM
Network adapter
Required for network access to the S87XX
Server, AUDIX, and other
network-connected systems.
Free serial ports
One free serial port capable of 9600-bps
operation is required for a connection to
each serial device (UPS).
Avaya recommends that PCs have at least
a 16550A UART or 16550A UART
simulator (capable of 56 kbps DTE-speed
connections). USB and internal modems
should emulate this hardware.
A second serial port is required for
simultaneous connection to AUDIX through
a serial connection.
Install ASA on your computer using the Avaya Site Administration CD. Place the ASA CD in the
CD-ROM drive and follow the installation instructions in the install wizard.
ASA supports a terminal emulation mode, which is directly equivalent to using SAT commands
on a dumb terminal or through an SSH session. ASA also supports a whole range of other
features, including the graphically enhanced interface (GEDI) and Data Import. For more
information see the Help, Guided Tour, and Show Me accessed from the ASA Help menu.
Starting Avaya Site Administration
To start ASA:
1. Start up ASA by double-clicking the ASA icon, or click Start>Programs>Avaya Site
Administration.
2. In the Target System field, use the pull-down menu to select the desired system.
3. Click Start GEDI.
You now are connected to the desired system.
Configuring Avaya Site Administration
When Avaya Site Administration is initially installed on a client machine, it needs to be
configured to communicate with Communication Manager on the Avaya S8XXX Server.
When you initially run ASA, you are prompted to create a new entry for the switch connection.
You are also prompted to create a new voice mail system if desired.
Issue 4.0 January 2008
27
28. System Basics
Adding a Switch Administration Item
To add a switch administration item:
1. Click File > New > Voice Mail System.
The system displays the Add Voice Mail System screen.
2. Enter a name in the Voice Mail System Name field.
3. Click Next. The connection type dialog box displays.
4. Click the Network connection radio button.
5. Click Next. The Network Connection dialog box displays.
6. Enter the IP address used to connect to the Avaya S8XXX Server.
7. Click Next. The Network Connection/Port Number dialog box displays.
8. In the TCP/IP Port Number field, enter port 5023.
9. Click Next. The Network Connection/Timeout Parameters dialog box displays. Leave the
default values for the timeout parameters.
10. Click Next. The login type dialog box displays.
11. Click the "I want to login manually each time" radio button.
12. Click Next. The Voice Mail System Summary dialog box displays.
13. Check the information, use the Back button to make corrections if necessary, and click the
Test button to test the connection.
14. When the connection is successfully tested, click Next and then Finish.
Note:
Note:
In order for ASA to work properly with the ASG Guard II, the Write (ms) field on
the Advanced tab of the Connection Properties screen must be set to a value
of 5 (i.e., delay of 5 ms). ASG Guard II is an outboard appliance providing access
security for Avaya products that do not have Access Security Gateway (ASG)
software as a native application. For more information on ASG Guard II, contact
your Avaya technical support representative.
Adding a new voice system
When you initially run ASA, you are prompted to create a new entry for the switch
connection if you have not already done so. To set up the desired system, click the New
VOICE SYSTEM icon (on the left of the toolbar row). Complete the Add Voice System
wizard to build the system record. When completed, the record will be available in the
Target System pull-down list.
28 Administrator Guide for Avaya Communication Manager
29. Logging into the System
Logging in with Access Security Gateway
Access Security Gateway (ASG) is an authentication interface used to protect the system
administration and maintenance ports and logins associated with Avaya Communication
Manager. ASG uses a challenge and response protocol to validate the user and reduce
unauthorized access.
You can administer ASG authentication on either a port type or login ID. If you set ASG
authentication for a specific port, it restricts access to that port for all logins. If you set ASG
authentication for a specific login ID, it restricts access to that login, even when the port is not
administered to support ASG.
Authentication is successful only when Avaya Communication Manager and the ASG
communicate with a compatible key. You must maintain consistency between the Access
Security Gateway Key and the secret key assigned to the Communication Manager login. For
more information about ASG, see Using Access Security Gateway (ASG) on page 459.
Before you can log into the system with ASG authentication, you need an Access Security
Gateway Key, and you need to know your personal identification number (ASG). The Access
Security Gateway Key must be pre-programmed with the same secret key (such as, ASG Key,
ASG Passkey, or ASG Mobile) assigned to the Avaya Communication Manager login.
Verify that the Access Security Gateway (ASG) field on the System-Parameters Customer
Options (Optional Features) screen is set to y. If not, contact your Avaya representative.
Logging in with ASG
To log into the system with ASG:
1. Enter your login ID. Press Enter.
The system displays the challenge number (for example, 555-1234) and system Product ID
number (for example, 1000000000). The Product ID provides Avaya Services with the
specific identifier of your Avaya MultiVantage communications application.
2. Press ON to turn on your Access Security Gateway Key.
3. Type your PIN. Press ON.
The Access Security Gateway Key displays a challenge prompt.
4. At the challenge prompt on the Access Security Gateway Key, type the challenge number
without the "-" character (for example, 5551234) from your screen. Press ON.
The Access Security Gateway Key displays a response number (for example, 999-1234).
5. At the response prompt on your terminal, type the ASG response number without the "-"
character (for example, 9991234). Press Enter.
The Command prompt displays.
Issue 4.0 January 2008
29
30. System Basics
Note:
If you make 3 invalid login attempts, the system terminates the session. For more
information, see the appropriate maintenance book for your system.
Note:
Login messages
Two messages may be displayed to users at the time of login.
●
The Issue of the Day message appears prior to a successful login. In general, use the
Issue of the Day to display warnings to users about unauthorized access. The client that is
used to access the system can affect when, how, and if the user sees the Issue of the Day
message.
●
The Message of the Day (MOTD) appears immediately after a user has successfully
logged in. In general, use the Message of the Day to inform legitimate users about
information such as upcoming outages and impending disk-full conditions.
Using the system default Issue of the Day
The Communication Manager file /etc/issue.avaya contains sample text that may be used for
the Issue of the Day message.
To use the system default Issue of the Day:
1. Log into the Communication Manager server and at the CLI enter
cp /etc/issue.avaya /etc/issue
cp /etc/issue.avaya /etc/issue.net
Setting Issue of the Day and Message of the Day
For more detailed information on setting login messages and interaction with individual access
services, see the See the Communication Manager Administrator Logins White Paper on
http://support.avaya.com/elmodocs2/white_papers/CM_Administrator_Logins.pdf.
In general, to administer the Issue of the Day and the Message of the Day, use
/bin/vi or
/usr/share/emacs to perform the following edits:
1. Configure etc/pam.d/mv-auth to include issue PAM module.
2. Edit /etc.issue and /etc.issue.net (if using telnet) to include the text for the Issue
of the Day.
30 Administrator Guide for Avaya Communication Manager
31. Logging off the System
3. Edit etc/motd to include the text for the Message of the Day.
Strings not permitted in a Message of the Day (case sensitive)
[513]
Software Version
Login:
incorrect login
513]
Password:
ogin
hallenge
]
assword
ogin:
SAT cannot be executed on a
standby server
SAT
Logging off the System
For security, log off any time you leave your terminal. If you use terminal emulation software to
administer Communication Manager, log off the system and exit the emulation application
before switching to another software package.
Instructions
To log off:
1. Type logoff. Press Enter.
If the Facility Test Call or Remote Access features are administered, Alarm origination is
disabled, or if you have busied out resources or active minor or major alarms, a security
screen displays. You might want to take appropriate action (for example, disable these
features or address any alarms) before you log off.
If none of the above special circumstances exist, the system logs you off.
Figure 1: Logoff screen
Facility Test Call Administered
Remote Access Administered
Alarm Origination is currently disabled
Active major/minor alarm detected; be sure to resolve it
Proceed with Logoff? [n]
Issue 4.0 January 2008
31
32. System Basics
2. At the Proceed with Logoff prompt, type y to log off.
If you log off with alarm origination disabled and the system generates an alarm, Avaya
support services will not receive any notification of the alarm. For more information about
alarms, see the maintenance book for your system.
Administering User Profiles and Logins
Authentication, Authorization and Accounting (AAA) Services allows you to store and maintain
administrator account (login) information on a central server. Login authentication and access
authorization is administered on the central server.
For details on administering user profiles and logins, see "AAA Services" in Feature Description
and Implementation for Avaya Communication Manager, 555-245-205, and Maintenance
Commands for Avaya Communication Manager, 03-300431.
Establishing Daylight Savings Rules
Avaya Communication Manager allow you to set the daylight savings time rules so that
features, such as time-of-day routing and call detail recording (CDR), adjust automatically to
daylight savings time. The correct date and time ensure that CDR records are correct. You can
set daylight savings time rules to transition to and from daylight savings time outside of normal
business hours, so the number of affected CDR records is small.
You can set up 15 customized daylight savings time rules. This allows Communication Manager
administrators with servers in several different time zones to set up a rule for each. A daylight
savings time rule specifies the exact time when you want to transition to and from daylight
savings time. It also specifies the increment at which to transition (for example, 1 hour).
32 Administrator Guide for Avaya Communication Manager
33. Establishing Daylight Savings Rules
Instructions
Establishing daylight savings rules
To modify a daylight savings rule:
1. Type change daylight-savings-rules. Press Enter.
The Daylight Savings Rules screen appears.
Figure 2: Daylight Savings Rules screen
change daylight-savings-rules
DAYLIGHT SAVINGS RULES
Rule
Change Day
0:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Month
Date
Time____Increment
No Daylight Savings
1:
Page 1 of 2
2:
3:
4:
5:
6:
7:
first
first
first
first
first
first
first
first
first
first
first
first
first
first
_ Sunday_
_ Sunday_
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
on
on
on
on
on
on
on
on
on
on
on
on
on
on
or
or
or
or
or
or
or
or
or
or
or
or
or
or
after
after
after
after
after
after
after
after
after
after
after
after
after
after
_March
November
________
________
________
________
________
________
________
________
________
________
________
________
8_
1_
__
__
__
__
__
__
__
__
__
__
__
__
at
at
at
at
at
at
at
at
at
at
at
at
at
at
2:00_
2:00_
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
01:00__
Rule 1 applies to all time zones in the U.S. and begins on the first Sunday on or after March
8 at 2:00 a.m. with a 01:00 increment. Daylight Savings Time stops on the first Sunday on or
after November 1 at 2:00 a.m., also with a 01:00 increment (used as a decrement when
switching back to Standard time. This is the default.
The increment is added to standard time at the specified start time and the clock time shifts
by that increment (for example, for 01:59:00 to 01:59:59 the clock time shows 01:59 and at
02:00 the clock shows 03:00).
Issue 4.0 January 2008
33
34. System Basics
On the stop date, the increment is subtracted from the specified stop time (for example, for
01:59:00 to 01:59:59 the clock time shows 01:59 and at 02:00 the clock shows 01:00).
Note:
You cannot delete a daylight savings rule if it is in use on either the Locations or
Date and Time screens. However, you can change any rule except rule 0 (zero).
Note:
2. To add a Daylight Savings Time rule, complete the Start and Stop fields with the day,
month, date, and time you want the system clock to transition to Daylight Savings Time and
back to standard time.
3. Press Enter to save your changes.
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
Note:
Displaying daylight savings time rules
To display daylight savings time rules:
1. Type display daylight-savings-rules. Press Enter.
The Daylight Savings Rules screen appears. Verify the information you entered is correct.
Setting Time of Day Clock Synchronization
Time of Day Clock Synchronization enables a server to synchronize its internal clock to UTC
time provided by Internet time servers. Avaya uses the LINUX platform system clock connected
to an Internet time server to provide time synchronization. The interface for these systems is
web-based.
LINUX is used in:
●
Avaya S8XXX Server IP-PNC
●
Avaya S8XXX Server Fiber-PNC
●
Avaya S8XXX Server
Before you start:
●
A standard TCP/IP LAN connection is required to connect to the Internet time servers. If a
LAN connection is not available, time sync will be done by setting the platform clock
manually through the command line or web interface.
34 Administrator Guide for Avaya Communication Manager
35. Setting Time of Day Clock Synchronization
●
Note:
On the target server running Communication Manager, verify if Daylight Savings Time is
on.
Note:
These instructions are for Avaya DEFINITY CSI servers. For more information,
see Avaya Call Center Automatic Call Distribution (ACD) Guide, 07-600779.
To set Time of Day Clock Synchronization:
1. Activate the Avaya Site Administration screen.
2. Click the Fault & Performance tab.
The Fault & Performance icons display.
Figure 3: Avaya Site Administration menu
3. Click Time Synchronization.
The Time Synchronization - Properties screen displays.
Issue 4.0 January 2008
35
36. System Basics
Figure 4: Time Synchronization - Properties screen
4. Click in the Offset box.
The Plus and Minus radio buttons and the Hours and Minutes fields display.
5. Click Next.
The Time Synchronization - Properties screen displays.
36 Administrator Guide for Avaya Communication Manager
37. Setting Time of Day Clock Synchronization
Figure 5: Time Synchronization - Properties screen
6. Click Plus to add hours to the remote station (located to the west of the system time) or
click Minus to subtract hours to the remote station (located to the east of the system time).
7. In the hours field, enter the number of hours to be added or subtracted to synchronize with
the remote site.
8. Click Next.
The Time Synchronization - Schedule displays.
Issue 4.0 January 2008
37
38. System Basics
Figure 6: Time Synchronization - Schedule screen
9. Select either:
●
Run Now to run this program immediately and click Next.
●
Schedule this task to run and check the field below to determine if the default setting is
satisfactory. If this setting is not satisfactory, click Schedule.
The Scheduler screen displays.
38 Administrator Guide for Avaya Communication Manager
39. Setting Time of Day Clock Synchronization
Figure 7: Scheduler screen
10. In the Date field, highlight each object and use the pull-down menu to select the desired
setting.
11. In the Time field, highlight each item of time and use the pull-down menu to select the
desired time.
12. In the Recurrent Pattern area, select one radio button for the desired frequency. Notice
that each radio button is explained in the area to the immediate right.
13. If there are times to be included, set to the desired frequency.
14. Click OK.
The Time Synchronization - Schedule displays.
15. Click Next.
The Time Synchronization - Summary screen displays.
Issue 4.0 January 2008
39
40. System Basics
Figure 8: Time Synchronization - Summary screen
16. If the time synchronization description is satisfactory, click Finish.
If the time synchronization is not satisfactory, click Back and revise the necessary
information.
Note:
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
For more information about setting time synchronization, see Avaya Call Center Release 4.0
Automatic Call Distribution (ACD) Guide, 07-600779.
40 Administrator Guide for Avaya Communication Manager
41. Setting the System Date and Time
Setting the System Date and Time
Update the date and time for events such as a leap year, the change to or from daylight savings
time, or a system restart after a power failure. The correct date and time assure that Call Detail
Recording (CDR) records are correct. CDR does not work until the date and time have been
entered.
Note:
Note:
Changing the date and time can modify CDR data by 9 hours and 59 minutes.
Therefore, you should change the date and time after normal business hours.
After you change the date and time, review the time settings for any adjunct
(other than AUDIX) linked to your system that uses the system time.
Before you can set the date and time, you need to know whether it is currently daylight savings
or standard time and know which daylight savings rule number you want to use. Daylight
savings rule numbers are located on the Daylight Savings Rules screen.
In our example, we set the date and time to Tuesday, November 5, 2006 at 8:30 p.m. standard
time.
To set the system date and time:
1. Type set time. Press Enter.
The Date and Time screen displays.
Figure 9: Date and Time screen
set time
DATE AND TIME
DATE
Day of the Week: _______
Day of the Month: __
Month: ________
Year: ____
TIME
Hour: __ Minute: __
________________
Second: __
Type:
Daylight Savings Rule: _
WARNING: Changing the date or time may impact BCMS, CDR, SCHEDULED EVENTS,
and MEASUREMENTS
2. Complete the Date fields.
a. Type Tuesday in the Day of the Week field.
b. Type November in the Month field.
Issue 4.0 January 2008
41
42. System Basics
c. Type 5 in the Day of the Month field.
d. Type 2006 in the Year field.
3. Complete the Time fields.
Use the 24-hour clock to set the hour, so if the current time is 2:00 p.m., you enter 14:00.
You cannot update Second — it automatically resets to 0 when you save your changes.
a. Type 20 in the Hour field.
b. Type 30 in the Minute field (8:30 p.m.).
c. Type standard in the Type field.
d. Type 1 in the Daylight Savings Rule field.
4. Press Enter to save your changes.
Some display telephones might not automatically refresh the display when you change the
date or time. If this occurs, have each user press the date/time button on their telephone to
update the display.
Note:
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
Displaying the system date and time
To display the system date and time:
1. Type display time. Press Enter.
The Date and Time screen displays. Verify the information you entered is correct.
Related topics
See Establishing Daylight Savings Rules on page 32 for more information about setting system
time.
For additional information, see Avaya Call Center Release 4.0 Automatic Call Distribution
(ACD) Guide, 07-600779.
42 Administrator Guide for Avaya Communication Manager
43. Using the Bulletin Board
Using the Bulletin Board
Avaya Communication Manager allows you to post information to a bulletin board. You can also
display and print messages from other Avaya server administrators and Avaya personnel using
the bulletin board. Anyone with the appropriate permissions can use the bulletin board for
messages. Only one user can post or change a message at a time.
Whenever you log in, the system alerts you if you have any messages on the bulletin board and
the date of the latest message. Also, if Avaya personnel post high-priority messages while you
are logged in, you receive notification the next time you enter a command. This notification
disappears after you enter another command and reoccurs at login until deleted by Avaya
personnel.
You maintain the bulletin board by deleting messages you have already read. You cannot delete
high-priority messages. If the bulletin board is at 80% or more capacity, a message appears at
login indicating how much of its capacity is currently used (for example, 84%). If the bulletin
board reaches maximum capacity, new messages overwrite the oldest messages.
Note:
Note:
The bulletin board does not lose information during a system reset at level 1 or
level 2. If you save translations, the information can be restored if a system reset
occurs at levels 3, 4, or 5.
Instructions
Displaying messages
To display the bulletin board:
1. Type display bulletin-board. Press Enter.
The Bulletin Board screen displays.
Issue 4.0 January 2008
43
44. System Basics
Figure 10: Bulletin Board screen
display bulletin-board
Message (* indicates high-priority)
*Avaya is in the process of
*investigating your trunk lockup problem.
*The Bulletin Board will be updated as
*we find information.
* We have identified the problem.
*The trunk you added does not provide
*disconnect supervision. However, the
*trunk group was administered as such.
*Please call Pat J. for details.
We recently added a new trunk group (14)
and have had many of the members getting
locked up.
We see the error - thanks for checking.
Page 1 of 3
Date
03/02/93
03/02/93
03/02/93
03/02/93
03/04/93
03/04/93
03/04/93
03/04/93
03/04/93
03/02/93
03/02/93
03/02/93
03/05/93
Posting a message
In our example, we post a message to the bulletin board about a problem with a new trunk
group, and an Avaya representative replies to our message.
To post a message to the bulletin board:
1. Type change bulletin-board. Press Enter.
The Bulletin Board screen displays. There are three pages of message space within the
bulletin board. The first page has 19 lines, but you can only enter text on lines 11-19. The
first 10 lines on page 1 are for high-priority messages from Avaya personnel and are noted
with an asterisk (*). The second and third pages each have 20 lines, and you can enter text
on any line. The system automatically enters the date the message was posted or last
changed to the right of each message line.
2. Type your message.
You can enter up to 40 characters of text per line. You also can enter one blank line. If you
enter more than one blank line, the system consolidates them and displays only one. The
system also deletes any blank line if it is line one of any page. You cannot indent text on the
bulletin board. The Tab key moves the cursor to the next line.
3. Press Enter to save your changes.
44 Administrator Guide for Avaya Communication Manager
45. Saving Translations
Deleting messages
To delete a message from the bulletin board:
1. Type change bulletin-board. Press Enter.
The Bulletin Board screen appears.
2. Enter a space as the first character on each line of the message you want to delete. Press
Enter.
3. Press Enter to save your changes.
Saving Translations
Communication Manager retains all translation data in memory while the system is operating. If
it goes down, you lose all this translation data. You must save in-memory translation data to the
memory card (flash ROM), disk, or tape. Saving translation data to memory card or tape is the
same as backing up your system.
Note:
Note:
Save translations on a daily basis. You might want to save translations after
business hours to prevent dial tone delays or during slow business hours if your
business is open 24 hours.
The save translation command writes two time-stamped identical copies of the translation
data to the selected memory card, disk, or tape. The save writes one complete copy first, then
writes the second copy in a different area of the device — both with the same time-stamp.
Failure during a save, including a system crash, usually affects only one copy. The affected
copy is marked "bad" and should not be used for backup.
You can set save translation to be completed automatically as part of regularly scheduled
maintenance or manually, as needed. For more information about saving translations
automatically, see the maintenance book for your system.
Tip:
Tip:
To determine if your system saves translations automatically, type display
system-parameters maintenance to see if you have scheduled
maintenance.
Translation copy protection assigns a number to a specific telephone system and to the flash
card or set of flash cards that belong to that system. For Avaya Communication Manager on a
DEFINITY Server CSI, this number is the same on both the translation storage device (flash
card) and the Flash PROM (Programmable Read Only Memory) of the processor circuit pack. In
a duplicated system, the Flash PROM of each processor circuit pack has a translation ID and
both ID’s are stored on the memory card.
Issue 4.0 January 2008
45
46. System Basics
An attempt to initialize (boot) the system with translations that do not contain the same
identification number as stored in the processor circuit pack raises a major alarm and disables
access to the save translations command for all non-Avaya logins. You also receive a
warning message on the copyright screen notifying you of the mismatch. Contact your Avaya
representative to correct this mismatch and reset the save translations command. You
must correct the mismatch before the end of the specified grace period, otherwise you cannot
access system management commands (such as: add, change, remove, and duplicate) that
modify translation data. Avaya specifies the grace period during a system installation or
following an upgrade.
Before you start
If you are saving translations to a memory card or tape, you must verify the memory card or
tape is in place and clear any active alarms from the alarms panel.
If you have Avaya Communication Manager on a DEFINITY Server CSI, verify the memory card
translation ID matches the translation ID of your server’s Flash PROM.
Instructions
In our example, we save translations to the tapes on both processor A and B.
To save translations manually:
1. Type save translation both tape. Press Enter.
The save process can take up to 10 minutes. You cannot administer your system while the
save is in process. The Save Translation screen displays.
Figure 11: Save Translation screen
SAVE TRANSLATION
Processor
SPE_A
SPE_B
Command Completion Status
Success
Success
Error Code
0
0
2. If there is an error message in the Command Completion Status field and an error code in
the Error Code field, clear the error and repeat the save process.
46 Administrator Guide for Avaya Communication Manager
47. Performing Backups
More information
When mass storage system (MSS) devices on both processors in a duplex system are
specified, translation data is saved from the active processor to the active and standby MSS
devices at the same time. If the save to one device fails or one device is out of service, the other
save continues. You receive the status of each save separately.
Note:
Note:
If you have a duplex system and you save translation data to both MSS devices
one at a time, translation data inconsistencies between the two devices can
occur.
Fixing problems
Note:
Note:
You cannot see whether the translation ID on the flash card corresponds to the
number on the Processor circuit packs. However, if the numbers do not match,
the system issues an error message when you attempt a save translation
operation.
When failures occur, the system responds with the following error codes.
Problem
Possible causes
Solution
1
Save translation cannot
write to the active drive.
Repeat the save translation
process for the active drive.
2
Save translation cannot
write to the standby drive.
Repeat the save translation
process for the standby drive.
For more information about error messages and how to correct them, or backing up or restoring
your system, see the maintenance book for your system.
Performing Backups
Information on performing backups to your system can be found in the Maintenance Procedures
for Avaya Communication Manager, Media Gateways and Servers, 03-300432.
Issue 4.0 January 2008
47
49. Chapter 2: Planning the System
Understanding Your Configuration
At a very basic level, Avaya Communication Manager consists of hardware to perform call
processing, and the software to make it run. You use the administration interface to let the
system know what hardware you have, where it is located, and what you want the software to
do with it.
You can find out which circuit packs are in the system and which ports are available by entering
the command list configuration all. There are variations on this command that display
different types of configuration information. Use the help function to experiment, and see which
command works for you.
To view a list of port boards on your system:
1. Type list configuration port-network. Press Enter.
The System Configuration screen appears.
Figure 12: System Configuration screen
SYSTEM CONFIGURATION
Board
Number
Board Type Code
Vintage
Assigned Ports
u=unassigned t=tti p=psa
01A05
01A06
01B05
DIGITAL LINE
ANALOG LINE
ANALOG LINE
TN754B 000002
TN742 000010
TN746B 000008
01C04
ANALOG LINE
TN746B 000008
01C05
DIGITAL LINE
TN2224 000004
01C06
01C10
HYBRID LINE
DIGITAL LINE
TN762B 000004
TN754 000004
01
01
u
u
u
u
01
u
u
01
u
u
02
u
u
u
u
u
u
u
02
u
03
03
u
u
u
u
u
u
u
u
u
u
04
u
u
u
u
04
u
u
u
u
05
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
07
u
u
u
u
u
07
u
u
u
u
08
u
u
u
u
u
08
u
u
u
u
The System Configuration screen shows all the boards on your system that are available for
connecting telephones, trunks, data modules and other equipment. You can see the board
number, board type, circuit-pack type, and status of each board’s ports. The u entries on this
screen indicate unused ports that are available for you to administer. These might also appear
as p or t, depending on settings in your system.
Issue 4.0 January 2008
49
50. Planning the System
You will find many places in the administration interface where you are asked to enter a port or
slot. The port or slot is actually an address that describes the physical location of the equipment
you are using.
A port address is made up of four parts:
●
cabinet — the main housing for all the server equipment. Cabinets are numbered starting
with 01.
●
carrier — the rack within the cabinet that holds a row of circuit packs. Each carrier within a
cabinet has a letter, A to E.
●
slot — the space in the carrier that holds an individual circuit pack. Slots are numbered
01-16.
●
port — the wire that is connected to an individual piece of equipment (such as a telephone
or data module). The number of ports on a circuit pack varies depending on the type.
So, if you have a single-carrier cabinet, the circuit pack in slot 06 would have the address
01A06. If you want to attach a telephone to the 3rd port on this board, the port address is
01A0603 (01=cabinet, A=carrier, 06=slot, 03=port).
50 Administrator Guide for Avaya Communication Manager
51. Understanding the Dial Plan
Understanding the Dial Plan
Your dial plan tells your system how to interpret dialed digits. For example, if you dial 9 on your
system to access an outside line, it is actually the dial plan that tells the system to find an
external trunk when a dialed string begins with a 9.
The dial plan also tells the system how many digits to expect for certain calls. For example, the
dial plan might indicate that all internal extensions are 4-digit numbers that start with 1 or 2.
Let us take a look at an example dial plan so you’ll know how to read your system’s dial plan.
The following figure shows an example of a simple dial plan.
Figure 13: Dial Plan Analysis Table screen
display dialplan analysis
Page 1 of x
DIAL PLAN ANALYSIS TABLE
Location: All
Dialed
String
00
1
2
3
3
4
4
5
5
6
7210
8
9
*
#
Total
Length
2
3
4
5
1
1
5
5
7
5
7
7
1
3
3
Call
Type
attd
dac
ext
ext
aar
ars
ext
ext
ext
ext
ext
ext
fac
fac
fac
Dialed
String
Percent Full: 7
Total Call
Length Type
Dialed
String
Total Call
Length Type
The Dial Plan Analysis Table defines the dialing plan for your system.
Note:
Note:
In Communication Manager 5.0 and later, you can administer dial plans
per-location. Typing the command change dialplan analysis displays the
all-locations Dial Plan Analysis screen. To access a per-location screen, type
change dialplan analysis location n, where n represents the number
of a specific location. For details on command options, see online help, or
Maintenance Commands for Avaya Communication Manager, Media Gateways
and Servers, 03-300431.
Issue 4.0 January 2008
51
52. Planning the System
The Call Type column in the Dial Plan Analysis Table indicates what the system does when a
user dials the digit or digits indicated in the Dialed String column. The Total Length column
indicates how long the dialed string will be for each type of call. For example, this dial plan
shows that when users dial a 5-digit number that starts with 3, they are dialing an extension.
The Dial Plan Analysis Table in our example contains the following call types:
●
Attendant (attd) — Defines how users call an attendant. Attendant access numbers can be
any number from 0 to 9 and contain 1 or 2 digits.
In our example figure, the system calls an attendant when users dial 00.
●
Dial access code — Allows you to use trunk access codes (TAC) and feature access
codes (FAC) in the same range. For example, you could define the group 100 to 199,
which would allow both FAC and TAC in that range. Dial access codes can start with any
number from 1 to 9, * and #, and contain up to 4 digits.
In our example figure, dial access codes begin with 1 and must be 3 digits long.
Note:
The Dial Plan Analysis Table does not allow you to enter a range specifically for
trunk access codes. However, the Trunk Group screen still allows you to assign
a TAC to a trunk group. The TAC you enter on the Trunk Group screen must
match the format you have administered for a DAC on the Dial Plan Analysis
Table.
Note:
●
Extensions (ext) — Defines extension ranges that can be used on your system. In our
figure, extensions must be in the ranges 30000 to 39999, 40000 to 49999 and 50000 to
59999.
●
Feature access codes (fac) only — FAC can be any number from 1 to 9 and contain up to
4 digits. You can use * or #, but only as a first digit. In our example, feature access codes
can begin with * or # and are 3-digits long.
The Dial Plan Analysis Table works with the Dial Plan Parameters Table for fully defining
your dial plan. The Dial Plan Parameters Table allows you to set system-wide parameters for
your dial plan, or to define a Dial Plan Parameters Table per-location.
Displaying your dial plan
You might want to take this opportunity to look at and interpret your own dial plan. To display
your system’s dial plan:
1. Type display dialplan analysis or display dialplan analysis location
n, where n represents the number of a specific location. Press Enter.
52 Administrator Guide for Avaya Communication Manager
53. Understanding the Dial Plan
Modifying your dial plan
It is easy to make changes to your dial plan. For example, we will add a new range of dial
access codes to the dial plan. We want to be able to assign both FAC and TAC in the 700 to 799
range.
1. Type change dialplan analysis or change dialplan analysis location n,
where n represents the number of a specific location. Press Enter.
The Dial Plan Analysis Table screen appears.
2. Move the cursor to an empty row.
3. Type 7 in the Dialed String column. Press Tab to move to the next field.
4. Type 3 in the Total Length column. Press Tab to move to the next field.
5. Type dac in the Call Type column.
6. Press Enter to save your changes.
Adding extension ranges
You might find that as your needs grow you want a new set of extensions. Before you can
assign a station to an extension, the extension must belong to a range that is defined in the dial
plan. We will add a new set of extensions that start with 3 and are 4 digits long (3000 to 3999).
To add this set of extensions to the dial plan:
1. Type change dialplan analysis or change dialplan analysis location n,
where n represents the number of a specific location. Press Enter.
The Dial Plan Analysis Table screen appears.
2. Move the cursor to an empty row.
3. Type 3 in the Dialed String column. Press Tab to move to the next field.
4. Type 4 in the Total Length column. Press Tab to move to the next field.
5. Type ext in the Call Type column.
6. Press Enter to save your changes.
Administering a Uniform Dial Plan
You can set up a Uniform Dialing Plan that can be shared among a group of servers. For more
information, see Feature Description and Implementation for Avaya Communication Manager,
555-245-205.
Issue 4.0 January 2008
53
54. Planning the System
Administering a Multi-Location Dial Plan
When a customer migrates from a multiple independent node network to a single distributed
server whose gateways are distributed across a data network, it might initially appear as if some
dial plan functions are no longer available.
The multi-location dial plan feature preserves dial plan uniqueness for extensions and
attendants that were provided in a multiple independent node network, but appear to be
unavailable when customers migrate to a single distributed server. This feature is available
beginning with Communication Manager, release 2.0.
For example, in a department store with many locations, each location might have had its own
switch with a multiple independent node network. The same extension could be used to
represent a unique department in all stores (extension 123 might be the luggage department). If
the customer migrates to a single distributed server, a user could no longer dial 123 to get the
luggage department in their store. The user would have to dial the complete extension to
connect to the proper department.
Instead of having to dial a complete extension, the multi-location dial plan feature allows a user
to dial a shorter version of the extension. For example, a customer can continue to dial 123
instead of having to dial 222-123.
Communication Manager takes leading digits of the location prefix and adds some or all of its
leading digits (specified on the Uniform Dial Plan screen) to the front of the dialed number. The
switch then analyzes the entire dialed string and routes the call based on the administration on
the Dial Plan Parameters and Dial Plan Analysis screens.
Note:
Before you can administer the multi-location dial plan feature, the Multiple
Locations field on the System Parameters Customer-Options (Optional
Features) screen must be enabled. To check if this is enabled, use the display
system-parameters customer-options command. The Multiple
Locations field is on page 3 of the System Parameters Customer-Options
(Optional Features) screen. Ensure that the field is set to y.
Note:
Prepending the location prefix to dialed numbers
Use the Insert Digits field on the Uniform Dial Plan Table screen to assign the location prefix
from the caller’s location on the Locations screen. The system adds some or all of its leading
digits (specified on the Uniform Dial Plan screen) to the front of the dialed number. The switch
then analyzes the entire dialed string and routes the call based on the administration on the Dial
Plan Parameters screen.
●
Non-IP telephones and trunks inherit the location number of the hardware they are
connected to (for example, the cabinet, remote office, or media gateway).
●
IP telephones indirectly obtain their location number.
54 Administrator Guide for Avaya Communication Manager