# PBX 101 programming

## 1) ARS Digits Dialed

Two route numbers must be defined in this form.

- Digit string "916135552001" is needed to set-up a data call to PBX 102.

- Route number 60 was assigned for data call set-up to PBX 102.

- Digit string "916135552002" is needed to set-up a voice call to PBX 102.

- Route number 60 was assigned for data call set-up to PBX 102.

Digits Dialed | # of Digits to Follow | Termination Type | Number
916135552 | 3 | Route | 60

## 2) ARS Routes

This form is used to assign Trunk Group Number, COR group Number, and Digit Modification to the Route Numbers defined in the ARS Digits Dialed form (just as you would with any, normal PRI trunk group).

Route # | Trunk Group # | COR Group # | Digit Modif. # | Digits Before Outpuls. | XNET Trunk Group # | Route Type | Compr.
60 | 3 | 1 | 1 | -- | -- | -- | --

## 3) ARS Digit Modification Plans

- A digit modification plan to absorb the "9" digit must be defined.

- A digit modification plan to absorb no digits must be defined.

Digit Modification # | # of Digits to Absorb | Digits to be Inserted | Final Tone Plan/Information Marker
1 | 1 | -- | --
10 | 0 | -- | --

## 4) ICP/PBX Networking

This form is used to set-up the Data channel signaling links between systems. Two entries are required, one for the "local system" (PBX 101) and one for the "remote system" (PBX 102).

Local system:

- PBX number "101" was entered in PBX Number.

- Local PBX set to "Yes".

- The unique IP address "101.101.101.101" was entered to identify the local PBX.

- The digits "9 1 2" were entered in the ISDN Network Signaling Location ID field to identify the ISDN card that will the PRI link, by cabinet, shelf and slot number.

- For the local system, ISDN Network Signaling Digits to dial are not required.

- The digits "1001" were entered into the ISDN Network Signaling Answer Point digits field to specify the digits that when received over PRI will set up PPP signaling to PBX 101.

- The ISDN Network Inactivity Timer was set to 15 seconds for this example.

Remote system:

- PBX number "102" was entered in PBX Number.

- Local PBX was set to "No" (indicating that this entry is "remote").

- The unique IP address "101.101.102.102" was entered to identify the remote PBX.

- For the remote system, ISDN Network Signaling Location ID is not required.

- The digits "916135552001" were entered into ISDN Network Signaling Digits to Dial to specify the digits needed to make an ISDN PRI call to PBX 101.

- The ISDN Network Inactivity Timer was set to match the value of the local system.

PBX Number | Local PBX | Network IP Address | IP Netw. Location ID | ISDN Netw. Sign. Location ID | ISDN Netw. Sign. Digits to Dial | ISDN Netw. Sign. Answer Point Digits | ISDN Netw. Inactivity Timer
101 | Yes | 101.101.101.101 | 1 | 9 1 2 | -- | 1001 | 00:00:15
102 | No | 101.101.102.102 | -- | -- | 916135552001 | -- | 00:00:15

## 5) XNET ICP/PBX Networking

This form is needed to set-up the voice channel signaling links between systems. Two entries are required, one for the "local system" (PBX 101) and one for the "remote system" (PBX 102).

Local system:

- ICP/PBX number was copied from the ICP/PBX Networking form

- Local PBX set to "Yes".

Remote system:

- ICP/PBX number was copied from the ICP/PBX Networking form.

- Local PBX set to "No".

- A value of 100 was entered into MAX # of VoIP Calls for this example.

- A value of 100 was entered into Max Number of VoTDM calls to specify to maximum number of both incoming and outgong calls that can be can set-up between the PBXs.

- The digits "916135552002" were entered into Outgoing Call Digits to Dial field to specify the complete digit string needed to establish a voice call with PBX 102.

- The digits "2002" were entered in the Outgoing Call Answer Point Digits field to specify the digits needed to set-up voice calls to PBX 102.

- The digits "1002" were entered in the Incoming Call Answer Point Digits field to specify the digits of the incoming DID numbers used by PBX 102 to set up voice calls to this system.

ICP/PBX Number | Local ICP/PBX | Max # of VoIP Calls | Max # of VoTDM Calls | Outgoing Call Digits to Dial | Outgoing Call Answer Point Digits | Incoming Call Answer Point Digits
101 | Yes | -- | -- | -- | -- | --
102 | No | 100 | 100 | 916135552002 | 2002 | 1002

## 6) Trunk Attributes

This form is needed to assign Class of Service, Class of Restriction, Baud Rate, Intercept Numbers and a Trunk Label to the XNET trunks.

Trunk Service # | Release Link Trunk | Class of Service | Class of Restriction | Baud Rate | Intercept Number | Non-dial In Trunks Answer Point - Day | Non-dial In Trunks Answer Point - Night 1 | Non-dial In Trunks Answer Point - Night 2 | Dial In Trunks Incoming Digit Modification - Absorb | Dial In Trunks Incoming Digit Modification - Insert: | Trunk Label
25 | No | 1 | 1 | 300 | 1 | -- | -- | -- | 0 | -- | --

## 7) IP/XNET Trunk Profiles

This form is used to program trunk service or interconnect restriction parameters specific to XNET.

- The Trunk Service Number assigned in the Trunk Attributes form was copied to the Trunk Service Number form.

- Interconnect Number was set to 1 for this example.

- Remote Profile Number was set to 1 for this example.

Local Profile Number | Trunk Service Number | Interconnect Number | Remote Profile Number | Comment
1 | 25 | 1 | 1 | Toronto

## 8) IP/XNET Trunk Groups

This form groups XNET trunks together for ARS purposes.

- XNET Trunk is system generated.

- The PBX number for PBX 102 was entered.

- Local Profile number "1" was copied from the IP/XNET Trunk Profiles form.

- For this example, "15" was entered for Maximum Network Hops.

- Network signalling Type must be set to "ISDN".

- Voice Medium Type must be set to "TDM".

- For this example, "20" was entered for Number of Trunks.

XNET Trunk Group # | PBX Number | Local Profile Number | Maximum Network Hops | Network Signaling Type | Voice Medium Type | Number of Trunks | Comments
10 | 102 | 1 | 15 | ISDN | TDM | 20 | Toronto

## 9) Final Route Assignment

This form must be used to create a route for the XNET calls.

- Route # is system-generated.

- Trunk Group # is not needed for this example.

- COR Group # "1" was assigned for this example.

- Digit Modification number "1" (defined in the ARS Digit Modification Plans form) was entered since we plan to absorb 0 digits.

- XNET trunk Group number 10 was entered (from the IP/XNET Trunk Groups form).

Route # | Trunk Group # | COR Group # | Digit Modif. # | Digits Before Outpuls. | XNET Trunk Group # | Route Type
20 |  | 1 | 10 | -- | 10 | --

## 10) Final ARS Digits Dialed

ARS programming allows the user to dial PBX 102.

- The Digits Dialed must be set to "2" since extension numbers on PBX 102 begin with "2".

- The Number of Digits to Follow must be set to "3" for a four-digit numbering plan.

- Termination Type Route must be selected for this example.

- The route Number (as defined in the ARS Routes form) must be set to point to the correct route (20).

Digits Dialed | Number of Digits to Follow | Termination Type | Number
2 | 3 | Route | 20