- Preface
- Introduction
- Planning the Usage of Voice Messaging Ports in Cisco Unity Connection
- Setting Up an Alcatel 4400 Analog PIMG Integration with Cisco Unity Connection
- Setting Up an Avaya Definity G3 Digital PIMG Integration with Cisco Unity Connection
- Setting Up an Avaya Definity ProLogix Digital PIMG Integration with Cisco Unity Connection
- Setting Up an Avaya S8300/S8500/S8700 Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Mitel SX-200 Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection
- Setting Up an NEC NEAX 2400 Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Nortel Meridian 1 Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Rolm 9751 Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Serial (SMDI, MCI, or MD-110) PIMG Integration with Cisco Unity Connection
- Setting Up a Siemens Hicom 150 Analog PIMG Integration with Cisco Unity Connection
- Setting Up a Siemens Hicom 300 E (European) Analog PIMG Integration with Cisco Unity Connection
- Setting Up a Siemens Hicom 300 E (North American) Digital PIMG Integration with Cisco Unity Connection
- Setting Up a Siemens Hipath 3750 Analog PIMG Integration with Cisco Unity Connection
- Setting Up a Siemens Hipath 4000 Analog PIMG Integration with Cisco Unity Connection
- Testing the Integration
- Adding New User Templates for Multiple Integrations
- Adding a Secondary Master PIMG Unit
- Application Note for the Ericsson MD-110 Serial PIMG Integration
- Application Note for the Nortel SL-100 Serial SMDI TIMG Integration
- Settings for PIMG Firmware Version 5.x
- Index
Setting Up a Nortel Meridian 1 Digital PIMG Integration with Cisco Unity Connection
For detailed instructions for setting up a Nortel Meridian 1 digital PIMG integration with Cisco Unity Connection, see the following sections in this chapter:
Task List to Create Integration with Nortel Meridian 1 PIMG Phone System
Before doing the following tasks to integrate Unity Connection with the Nortel Meridian 1 phone system using PIMG units (media gateways), confirm that the Cisco Unity Connection server is ready for the integration after completing the server installation, following the tasks in the “Installing Cisco Unity Connection” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection, Release 10.x, available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx/10xcuciumg010.html.
1. Review the system and equipment requirements to confirm that all phone system and Cisco Unity Connection server requirements have been met. See the “Requirements” section.
2. Plan how the voice messaging ports are used by Unity Connection. See the “Planning the Usage of Voice Messaging Ports in Cisco Unity Connection” chapter.
3. Program the Nortel Meridian 1 phone system and extensions. See the “Programming Nortel Meridian 1 PIMG Phone System Integration” section.
4. Set up the PIMG units. See the “Setting Up Digital PIMG Units” section.
5. Create the integration. See the “Creating New Integration with Nortel Meridian 1 Phone System” section.
6. Test the integration. See the “Testing the Integration” chapter.
7. If this integration is a second or subsequent integration, add the applicable new user templates for the new phone system. See the “Adding New User Templates for Multiple Integrations” chapter.
Requirements
The Nortel Meridian 1 PIMG integration supports configurations of the following components:
Phone System
– Nortel Meridian 1 phone system (Option 11, 21, 51, 61, 71, or 81), software release 17 or later.
– Nortel Succession (CS 1000) phone system, software release 3.0 or later.
– The Nortel SL 1 phone system, when upgraded to Meridian 1 so that it is compatible with the M2616 digital phone.
– Package 19, Digit Display Software (DDSP)
– Package 46, Message Waiting Center (MWC)
- One or more digital lines that are compatible with the M2616 digital phone for connecting to the PIMG units.
- One or more of the applicable PIMG units. For details, see the “Introduction” chapter.
- The voice messaging ports in the phone system connected by digital lines to the ports on the PIMG units.
To simplify troubleshooting, we recommend that you connect the voice messaging ports on the phone system to the ports on the PIMG units in a planned manner. For example, connect the first phone system voice messaging port to the first port on the first PIMG unit, connect the second phone system voice messaging port to the second port on the first PIMG unit, and so on. Alternatively, if you have multiple PIMG units, you can reduce answer times in the event of a PIMG unit failure by connecting the phone system ports to the PIMG units in a round-robin fashion. For example, connect the first phone system voice messaging port to the first port on the first PIMG unit, connect the second phone system voice messaging port to the first port on the second PIMG unit, and so on.
- The PIMG units connected to the same LAN or WAN that Unity Connection is connected to.
- If the PIMG units connect to a WAN, the requirements for the WAN network connections are:
– For G.729a codec formatting, a minimum of 32.76 Kbps guaranteed bandwidth for each voice messaging port.
– For G.711 codec formatting, a minimum of 91.56 Kbps guaranteed bandwidth for each voice messaging port.
– No network devices that implement network address translation (NAT).
Unity Connection Server
- Unity Connection installed and ready for the integration after completing the server installation, following the tasks in the “Installing Cisco Unity Connection” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection, Release 10.x, available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx/10xcuciumg010.html.
- A license that enables the applicable number of voice messaging ports.
Centralized Voice Messaging
Unity Connection supports centralized voice messaging through the phone system, which supports various inter-phone system networking protocols including proprietary protocols such as Avaya DCS, Nortel MCDN, or Siemens CorNet, and standards-based protocols such as QSIG or DPNSS. Note that centralized voice messaging is a function of the phone system and its inter-phone system networking, not voicemail. Unity Connection supports centralized voice messaging as long as the phone system and its inter-phone system networking are properly configured. For details, see the “Centralized Voice Messaging” section in the “Integrating Cisco Unity Connection 10.x with the Phone System” chapter of the Design Guide for Cisco Unity Connection, Release 10.x, available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/design/guide/10xcucdgx/10xcucdg050.html.
Programming Nortel Meridian 1 PIMG Phone System Integration
If you use programming options other than those supplied in the following procedure, the performance of the integration may be affected.
The following programming instructions are provided as an example only. The specific programming for your phone system may vary depending on its configuration.


To Program the Nortel Meridian 1 Phone System
Step 1 Assign extensions for the voice messaging ports.
Step 2 Confirm that the software on the phone system has the necessary following option packages using overlay 22:
If either of these options is missing, contact your sales representative.
Step 3 On overlay 11, set the following options to create the M2616 digital set emulation for the first port.
|
|
---|---|
Enter the primary number for this PIMG unit. Enter any valid unused number. |
|
Step 4 Set the following options to create the digital set emulation for the second port.
|
|
---|---|
Enter the extension for this PIMG unit port. Enter any valid unused number. |
|
Step 5 Repeat Step 4 for all remaining ports on the PIMG units.
Step 6 On overlay 95, set the following options to enable display of a four-letter code that represents why the call was forwarded.
|
|
---|---|
Step 7 On each subscriber phone, program the phone to forward calls to the pilot number assigned to the voice messaging ports, based on one of the Unity Connection call transfer types shown in Table 10-4 .
Step 8 Use Table 10-5 to determine the hunt method that you want to use, and do the applicable procedure.
To Set Up a Hunt Group for Up to 30 Ports
See Table 10-5 for considerations about using this procedure.
Step 1 Set up the first voice messaging port as the pilot number of the hunt group.
Step 2 Set the first voice messaging port to hunt to the second voice messaging port.
Step 3 Set the second voice messaging port to hunt to the third, then continue up to the 30th.
Step 4 Set the 30th voice messaging port to hunt to the first voice messaging port. See the example in Table 10-6 .
|
|
|
---|---|---|
To Set Up an ACD Hunt Group for More Than 30 Ports
See Table 10-5 for considerations about using this procedure.
Step 1 Set up ACD 1 as the pilot number of the hunt group.
Step 2 With the Night Call Forward Destination (NCFW) command, set ACD 1 to forward to the first voice messaging port.
Step 3 Set the first voice messaging port to hunt to the second, then continue up to the 30th.
Step 4 Set the 30th voice messaging port to hunt to ACD 2.
Step 5 With the NCFW command, set ACD 2 to forward to the 31st voice messaging port.
Step 6 Set the 31st voice messaging port to hunt to the 32nd, and so on.
Step 7 Continue creating 30-port hunt groups in this manner until the last voice messaging port.
Step 8 Set the last voice messaging port to hunt to ACD 1. See the example in Table 10-7 .
|
|
|
---|---|---|
To Set Up the Group Hunt Feature
See Table 10-5 for considerations about using this procedure.
Step 1 In LD 22, verify that software package 120 is equipped.
|
|
---|---|
Step 2 In LD 18, create a Group Hunt list number.
|
|
---|---|
Enter the list number for the Group Hunt list. For example, enter 1. |
|
Step 3 In LD 57, define the Pilot DN (PLDN) and associate it with the number for the Group Hunt list.
Step 4 In LD 18, modify the Group Hunt list number.
|
|
---|---|
Enter the list number for the Group Hunt list that you created in Step 2. For example, enter 1. |
|
Enter the first DN in the Group Hunt list in the following format: |
|
Enter the second DN in the Group Hunt list in the following format: |
|
Enter the third DN in the Group Hunt list in the following format: |
|
Enter the last DN in the Group Hunt list in the following format: |
Step 5 In LD 11, enter a Group Hunt Pilot DN (PLDN) for each DN in the Group Hunt list that connects to a PIMG port.
|
|
---|---|
Enter the first DN in the Group Hunt list. For example, enter 2616. |
|
Enter FDN <extension> for the PLDN that you configured in Step 3. |
|
Enter HUNT <extension> for the PLDN that you configured in Step 3. |
|
If applicable, enter EHT <extension> for the PLDN that you configured in Step 3. |
|
If applicable, enter EFD <extension> for the PLDN that you configured in Step 3. |
Step 6 Repeat Step 5 for all remaining DNs in the Group Hunt list.
Setting Up Digital PIMG Units
Do the following procedures to set up the digital PIMG units that are connected to the Nortel Meridian 1 phone system.
These procedures require that the following tasks have already been completed:
- The phone system is connected to the PIMG units using digital lines.
- The PIMG units are ready to be connected to the LAN or WAN.
- The PIMG units are connected to a power source.
Fields that are not mentioned in the following procedures must keep their default values. For the default values of all fields, see the manufacturer documentation for the PIMG units.
To Download the PIMG Firmware Update Files for Digital PIMG Units
Step 1 On a Windows workstation that have access to the PIMG units, go to the following link:
http://software.cisco.com/download/navigator.html?mdfid=280082558&i=rm.

Note To access the software download page, you must be signed in to Cisco.com as a registered user.
This procedure describes the steps when using Internet Explorer as your web browser. If you are using a different web browser, the steps may differ.
Step 2 In the tree control on the Downloads Home page, expand Unified Communications> Unified Communications Applications > Messaging > Cisco Unity and select Cisco Unity Telephony Integration.
Step 3 On the Log In page, enter your username and password, then select Log In.
Step 4 On the Select a Release page, under Latest Releases, select the most recent release.
Step 5 In the right column, select the version of the firmware for digital PIMG units.

Step 6 On the Download Image page, select Download.
Step 7 On the Supporting Document(s) page, select Agree.
Step 8 In the File Download dialog box, select Save.
Step 9 In the Save As dialog box, browse to the Windows workstation that have access the PIMG units, browse to a directory where you want to save the file, and select Save.
Step 10 In the Download Complete dialog box, select Open. The window for extracting the PIMG firmware update files appears and select Extract.
Step 11 In the Extract dialog box, browse to the directory where you want the extracted files, and select Extract.
Step 12 Close the window for the extracting application.
To Set Up the Digital PIMG Units (Firmware Version 6.x)
Step 1 On the Windows workstation, add a temporary route to enable access to the PIMG units.
a. On the Windows Start menu, select Run.
b. Enter cmd, and press Enter. The Command Prompt window appears.
c. At the command prompt, enter route add 10.12.13.74 <IP Address of Workstation>, and press Enter.
For example, if the IP address of the workstation is 198.1.3.25, enter “route add 10.12.13.74<space>198.1.3.25” in the Command Prompt window.
d. Close the Command Prompt window.
Step 2 Connect a PIMG unit to the network.
Step 3 In the web browser, go to http://10.12.13.74.
Step 4 To sign in, enter the following case-sensitive settings.
|
|
---|---|
Step 6 On the System menu, select Upgrade.
Step 7 On the Upgrade page, select Browse.
Step 8 In the Choose File dialog box, browse to the directory on the Windows workstation that has the extracted PIMG firmware update files.
Step 9 Select Ami<xx>.app (where <xx> is multiple digits), and select Open.
Step 10 On the Upgrade page, select Install File.
Step 11 After the file is installed, a message prompting you to restart the PIMG unit appears. Select Cancel.

Step 12 Repeat Step 6 through Step 11 for each of the following files:
Step 13 On the Configuration menu, select Import/Export.
Step 14 On the Import/Export page, select Browse.
Step 15 In the Choose File dialog box, browse to the file DNI_Cfg_Generic.ini.
Step 16 Select DNI_Cfg_Generic.ini, and select Open.
Step 17 On the Import/Export page, select Import File.
Step 18 After the file is imported, a message prompting you to restart the PIMG unit appears. Select OK.
Step 19 In the web browser, go to http://10.12.13.74.
Step 20 To sign in, enter the following case-sensitive settings.
|
|
---|---|
Step 22 Do the following substeps to configure an RTP port range of 16384 to 32767 and to configure updating the calling number.


Note The default RTP port range for PIMG units is 49000 to 50000. Some Unity Connection configurations require a different RTP port range.
a. On the Configuration menu, select Import/Export.
b. On the Import/Export page, under Export Settings, select Export All Settings.
c. In the File Download dialog box, select Save.
d. In the Save As dialog box, browse to the Windows workstation that has access to the PIMG units, browse to a directory where you want to save the file, and select Save.
e. In the Download Complete dialog box, select Open. Notepad opens the file Config.ini that you saved.
f. Locate the line with the following parameter:
g. Change the value of the parameter to “yes” so that the line reads as follows:
h. Locate the line with the following parameter:
i. Change the value of the parameter to 16384 so that the line reads as follows:
j. Locate the line with the following parameter:
k. Change the value of the parameter to 32767 so that the line reads as follows:
l. Save the file, and exit Notepad.
m. On the Configuration menu of the PIMG unit, select Import/Export.
n. On the Import/Export page, under Browse for Import File, select Browse.
o. In the Choose File dialog box, browse to the file Config.ini that you saved.
p. Select Config.ini, and select Open.
q. On the Import/Export page, select Import File.
r. When prompted to restart the PIMG unit, select OK.
s. When the PIMG unit has restarted, in the web browser, go to http://10.12.13.74.
t. To sign in, enter the following case-sensitive settings.
|
|
---|---|
Step 23 On the System menu, select Password.
Step 24 On the Change Password page, enter the following settings.
|
|
---|---|
Step 26 On the Configuration menu, select Routing Table.
Step 27 On the Routing Table page, under Router Configuration, select VoIP Host Groups.
Step 28 Under VoIP Host Groups, enter the following settings for the first VoIP Host Group.
|
|
---|---|
Accept the default or enter another descriptive name of the VoIP host group. |
|
Step 29 For Unity Connection without a cluster, under Host List, enter the host name or IP address of the Unity Connection server and the server port in the format <host name or IP address>:5060.
For Unity Connection with a cluster configured, under Host List, enter the host name or IP address of the subscriber server (the second Unity Connection server that you installed) and the server port in the format <host name or IP address>:5060.
Step 30 For Unity Connection without a cluster, continue to Step 32. For Unity Connection with a cluster configured, select Add Host.
Step 31 In the second field, enter the host name or IP address of the publisher server (the first Unity Connection server that you installed) and the server port in the format <host name or IP address>:5060.

Step 33 Under Router Configuration, select TDM Trunk Groups.
Step 34 Under TDM Trunk Groups, select Add Trunk Group.
Step 35 Under TDM Trunk Groups, enter the following settings for the first TDM trunk group.
Step 36 Under TDM Trunk Groups, select Add Trunk Group.
Step 37 Enter the following settings for the second TDM trunk group.
Step 38 Under TDM Trunk Groups, select Add Trunk Group.
Step 39 Enter the following settings for the third TDM trunk group.
Step 41 Under Router Configuration, select Inbound VoIP Rules.
Step 42 Under Inbound VoIP Rules, uncheck the Enabled check box for the default rule.
Step 44 Under Inbound VoIP Rules, enter the following settings for the first new inbound VoIP rule.
|
|
---|---|
Enter MWI_Calls or another name. This inbound VoIP rule handles all MWI calls from Unity Connection. |
|
Step 45 Under Inbound VoIP Request Matching, enter the following settings.

|
|
---|---|
Step 46 Under Outbound Routes, enter the following settings.

|
|
---|---|
Select the name of the TDM trunk group that you created for MWIs in Step 37. For example, select “MWIs.” |
|
Step 47 Under Inbound VoIP Rules, select Add Rule.
Step 48 Under Inbound VoIP Rules, enter the following settings for the second new inbound VoIP rule.
|
|
---|---|
Enter Outbound_UC_Calls or another name. This inbound VoIP rule handles all outbound calls from Unity Connection. |
|
Step 49 Under Inbound VoIP Request Matching, enter the following settings.

|
|
---|---|
Step 50 Under Outbound Routes, enter the following settings.

|
|
---|---|
Select the name of the TDM trunk group that you created for outbound calls in Step 39. For example, select “Outbound_PBX_Calls.” |
|
Step 52 Under Router Configuration, select Inbound TDM Rules.
Step 53 Under Inbound TDM Rules, enter the following settings for the first inbound TDM rule.
|
|
---|---|
Enter Inbound_Rule_1 or another name. This inbound TDM rule handles all incoming calls from the phone system. |
|
Select the name of the TDM trunk group that you created for incoming calls from the phone system in Step 35. For example, select “Inbound_PBX_Calls.” |
Step 54 Under Inbound TDM Request Matching, enter the following settings.

Step 55 Under Outbound Routes, enter the following settings.

|
|
---|---|
Select the name of the VoIP host group that you created for Unity Connection in Step 28. |
|
Step 56 If you want to create more Inbound TDM rules, under Inbound TDM Rules, select Add Rule. Otherwise, continue to Step 58
.
Step 57 Repeat Step 53 through Step 56 for all remaining inbound TDM rules that you want to create.
Step 59 On the Configuration menu, select TDM > Digital.
Step 60 On the Digital Telephony page, in the Telephony Switch Type field, select M1.
Step 62 On the Configuration menu, select TDM > General.
Step 63 On the TDM General Settings page, enter the following settings.
|
|
---|---|
Enter the pilot number of the Unity Connection voice messaging ports. |
|
Step 65 On the Configuration menu, select TDM > Port Enable.
Step 66 On the TDM Port Enabling page, select No for the ports that you want to disable on the PIMG unit.
Step 67 Confirm that Yes is selected for all other ports on the PIMG unit.
Step 69 On the Configuration menu, select VoIP > General.
Step 70 On the VoIP General Settings page, enter the following settings.
Step 72 On the Configuration menu, select VoIP > Media.
Step 73 On the VoIP Media Settings page, enter the following settings.
Step 75 On the Configuration menu, select VoIP > QOS.
Step 76 On the VoIP QOS Configuration page, enter the following settings.
|
|
---|---|
Step 78 On the Configuration menu, select IP.
Step 79 On the IP Settings page, enter the following settings.
Step 81 On the Configuration menu, select Tone Detection.
Step 82 On the Tone Detection page, under Call Progress Tone - Learn, in the Learn Tone Event field, select Busy and do the following substeps
to verify that the tone is correct.
a. From a available phone, call a second phone.
b. Answer the second phone when it rings, and leave both handsets off so that both phones are busy.
c. From a third phone, dial one of the busy phones.
d. Confirm that you hear a busy tone.
e. Hang up the third phone but leave the handsets for the other two phones off.
Step 83 Under Call Progress Tone - Learn, in the Dial String field, enter the extension that you dialed in Step 82c. from the third phone.
Step 85 On the Tone Detection page, under Call Progress Tone - Learn, in the Learn field, select Error and do the following substeps
to verify that the tone is correct.
a. From an available phone, dial an extension that does not exist.
b. Confirm that you hear the reorder or error tone.
Step 86 Under Call Progress Tone - Learn, in the Dial String field, enter the extension that you dialed in Step 85a.
Step 88 On the Tone Detection page, under Call Progress Tone - Learn, in the Learn field, select Ringback and do the following substeps
to verify that the tone is correct.
a. From an available phone, dial an extension that does exist
b. Confirm that you hear the ringback tone.
Step 89 Under Call Progress Tone - Learn, in the Dial String field, enter the extension that you dialed in Step 88a.
Step 92 Hang up the phones that you used in Step 82.
Step 93 On the System menu, select Restart.
Step 94 On the Restart page, select Restart Unit Now.
Step 95 Repeat Step 2 through Step 94 on all remaining PIMG units.
Creating New Integration with Nortel Meridian 1 Phone System
After ensuring that the Nortel Meridian 1 phone system, the PIMG units, and Unity Connection are ready for the integration, do the following procedure to set up the integration and to enter the port settings.
Step 1 In Cisco Unity Connection Administration, expand Telephony Integrations, then select Phone System.
Step 2 On the Search Phone Systems page, under Display Name, select the name of the default phone system.
Step 3 On the Phone System Basics page, in the Phone System Name field, enter the descriptive name that you want for the phone system.
Step 4 If you want to use this phone system as the default for TRaP connections so that administrators and users without voicemail boxes can record and playback through the phone in Unity Connection web applications, check the Default TRAP Switch check box. If you want to use another phone system
as the default for TRaP connections, uncheck this check box.
Step 5 Under Message Waiting Indicator Settings, select Use Same Port for Enabling and Disabling MWIs.
Step 7 On the Phone System Basics page, in the Related Links drop-down box, select Add Port Group and select Go.
Step 8 On the New Port Group page, enter the applicable settings and select Save.
|
|
---|---|
Select the name of the phone system that you entered in Step 3. |
|
Select Port Group Template and select SIP to DMG/PIMG/TIMG in the drop-down box. |
|
Enter a descriptive name for the port group. You can accept the default name or enter the name that you want. |
|
Select the SIP transport protocol that Unity Connection use. |
|
Enter the IP address of the PIMG unit that you are integrating with Unity Connection. |
|
Do not enter a value in this field. IPv6 is not supported for PIMG integrations. |
|
Enter the IP address of the PIMG unit that you are integrating with Unity Connection. |
|
Enter the SIP port of the PIMG unit that Unity Connection connects to. We recommend that you use the default setting. ![]() |
Step 9 On the Port Group Basics page, under Message Waiting Indicator Settings, uncheck the Enable Message Waiting Indicators check box and select Save.
Step 10 In the Related Links drop-down box, select Add Ports and select Go.
Step 11 On the New Port page, enter the following settings and select Save.
|
|
---|---|
(If you want to use fewer than eight voice messaging ports, enter the number of voice messaging ports that you want to use on this PIMG unit.) Note For a Unity Connection cluster, the server must have the number of voice messaging ports that are set up on the phone system for the PIMG integration so that this server can handle all voice messaging traffic for the cluster if one of the servers stops functioning. For example, if the phone system is set up with 16 voice messaging ports, this server must have 16 voice messaging ports. |
|
Select the name of the phone system that you entered in Step 3. |
|
Select the name of the port group that you added in Step 8. |
Step 12 On the Search Ports page, select the display name of the first voice messaging port that you created for this phone system integration.

Note By default, the display names for the voice messaging ports are composed of the port group display name followed by incrementing numbers.
Step 13 On the Port Basics page, set the voice messaging port settings as applicable. The fields in the following table are the ones that you can change.
Step 16 Repeat Step 13 through Step 15 for all remaining voice messaging ports for the phone system.
Step 17 In Cisco Unity Connection Administration, expand Telephony Integrations, then select Phone System
.
Step 18 On the Search Phone Systems page, under Display Name, select the name of the phone system that you entered in Step 3.
Step 19 Repeat Step 7 through Step 18 for each remaining PIMG unit is integrated with Unity Connection.

Note Each PIMG unit is connected to one port group with the applicable voice messaging ports. For example, a system that uses five PIMG units requires five port groups, one port group for each PIMG unit.
Step 20 To create a port group for MWIs, do the following substeps.

Note All MWI requests are handled by the master PIMG unit and sent to the phone system over the RS-232 serial cable (without using voice messaging ports). So the following substeps create a separate port group without voice messaging ports and enable the port group for MWIs that are “not port specific” (they do not use ports).
a. In Cisco Unity Connection Administration, expand Telephony Integrations, then select Port Group.
b. On the Search Port Groups page, select Add New.
c. On the New Port Group page, enter the applicable settings and select Save.
|
|
---|---|
Select the name of the phone system that you entered in Step 3. |
|
Select Port Group Template and select SIP to DMG/PIMG/TIMG in the drop-down box. |
|
Enter a MWI Port Group or another descriptive name for the port group. |
|
Select the SIP transport protocol that Unity Connection uses. |
|
Do not enter a value in this field. IPv6 is not supported for PIMG integrations. |
|
Enter the SIP port of the master PIMG unit. ![]() |
d. On the Port Group Basics page, on the Edit menu, select Advanced Settings.
e. On the Edit Advanced Settings page, under SIP MWI Requests, select Not Port Specific. and select Save.
f. On the Edit menu, select Port Group Basics.
g. Under Port Group, select Reset.
h. Under Message Waiting Indicator Settings, confirm that the Enable Message Waiting Indicators check box is checked and select Save.
Step 21 If another phone system integration exists, in Cisco Unity Connection Administration, expand Telephony Integrations, then select Trunk. Otherwise, skip to Step 25
.
Step 22 On the Search Phone System Trunks page, on the Phone System Trunk menu, select New Phone System
Trunk.
Step 23 On the New Phone System Trunk page, enter the following settings for the phone system trunk and select Save.
Step 24 Repeat Step 22 and Step 23 for all remaining phone system trunks that you want to create.
Step 25 In the Related Links drop-down list, select Check Telephony Configuration and select Go to confirm the phone system
integration settings.
If the test is not successful, the Task Execution Results displays one or more messages with troubleshooting steps. After correcting the problems, test the connection again.
Step 26 In the Task Execution Results window, select Close.