# Programming Hybrid XNET Trunks

## Description

This feature is useful where LAN infrastructure exists, but the available bandwidth is not adequate for full voice-over-IP support. In such situations, voice quality over the LAN may be poor, so the alternative approach of carrying voice over TDM may be the best solution.

NOTES

- The TDM XNET feature is not supported in MiVoice Business 9.0.

- Hybrid XNET is available on all digital trunks, including both single and dual embedded T1/E1 modules.

- The Hybrid XNET feature is not supported on an EX Controller.

## Programming

1. Program ARS, trunks, trunk groups, etc. for the TDM trunks to be used for the hybrid XNET B channels.

2. Ensure that the System Type is "Enterprise."

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

4. 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) must be completed to ensure a proper ARS path is created for IP trunking calls.

5. ICP/PBX Networking form

- Assign a PBX Number to each element. The PBX Number must match the element's CEID index (from the element's Cluster Elements form ( ). Program the Local system first (Local ICP/PBX field = "Yes"), and then the remote systems. Enter the unique IP address of the system in the Network IP Address field. The rest of the fields in this form do not apply to Hybrid XNET.

NOTES

- When programming both IP Networking and XNET, all XNET IP restrictions apply to the range of IP addresses used on the MiVoice Business RTC. Each MiVoice Business controller requires an IP address to identify the different units and uses a fixed effective subnet mask of 255.255.255.192. IP addresses between units must be different than the effective mask. Refer to the MiVoice Business Engineering Guidelines for examples.

- It is recommended that the ISDN Network Inactivity timer (ICP/PBX Networking form) for IP signalling be set to a few seconds (for example, 30 seconds) if the expected traffic rate is low, an hour or more if the traffic rate is moderate, or be left blank if the rate is high. This ensures that the socket once established for the IP session will remain open to minimize subsequent call setup delays should the socket close following an idle period.

- DID numbers are used to set-up outgoing XNET calls. Once these calls are set-up, the DID numbers are freed up, so you should reserve enough of them to handle the expected peak number of simultaneous call set-ups.

1. CAUTION: In a Clustered environment, the PBX Number for each element must match the element's CEID index.

6. ICP/PBX Networking form

Program the local switch by pressing Add, typing the local ICP/PBX number, and, optionally, entering a comment.

6. Enter the ICP/PBX Number as defined in the ICP/PBX Networking form.

7. If IP trunking is to be used between the local system and this remote system, enter the number of IP trunking calls that can be supported concurrently between the remote system and this system in the "Max Number of VoIP Calls" field. This value must be the same for the local and remote systems.

8. Enter the number of TDM trunking calls that can be supported concurrently between the remote system and this system in the "Max Number of VoTDM Calls" field. This value must be the same for the local and remote systems.

9. Enter the digits to be dialed from an originating system in the Outgoing Call Digits to Dial field. These digits may be modified by digit modification at the originating system, the CO, or at the terminating system.

10. Enter the Answer Point of the outgoing DID numbers to be used when setting up MSDN/DPNSS B-channel calls to Remote systems in the network in the Outgoing Call Answer Point Digits field.

11. Enter the Answer Point of the DID numbers to be used by the remote system when setting up MSDN/DPNSS B-channel calls to this system in the Incoming Call Answer Point Digits field.

7. Trunk Attributes form

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

7. Assign a Class of Service

8. Assign a Class of Restriction

9. Set incoming trunks to a "Non-Dial-In Trunks Answer Point" or set the "Dial-In Trunks Incoming Digit Modification Absorb" field to '0'.

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

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

8. 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.

9. IP/XNET Trunk Groups form

- Set up the desired IP/XNET trunk groups. The Remote system number is the unique number previously assigned. The Voice Medium type must be set to "TDM" for voice, "IP" for signaling.

10. ARS Routes form

- 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. The Compression field does not apply. Multiple routes may be programmed in order to accommodate IP trunking, TDM and hybrid XNET calls between a pair of systems and to allow different trunk profiles for the same type of trunking.

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

- 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

- Hybrid XNET Programming Example

- IP Networking Programming