This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 4 of 150
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 5 of 150
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 82 of 150
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 84 of 150
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 86 of 150
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.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com Page 150 of 150
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)