There are three basic environments that the Elite Gateway* can be applied to. They are described in the following sections.

Application A: FXS
Application A has two possible connections. The A-1 connection shows the connection between the gateway and telephone set (POTS) or FAX machine. The FXS module is used in the A-1 connection. The A-2 connection on the right hand side is used to connect the gateway and PBX that has the Central Office (CO) trunk interface. FXS is also used in this connection. The telephone sets connected to the PBX can be either POTS or digital telephone depending upon the PBX capability.

Application B: FXS/FXO Combination
Application B has three possible connections. The B-1 connection is a normal trunk connection between the CO switch and a PBX. The B-2 connection is identical to the A-1 connection mentioned in Application A. The B-3 connection is used to connect the PBX and gateway through the internal analog lines provided by the PBX. In this case, the FXO module has to be used and the FXO ports will serve the same roles as the analog telephone sets.

Note: If the PBX used in the B-3 connection is a digital type an analog terminal adapter is needed to provide an analog interface to the FXO module.

In this application the caller in the B-2 connection can use the gateway through its FXS module to communicate with the party on the other end of the B-3 connection. The phone call is forwarded through the FXS module in the B-2 Gateway and is received by the FXO module in the B-3 gateway, which is connected to the PBX, which will then switch to the dedicated terminal.

The same caller can also use the feature that the Gateway provides to redial the local number through the PBX to the public switch in order to reach the person inside the region that the public switch serves.

Application C: FXS/FXO Extended Combination
Application C has four possible connections. The C-1 connection is a normal trunk connection between the CO switch and PBX (identical to connection B-1 in the previous application) The C-2 connection is identical to the A-1 connection mentioned in Application A. The C-3 connection connects the PBX and gateway through the internal analog line provided by the PBX (identical to the B-3 connection). The C-4 connection connects the CO switch to the gateway using the FXO module (similar to the C-3 connection).

The C-2 connection can be replaced by the C-3 connection, but it must then use an FXO module instead of an FXS module. In this application, the user can benefit from the VoIP application even when not in the office. With a properly configured dial plan, the user can make a phone call through a public switch back to the office, and the PBX will relay the phone call to the other end which may be located in another city, state, or even country.

Configuration Examples

Scenario 1 description

1. 3 sets of Elite Gateways are connected to Internet. One of Elite Gateways has an FXO module and the other two are equipped with an FXS module.
2. Telephone address description
   • Elite Gateway A: 408 and 415 are address specific PSTN connections on PBX CO trunk, and 90 are address specific connections on PBX internal lines on Elite Gateway A FXO ports
   • Elite Gateway B: 0900, 0901, 0902, 0903 are specific telephone address on Elite Gateway B FXS ports
   • Elite Gateway C: 0800, 0801, 0802, 0803 are specific telephone address on Elite Gateway C FXS ports

Elite Gateway A hunt group table

Group id Type #Members Member ids 1 2 4 1 2 3 4 11 2 1 11 12 2 1 12

Elite Gateway A destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 11 H.323 Dest = 210.243.230.20/1720 TCP 12 H.323 Dest = 210.243.230.30/1720 TCP

Elite Gateway B address translation table

Address Entry Hunt Grp_Id Min. Digits Max. Digits Prefix strip Prefix Address 0900 1 4 4 0 None 0901 2 4 4 0 None 0902 3 4 4 0 None 90 11 0 6 0 None 408 11 0 10 0 None 415 11 0 10 0 None 08 12 4 4 0 None

Elite Gateway B hunt group table

Group id Type #Members Member ids 1 2 1 1 2 2 1 2 3 2 1 3 4 2 1 4 11 2 1 11 12 2 1 12

Elite Gateway B destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 11 H.323 Dest = 210.243.230.10/1720 TCP 12 H.323 Dest = 210.243.230.30/1720 TCP

Elite Gateway C address translation table

Address Entry Hunt Grp_Id Min. Digits Max. Digits Prefix strip Prefix Address 0800 1 4 4 0 None 0801 2 4 4 0 None 0802 3 4 4 0 None 0803 4 4 4 0 None 90 11 0 6 0 None 408 11 0 10 0 None 415 11 0 10 0 None 09 12 4 4 0 None

Elite Gateway C hunt group table

Group id Type #Members Member ids 1 2 1 1 2 2 1 2 3 2 1 3 4 2 1 4 11 2 1 11 12 2 1 12

Elite Gateway C destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 11 H.323 Dest = 210.243.230.10/1720 TCP 12 H.323 Dest = 210.243.230.20/1720 TCP

Note: An FXO module was added to both Elite Gateway B and Elite Gateway C.

Scenario 2 description:

1. 3 sets of Elite Gateways were connected to Internet and all of Elite Gateways are built-in FXO and FXS modules.
2. Telephone address description:
   • Elite Gateway A: 408 and 415 are address specific PSTN connections on PBX CO trunk, and 90 are address specific connections on PBX internal lines on Elite Gateway A FXO ports
   • Elite Gateway B: 0900, 0901, 0902, 0903 are address specific telephone on Elite Gateway B FXS ports and 932 and 934 are address specific PSTN connections on Elite Gateway B FXO ports
   • Elite Gateway C: 0800, 0801, 0802, 0803 are address specific telephone on Elite Gateway C FXS ports and 712 are address specific PSTN connections on Elite Gateway C FXO ports

Elite Gateway A address translation table

Address Entry Hunt Grp_Id Min. Digits Max. Digits Prefix strip Prefix Address 90 1 0 6 2 None 408 1 0 10 3 "0" 415 1 0 10 0 "0" 09 11 4 4 0 None 08 12 4 4 0 None 932 11 10 10 0 None 934 11 10 10 0 None 712 12 10 10 0 None

Elite Gateway A hunt group table

Group id Type #Members Member ids 1 2 4 1 2 3 4 11 2 1 11 12 2 1 12

Elite Gateway A destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 11 H.323 Dest = 210.243.230.20/1720 TCP 12 H.323 Dest = 210.243.230.30/1720 TCP

Elite Gateway B address translation table

Address Entry Hunt Grp_Id Min. Digits Max. Digits Prefix strip Prefix Address 0900 1 4 4 0 None 0901 2 4 4 0 None 0902 3 4 4 0 None 0903 4 4 4 0 None 90 11 0 6 0 None 408 11 0 10 0 None 415 11 0 10 0 None 08 12 4 4 0 None 932 5 10 10 3 None 934 5 10 10 0 None 712 12 10 10 0 None

Elite Gateway B hunt group table

Group id Type #Members Member ids 1 2 1 1 2 2 1 2 3 2 1 3 4 2 1 4 5 2 4 5 6 7 8 11 2 1 11 12 2 1 12

Elite Gateway B destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 5 Local PORT = 4 6 Local PORT = 5 7 Local PORT = 6 8 Local PORT = 7 11 H.323 Dest = 210.243.230.10/1720 TCP 12 H.323 Dest = 210.243.230.30/1720 TCP

Elite Gateway C address translation table

Address Entry Hunt Grp_Id Min. Digits Max. Digits Prefix strip Prefix Address 0800 1 4 4 0 None 0801 2 4 4 0 None 0802 3 4 4 0 None 0803 4 4 4 0 None 90 11 0 6 0 None 408 11 0 10 0 None 415 11 0 10 0 None 09 12 4 4 0 None 712 5 10 10 3 None 932 12 10 10 0 None 934 12 10 10 0 None

Elite Gateway C hunt group table

Group id Type #Members Member ids 1 2 1 1 2 2 1 2 3 2 1 3 4 2 1 4 5 2 4 5 6 7 8 11 2 1 11 12 2 1 12

Elite Gateway C destination table

Dest id Mode Destination 1 Local PORT = 0 2 Local PORT = 1 3 Local PORT = 2 4 Local PORT = 3 5 Local PORT = 4 6 Local PORT = 5 7 Local PORT = 6 8 Local PORT = 7 11 H.323 Dest = 210.243.230.10/1720 TCP 12 H.323 Dest = 210.243.230.20/1720 TCP

This applies to:

Elite Gateway*