Administration

Analog Card – Extend E-MetroTel SIP Trunks to 3rd Party systems using FXS Ports

For customers interested in moving to SIP trunks but are not quite ready to deploy E-MetroTel UCX software to replace their legacy PBX, E-MetroTel FXS Gateway cards can be used. The FXS cards can be deployed in a Galaxy Express or even a Galaxy Expand chassis and the possibly re-used within the new UCX configuration whenever it is deployed. Standard E-MetroTel SIP trunks and FXS Gateway cards (and firmware are required.

Step 1 – Connect to the E-MetroTel Partner Portal

Create the E-MetroTel PSTN account in Cloud Services on the E-MetroTel Portal

Log into the E-MetroTel Partner Portal and proceed to the Cloud Services

  1. Add a SIP Trunk using Registration. This will be used for all the FXS ports to act as a trunk group. Take note of the VOIP Username and VOIP Password information provided for use in step 2. Also note the Serial Number and Softswitch Address indicated for your SIP Trunk.
  2. Add one or more DID Number(s) to the Trunk. Multiple DIDs can be configured to terminate to a group, but they will all be associated with the same inbound call group, as the analog interfaces cannot relay any DID information to the 3rd party FXO port..
  3. In the Action menu on the SIP Trunks page, select Change Caller ID, and select the DID that you want associated with this trunk group. Only one DID can be selected for outbound calls.

Step 2 – Configure the FXS Gateway Card

Connect to the Analog FXS Gateway

Refer to the following documents for basic connection, activation, and firmware updates to the FXS Gateways card.

Analog Card – Accessing the System

Analog Card – Activation

Analog Card – Updating the Firmware

Add a Profile in the Profiles section

  1. Navigate to the Profiles page in the system menu
  2. Select a Profile (1 to 4)
  3. In the SIP Settings tab:
    1. Enter the SIP Trunk domain name as the SIP Primary Server. This would be the Softswitch Address identified in the Partner Portal in the previous step.
    2. Set the SIP Primary Server Port to 5960
    3. Press Save
      FXSTrunkProfile1SIPSettings.png
  4. In the Digitmap Settings
    1. Verify the Dialing Rules filed is set to x.
    2. If any change was made, press Save
      FXSTrunkProfile1DigitMapSettings.png

Configure the Port Settings

  1. Navigate to the Port / Port Settings page in the system menu
  2. Ensure any unused ports are set as follows:
    1. In the Basic Setting tab: Enable Port and Enable Registration are set to No, and Group ID is empty
    2. In the Call Setting tab: Call Waiting, Call Forwarding, Call Hold, Three-Way Calling, and Do Not Disturb are set to Disable
    3. In the Advanced Setting tab: Use P-Asserted Identity, Use Remote Party ID Header Field, User User=Phone Header Field, Use P-Access-Network Info Header Field, and  Use P-Emergency-Info Filed are set to No
  3. For each group of physical FXO ports that will be used as a trunk group:
    1. In the Basic Setting tab, set the SIP User ID, and the Authentication ID fields to the VOIP Username (Serial Number) of the E-MetroTel SIP Trunk and the Password is set to the VOIP Password noted in Step 1.
    2. In the Basic Setting tab, set the Password field to the VOIP Password noted in Step 1.
    3. In the Basic Setting tab, ensure the Profiles field is set to the same Profile configured in the Profiles section above.
    4. In the Basic Setting tab, set the Enable Port field to Yes
    5. In the Basic Setting tab, set the Enable Registration field of the FIRST port of the group to Yes, and the others in that group to No
    6. In the Basic Setting tab, assign the same Group ID(4-63) to all ports in that group, (eg. Group ID = 40)
      FXSTrunkPortBasicSetting.png
    7. In the Call Setting tab, set the Unconditional Transfer field to “DAHDI/gXX“, where XX = the group number assigned in the Group ID Field in the previous step (eg DAHDI/g40)
      FXSTrunkPortCallSetting.png
    8. In the Advanced Setting tab, set the CID Message Format to select the CID Only, Display Name Only, or Display Name and CID format as supported or required by your existing third party FXO interface.
      FXSTrunkPortAdvancedSetting.png
    9. Press Save
  4. Repeat the previous settings for each additional group of physical FXO ports you plan to use.

Step 3 – Adjust the Disconnect Options

Some FXO devices that connect to the Galaxy FXS expect a signal from the FXS port to indicate that the far end has hung up (i.e. Disconnect Supervision). Without such a signal the local device may remain connected indefinitely.

The most common Disconnect Supervision signal methods are:

  • Polarity Reversal: This involves reversing the polarity on the FXS port when the UCX detects that the far end has gone back on-hook (i.e. hung up). The locally attached FXO device senses the change in battery polarity and in turn also hangs up, allowing the Galaxy FXS card to disconnect as well.
  • Open Switching Interval (OSI): This involves the creation of a short period where the FXS port removes the battery from the line when the far end has gone back on-hook (i.e. hung up). The locally attached FXO device senses the brief open connection and in turn hangs up, allowing the Galaxy FXS card to disconnect as well.

To enable Polarity Reversal on the Galaxy FXS port

  1. On the FXOS or FXS16 menu, navigate to Profile / Analog Settings
  2. Ensure that the Polarity Reversal For Hangup function is set to Yes
  3. Click the Save button

To enable Open Switching Interval (OSI) on the Galaxy FXS port

  1. On the FXOS or FXS16 menu, navigate to Profile / Advanced Configuration / Analog Settings
  2. Ensure that the Ports Signaling function in the General section is set to KEWLSTART
  3. Click the Save button

Contents