FourteenIP T1 Gateway Configuration Guide

The FourteenIP T1GW bridges SIP services with T1-based carrier and PBX equipment. This guide shows how to generate and import the BroadWorks configuration, followed by complete setup procedures in this order:

1. Default SIP or Reverse SIP

2. EV Connect

3. EV Connect Pro

The EV Connect and EV Connect Pro routing tables are included as editable text inside their respective setup sections. Additional tag references, routing syntax, TLS settings, failover behavior, and acceptance tests follow the deployment procedures.

Scope: BroadWorks generates the site configuration, but the technician downloads and imports it manually. This is not zero-touch autoprovisioning.

1. Hardware and factory access

Product overview

The FourteenIP T1GW is a carrier-grade SIP-to-T1 gateway used to connect BroadWorks or EVA SIP services to traditional T1 carrier and PBX equipment. It provides hardware DSP processing, T1 signaling, SIP trunking, call routing, digit manipulation, fax relay, and SIP failover functions in a 1U platform.

Hardware specifications

The gateway GUI can expose both T1 and E1 choices. All deployment procedures in this guide use T1, mu-law, ESF, and B8ZS unless a documented site requirement states otherwise.

Physical installation and cabling

1. Mount the gateway in a grounded 19-inch rack with adequate airflow.

2. Connect protected AC power within the supported input range.

3. Connect the management Ethernet interface to the provisioning network.

4. For Default SIP, Reverse SIP, or EV Connect, connect the site’s single T1 circuit to Trunk 1.

5. For EV Connect Pro, connect the carrier/Vega circuit to Trunk 1 / ISDN 1 and the PBX circuit to Trunk 2 / ISDN 2. Label both cables before configuration so the ports are not reversed.

6. Do not assume that physical link indicates correct clocking or switch-side configuration. Confirm the DS1 link, D channel, and bearer channels after the software configuration is complete.

Factory network and credentials

Connect a workstation to the factory subnet and browse to:

https://192.168.2.240

The factory certificate can cause a browser warning. Continue only after confirming that the address belongs to the gateway being configured.

Factory SSH access

SSH is enabled by default on port 22. Connect with:

ssh (contact support for user)@<gateway-IP-address>

Use the factory SSH credentials:

For administrator access, enter (contact support) and use the factory administrator password (contact support) when prompted. Change or secure factory credentials according to the approved deployment procedure after installation.

2. BroadWorks configuration and file download

Create the BroadWorks assignment

1. Create the required trunk and pilot user in BroadWorks.

2. Select FourteenIP_T1GW as the Identity/Device Profile Type.

3. Confirm the trunk-group identity, pilot authentication user, password, SIP domain, and Calling Line ID values.

4. Open the assigned Identity/Device Profile.

5. Select Custom Tags.

6. Enter the site network, country-tone, and time-zone values described in Section 8.

7. Save the profile.

BroadWorks displays tag names without surrounding percent signs. In the template, the same value appears as %TAG_NAME%.

Rebuild and select the deployment file

1. Open the Identity/Device Profile Files tab.

2. Click Rebuild the files when the profile or tag values have changed.

3. Wait for the rebuild to complete.

4. Locate the file for the required deployment.

5. Download the Repository File, not the Template File.

Use the complete generated filename shown by BroadWorks. Every gateway import file must be an .ini file.

Screenshot note: Some beta screenshots show the former Redstone profile name or an earlier device-type label. Production profiles display FourteenIP_T1GW; the Files-tab workflow and deployment file labels remain the same.

3. Import the BroadWorks file

1. Sign in to the gateway at its current management address.

2. Navigate to Tools > Configuration Maintenance.

3. Under Import data, click Choose File.

4. Select the downloaded BroadWorks Repository File.

5. Click Import.

6. When the confirmation page appears, click Next.

7. Confirm that the upload completes successfully.

8. Do not interrupt power or network connectivity during the import.

9. Reboot when prompted.

10. Reconnect using the imported static IP address and post-import administrator password.

4. Deployment profiles

5. Default SIP and Reverse SIP setup

Default SIP and Reverse SIP use Per SIP trunk registration. Reverse SIP follows the same process with TDM 1 timing and the Trunk 1 switch side set to User.

Step 1 – Configure SIP registration

1. Navigate to Basic > SIP.

2. Enter the assigned Registrar server, Proxy server, SIP domain, and signaling port.

3. Set SIP Registrar mode to Per SIP trunk.

4. Click Save.

5. Open Basic > SIP Repeater, which becomes available after Per SIP trunk mode is saved.

6. Enter the trunk registration username, authentication name, password, and registration expiration.

The screenshot identifies the Basic SIP fields. Use the assigned BroadWorks values and select Per SIP trunk for Default SIP and Reverse SIP.

Step 2 – Configure the DS1 interface

Navigate to Basic > DS1 configuration.

Disable the unused second T1 interface.

Step 3 – Configure Trunk 1 and P-Preferred-Identity

Navigate to Trunk > Trunk 1.

Enter P-Preferred-Identity in this exact format:

<sip:TRUNK-IDENTITY@SIP-DOMAIN>

Example:

<sip:3213061506@dmstg.ev.com>

Step 4 – Configure Advanced SIP for PPI

Navigate to Advanced > SIP.

Step 5 – Configure site routing and test

Open Routing > Routing table and apply the routing table approved for the Default SIP or Reverse SIP site. Save the table, then verify registration, T1 link state, inbound calling, outbound calling, caller ID, DTMF, audio, and disconnect behavior.

6. EV Connect setup

EV Connect uses one T1 interface for the PBX and Per gateway EVA registration.

Step 1 – Configure EVA registration

1. Navigate to Basic > SIP.

2. Enter the EVA Registrar server, Proxy server, subdomain, username, authentication name, password, and registration expiration.

3. Set SIP Registrar mode to Per gateway.

4. Configure TLS, SRTP, DNS SRV, and NAPTR as described in Section 10.

5. Click Save.

Step 2 – Configure DS1, Trunk 1, and PPI

1. Under Basic > DS1 configuration, use T1, mu-law, Local timing, ESF, B8ZS, Short haul/110 ft, and ISDN unless the site requires CAS.

2. Disable the unused second T1 interface.

3. Under Trunk > Trunk 1, set the switch side to Network.

4. Use Timeslot 24, NI-2, Forward hunting, and B channels 1 through 23.

5. Enter the EVA P-Preferred-Identity on Trunk 1 in the form <sip:EVA-USER@EVA-DOMAIN>.

Step 3 – Configure Advanced SIP

Navigate to Advanced > SIP and enable IMS, select PPI, leave Username add domain unchecked, enable Re-register on INVITE failure, and apply the tested Via-validation setting.

Step 4 – Enter the EV Connect routing table

Replace the site-specific examples before saving:

Navigate to Routing > Routing table and paste these editable rules:

ISDN[1] 933 REPLACE CPN-4/3213061530
ISDN[1] 933 END
ISDN[1] 141414 REPLACE CPN0/EVAJUPITER
ISDN[1] 141414 END
ISDN[1] 141415 REPLACE CPN0/EVAJUPITER
ISDN[1] 141415 END
ISDN[1] CPNXXXXXXX END
ISDN[1] CPNX REPLACE 3213061541
ISDN[1] X END
IP CPNEVAJUPITERX REMOVE 10
IP[127.0.0.1] 141414 REPLACE 7368
IP[127.0.0.1] 141414 ROUTE ISDN 1
IP[127.0.0.1] 141415 REPLACE 7368
IP[127.0.0.1] 141415 ROUTE ISDN 1
IP EVAJUPITERX REMOVE 10
IP X ROUTE ISDN 1

The table is editable text. Technicians can copy it, replace site values, or remove rules that are not approved for the deployment.

Step 5 – Validate EV Connect

• PBX calls to 141414 and 141415 reach EVA.

• EVA transfers reach PBX extensions with and without Alternate Trunk ID.

• Seven-or-more-digit caller IDs remain unchanged.

• Short extension caller IDs use the site outbound caller ID.

• 933 reads back the expected emergency caller ID and registered address.

• When EVA is unreachable and the gateway returns the failed call locally, both EVA numbers reach the PBX fallback extension.

• When EVA connectivity returns, calls return to the normal EVA path.

7. EV Connect Pro setup

EV Connect Pro physically separates the carrier and PBX paths:

Carrier/Vega <-> Trunk 1 / ISDN 1 <-> FourteenIP T1GW <-> Trunk 2 / ISDN 2 <-> PBX
                                                    |
                                                    +---- SIP/TLS ---- EVA

Trunk 1 faces the carrier and operates as User. Trunk 2 faces the PBX and operates as Network.

Step 1 – Configure EVA registration

1. Navigate to Basic > SIP.

2. Enter the EVA Registrar server, Proxy server, subdomain, registration username, authentication name, password, and registration expiration.

3. Select Per gateway.

4. Apply the TLS settings in Section 10.

5. Click Save.

Step 2 – Configure both DS1 interfaces

Navigate to Basic > DS1 configuration.

Step 3 – Configure Trunk 1 for the carrier

Navigate to Trunk > Trunk 1 and configure:

Step 4 – Configure Trunk 2 for the PBX

Navigate to Trunk > Trunk 2 and configure:

Step 5 – Configure Advanced SIP for PPI

Navigate to Advanced > SIP and configure:

These settings allow the P-Preferred-Identity configured on both trunks to be used when calls move among the carrier, PBX, and EVA paths.

Step 6 – Enter the EV Connect Pro routing table

Replace the site-specific examples before saving:

Navigate to Routing > Routing table and change whatever your mainline, emergency number, CLID and fallback number will be for your specified site(Group IDs will already be assigned dynamically via Broadworks):

ISDN[1] 1530 REPLACE 141414
ISDN[1] 1530 END
ISDN[1] CPNX ADD 00
ISDN[1] X ROUTE IP 127.0.0.1:5060
ISDN[2] 141414 REPLACE CPN0/EVAJUPITER
ISDN[2] 141414 END
ISDN[2] 141415 REPLACE CPN0/EVAJUPITER
ISDN[2] 141415 END
ISDN[2] XXXXXXX ROUTE IP 127.0.0.1:5060
ISDN[2] XXXX END
ISDN[2] XXX ROUTE IP 127.0.0.1:5060
IP[127.0.0.1] CPN00 REMOVE 2
IP[127.0.0.1] CPN00 ROUTE ISDN 2
IP[127.0.0.1] 141414 REPLACE 7368
IP[127.0.0.1] 141414 ROUTE ISDN 2
IP[127.0.0.1] 141415 REPLACE 7368
IP[127.0.0.1] 141415 ROUTE ISDN 2
IP EVAJUPITERX REMOVE 10
IP EVAJUPITERX ROUTE ISDN 2
IP[127.0.0.1] CPNXXXXXXX ROUTE ISDN 1
IP[127.0.0.1] CPNX REPLACE 3213061535
IP[127.0.0.1] 933 ROUTE ISDN 1
IP[127.0.0.1] XXXXXXX ROUTE ISDN 1
IP[127.0.0.1] XXX ROUTE ISDN 1
IP XXXXXXX ROUTE ISDN 1
IP[127.0.0.1] XXXX ROUTE ISDN 2
IP X ROUTE ISDN 2

The table is an example of what it will look like when you see it in the Gateway. The table will already be inserted once you import the config, and you can change accordingly with your sites specified numbers.

8. Additional BroadWorks tags

These site values can be selected before the file is rebuilt and exported. The matching GUI location is included for verification or correction after import.

Network settings

The gateway ships at 192.168.2.240. Standard testing and production deployments use a static address.

Configure the site’s default gateway at Basic > Network > Default gateway. If the BroadWorks profile exposes a default-gateway tag, populate it before rebuilding; otherwise enter it manually after import.

[NETWORK]
ETH1_DHCP=%ETH1_DHCP%
ETH1_IP_ADDRESS=%ETH1_IP_ADDRESS%
ETH1_NETMASK=%ETH1_NETMASK%
ETH2_IP_ADDRESS=%ETH2_IP_ADDRESS%
ETH2_NETMASK=%ETH2_NETMASK%
DNS_RESOLVE=%DNS_RESOLVE%
DNS_SERVER=%DNS_SERVER%
DNS_SERVER2=%DNS_SERVER2%

After import, reconnect to https://<assigned-ETH1-IP-address> and verify the address, subnet mask, default gateway, and DNS values.

Country-tone tag

COUNTRY=%COUNTRY%

For the United States, set %COUNTRY% to 1. After import, verify or change the selection at Advanced > Tones.

Time-zone tag

TIMEZONE=%TIMEZONE%

Preserve capitalization, hyphens, and underscores exactly.

After import, verify or change the selection at Advanced > System time.

9. Routing-rule reference

Rules are evaluated from top to bottom. Put exact matches before broad wildcard rules and digit or caller-ID manipulation before the associated ROUTE or END action.

Routing sources

Number patterns

Commands

Navigate to Routing > Routing table, paste only the ordered rule lines, and click Save. Do not paste [ROUTE] or ROUTE_TABLE= into the GUI field.

Group ID removal

REMOVE 10 removes the ten-character Group ID EVAJUPITER; it does not remove a four-digit extension. The remaining extension can have another supported length. If the Group ID changes, change the removal count to its exact character count.

IP CPNEVAJUPITERX REMOVE 10 removes the Group ID from the calling number so the PBX displays the remaining extension. IP EVAJUPITERX REMOVE 10 removes it from the called number before routing the extension to the PBX.

10. TLS, SRTP, DNS SRV, and NAPTR

Enable TLS registration

1. Navigate to Basic > SIP.

2. Set Registrar server to the assigned secure SBC FQDN using port 5061.

3. Set Proxy server to the same secure SBC FQDN using port 5061.

4. Under TLS & SRTP, set TLS SIP Server to the same secure SBC FQDN using port 5061.

5. Set the gateway’s Local signaling port to 5061.

6. Leave Only Accept Trusted Certificates cleared unless the approved deployment requires it.

7. Set SRTP mode to Mandatory.

8. Under DNS SRV, select Enable.

9. Click Save.

10. Reboot the gateway. The reboot is required so the gateway can register again using TLS.

11. After the gateway returns, confirm that it is registered to the secure SBC over TLS.

Use the same regional secure SBC destination in all three server fields. The TLS port must be included directly after the FQDN as :5061.

For example, a United States deployment must use the following values:

Registrar server: us-sbc-secure.14ip.net:5061
Proxy server: us-sbc-secure.14ip.net:5061
TLS SIP Server: us-sbc-secure.14ip.net:5061

Verify SIP_TRANSPORT and DNS_SRV_NAPTR through the XML procedure in Section 12 when troubleshooting or confirming the imported configuration.

The tested gateway GUI does not provide a separate SIP transport selector. On the tested firmware, configuring the TLS SIP Server, using the secure FQDN and port 5061 for the Registrar and Proxy, saving, and rebooting causes the gateway’s external SIP registration to use TLS. The internal SIP_TRANSPORT parameter should report 2 for TLS. Port 5061 alone is not proof that TLS is active.

Confirm the active transport after reboot by checking SIP_TRANSPORT through XML and reviewing the SIP log for SIP/2.0/TLS or transport=tls on traffic to the secure SBC. UDP traffic to the local 127.0.0.1 loopback can still appear in EV Connect Pro logs and does not mean that the external SBC connection is using UDP.

11. Connect Without Internet behavior

The routing table does not monitor Internet access or registration by itself. The loopback rules provide the PBX destination after the gateway’s SIP failure logic returns a failed EVA call to 127.0.0.1.

Verify these failover parameters in the imported file or through XML lookup:

IP_FAIL_FALLBACK_METHOD=1
IP_FAILOVER_TIME=30
DNS_SRV_SUPPORT=1
DNS_SRV_NAPTR=yes
DNS_SRV_FAIL_TO=300
SIP_FG_INV_REG=1

Expected behavior:

1. While EVA is reachable, 141414 and 141415 use the registered SIP path.

2. If EVA cannot be reached and the gateway invokes its failure path, the failed call returns through 127.0.0.1.

3. The routing table changes the EVA number to the configured PBX fallback extension.

4. When SIP reachability recovers, calls return to the normal EVA path.

Validate both loss and restoration of registration. Loopback rules alone do not prove that failover detection and automatic recovery are working.

12. XML parameter lookup and controlled changes

The XML interface returns the firmware-specific parameter ID and current value:

https://<gateway-ip>/xml?method=gw.config.get&name=SIP_TRANSPORT
https://<gateway-ip>/xml?method=gw.config.get&name=DNS_SRV_NAPTR

An enabled NAPTR response can show value="yes".

After obtaining the parameter ID, change its value with:

https://<gateway-ip>/xml?method=gw.config.set&id<ID>=<VALUE>

Always run get first. IDs can vary by firmware, so never reuse an ID taken from another gateway or software version. Record the original value before changing it.