This document provides a high-level overview and introduction of the Avaya IP Office unified communications platform. It describes the various editions available from Basic to Server Edition, the hardware and software components, and reference configurations. Licensing and deployment options are also summarized. The document is intended to familiarize technical persons with the IP Office solution.
Avaya Aura® Session Border Controller, powered by Acme Packet, secures the IP border for the real time interactive communications that flow outside your internal network. With Avaya Aura® Session Border Controller, your Unified Communications and Contact Center Solutions can securely leverage SIP, while simultaneously extending the power of the Avaya Aura® architecture throughout your enterprise to realize the true benefits of open standards.
Join us for an introductory webinar on VoIP and learn:
- The fundamental principles of VoIP including RTP and SIP
- What voice metrics to measure and why they matter
- The different methods to monitor and troubleshoot VoIP
Avaya Aura® Session Border Controller, powered by Acme Packet, secures the IP border for the real time interactive communications that flow outside your internal network. With Avaya Aura® Session Border Controller, your Unified Communications and Contact Center Solutions can securely leverage SIP, while simultaneously extending the power of the Avaya Aura® architecture throughout your enterprise to realize the true benefits of open standards.
Join us for an introductory webinar on VoIP and learn:
- The fundamental principles of VoIP including RTP and SIP
- What voice metrics to measure and why they matter
- The different methods to monitor and troubleshoot VoIP
It is a concern for many call centers to choose the right Cisco platform for optimum performance. This ppt will help you better understand the difference between UCCE, PCCE, and UCCX basis the agent headcount, and other functionalities.
Over the past 10 years the Session Initiation Protocol (SIP) has moved from the toy of researchers and academics to the de-facto standard for telephony and multimedia services in mobile and fixed networks.
Probably one of the most emotionally fraught discussions in the context of SIP was whether Session Border Controllers (SBC) are good or evil.
SIP was designed with the vision of revolutionizing the way communication services are developed, deployed and operated. Following the end-to-end spirit of the Internet SIP was supposed to turn down the walled gardens of PSTN networks and free communication services from the grip of large telecom operators. By moving the intelligence to the end systems, developers were supposed to be able to develop new communication services that will innovate the way we communicate with each other.
This was to be achieved without having to wait for the approval of the various telecommunication standardization groups such as ETSI or the support of incumbent telecoms.
Session border controllers are usually implemented as SIP Back-to-Back User Agents (B2BUA) that are placed between a SIP user agent and a SIP proxy. The SBC then acts as the contact point for both the user agents and the proxy. Thereby the SBC actually breaks the end-to-end behavior of SIP, which has led various people to deem the SBC as an evil incarnation of the old telecom way of thinking. Regardless of this opposition, SBCs have become a central part of any SIP deployment.
In this paper we will first give a brief overview of how SIP works and continue with a description of what SBCs do and the different use cases for deploying SBCs.
SSDN Technologies is Microsoft partner training institute of MCSA Windows server 2012 in Gurgaon, Delhi. We also provide mcsa windows server 410 lesson training by certified trainers in India.
It is a concern for many call centers to choose the right Cisco platform for optimum performance. This ppt will help you better understand the difference between UCCE, PCCE, and UCCX basis the agent headcount, and other functionalities.
Over the past 10 years the Session Initiation Protocol (SIP) has moved from the toy of researchers and academics to the de-facto standard for telephony and multimedia services in mobile and fixed networks.
Probably one of the most emotionally fraught discussions in the context of SIP was whether Session Border Controllers (SBC) are good or evil.
SIP was designed with the vision of revolutionizing the way communication services are developed, deployed and operated. Following the end-to-end spirit of the Internet SIP was supposed to turn down the walled gardens of PSTN networks and free communication services from the grip of large telecom operators. By moving the intelligence to the end systems, developers were supposed to be able to develop new communication services that will innovate the way we communicate with each other.
This was to be achieved without having to wait for the approval of the various telecommunication standardization groups such as ETSI or the support of incumbent telecoms.
Session border controllers are usually implemented as SIP Back-to-Back User Agents (B2BUA) that are placed between a SIP user agent and a SIP proxy. The SBC then acts as the contact point for both the user agents and the proxy. Thereby the SBC actually breaks the end-to-end behavior of SIP, which has led various people to deem the SBC as an evil incarnation of the old telecom way of thinking. Regardless of this opposition, SBCs have become a central part of any SIP deployment.
In this paper we will first give a brief overview of how SIP works and continue with a description of what SBCs do and the different use cases for deploying SBCs.
SSDN Technologies is Microsoft partner training institute of MCSA Windows server 2012 in Gurgaon, Delhi. We also provide mcsa windows server 410 lesson training by certified trainers in India.
Hosted IP offers flexible and affordable solutions over a fully managed IP network for complete data and voice integration, requiring minimal capital costs and limited IT support.
As a network-based hosted IP-PBX solution for enterprises, Hosted IP delivers all call processing, intelligence, and voicemail functionality over MPLS with full end-to-end Quality of Service (QoS).
Our technology experts will manage it all so you don’t have to – all backed by our unmatched service and support
Advantech is offering a complete modular series of Automation Panel from Industrial Monitor up to Control panel . In this presentation you will understand the unique advantaged making TPC-5000 enabler of the next generation of your machine.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
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.
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!
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
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
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Avaya ip office beginners training
1. AVAYA IP OFFICE
Beginners Training
Shashank Kapil
Shashank.kapil@gmail.com
Abstract
This document is prepared of introduce skilled technical persons to
Avaya IP Office unified communication solution
2. Avaya IP Office Beginners Training
Table of Contents
1 Avaya IP Office Platform Solution Description................................................................................3
1.1 Introduction ............................................................................................................................3
1.2 Avaya IP Office Platform Overview.........................................................................................3
1.2.1 IP Office editions.............................................................................................................3
1.2.2 Components....................................................................................................................4
1.3 Solution Specification..............................................................................................................8
1.3.1 Reference configuration .................................................................................................8
1.3.2 Hardware and software options ...................................................................................10
1.3.3 Licenses.........................................................................................................................11
2 Avaya IP Office Platform Feature Description ..............................................................................12
2.1 Features ................................................................................................................................12
2.1.1 Call handling features ...................................................................................................12
2.1.2 IP telephony features....................................................................................................12
2.1.3 Messaging features.......................................................................................................13
2.1.4 Mobility features...........................................................................................................13
2.1.5 Contact Centre features (short introduction)...............................................................14
2.2 Applications...........................................................................................................................15
2.2.1 IP office manager ..........................................................................................................15
2.2.2 Web manager................................................................................................................15
2.2.3 SysMonitor....................................................................................................................15
3 Avaya IP Office Administration and Maintenance........................................................................16
3.1 Manager Modes..........................................................................................................................16
3.1.1 Security Configuration Mode...............................................................................................16
3.1.2 Small Community Network Management ...........................................................................17
3.1.3 Embedded File Management...............................................................................................17
3.1.4 Upgrade Wizard ...................................................................................................................17
3.2 Configuration Mode Field Descriptions ......................................................................................17
3.2.1 System..................................................................................................................................18
3.2.2 Line.......................................................................................................................................18
3.2.3 Extension..............................................................................................................................18
3.2.3 User......................................................................................................................................18
3.2.3 Group ...................................................................................................................................18
3. 3.2.4 Short Code............................................................................................................................19
3.2.5 Incoming Call Route .............................................................................................................20
3.2.6 IP Routes ..............................................................................................................................20
3.2.7 License..................................................................................................................................20
3.2.8 User Rights ...........................................................................................................................21
3.2.9 ARS .......................................................................................................................................21
3.3 Avaya IP Office Maintenance......................................................................................................22
3.3.1 System Status.......................................................................................................................22
3.3.2 System Monitor....................................................................................................................23
4 Deploying Avaya IP Office ..................................................................................................................24
4.1 Deploying Avaya IP Office server edition....................................................................................24
4.1.1 Installing IP Office Server Edition.........................................................................................24
4.1.2 Default parameters..............................................................................................................24
4.1.3 Configuring IP Office Server Edition using the ignition process...........................................25
4.2 Deploying ip500v2 ......................................................................................................................34
4.3 Installing the IP Office Anywhere Demonstration Software.......................................................35
4. 1 Avaya IP Office Platform Solution Description
This document describes IP Office from a holistic perspective focusing on the strategic, enterprise,
and functional views of the architecture.
1.1 Introduction
This document includes a high-level description of solution specifications and available reference
configurations.
1.2 Avaya IP Office Platform Overview
IP Office is an integrated, modular communications solution that scales up to 3000 extensions and
150 sites in a multisite network with resiliency. Match a deployment model to infrastructure needs
from simple appliances to virtualized software in a data center with options in between.
1.2.1 IP Office editions
IP Office is available in many deployment models based on the size of the enterprise and the
features required using one or all the following elements:
• Virtualized IP Office software running in a virtual machine
• Dedicated server
• IP Office 500 version 2 (IP500 V2) control unit
Edition Platform
Business size
(users) Addresses business needs
Basic Edition IP500 V2 Less than 25
Simple telephony and messaging capabilities
only
Essential Edition IP500 V2 20–99
Simple telephony and messaging capabilities
plus IP telephony with essential mobility
Preferred Edition IP500 V2 21–250
Essential Edition capabilities plus unified
communications with preferred mobility
Server Edition
Linux Server/IP500
V2 and Linux
Expansion 100 — 2000
Essential Edition capabilities plus unified
communications with preferred mobility
Server Edition Select
Linux Server/IP500
V2 and Linux
Expansion 100 — 3000
Essential Edition capabilities plus unified
communications with preferred mobility
Server Edition or Server
Edition Select with
Virtualized Software Virtualized
100 — 2000 (or)
100 — 3000
Essential Edition capabilities plus unified
communications with preferred mobility
Server Edition or Server
Edition Select hosted in
Cloud Cloud
100–2000 (or)
100–3000
Essential Edition capabilities plus unified
communications with preferred mobility
IP Office Essential and Preferred editions are also referred to as IP Office Standard Mode. Each
edition builds upon the next to offer additional functionality.
5. 1.2.2 Components
i. IP Office control unit
IP Office control unit (IP500 V2) is a stackable unit with an optional 19" rack mounting kit and an
optional wall mounting kit for smaller configurations.
The IP500 V2 control unit is compatible with all IP500 base extension and Voice Compression
Module (VCM) cards as well as all external IP500 expansion modules.
The IP500 V2 control unit has 4 slots for the insertion of IP500 base cards. The slots are numbered 1
to 4 from left to right. Normally they can be used in any order, however if the capacity for a
particular type of card is exceeded, the card in the rightmost slot will be disabled. Each base card
includes an integral front panel with ports for cable connections.
6. ii. Base cards
IP500 V2 base cards
Base card
Maximum
per
system
RJ45 port assignment description
Digital Station
(DS8)
3
Ports 1–8: Digital stations
With trunk card:
Ports 9–12: Central Office lines
Analogue Phone 2 4
Ports 1–2: Analog station
With trunk card:
Ports 9–12: Trunk connections
Analogue Phone 8 4
Ports 1–8: Analog station
With trunk card:
Ports 9–12: Trunk connections
Digital Station
(TCM8)
4
Ports 1–8: BST digital station
With trunk card:
Ports 9–12: Central Office lines
Voice Compression
module (VCM V2)
2
Ports 1–8: Not present
With trunk card:
Ports 9–12: Central Office lines
ATM Combination
(ATM V2)
2
Ports 1–6: Digital stations
Ports 7–8: Analog stations
Ports 9–12: Central Office lines
10 voice compression channels. Codec support is G.711, G729a and G.723
with 64ms echo cancellation. G.722 is supported by release 8.0 and higher.
BRI Combination 2
Ports 1–6: Digital stations
Ports 7–8: Analog stations
Ports 9–10: BRI trunk ports (4 BRI channels)
10 voice compression channels. Codec support is G.711, G729a and G.723
with 64ms echo cancellation. G.722 is supported by IP Office Release 8.0
and higher.
Unified
Communications
Module (UCM V2)
1
Requires separate Preferred Edition license.
Not supported on Server Edition.
ETR6 3
Ports 1–6: ETR stations
With ATM4:
Ports 7–8: Power Failure Transfer
Ports 9–12: Central Office lines
(Not supported on Server Edition)
7. iii. Trunk cards
Trunk cards can be fitted to existing base cards to provide support for trunk ports. The trunk cards
uses the ports provided on the base card for cable connection.
These cards are used for PSTN/FXS gateways with IP Office for Linux.
IP500 V2 trunk cards
Trunk Card Maximum per system Work with these base cards
Analog (V2) 4
ETR6
DS8
TCM8
Analog Phone 2/8
Universal PRI (PRI-U) 4
ETR6
DS8
TCM8
Analog Phone 2/8
VCM
BRI (Euro ISDN) 4
DS8
TCM8
Analog Phone 2/8
VCM
iv. External expansion modules
External expansion modules can be used with the IP500 V2 control unit.
Analog phone expansion modules
Expansion module Telephones supported
Analog Phone 16
16 analogue stations with calling line
presentation
Analog Phone 30
30 analogue stations with calling line
presentation
Digital station expansion modules
Expansion module Description
DS16A 16 digital station ports
DS30A 30 digital station ports
DS16B, DS16B2
16 digital station ports
(Avaya phones only)
DS30B, DS30B2
30 digital station ports
(Avaya phones only)
8. Analog trunk modules
This type of module can be used to add 16 additional analogue trunks to an IP500 V2 system. The
module supports both loop-start and ground-start trunks.
Expansion module Description
ATM16 16 analogue trunks
v. Application server
The IP Office Application Server provides reliability, scalability and processing power for larger scale
IP Office deployments. It is an external, rack mounted server that provides scalability for larger
installations and multisite deployments not currently supported with the Unified Communications
Module (UCM V2).
The IP Office Application Server is a single installation of selected IP Office™ Platform applications
running on Linux.
The IP Office Application Server hosts the following applications:
• Management Services
• one-X Portal for IP Office
• Voicemail Pro
• Web License Manager (WebLM)
• Web Manager
• Optional Services
- Integrated Contact Reporter
- Media Manager
- Web Collaboration
- Contact Recorder for IP Office
- WebRTC Gateway
9. 1.3 Solution Specification
IP Office is sold in different editions, reference configurations, and deployment scenarios to meet
different customer requirements. The editions build on one another to offer advanced functionality,
including presence, instant messaging, web collaboration, and Microsoft software integration.
1.3.1 Reference configuration
The following sections summarize IP Office editions and other configuration options.
I. IP Office Basic Edition
IP Office Basic Edition is intended for small and growing enterprises.
IP Office Basic Edition provides basic telephony features such as:
• 64 trunk capacity: analog, PRI/T1, and SIP
• Key system operation
• 64 party conferencing capacity
• Automated Attendant
• Multiple language support
• Call forwarding
• Caller ID
• Dial by name
• Breakout to reception
• Integrated voicemail:
- Maximum of 6 concurrent calls to voicemail with approximately 25 hours of storage
- Message control including Save, Delete, Forward, Repeat, Rewind, Fast Forward, and
Skip Message
- Visual voicemail
- Message time and date stamping
Modes of operation
IP500V2 control units are supplied with no installed firmware or configuration. When first powered
up, the control unit loads and installs the necessary firmware from the system SD card installed in it.
It creates a default configuration matching the card installed in the control unit and external
expansion modules attached to it.
Mode SD Card
IP Office Basic Edition Quick mode
a-law telephony PBX system operation
μ-law telephony key system operation
IP Office Basic Edition - PARTNER Mode Defaults to a-law telephony PARTNER mode operation
IP Office Basic Edition - NORSTAR Mode Defaults to μ-law telephony NORSTAR mode operation
Basic Edition runs on the IP500V2 control unit. An SD is required and is installed in the rear of the
control unit, providing operating software, feature keys, and licenses. An optional SD card can be
installed in the optional SD card slot, providing redundant backup and system upgrade capabilities.
II. IP Office Essential Edition
• IP Office Essential Edition provides the same features as Basic Edition as well as the
following:
• Mobile call control with one number access and simultaneous ringing on mobile devices
• Up to 4 remote workers through an internet connection and an Avaya 9600 series IP phone
• 24-hour access with customized voicemail greetings for each staff member
• Voicemail:
10. - Maximum of 6 concurrent calls to voicemail
- Send voicemails to email
- Up to 25 hours of voicemail storage (with 6 ports)
- Up to 40 automated attendants with a maximum of 6 concurrent calls
• Multiple language support
• Up to 128 party audio conference bridge with 64 in any one conference
III. IP Office Preferred Edition
IP Office Preferred Edition provides intelligent call routing, messaging, call handling and application
integration.
In addition to the features provided with Essential Edition, IP Office Preferred Edition provides the
following:
• Scalable voicemail:
- Up to 40 simultaneous calls
- Send a voicemail to all employees, a department, or a team
- Address messages by extension or by name
- Voicemail messages can “find” users to alert them a message is waiting
• Secure conferencing for up to 128 parties with 64 per conference
• Automated call routing with an unlimited number of automatic attendants that can be
customized for time of day, day of week or other variables as well as to recognize callers and
deliver personalized messages
• Call recording for incoming and outgoing calls that can be sent to voicemail or email inboxes
as WAV files
IV. IP Office Server Edition
IP Office Server Edition provides IP Office telephony capabilities, unified communications, mobility,
and collaboration. It also provides high availability, IP Office Server Edition supports up to 150 sites,
3000 users, and comprehensive resilience.
IP Office Server Edition Solution provides the following:
• A single Server Edition Primary server provides IP Office, Voicemail Pro, and Avaya one-X®
Portal for IP Office
• A Server Edition Secondary server increases the capacity and provide resilience
• Expansion systems, which provide additional capacity, support analogue or digital interfaces,
and remote locations
• A Select IP Office Server Edition Solution provides additional capacity
• Support for an existing IP500 V2 control unit optimized for a hybrid of analog/TDM and IP
deployments, or a Linux server optimized for IP only deployments
• Users and extensions can be configured on the IP Office Server Edition server or the Server
Edition Expansion System
• Software distribution includes the various user and administration applications such as IP
Office Manager, SSA, Voicemail Pro, and IP Office SoftConsole
• Components can be in the same location or in different locations
• Optionally configure a separate application server dedicated to Avaya one-X® Portal to
provide more user capacity than the Server Edition Primary supports
• Add additional servers and expansion systems any time
V. Topology
IP Office Server Edition is based on a double star network topology that provides comprehensive
features and their management, enables ease of use, installation, and administration. The overall
solution provides a flexible and modular architecture starting with a single server and you can scale
11. up the number of users and locations by networking multiple servers. The components automatically
act as a single logical unit and you can administer the components from a single console through an
integrated management system.
1.3.2 Hardware and software options
I. Hardware options
Server, base card, trunk card, and expansion module hardware options are available depending on
the edition required:
• Dell PowerEdge™ R210 or R620
• Hewlett Packard ProLiant DL120 G7 or DL360 G7
• Avaya IP500 V2
II. Software options
IP Office acts as a server for a variety of applications, including:
• Avaya Communicator for IP Office supported on Windows and iPad devices
• Avaya one-X Mobile for IP Office
• Avaya one-X Portal for IP Office
• Lync Integration for IP Office
• IP Office SoftConsole
• Contact Recorder for IP Office
IP Office can also be deployed with other components. You can deploy IP Office with Radvision or
other video endpoints. You can also use IP Office Branch solution offer to connect IP Office branches
to the Avaya Aura® infrastructure, allowing users to leverage core Avaya Aura applications and
services including centralized dial plans, voice mail, management, and licensing.
12. 1.3.3 Licenses
Many solutions, applications, and features on IP Office systems are licensed and only operate when
a valid license is detected. This includes features within IP Office applications connected to the IP
Office system.
Ports, channels, and users
Some licenses enable a number of ports, channels, or users. Depending on the particular license,
each supported instance can be consumed either when it is configured for use or when it is actually
being used. When no further instances of a license are available, further use of the licensed feature
is not allowed.
Multiple licenses can be added to give a higher number of supported ports, channels, or users.
However, licenses above the capacity supported by the particular IP Office control unit will not work.
PLDS licensing
IP Office uses the Avaya Product Licensing and Delivery System (PLDS) to manage licenses. PLDS is an
online, web-based tool for managing license entitlements and electronic delivery of software and
related license files.
PLDS license files
Licenses are delivered from PLDS with license files. A PLDS license file is generated for installing on a
specific machine. There are two deployment options:
• PLDS Nodal license files are generated for and installed on particular IP Office nodes.
• PLDS WebLM license files are generated for and installed on a WebLM server that can
license multiple IP Office nodes.
WebLM centralized licensing is supported in IP Office Server Edition and in IP Office Branch
deployments, but not in non-Branch deployments of IP Office Standard mode.
PLDS host ID
Each PLDS license file must be created with the PLDS host ID of the system where the license file
is to be loaded. PLDS Nodal license files are machine specific and you must specify the host ID in
the PLDS host ID field in IP Office Manager or Web Manager.
IP500 V2 systems: You can find the PLDS host ID in the Licensing tab of IP Office Manager and Web
Manager. The PLDS host ID is made of the two digits “11”, followed by the 10-digit feature key serial
number printed on the IP Office SD card. If the SD card is changed, the PLDS host ID will also change.
IP Office Linux servers: The PLDS host ID can be found on the server labeling, the server packaging
label, and the system ignition Login screen. The PLDS host ID is derived from the system ID. If the
system ID changes, the PLDS host ID will also change.
WebLM: The WebLM host ID is the Mac address of the WebLM server. In a virtual environment, the
WebLM host ID is a virtual Mac address that starts with the letter “V”. The WebLM host ID must be
used when generating a PLDS license file for the WebLM server in order to implement a centralized
licensing scheme for multiple IP Office systems. The WebLM host ID can be found on the server
labeling, the server packaging label, the system ignition Login screen, and through the WebLM
management interface.
Web License Manager (WebLM)
The Web License Manager (WebLM) is a web-based application for managing licenses. If you use the
WebLM server running on the IP Office server, then you can use IP Office Web Manager to log in to
the WebLM server by selecting Applications > Web License Manager (https://Server IP
Address:52233/WebLM). WebLM credentials are managed separately from IP Office system
passwords (Default ID: admin, default Password: weblmadmin)
13. 2 Avaya IP Office Platform Feature Description
IP Office provides a comprehensive set of telephony features to enable fast and efficient responses
to phone calls. Wireless handsets and twinning offer employees’ mobility around the office. For
those employees working away from the office, users can handle incoming calls efficiently using
either direct dialing (DDI/DID) or dedicated operators.
2.1 Features
2.1.1 Call handling features
Automatic Callback
A user can set an automatic callback two ways:
• When calling an extension that is busy, request a call when the extension becomes free.
• When calling an extension that only rings, request a call when the extension is next used.
Distinctive ringing
The system uses various ringing sequences to indicate call types. For example, internal and external
calls can have different rings, called distinctive ringing.
Call screening
Users can screen for important calls and decide to answer a call or let it go to voice mail.
Forwarding
Users can forward calls to another extension or external number including mobile devices.
Coverage to Operator
Administrators can configure an operator or a group of operators to provide coverage for external
calls that would otherwise go to voicemail.
Follow Me
Hold
Park
Personalized ringing
Transfer
Call recording
Users can record a call and save the recording to a voicemail mailbox, a group mailbox or the voice
recording library.
Call waiting
Conferencing
The system supports 128 conferencing channels on the IP500 V2, allowing multiple conferences of
any size from 3 to 64 parties.
2.1.2 IP telephony features
Auto-create extensions
Implementation engineers can configure IP Office to create extension entries for new IP phones
added onto the local area network.
Direct media path
Direct media path allows the speech path between two IP extensions (after call setup) to be routed
directly to each other.
Fax transport
IP Office supports Avaya proprietary and T.38 fax transport protocols.
• Avaya proprietary fax transport protocol
14. FAX calls route over VoIP trunks between IP Office systems on an IP network using a proprietary
Avaya transport protocol.
• T.38 fax transport protocol
IP Office supports the T.38 protocol for fax messages transmission between IP Office and SIP trunks
and SIP extensions. (T.38 protocol is not supported on Server Edition systems. G.711 fax transport is
used.)
2.1.3 Messaging features
Voicemail in general provides a phone answering machine with a personalized greeting on every
employee's desk and allows callers to leave spoken messages when the user cannot answer a phone
call.
Voicemail options available are:
• IP Office Essential Edition Embedded Voicemail enables some basic messaging through the
ability to forward voicemail messages to the user's email inbox.
• IP Office Preferred Edition
- Voicemail Pro - for single site use but use in an SCN from remote users
- Distributed Voicemail Pro - for multisite use in an SCN
- Centralized Modular Messaging - for use with Avaya Aura® Communication Manager
Capacity Voicemail Pro Embedded Voicemail
Number of mailboxes
No Limit - Limited only by IP
Office configuration.
Limited only by IP Office
configuration.
Concurrent calls (ports)
Up to 40 dependent on
license 6 simultaneous calls
Recording time
PC dependent (Requires 1 MB
per minute)
2 ports: Up to 15 hours
4 ports: Up to 20 hours
6 ports: Up to 25 hours
2.1.4 Mobility features
Hot Desking
Hot desking allows users nonexclusive use of a single extension.
Remote hot desking
Users can make and receive calls from any office as if using the phone on their own desk. Users have
access to the centralized system and personal directory as well as their call logs.
Remote Worker
Remote Worker allows the connection of remote 9600 Series IP phones with the H.323 FW which
resides behind a NAT router to IP Office. The configuration does not require any VPN concentrator
equipment with IP Office.
Telecommuter mode
Users can make and receive calls and the retrieve voicemails from an external phone number as if
they were in the office, with the server providing the call control.
Twinning
Twinning allows a primary extension and a secondary number (extension or external) to operate
together as a single phone.
VPN Phone
VPN Phone is a full-featured IP telephony solution that provides secure communication over public
ISP networks to IP Office at the company headquarters.
15. 2.1.5 Contact Centre features (short introduction)
Account codes
Through the call records, supervisors and administrators can group calls by account code for the
purpose of call costing and tracking. Supervisors and administrators can also restrict outgoing calls
by requiring users to enter valid account codes.
Acquire Call
The Acquire Call feature allows users to take over a call connected to another extension. This feature
is also known as Call Steal.
Hold music
Administrators can access up to 32 sources for music on hold. On Linux systems up to four USB
sources are supported.
Agent login
Contact center agents must log in before they can make or receive calls.
Monitor calls
Users can monitor another user’s call by listening in.
Hunt groups
A hunt group is a collection of users, typically users handling similar types of calls, for example a
sales department. An incoming caller wishing to speak to someone in a group can call one number
and the call can be answered by any number of extensions that are members of the hunt group.
There are four ways a hunt group can process calls:
• Sequential One extension at a time sequentially, always starting at the top of the list.
• Collective All extensions in the hunt group simultaneously.
• Rotary Start with the extension in the list immediately following the extension that
answered the last hunt group call.
Announcements
Use voicemail in conjunction with hunt groups to:
• Record all group related messages.
• Play an announcement when the hunt group is in Night Service or Out of Service mode.
• Play announcements while a call is held in a queue.
16. 2.2 Applications
2.2.1 IP office manager
Use the Manager to manage IP Office standalone systems or systems in a small community network
(SCN). Manager tracks system configuration changes, manages upgrades, and configuration imports
and exports.
IP Office Manager is also used for maintenance functions such as:
• Upgrade to the IP Office system software
• Ability to send software over an IP network link to a system and have it validated before
committing to the upgrade
• Backwards compatibility with systems from Release 2.1 onwards to allow a single
management application
• Importing and Exporting IP Office configuration information in ACSII-CSV files.
2.2.2 Web manager
Web Manager is a browser-based management tool designed to simplify the installation and
maintenance process and provides access to most, but not all, IP Office configuration settings. Web
Manager eliminates the need to have windows operating system because it can run on any device
that supports standard browsers.
2.2.3 SysMonitor
Use SysMonitor to troubleshoot IP Office from both local (LAN) and remote locations (WAN).
Select the protocols and interfaces to monitor and diagnose through a graphical interface. Capture
traces directly to the screen or as a log file for later analysis. Color code different traces to improve
the clarity in large files. The utility also captures system alarms and displays the activity log of the
last 20 alarms that have occurred.
17. 3 Avaya IP Office Administration and Maintenance
Avaya IP Office Manager runs on a Windows PC and connects to the IP Office system via Ethernet
LAN or WAN connections. Manager is an off-line editor. It receives a copy of the system's current
configuration settings. Changes are made to that copy and it is then sent back to the system for
those changes to become active.
3.1 Manager Modes
The menus and options displayed by Manager vary depending on the actions you are performing.
Manager runs in the following modes.
(Basic Edition is not supported in release 10 and higher)
3.1.1 Security Configuration Mode
Manager can be used to edit the security settings of IP Office systems.
The following conditions apply when editing the IP Office security settings.
• Editing of security settings may only be done online to a system. No offline saving or editing
is allowed for security purposes.
• No errors in the security settings are allowed to persist. This prevents the system becoming
inaccessible through operator error.
• Sets of changes to security objects may be made without the need for the OK button to be
selected every time. This allows a coordinated set of changes to be accepted or canceled by
the operator.
18. 3.1.2 Small Community Network Management
Manager supports loading the combined configurations from systems in a Small Community
Network.
3.1.3 Embedded File Management
For systems with a memory card installed, Manager can be used to view and manage the files
stored on the card. Embedded File Management can be accessed by selecting File | Advanced |
Embedded File Management.
3.1.4 Upgrade Wizard
The Upgrade Wizard is a component of Manager used to upgrade the firmware run by the system.
3.2 Configuration Mode Field Descriptions
Depending on the type and locale of the system some settings and tabs may be hidden as they are
not applicable. Other settings may be grayed out. This indicates that the setting is either for
information only or that another setting needs to be enabled first.
• Standard Mode Configuration Mode
This is the mode used when a Standard Mode configuration is opened. Standard Mode includes
systems running Standard, Preferred, or Advanced Edition.
• Server Edition Configuration Mode
This is the mode used when a Server Edition network configuration is opened.
19. 3.2.1 System
There is one System record for each system being managed. When managing multi system Server
Edition or Small Community Network deployments, clicking on the System icon for a particular
system displays a system inventory page for that system.
3.2.2 Line
The line settings shown in the system configuration will change according to the types of trunk cards
installed in the control unit or added using external expansion modules.
3.2.3 Extension
By default, each extension is normally associated with a user and uses that user's directory number
and other setting. Users with a log in code can move between extensions by logging in and out, so
the directory number is not a fixed property of the extension.
• Non-IP Extensions
Physical extension ports are either integral to the control unit or added by the installation of an
analog or digital phone expansion module. Extension records are automatically created for each
physical extension port within the system. These ports cannot be added or deleted manually. For
Server Edition, non-IP extensions are only supported on Expansion System (V2) units.
3.2.3 User
Users are the people who use the system. They do not necessary have to be an extension user, for
example users are used for RAS dial in data access. In addition, more users can be created than there
are extensions, with users logging in to an extension when they want to receive calls.
By default, a user is automatically created to match each extension.
3.2.3 Group
A group is a collection of users accessible through a single directory number. Calls to that group can
be answered by any available member of the group. The order in which calls are presented can be
adjusted by selecting different group types and adjusting the order in which group members are
listed.
Group Types
• Collective Group
An incoming call is presented simultaneously to all the available group members.
20. • Sequential Group
An incoming call is presented to the first available member in the list. If unanswered, it is presented
to the next available member in the list.
The next incoming call uses the same order. It is presented to the available members starting again
from the top of the list.
• Rotary Hunt Type
This hunt type operates similarly to Sequential. However, the starting point for call presentation is
the first available member after the last member to answer a call.
• Longest Waiting Hunt Type
This hunt type does not present calls to hunt group members in the order that they are listed. It
presents calls using the order of how long the available hunt group members have been idle.
An incoming call is first presented to the available member who has been idle the longest. If
unanswered it is presented to the next longest idle member.
3.2.4 Short Code
The system uses short codes to match the number dialed to an action. The number dialed or part of
the number dialed can be used as parameter for the feature.
• Short Code Matching Examples
Short Code 1 = 60/Dial Extn/203
Dial Delay Count = 0. Dial Delay Time = 4 seconds.
Test Dialing Effect
1 8 No possible match, incompatible returned immediately
2 6 No exact match but there is a potential match, so the system waits. When the Dial
Delay Time expires, no exact match is found so incompatible is returned.
21. 3 60 Exact match to Short Code 1. Extension 203 called immediately.
4 61 No possible match, the system returns incompatible.
3.2.5 Incoming Call Route
Incoming call routes are used to determine the destination of voice and data calls received by the
system. On systems where a large number incoming call routes need to be setup for DID numbers,
the MSN/DID Configuration tool can be used.
Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based
on incoming number received as if dialed on-switch. Line short codes on those trunks can be used to
modify the incoming digits.
For a Server Edition network, these settings can be configured at the network level and are then
automatically replicated in the configuration of all systems in the network. They can only be seen
and edited at the individual system configuration level if record consolidation is switched off.
• Incoming Call Routing Examples
For this example, the customer has subscribes to receive two 2-digit DID numbers. They want calls
on one routed to a Sales hunt group and calls on the other to a Services hunt group. Other calls
should use the normal default route to hunt group Main. The following incoming call routes were
added to the configuration to achieve this:
Line Group Incoming Number Destination
0 77 Sales
0 88 Services
0 blank Main
Note that the incoming numbers could have been entered as the full dialed number, for example
7325551177 and 7325551188 respectively. The result would still remain the same as incoming
number matching is done from right-to-left.
Line Group Incoming Number Destination
0 7325551177 Sales
0 7325551188 Services
0 blank Main
3.2.6 IP Routes
The system acts as the default gateway for its DHCP clients. It can also be specified as the default
gateway for devices with static IP addresses on the same subnet as the system. When devices want
to send data to IP addresses on different subnets, they will send that data to the system as their
default gateway for onward routing.
The IP Route table is used by the system to determine where data traffic should be forwarded. This
is done by matching details of the destination IP address to IP Route records and then using the
Destination specified by the matching IP route. These are referred to as 'static routes'.
3.2.7 License
Identifies the status of the system licenses. The two license configuration types are nodal and
WebLM. Nodal licenses are licenses that are present on the system. WebLM licenses means licenses
obtained from the WebLM server.
22. 3.2.8 User Rights
User Rights act as templates for selected user settings. The settings of a user rights template are
applied to all users associated with that template. The use of a template can also be controlled by a
time profile to set when the template is used for a particular user.
3.2.9 ARS
Each ARS form contains short codes which are used to match the result of the short code that
triggered use of the ARS form, ie. the Telephone Number resulting from the short code is used
rather than the original number dialed by the user.
• ARS Operation
The diagram below illustrates the default ARS routing applied to. In summary:
Any dialing prefixed with 9 will match the default system short code 9N.
That short code routes calls to the default ARS form 50:Main.
The short codes in that ARS form route all calls to an available line that has its Outgoing Group ID set
to 0.
23. 3.3 Avaya IP Office Maintenance
3.3.1 System Status
System Status is a diagnostic tool for system managers and administrators, used to monitor and
check the status of systems. System Status connects to systems running IP Office Release 4.0 and
higher software, using an IP connection.
System Status provides information on the following:
• Alarms
System Status displays all alarms for any system components. It shows the number of such alarms
and the date and time of the last occurrence.
• Call Details
Information on incoming and outgoing calls; including call length, call reference and routing
information.
• Extensions
System Status lists all extensions on the system, including device type, port location and status.
• Trunks
System Status lists all system trunks and connections (VoIP, analog and digital) and shows their
status.
• System Resources
Systems include central resources utilized to perform various functions. Diagnosing these resources
is often critical to the successful operation of the system.
24. 3.3.2 System Monitor
System Monitor can assist in the detailed diagnosis of system problems. Through configuration of its
trace options, it is able to display information on specific areas of a system's operation. It can also
record that information as log files for later analysis.
25. 4 Deploying Avaya IP Office
4.1 Deploying Avaya IP Office server edition
IP Office server edition installer available as;
ISO image: to install on standalone server
OVA image: to install on VMWare
CPE image: to install on Hyper-V
To deploy an IP Office Server Edition Solution the key steps that you need to perform are:
1. If server not purchased a pre-installed server from Avaya, then install Server Edition on a
supported server.
2. Configure the role of the server using the ignition process.
3. Configure the server using the Initial Configuration Utility.
4. Add the optional components such as a Server Edition Secondary server and a Server Edition
Expansion System.
5. Upgrade to the latest IP Office Server Edition software release if a new version is available.
6. Add the licenses for a Server Edition Secondary and Server Edition Expansion System.
7. Administer the various components using IP Office Web Manager and IP Office Manager.
4.1.1 Installing IP Office Server Edition
You can install Server Edition automatically using the installation USB drive. The system
automatically configures the default parameters during the installation.
1. Insert the installation USB drive in the USB port of the Server Edition server.
2. Restart the Server Edition server.
To restart Server Edition server, always use Web Manager. For a new installation, turn off
the power supply to the server.
The system restarts and boots from Server Edition installation USB.
4.1.2 Default parameters
When you install using the installation USB for automatic installation, the system configures the
default parameters for various settings. The default parameters that the system configures during an
automatic installation are as follows:
Language for installation US English
Keyboard for the system US English
Hostname: The eth0 MAC address of the server
System eth0
• Connection name: System eth0
• IP address: 192.168.42.1
• Netmask: 255.255.255.0
• Gateway: 0.0.0.0
System eth1
• Connection name: System eth1
• IP address: 192.168.43.1
• Netmask: 255.255.255.0
• Gateway: 0.0.0.0
Root Password Administrator
26. 4.1.3 Configuring IP Office Server Edition using the ignition process
You can run the Ignition process only once and you cannot rerun the Ignition process unless you
reinstall the server completely.
If the Ignition process is not completed. For example, if you click the Cancel button. The system
displays the Ignition menu when your login the next time.
• On a client computer, start the browser and type https://<IP address of IP Office Server
Edition> : 7070
• Log in as root
27. The system displays the Accept License page.
• In the Accept License page, select I Agree.
• Click Next
28. The system displays the Server Type page.
• In the Server Type page, select the role of the server
You cannot reset the type of server that you select after the ignition process is complete.
• Click Next
29. The system displays information for additional hardware. The page is populated when an additional
hard disk is added to be used when running Contact Recorder for IP Office on the server.
• Accept the default settings
Name is needed later by the Contact Recorder for IP Office application. It is used to configure where
to store the call recordings it collects from the Voicemail Pro server.
• Click Next
30. The system displays the default network configurations. Ensure that the network configuration
details match that of the server for which a role is assigned. Otherwise, update the network
configuration details.
• In the Configure Network page, click Next
31. In the Time & Companding page
• Select Use NTP
• Select the type of Companding
Typically μ-law is for North America and Japan, A-law for Europe and other parts of the world.
• Click Next
32. In the Change Password page, you must change the root and security account password, the
Administrator account password, and the System account password to ensure that the system is
secure.
• Type a password in the New Password field
• Retype a password in the New Password (verify) field
You can also change the password and the password complexity requirements any time after the
Ignition process using Linux Platform settings.
• Click Next
33. In the Security page, you can automatically generate a signing certificate for the internal Certificate
Authority or import a third party signing certificate.
The system does not display the Certificate Authority option when you assign the role of a server as
Secondary Server or Expansion System.
• To automatically generate a certificate, select Generate CA automatically and then click Next
• To import a certificate, perform the following
a. Select Import CA
b. Click Browse, navigate to the certificate location and select the file.
c. Click Upload
d. In the Password field, enter the password for the certificate.
• Click Next
34. On a Primary or Application server, the system displays the details of the Server Edition
server.
• In the Certified Authority field, there two links for downloading the certificate. Click on both
links and download the files to the PC.
The system does not display the Certificate Authority option when you assign the role of a server as
Secondary Server or Expansion System.
• You can review the settings that you selected during the ignition process.
Avaya recommends that you save a copy of the ignition settings for future reference in case of
server re-installation.
• Click Apply
The system applies the changes. The ignition process can take up to eight minutes.
35. The system displays the Web Manager login page. The first time you log in, you receive a prompt
regarding background synchronization. Click Yes.
After login system will again prompt for network setting please enter the same and click on Apply.
4.2 Deploying ip500v2
IP Office systems can run in several modes. For IP Office Release 10.0, only the following modes are
supported for IP500 V2 control units:
IP Office Basic Edition Modes
The following operating modes are collectively referred to as IP Office basic mode.
· IP Office Basic Edition
· IP Office Basic Edition - Norstar Mode
· IP Office Basic Edition - PARTNER Mode
IP Office Standard Modes
The following operating modes are collectively referred to as IP Office standard mode.
· IP Office Essential Edition
· IP Office Preferred Edition
This mode is enabled by adding a Preferred Edition (Voicemail Pro) license to a system already
licensed for Essential Edition.
Other Modes
· Server Edition
An IP500 V2 system can be used in a Server Edition network as an IP500 V2 Expansion System.
· IP Office Platform Select
This mode enabled additional capacity features on Server Edition systems.
System SD Cards
IP500 V2 control unit must be fitted with a System SD card. The default mode of the system is
determined by the type of System SD card present. By using IP Office Manager and adding licenses
the mode of the system can be changed.
The different System SD cards are:
36. · IP Office U-Law SD Card
A system fitted with this type of card defaults to U-Law telephony and IP Office Basic Edition Key
System operation. Intended for North American locales.
· IP Office A-Law SD Card
A system fitted with this type of card defaults to A-Law telephony and IP Office Basic Edition PBX
System operation. Intended for locales outside North America.
Starting the System
1.Before inserting the System SD card:
2.With the control unit shut down or unpowered:
a. The SD card slots are covered by a plastic tab. Partially release the screw holding the tab so that it
can be moved clear of the required card slot.
b. Insert the card into the System SD slot on the rear of the control unit.
3.Apply power to any external expansion modules.
4.Apply power to the control unit.
5.The control unit loads firmware from the System SD card with which it upgrades itself and its
internal components. This takes approximately a minute. The end of this process is indicated by
LED1 on each base card flashing every 5 seconds. LED9 on each base card fitted with a trunk
daughter card also flashes.
6.The control unit then begins upgrading the external expansion modules if necessary. This is
indicated by the center LED on the module flashing red. This process is completed when the LED
changes to steady green.
7.If a configuration file is already present on the System SD card it is loaded by the IP Office. If not,
new systems create a default configuration and copy that configuration onto the System SD card.
8.It should be possible now to use IP Office Manager to access the configuration of the IP Office.
To upgrade/recreate a System SD card
1.Once started do not interrupt this process, for example by removing the SD card. This process
takes approximately 20 minutes.
2.Insert the SD card into a card reader on the IP Office Manager PC.
3.Using IP Office Manager, select File Advanced Recreate IP Office SD Card.
4.Select IP Office A-Law or IP Office U-Law. This selection affects how the IP Office systems operates
when defaulted with this card present in its System SD card slot.
5.Browse to the card location and click OK.
6.IP Office Manager will prompt whether you want to include Avaya IP Office Web Manager files as
part of the recreate process.
7.IP Office Manager will start creating folders on the SD card and copying the required files into
those folders. This process will take approximately 20 minutes.
8.Do not remove the SD card during the process. Wait until the IP Office Manager displays a
message.
4.3 Installing the IP Office Anywhere Demonstration Software
IP Office Anywhere is special demonstration version of the IP Office service. It can be run on any
platform that supports Linux-based IP Office including virtual server platforms. The IP Office
Anywhere service includes a pre-built and licensed configuration with a set of demonstration users,
extensions and groups.
steps to activate demo system as follows
• Installing IP Office from an ISO File or OVA File
• complete the Server Edition Ignition process
37. • Changing the IP Office Service to IP Office Anywhere
To change IP Office Server to IP Office Anyware;
Login to the server using port 7071 (https://192.168.42.1:7071)
Switch to Updates tab and uninstall IP Office
After IP Office uninstall finished Install IP Office Demo and IP Office Demo Default Confing
38. After default configuration loaded system eth0 IP address will changed to 192.168.42.230 and
Administrator login password will also reset to default