Mitel 3300 Integrated Communications Platform … network topology diagram (Figure 1) shows the test...

of 150 EDCS#619038 Rev # Initial version

Application Note

Mitel 3300 Integrated Communications Platform Release 7.1 using T1 ISO QSIG to Cisco Unified Communications Manager 6.0

September 11, 2007, Initial version

Table of Contents

Introduction .............................................................................................................................................................................................................. 2 Network Topology.................................................................................................................................................................................................... 2 Limitations................................................................................................................................................................................................................ 4 System Components ................................................................................................................................................................................................. 6

Hardware Requirements ...................................................................................................................................................................................... 6 Software Requirements ....................................................................................................................................................................................... 6

Features .................................................................................................................................................................................................................... 7 Features Supported .............................................................................................................................................................................................. 7 Features Not Supported ....................................................................................................................................................................................... 7

Configuration............................................................................................................................................................................................................ 8 Configuring the Mitel 3300 ICP, Release 7.1...................................................................................................................................................... 8 Configuring the Cisco Unified Communications Manager 6.0.......................................................................................................................... 73 Configuring Mailboxes on Cisco Unity........................................................................................................................................................... 139 Configuring the Cisco Unified IOS Gateway 2851 ......................................................................................................................................... 141

Acronyms ............................................................................................................................................................................................................. 148

Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 2 of 150

Introduction

This is an application note for connectivity of Mitel 3300 Integrated Communications Platforn Release 7.1 with Cisco Unified Communications Manager Release 6.0 via Cisco 2851 as MGCP gateway using ISO QSIG protocol. A VWIC-2MFT-T1 is used to provide the physical T1 interface on the Cisco 2851.

The network topology diagram (Figure 1) shows the test setup for end-to-end interoperability with the Cisco Unified Communications Manager connected to the Mitel 3300 ICP via Cisco 2851 as MGCP gateway. Interoperability is achieved by using the PRI QSIG T1 protocol type on the MGCP gateway with Communications Manager Service parameter QSIG variant of ISO and ISO switch type on the Mitel 3300 ICP.

This Application Note uses the Cisco 2851 w/ VWIC-2MFT-T1 voice gateway. However, other Cisco voice gateways are also an option to use since Communications Manager QSIG implementation does not depend on the physical interface.

Network Topology

Figure 1. Basic Call Setup

Figure 2. Call Setup for Path Replacement (Route Optimization) in 3 PINX scenario.

Limitations

The following section lists known limitations, caveats, or integration issues.

On calls from the Mitel 3300 Integrated Communications Platform using overlap dialing, there was audible interdigit ringback after the first digits (matching the ARS string) were dialed.

The Mitel 3300 ICP general installation guide says that Connected Name and Number Restriction are supported. However, there appeared to be no way to enable this feature from the System Administration Tool, and there was no help found for it in the tool. The Mitel 3300 ICP did honor Connected Name and Number Restriction from Cisco Unified Communications Manager 6.0.

Cisco Unified IP Phones registered on Cisco Unified Communications Manager 6.0 do not display Busy Name sent over QSIG. Cisco Unified Communications Manager 6.0 does not support decode and display of Busy Name. It does support sending Busy Name.

The Mitel 3300 Integrated Communications Platform did not support busy name, and no mention of it was found in the Mitel 3300 ICP general installation guide.

On call transfers, original Calling Name and Number information was displayed on the final destination phone only after the transfer was complete.

On call transfers originating from a Mitel 3300 ICP extension to a Cisco Unified Communications Manager 6.0 extension, the Mitel 3300 ICP always proposed Path Replacement. Where the final destination was another Cisco Unified Communications Manager 6.0 extension (e.g., phone A calls phone C1, and phone C1 transfers to phone D1), the Path Replacement Proposal was rejected by Cisco Unified Communications Manager 6.0. Where the final destination was another Mitel 3300 ICP extension (e.g., phone A calls phone C1, and phone C1 transfers to phone B), the Path Replacement Proposal was successful and the ”hairpin” connection was torn down.

On network/external call transfers originating from a Cisco Unified Communications Manager 6.0 extension to a Mitel 3300 ICP extension and then transferred to another Cisco Unified Communications Manager 6.0 extension (e.g., phone C1 calls phone A, and phone A transfers to phone D1), the Caller ID information (Calling Number, Calling Name, Connected Number, Connected Name) was not updated. This was due to the Mitel 3300 ICP not sending updated Caller ID information in the ”CallTransferComplete” and ”CallTransferUpdate” FACILITY messages.

On calls forwarded to a Mitel 3300 ICP extension, the Mitel 3300 ICP destination did not display the forwarding name. They also did not display the orignating party’s information (only the forwarding number), until the call was answered. Afterward, the originating party’s name and number were displayed.

On calls originaterd from a Cisco Unified Communications Manager 6.0 extension to a Mitel 3300 ICP extension and then forwarded to another Cisco Unified Communications Manager 6.0 extension (e.g., phone C1 calls phone A, and phone A forwards to phone D1), where reroute is not invoked, the forwarding name and number information was not passed from the Mitel 3300 ICP to the Cisco Unified Communications Manager 6.0. Hence, the forwarding party information was not displayed on the final destination.

On calls originaterd from a Cisco Unified Communications Manager 6.0 extension to a Mitel 3300 ICP extension and then forwarded to another Cisco Unified Communications Manager 6.0 extension (e.g., phone C1 calls phone A, and phone A forwards to phone D1), where reroute is invoked, the forwarding name information was not sent by the Mitel 3300 ICP. Hence, the forwarding party name information was not displayed on the final destination.

Call Back (or Call Completion) from a Cisco Unified Communications Manager 6.0 extension to a Mitel 3300 ICP extension, for either CC-Busy or CC-No Reply, was not possible. The Cisco Unified Communications Manager 6.0 extension was able to book the call on the Mitel 3300 ICP, and the Mitel 3300 ICP sent the “CcExecPossible” when the target station was made available. However, the “CcExecPossible” message from the Mitel 3300 ICP contained a bearer cap mismatch from the original “ccbsRequest” / ”ccnrRequest”, and Cisco Unified Communications Manager 6.0 rejected it.

Call Back (or Call Completion) from a Mitel 3300 ICP extension to a Cisco Unified Communications Manager 6.0 extension was not possible. The Mitel 3300 ICP was able to book the call on Cisco Unified Communications Manager 6.0, and Cisco Unified Communications Manager 6.0 sent the “CcExecPossible” when the target station was made available. Further, the bearer cap information matched what was sent from the Mitel 3300 ICP (compare to the note above). However, the Mitel 3300 ICP rejects the “CcExecPossible” and sends a “CcCancel”. So, no call back took place.

For Path Replacement (or Route Optimization) in a 3 PINX scenario, where a call was originated from a Cisco Unified Communications Manager 6.0 extension to a Mitel 3300 ICP extension , and transferred to a Mitel 3300 ICP extension on another node (e.g., phone C1 calls phone E, and phone E transfers to phone A), the original calling name and number were not displayed on the final destination. The transferring party’s information was still displayed. This was because the middle Mitel 3300 ICP node did not pass the new name and number information in the ”CallTransferComplete” and ”CallTransferUpdate” FACILITY messages.

Path Replacement (or Route Optimization) did not occur on forward-switched calls in a 3 PINX scenario. For calls originating from the Cisco Unified Communications Manager 6.0 (e.g., from figure 2, phone C1 calls phone E, which forwards to phone A), no diverting leg information was provided by the Mitel 3300 ICP. For calls originating from the Mitel 3300 ICP (e.g., from figure 2, phone E calls phone C1, which forwards to phone A), there was no Path Replacement proposal from the Mitel 3300 ICP.

For Path Replacement (or Route Optimization) on ”trombone” connections originated by a Cisco Unified Communications Manager 6.0 extension (e.g., phone C1 calls phone A, and phone A transfers to phone D1), the name and number information on both ends of the call (i.e., Calling Number, Calling Name, Connected Number, Connected Name) was updated only after Path Replacement occured. This was due to the Mitel 3300 ICP not sending updated Caller ID information in the ”CallTransferComplete” and ”CallTransferUpdate” FACILITY messages. After Path Replacement, the Caller ID information was updated locally on Cisco Unified Communications Manager 6.0.

On the Mitel 3300 ICP, Reroute had to be enabled (DPNSS/QSIG Diversion Enabled = ”yes” under System Options) to achieve a full voice mail integration.

On the Mitel 3300 ICP, the Feature Access Codes for ”Message Waiting – Activate” and ”Message Waiting – Deactivate” had to be entered before MWI was enabled.

For a full voice mail integration with Unity, an additinal route pattern from Cisco Unified Communications Manager 6.0 to the Mitel 3300 ICP was needed. It inlcuded a transformation to include the voice mail pilot as calling number. No calling number went out from CCM on Unity MWI messages, and the Mitel 3300 ICP required it. This also needs to be only in the route pattern that corresponds to messages from Unity, as it will otherwise display the wrong caller ID information on basic calls. Adding this route pattern with the calling number transformation gave the additional benefit of access to Unity voice messages by pressing the ”messages” softkey on Mitel 3300 ICP extensions.

System Components

Hardware Requirements

The following hardware is required:

Cisco Unified IOS gateway 2851 with NM-HD-2VE and VWIC-2MFT-T1

Cisco MCS 7800 server (for Cisco Unified Communications Manager and Cisco Unity)

Cisco Unified IP Phones 7960 and 7961

Mitel 3300 MX Controller and dual T1/E1 interface card

(2) Mitel 5220 IP phones

Software Requirements

The following software is required:

Cisco Unified Communications Manager Release 6.0

Mitel 3300 ICP software release 7.1

Cisco IOS Release 12.4

Features

This section lists new and changed features and features that are not supported.

Features Supported

Basic Call (Overlap and ENBLOC dialing)

CLIP-Calling Line (Number) Identification Presentation

CLIR-Calling Line (Number) Identification Restriction

CNIP-Calling Name Identification Presentation

CNIR-Calling Name Identification Restriction

COLP-Connected Line (Number) Identification Presentation

COLR- Connected Line (Number) Identification Restriction (See Limitations)

CONP-Connected Name Identification Presentation

CONR- Connected Name Identification Restriction (See Limitations)

Alerting Name (See Limitations)

Tandem Call through PBX to/from PSTN

Consultation Transfer – Local and Network/External (See Limitations)

Blind Transfer – Local and Network/External (See Limitations)

Call Forward Unconditional by Join – Local and Network/External (See Limitations)

Call Forward Busy by Join – Local and Network/External (See Limitations)

Call Forward No Reply by Join – Local and Network/External (See Limitations)

Call Forward Unconditional by Reroute – Network/External (See Limitations)

Call Forward Busy by Reroute – Network/External (See Limitations)

Call Forward No Reply by Reroute – Network/External (See Limitations)

Path Replacement for Call Transfer in 3-PINX scenario (See Limitations)

Path Replacement for Trombone connection (See Limitations)

MWI (See Limitations)

Features Not Supported

Busy Name

Call Back/Call Completion – Busy and No Reply

Path Replacement for Call Diversion by Forward Switch

Configuration

Configuring the Mitel 3300 ICP, Release 7.1

Software Version

The specific software version was 7.1.5.13.

Trunk Configuration

Link Descriptor Assignment – 1 of 1.

Digital Link Assignment – 1 of 1.

Trunk Circuit Descriptor – 1 of 1.

Trunk Service Assignment – 1 of 1.

Digital Trunk Assignment – 1 of 5.

Trunk Groups

Trunk Group 22 Assignment – 1 of 3.

Routing

ARS Digits Dialed Assignment – 1 of 1.

ARS Leading Digits Assignment – 1 of 1.

Route Assignment: Route 22 to Cisco Unified Communications Manager 6.0 – 1 of 1.

Route Assignment: Route 111 to Mitel 3300 ICP node 2 – 1 of 1.

Configuring Route 111 for overlap dialing – 1 of 1.

Route 111 configured for overlap dialing – 1 of 1.

Digit Modification Assignment – 1 of 1.

Bearer Capabilities

Bearer Capabilities – 1 of 1.

Classes of Service

COS Form – 1 of 1.

COS-Trunks – 1 of 6.

COS-Phones – 1 of 6.

Interconnect Restriction

Interconnect Restriction – 1 of 1.

Feature Access Codes

Feature Access Codes – 1 of 6.

Node ID

Node ID – 1 of 1.

Protocol Assignment

Protocol Assignment – 1 of 1.

Protocol Assignment: Configuring for Overlap Dialing – 1 of 1.

Protocol Assignment: Configured for Overlap Dialing – 1 of 1.

System Options

System Options – 1 of 2.

System Options – 2 of 2.

System Options: Disabling Reroute – 1 of 1.

System Options: Reroute Disabled – 1 of 1.

Caller ID Restriction

CLIR on – 1 of 1.

CLIR off – 1 of 1.

Extensions

IP Telephones – 1 of 1.

User Configurations – 1 of 1.

User 15221 Configuration – 1 of 2.

User 15222 Configuration – 2 of 2.

Voice Mail

Hunt Groups – 1 of 3.

Voice Mail Options Assignment – 1 of 1.

Voice Mail Port Assignment – 1 of 1.

Voice Mail Box Configuration – 1 of 1.

Voice Mail Box 15221 Configuration – 1 of 2.

Voice Mail Box 15221 Configuration – 2 of 2.

Configuring the Cisco Unified Communications Manager 6.0

Software Version

Software Version – 1 of 1.

ISO Parameter

ISO Service Parameter – 1 of 1.

Voice Gateways

Cisco Unified Voice Gateways – 1 of 1.

Cisco Unified Voice Gateway 2851 – 1 of 1.

Cisco 2851 T1 PRI QSIG Trunk 1/0/0– 1 of 3.

Route Patterns

Route Patterns – 1 of 1.

522X ENBLOC Route Pattern – 1 of 2.

522X ENBLOC Route Pattern – 2 of 2.1

1 The prefix digit “1” was used to adapt the Cisco Unified Communications Manager 6.0 number plan, which contained 4 digits, to the Mitel 3300 ICP number plan, which contained 5 digits.

9.X Overlap Route Pattern – 1 of 2.

9.X Overlap Route Pattern – 2 of 2. 2

2 The prefix digit “1” was used to adapt the Cisco Unified Communications Manager 6.0 number plan, which contained 4 digits, to the Mitel 3300 ICP number plan, which contained 5 digits.

1522X Route Pattern (with Calling Party Transform Mask) for Cisco Unity – 1 of 2.

1522X Route Pattern (with Calling Party Transform Mask) for Cisco Unity – 2 of 2. 3

3 There is no prefix digit “1” in this route pattern, because a 5-digit route pattern (1522X) was used to map directly from Cisco Unified Communications Manager 6.0 to the Mitel 3300 ICP for messages originating from Cisco Unity. Whereas the Cisco IP phones used 4-digit dialing, Cisco Unity used the actual mailbox number (e.g., 15221) to reach the remote Mitel extension. Also, the voice mail pilot number for Cisco Unity (5090) was supplied in the Calling Party Transformation Mask, and was needed for a full integration with Cisco Unity.

Calling Line ID Restriction CLIR on 522X Route Pattern – 1 of 1.

Translation Patterns

List Translation Patterns – 1 of 1.

Translation Pattern 235.XXXX – 1 of 1.

Connected Line ID Restriction

Translation Pattern 5010 - Connected Name / Number Restriction for 5001 – 1 of 1.

Call Back

Call Back Service Parameters – 1 of 1.

Soft Key Templates – 1 of 1.

Call Back Soft Key Template – 1 of 1.

Call Back Soft Key Layout – On hook – 1 of 1.

Call Back Soft Key Layout – Ring out – 1 of 1.

Phone x5001 set up for Call Back (Call Back Softkey Template Applied) – 1 of 1.

Route Optimization

Path Replacement Service Parameter – 1 of 1.

Reroute Service Parameter – 1 of 1.

IP Phones

IP Phones – 1 of 1.

Cisco Unified IP Phone 7960, x5001, SCCP – 1 of 4.

Line 5001 – 1 of 4.

Line 5001 – 2 of 4.

Line 5001 – 3 of 4.

Line 5001 – 4 of 4.

Cisco Unified IP Phone 7961, x5007, SIP – 1 of 5.

Line 5007 – 1 of 4.

Line 5007 – 2 of 4.

Line 5007 – 3 of 4.

Line 5007 – 4 of 4.

Call Forwarding Call Forwarding: line 5007 set up to forward to 5002 – 1 of 1.

Cisco Unity Integration List Hunt Pilots – 1 of 1.

Hunt Pilot 5090 – 1 of 2.

Hunt Pilot 5090 – 2 of 2.

Hunt List – 1 of 1.

Line Group – 1 of 2.

Line Group – 2 of 2.

Line Group Line 5091 – 1 of 2.

Line Group Line 5091 – 2 of 2.

Voice Mail Profiles – 1 of 1.

Unity Voice Mail Profile – 1 of 1.

Voice Mail Pilots – 1 of 1.

Voice Mail Pilot 5090 – 1 of 1.

Voice Mail Ports – 1 of 1.

Voice Mail Port 5091 – 1 of 1.

MWI Numbers – 1 of 1.

iDivert

iDivert Softkey Template – 1 of 1.

iDivert Softkey Template Layout – Connected – 1 of 1.

iDivert Softkey Template Layout – Hold – 1 of 1.

iDivert Softkey Template Layout – Ring in – 1 of 1.

iDivert Service Parameters set for Legacy – 1 of 1.

iDivert Service Parameters set for *50 (data-pass-through) – 1 of 1.

Configuring Mailboxes on Cisco Unity

Subscriber Profile – 1 of 1.

Subscriber Messages – 1 of 1.

Configuring the Cisco Unified IOS Gateway 2851

2851_pbx# sho ver

Cisco IOS Software, 2800 Software (C2800NM-IPVOICE-M), Version 12.4(11)T, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Sat 18-Nov-06 17:16 by prod_rel_team

ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1)

2851_pbx uptime is 4 weeks, 1 hour, 5 minutes

System returned to ROM by power-on

System image file is "flash:c2800nm-ipvoice-mz.124-11.T.bin"

Cisco 2851 (revision 53.51) with 251904K/10240K bytes of memory.

Processor board ID FTX1002C063

2 Gigabit Ethernet interfaces

48 Serial interfaces

2 Channelized T1/PRI ports

DRAM configuration is 64 bits wide with parity enabled.

239K bytes of non-volatile configuration memory.

62720K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

2851_pbx#sho run

Building configuration...

Current configuration : 3367 bytes

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

hostname 2851_pbx

boot-start-marker

boot-end-marker

logging buffered 1000000

enable secret 5 $1$Aofo$VpNFzm5wFXJFI.udPvRnm/

enable password cisco

no aaa new-model

network-clock-participate slot 1

ip tcp synwait-time 13

ip cef

no ip domain lookup

ip host CM-SATURN 172.20.235.254

ip name-server 172.20.235.254

multilink bundle-name authenticated

isdn switch-type primary-qsig

isdn gateway-max-interworking

voice-card 0

no dspfarm

voice-card 1

dspfarm

username pbx privilege 15 secret 5 $1$Dby8$s6cwlUG35kFpoBqcoZocH/

username cisco password 0 cisco

controller T1 1/0/0

framing esf

linecode b8zs

pri-group timeslots 1-24 service mgcp

controller T1 1/0/1

framing esf

linecode b8zs

pri-group timeslots 1-24 service mgcp

interface GigabitEthernet0/0

description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$

ip address 172.20.33.128 255.255.255.0

duplex auto

speed auto

interface GigabitEthernet0/1

no ip address

shutdown

duplex auto

speed auto

interface Serial1/0/0:23

no ip address

encapsulation hdlc

isdn incoming-voice voice

isdn bind-l3 ccm-manager

isdn bchan-number-order ascending

no cdp enable

interface Serial1/0/1:23

no ip address

encapsulation hdlc

isdn incoming-voice voice

isdn bind-l3 ccm-manager

no cdp enable

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0

ip route 0.0.0.0 0.0.0.0 172.20.33.1

ip http server

ip http authentication local

ip http timeout-policy idle 5 life 86400 requests 10000

control-plane

voice-port 1/0/0:23

voice-port 1/0/1:23

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server 172.20.235.254

ccm-manager config

mgcp call-agent CM-SATURN 2427 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

no mgcp package-capability res-package

mgcp package-capability sst-package

no mgcp package-capability fxr-package

mgcp package-capability pre-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

mgcp rtp payload-type g726r16 static

mgcp profile default

dial-peer cor custom

banner login ^C

-----------------------------------------------------------------------

Cisco Router and Security Device Manager (SDM) is installed on this device.

This feature requires the one-time use of the username "cisco"

with the password "cisco".

Please change these publicly known initial credentials using SDM or the IOS CLI.

Here are the Cisco IOS commands.

username <myuser> privilege 15 secret 0 <mypassword>

no username cisco

Replace <myuser> and <mypassword> with the username and password you want to use.

For more information about SDM please follow the instructions in the QUICK START

GUIDE for your router or go to http://www.cisco.com/go/sdm

-----------------------------------------------------------------------

line con 0

line aux 0

line vty 0 4

privilege level 15

login local

transport input telnet

line vty 5 15

privilege level 15

login local

transport input telnet

scheduler allocate 20000 1000

2851_pbx#

Acronyms

Acronym Definitions CUCM Cisco Unified Call Manager CCBS Call Completion to Busy Subscriber CCNR Call Completion on No Reply CFB Call Forwarding on Busy CFNR Call Forwarding No Reply CFU Call Forwarding Unconditional CLIP Calling Line (Number) Identification Presentation CLIR Calling Line (Number) Identification Restriction CNIP Calling Name Identification Presentation CNIR Calling Name Identification Restriction COLP Connected Line (Number) Identification Presentation

Important Information

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE

WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO

BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE

FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR

INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA

ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Corporate Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100

European Headquarters

Cisco Systems International BV Haarlerbergpark Haarlerbergweg 13-19 1101 CH Amsterdam The Netherlands www-europe.cisco.com Tel: 31 0 20 357 1000 Fax: 31 0 20 357 1100

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA www.cisco.com Tel: 408 526-7660 Fax: 408 527-0883

Asia Pacific Headquarters

Cisco Systems, Inc. Capital Tower 168 Robinson Road #22-01 to #29-01 Singapore 068912 www.cisco.com Tel: +65 317 7777 Fax: +65 317 7799

Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices.

Argentina • Australia • Austria • Belgium • Brazil • Bulgaria • Canada • Chile • China PRC • Colombia • Costa Rica • Croatia • Czech Republic • Denmark • Dubai, UAE • Finland • France • Germany • Greece • Hong Kong SAR • Hungary • India • Indonesia • Ireland • Israel • Italy • Japan • Korea • Luxembourg • Malaysia • Mexico • The Netherlands • New Zealand • Norway • Peru • Philippines • Poland • Portugal • Puerto Rico • Romania • Russia • Saudi Arabia • Scotland • Singapore • Slovakia • Slovenia • South Africa • Spain • Sweden • Switzerland • Taiwan • Thailand • Turkey Ukraine • United Kingdom • United States • Venezuela • Vietnam • Zimbabwe

CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0708R)

Printed in the USA

Mitel 3300 Integrated Communications Platform … network topology diagram (Figure 1) shows the test...

Documents

MITEL SX-200 IP Communications Platform - bcstel.com · MITEL SX-200 IP Communications Platform 5330 IP and 5340 IP Phones User Guide

MITEL COMMUNICATIONS DIRECTOR PLATFORMedocs.mitel.com/UG/EN/MCD_5330e-5340e_UG_R6.0_EN.pdf · MITEL COMMUNICATIONS DIRECTOR PLATFORM - ii - ... Off Your phone is idle, or you are

MITEL SX-200 IP Communications Platform - Mitel Edocs - Technical

Vidyo for Mitel Unified Communications - VoIPInfo.net for Mitel UC... · 2017. 2. 21. · Vidyo for Mitel Unified Communications Solution overview Mitel® Unified Communications &

5000 Communications Platform (CP) · 5000 Communications Platform (CP) MITEL Administrator Phone Guide. Mitel® 5000 CP Administrator Phone Guide ... Refer to the appropriate Voice

MITEL Communications Director - PSG · PDF filesoftware and its host hardware platforms, the Mitel® 3300 IP Communications Platform (ICP) ... Mitel Communications Director - General

410 1018-Teleworker Soln App Note:Layout 1 - Tele … · The Mitel ® Teleworker ... Mitel 3300 IP Communications Platform (ICP) or Mitel SX-200® IP Communications Platform (ICP)

MITEL 5000 COMMUNICATIONS PLATFORM (CP) · The instructions in this guide are for using the Mitel 5320e/5330e/5340e Internet Protocol (IP) Phone on the Mitel 5000 Communications Platform

COMMUNICATIONS DIRECTOR - Mitel

MITEL COMMUNICATIONS DIRECTOR · Mitel Communications Director ... • Your Mitel SAP account number • Specify if you would like your user ID and pa ssword delivered to you by fax,

MITEL 3300 IP Communications Platform - Mitel …edocs.mitel.com/UG/EN/5224_5324_Agent_Guide_MCD4.0_EN.pdfMITEL 3300 IP Communications Platform ACD Agent Guide for the Mitel 5224 and

MITEL 3000 Communications System (CS) Sales Guide · Mitel 3000 Communications System Overview The Mitel 3000 Communications System product line has proven to be a great addition

MITEL 3300 IP Communications Platform - 4net … · MITEL 3300 IP Communications Platform ... are incorporated tightly into your business processes and extend the benefits of presence

MITEL 5000 Communications Platform - ashtelecom.co.uk

MITEL Multi-Instance Communications Director for Service ... Comm Director f… · Mitel® Multi-Instance Communications Director (MICD) enables service providers to deploy rich,

MITEL 3000 Communications System for Business · The Mitel 3000 Communications System Business Solution Offers: † An affordable path to convergence, allowing you to reduce operating

MITEL SX-200 IP Communications Platformedocs.mitel.com/UG/EN/2ICP_5312-5324_UG_R4_UR5_EN.pdf · MITEL SX-200 IP Communications Platform ... Call Forward ... Date and Time Setup

MITEL COMMUNICATIONS DIRECTOR PLATFORM€¦ · mitel 5330e and 5340e ip phones user guide mitel communications director platform

MITEL 5000 COMMUNICATIONS PLATFORM (CP)

Mobile Unified Communications - Mitel