# IP Networking/XNET Planning

- Create a numbering scheme to provide each system with a unique ID number (valid numbers are from 1 to 999). The numbers are used to distinguish between systems when entering information in the forms.

NOTES

- If you plan to program both IP Networking and XNET, keep in mind that they use the same IP addresses and that XNET requires IP addresses to be at least 64 numbers apart. (The PRI card ignores the last 6 binary digits and cannot distinguish between two IP addresses within a 64 number range.) If IP addresses on the network do not meet this requirement, you'll need to re-configure IP addresses before enabling XNET.

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

## Conditions and Feature Interactions

- Each system must be assigned a unique ID.

- For IP Trunking, real IP addresses must be assigned.

- Devices on a network of systems using IP Networking or XNET must have unique IP addresses.
  If IP trunking is used, ensure that the IP addresses differ from those on the data network. With IP trunking, these IP addresses are exposed and will cause conflicts if not unique.

- Maintenance support is provided for the Message, Resources, Rmessage, Busy, Return to Service, and State commands.

- The total number of both real and virtual IP trunking and conventional (PSTN B-channel) XNET calls that can be concurrently supported on an ICP is 2000.

- The maximum simultaneous signaling connections for IP XNET is 200.

Related Topics

- IP Networking/XNET Call Processing

- IP Networking/XNET Compression

- IP Networking/XNET Description

- XNET Programming

- IP Networking Programming