# Programming IP Networking

## Description

The procedures below describe two ways to provision IP trunks in a voice network or cluster. One way uses traditional IP/XNET trunk groups and profiles; the other uses a special ARS route (Direct IP Route) that bypasses the need for such groups and profiles. Using the traditional way, you have to set up the COS, COR, and Interconnect Restrictions that define the service levels, signaling, and other attributes of the IP trunks. The Direct IP Route requires none of this setup. Instead, it uses factory-set attributes which allow for more rapid trunk provisioning, especially in a greenfield (new) installation of MCD 5.0 systems.

The traditional method of IP trunk provisioning is still supported. Use it if an issue arises that requires some IP trunks in the network or cluster to have a different COS or COR than the others.

Provisioning using the Direct IP Route assumes the following about the network/cluster:

- each element in the network or cluster is running MCD 5.0 software.

- data in the network or cluster is shared and synchronized.

NOTE: Outgoing IP trunk calls routed by ARS via the Direct IP Route go directly to the MiVoice Business system identified in the ARS route. The identified system must be running MCD 5.0 software for the call to proceed. If not, the route is considered out of service for that call. IP trunk calls using IP/XNET trunk groups to the same MiVoice Business system will proceed.

## Before You Begin

- Previously completed XNET programming will be restored (on upgrade) to the various fields in the ICP/PBX Networking form; however, if XNET was only partially programmed, the data may not be restored correctly.

- Set the system date and time on each system in the network, through Server Manger (Configuration > Date and Time), to take full advantage of IP Networking functionality.

- Realtime Control Protocol (RTCP) is not supported across IP trunks.

## Programming

Provisioning IP trunks requires programming on each element in the network or cluster. You can log into each element separately to do the programming or you can log in once from any member element and access the others by using Application Reach Through.

### Using the Direct IP Route method

The Direct IP Route is used to provision IP trunks between MiVoice Business systems. Trunks seized via the Direct IP Route medium use Interconnect Restriction 65 and the same fixed trunk attributes at both the originating (local) and destination (remote) end. The attributes are as follows:

- Release Link Trunk is “No”

- Call Recognition Serivce is “Off”

- Class of Service is “100”

- Class of Restriction is “100”

- Baud Rate is “300”

- Intercept Number is “35”

- Non-dial In Trunks Answer Point(s) are all blank

- Dial In Trunks Incoming Digit Modification – Absorb is “0”

- Dial In Trunks Incoming Digit Modification – Insert is blank

- Trunk Label is blank

The IP trunk calls originated via the “Direct IP Route” ARS routing medium default to use COR Group 65 and Digit Modification number 805. You can select different values, but typically should not have to.

You can change COS 100 parameters, restrictions for COR Group 65, restrictions for Interconnect 65 and define intercept handling for Intercept 35.

To program Direct IP routes:

1. License and Option Selection form

- Ensure that the System Type is "Enterprise" for each element in the network/cluster. (Required for IP Networking.)

2. Shared System Options form

- Set the DPNSS/QSIG Diversion Enabled option to "Yes".

- Repeat on each element in the network/cluster.

3. Ensure that IP Networking/XNET Planning has been completed.

4. Plan initial ARS programming (in the ARS Leading Digits, ARS Digits Dialed, ARS Routes, ARS Route Lists, ARS Route Plans, and ARS Digit Modification Plans forms) for DID calls to ensure a proper ARS path is created for IP trunking calls. Actual programming is done later in the procedure.

5. Network Elements form

- Add the MiVoice Business system making sure to assign it a unique PBX number. This automatically adds an entry in the ICP/PBX Networking form.

6. ICP/PBX Networking form

- Select the entry for the local MiVoice Business system from the list at the top of the form.
  Note: The system must be in the Network Elements form for it to appear in the list.

- Set the Local ICP/PBX field to Yes (for local MiVoice Business system only).

- (Optional) Add the Network Element name to the Comment field for identification purposes (helps if you need to change entries later on).

6. Enter the number of IP trunking calls that can be supported concurrently between the remote system and this system in the Max IP Trunk Calls to ICP/PBX field.

7. Click the IP Networking tab, (optional) enter an Inactivity Timer value to have the remote MiVoice Business system terminate the IP connection to the local MiVoice Business system if there are no calls in progress for duration of the timer.

8. Repeat for each remote MiVoice Business system listed.

The remaining fields on the ISDN Networking and PSTN Voice Channel Digits tabs do not apply to IP Networking.

7. ARS Routes form on the local (master) element

- Select the route number designated in the planning stage, and the click Change.

- Set the routing medium to Direct IP Route.

- Select the PBX Number/CEID Element ID of the destination element for calls taking this route.

- Click Save.

8. ARS Digits Dialed form on the local (master) element

- Click Add.

- In the Digits Dialed box, enter digits that match the remote element's CEID digits. Set the Number of Digits to Follow to the planned value, the Termination Type to Route and in the Termination Number box, enter the route number that corresponds to the ARS route to the remote element.

- Click Save.

9. Repeat steps 6 and 7 for each element in the cluster, entering the master element's CEID digits in the PBX Number/CEID Element ID (ARS Routes form) and Digits Dialed (ARS Digits Dialed) boxes.

### Using the traditional method (IP/XNET trunk groups and profiles)

1. Complete steps 1 through 6 of the Direct IP Route method.

2. Trunk Attributes form

Use this form to assign a trunk service number (required for the Trunk Profile form). Select an unused Trunk Service Number:

6. Assign a Class of Service

7. Assign a Class of Restriction

8. Set incoming trunks to a "Non-Dial-In Trunks Answer Point" or set the "Dial-In Trunks Incoming Digit Modification Absorb" field to '0'. If you set the "Dial-In Trunks Incoming Digit Modification Absorb" field to '0', ensure that it is also set to '0' in the Trunk Attributes form of the destination switch.

9. If specifying an answer point, enter a directory number as the answer point for Day Service, Night Service 1, and Night Service 2.

10. (Optional) Assign a Trunk Label to appear on display telephones and attendant consoles during incoming and outgoing calls.

3. IP/XNET Trunk Profiles form

- Program the trunk service number and interconnect restriction parameters specific to IP Networking/XNET. The Remote Profile Number field must be filled with the Local Profile Number of the Remote system.

4. IP/XNET Trunk Groups form

- Set up the desired IP/XNET trunk groups. The Remote system number is the unique number previously assigned.

- Set the Network Signaling Type and Voice Medium fields to "IP".

- Complete the Number of Trunks field. If more than one XNET trunk group is created to this remote PBX, the total of all trunks assigned in the form should not exceed the Max IP Trunk Call to ICP/PBX field of the ICP/PBX Networking form.

5. ARS Routes form

6. Set up the IP/XNET Trunk Groups using the numbers assigned in the IP/XNET Trunk Groups form. Ensure that no trunk group numbers are assigned, only IP/XNET Trunk Group numbers. Set Compression as required for the IP trunks of the route.

- Complete normal ARS programming for the destination numbers on each Remote system.

7. ARS Leading Digits ( ) and the ARS Digits Dialed ( ) forms

- Program the destination numbers using the Route Number.

Related Topics

- IP Networking/XNET Description

- IP Networking/XNET Call Processing

- IP Networking/XNET Compression

- IP Networking/XNET Planning

- XNET Programming