# ICP/PBX Networking

## Purpose

The ICP/PBX Networking form is used to set up signaling links between systems and to establish how long the signaling session will stay up after the call clears down. It is also used to program the incoming and outgoing digits used for XNET call B-channel setup.

The form must be programmed for each system, including the local system, that will communicate using remote messaging. Refer to IP Networking or XNET for programming instructions.

Use this form when performing the following tasks:

- IP Networking Programming

- XNET Programming (see XNET Programming Example)

For more information:

- IP Networking/XNET Description

- IP Networking/XNET Planning

NOTES

- The information in this form replaces the former Network Signaling PLID and Network Signaling IP fields in the System Access Points form.

- A ICP/PBX networking entry cannot be deleted if it is referenced in another networking-related form or an ARS form—for example, the IP/XNET Trunk Group form or the ARS Routes form. You must delete the element or its PBX number from the Network Elements form or the reference(s) to it in the other form(s). The system identifies which forms they are when you try to delete the entry in this form.

- ICP/PBX Networking entries are added automatically by configuring MiVoice Business Network Element entries with unique PBX Numbers/CEIDs in the Network Elements form. Conversely, ICP/PBX Networking entries are not automatically deleted by the Network Element form. Deletion of ICP/PBX Networking entries must be performed in ICP/PBX Networking form.

IMPORTANT: The ICP/PBX Networking form must be completed before creating resilient users. Otherwise, a reboot will be required after the Network IP addresses of the MiVoice Business systems are entered in this form.

## Field Descriptions

Parameter | Description | Default Value
Profile
ICP/PBX Number | The unique network ID number (in the range 1 to 999) assigned to systems in the Network Elements form. Change the number only if necessary to clean up programming where there are blank and/or duplicated PBX Numbers assigned to Network Elements in the Network Element form. NOTES Entry of a unique ICP/PBX Number with a matching entry in the Network Elements form is mandatory for IP Trunking, XNET, and cluster elements, but not enforced by the system in MCD Release 5.0. Enforcement will come in a future release. In the meantime, a message box will display each time the form is opened (unless you use the check box to stop it) as a reminder to comply with this new requirement. In a clustered, redirected, or resilient environment, the PBX Number must match the CEID Index Number defined in the Cluster Elements form. Changes to the ICP/PBX number for cluster elements must be made in the Network Elements form. Furthermore, the changes must be made from a member of the same cluster where all members are sharing with each other and running MCD Release 5.0. For non-clustered elements with unique PBX numbers, you are advised to make any numbering changes in the Network Elements form since the form is shared with other MiVoice Business systems in the same SDS community. If the PBX number is duplicated, then you should change the PBX number in the Network Element form first, and then in the ICP/PBX Networking form of each MiVoice Business system in the cluster. The ICP/PBX Networking form is not shared by SDS and so must be manually updated. For more recommendations, see Tips on Assigning and Changing PBX Numbers. | Populated by the Network Elements form.
Network Element | System generated, protected field. This is the name of the element as entered in the Network Elements form. A blank field indicates that either the element's ICP/PBX number is duplicated or missing in the Network Elements form. |
Local ICP/PBX | Select "Yes" if this form pertains to the Local system. | No
Max Number of VoIP Calls | The total number of VoIP sessions (calls) allowed between two ICPs/PBXs, one local and the other remote, that use IP as the voice medium. The total includes both incoming and outgoing calls. Values can be between "0" and "2000" for all MiVoice Business systems. A value of "0" suppresses IP trunking calls to the remote ICP/PBX. NOTE: This value must be the same for the local and remote systems. |
Max Number of VoTDM Calls | The total number of VoTDM sessions (calls) allowed between two ICPs/PBXs, one local and the other remote, that use TDM as the voice medium. The total includes both incoming and outgoing calls. Values can be between "0" and "2000". A value of "0" suppresses TDM trunking calls to the remote ICP/PBX. NOTE: This value must be the same for the local and remote systems. This field can only be programmed if the IP Network Location ID field in the ICP/PBX Networking form has been programmed. |
Zone ID | The number of the network zone (in the range 1 to 999) for IP voice media originating or terminating at the MiVoice Business system. This also specifies the default zone of the system. |
Comment | Enter information to identify the system. This field accepts up to 25 characters. | Blank
IP Networking |
Inactivity Timer (hh:mm:ss) | Performs the same function as the ISDN Network Inactivity timer described below. | Blank
QSIG Network Features Only | Select "Yes" if the PBX being connected uses the QSIG network features. NOTE: The "Local ICP/PBX" field must be set to No. |
ISDN Networking
ISDN IP Address | The ISDN IP address is required for the local MiVoice Business system when using PPP signaling (over ISDN PRI B-Channel). An ISDN IP address is not required for the remote MiVoice Business system (i.e., systems configured as "Local ICP/PBX = No"). The address does not have to be a "real" globally unique IP address, but should be unique within the XNET network. Repeat the same configuration on the other MiVoice Business systems in the PPP XNET network. | Blank
Signaling Location ID | Enter the Location ID or PLID of the PRI card supporting XNET PPP signaling. Only program this field when the Local ICP/PBX field is set to "Yes". | Blank
ISDN Network Signalling Digits to Dial | Enter the digits to dial to make an ISDN PRI call to support PPP signaling to this specific ICP/PBX. If the Local ICP/PBX field is set to "Yes", only program this field if loop-back calls to this PBX using PPP signaling are desired. NOTE: This field is mandatory for remote ICP entries. | Blank
ISDN Network Signaling Answer Point Digits | Enter the answer point digits that when received over PRI will set up PPP signaling to this PBX. Only program this field when the Local ICP/PBX field is set to "Yes". If you need to change programming for a non-local member you must delete any answer point digits from this field. | Blank
Inactivity Timer (hh:mm:ss) | Enter the length of time a signaling link should be kept up to the remote system after the last call using it clears down. The default value is blank, which indicates that the signaling link will be kept up indefinitely. The time can be set between 0 and 23 hours, 59 minutes, and 59 seconds at a 1 second resolution. A value of "0" indicates that the link should be cleared immediately after the last call using it clears. If the values programmed on the two switches are not set to the same value, the longer of the two values is used. In the extreme situation, when one the timer is set to a short value (say 5 seconds) at one end of the link, and the timer is not programmed at the other end, the default value for this field is blank, indicating that the link should be left up forever. | Blank
PSTN Voice Channel Digits
Outgoing Call Digits to Dial | The digits to be dialed from an originating system. | Blank
Outgoing Call Answer Point Digits | The answer point digits to be used by this system when setting up MSDN/DPNSS B-channel calls to remote systems in the network. | Blank
Incoming Call Answer Point Digits | The answer point digits of the incoming DID numbers used by remote systems to set up the MSDN/DPNSS B-channel calls to this system. | Blank