Example: Configuring an Integrated Convergence Services Basic Media Gateway

This example shows how to create a basic configuration for an Integrated Convergence Services SRX Series MGW. You can take this approach to get started with your deployment to ensure that you can place and receive calls.

• Requirements
• Overview
• Configuration
• Verification

Requirements

This example uses the following components

• An SRX210 or SRX240 device with Integrated Convergence Services.
• Two analog phones for the branch office that are attached to FXS interfaces on the device.
• One or more SIP phones for the branch office.

Overview

This example shows how to configure a basic SRX Series MGW that allows you to make calls from SIP and analog phones configured for it and receive calls for these phones. It presumes that the peer call server is accessible to provide call handling and routing services for phones at the branch office.

In this example, you configure the following components:

• A peer call server.

  The peer call server is configured with the minimum amount of information required for the SRX Series MGW and SRX Series SCS to communicate with it. You can accept default values for all other options. When the peer call server is in control, it provides call handling and routing services for analog and SIP stations behind the SRX Series MGW.

  The SRX Series SCS monitors the peer call server to ensure that it is reachable, and if it is not, the SRX Series SCS takes control. When it is reachable again, the SRX Series SCS returns control to the peer call server.

• A COR configuration for the administrator’s station.

  The COR allows the administrator to make local and interbranch office calls.

• Two analog stations:
  • An administrator phone—The station configuration includes:
    • The cor-for-admins COR configuration. It allows the administrator to make local and interbranch office calls.
    • A direct-inward-dialing (DID) number so that outside parties can call the administrator directly.
    • Caller ID information to let dialed parties know who is calling.
  • A lobby phone—The example shows how to configure caller ID information to let dialed parties know who is calling.
• A SIP template.

  The sip-template-for-managers SIP template is used for the manager’s station. It specifies the cor-for-managers configuration. The following default values for other SIP template parameters are assumed:

  • 711-μ, G711-A, G729AB for the codec.
  • RFC-2833 for DTMF.
  • caller-id-transmit is enabled.
• A COR configuration for the manager’s SIP station.

  The cor-for-managers COR configuration gives the manager the right to make inter-branch, local, long-distance, and international calls.

• A SIP station

  The SIP station for the manager specifies the sip-template-for-managers SIP template that allows the manager to make interbranch, local, long-distance, and international calls. Values specified in the cor-for-managers COR configuration and the default values for the sip-template-for-managers are applied to the station.

Note: By default, users can make only intrabranch office and emergency calls.

Figure 3 shows how the SRX Series MGW, on behalf of analog phones and faxes, communicates with the peer call server when the peer call server is reachable. It also shows how SIP phones communicate with the peer call server.

In addition, the figure shows:

• That the SRX Series MGW handles calls to the peer call server and from it for analog phones at the branch office. For both outgoing and incoming calls, the device applies firewall, NAT, ALG, and IPsec (FNAI) processing.
• That SIP phones behind the SRX Series MGW register directly to the peer call server without going through the SRX Series MGW. For calls from them and to them, the device applies firewall, NAT, ALG, and IPsec (FNAI) processing.

Configuration

• Configuring the Peer Call Server
• Configuring a Class of Restriction Policy for an Analog Station
• Configuring an Analog Station for a User
• Configuring an Analog Station for a Lobby Phone
• Creating a Class-of-Restriction Configuration for SIP Stations
• Configuring a SIP Template
• Configuring a SIP Station

Configuring the Peer Call Server

CLI Quick Configuration

To quickly configure the peer call server, copy the following command and paste it into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the peer call server with the minimum required information:

1. Define the peer call server.
   1. Select Configure > Convergence Services > Call Server, and click Add.
   2. In the Name box, type peer-call-server-new-yorkHQ.
   3. In the IPv4 box of the Address pane, type 13.14.16.14.
2. Click OK to check your configuration and save it as a candidate configuration.
3. If you are done configuring the device, click Commit Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To configure the peer call server with minimum required information:

1. Specify the peer call server name and its IPv4 address.
   [edit services convergence-services]user@host# set peer-call-server peer-call-server-new-yorkHQ address ipv4-addr 13.14.16.14

Results

From configuration mode, confirm your configuration by entering the show services convergence-services peer-call-server command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring a Class of Restriction Policy for an Analog Station

CLI Quick Configuration

To quickly configure the COR policy for the analog station, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To create the COR policy for the analog station:

1. Select Convergence Services > Station > Class of Restriction, and click Add to add the new class of restriction configuration.
2. In the Class of restriction box, type cor-for-admins.
3. Click Add to add a policy that allows a user to make inter-branch office calls.
4. In the Policy name box, type allow-inter-branch-calls.
5. Select Allow from the Permission list.
6. Select inter-branch-call from the Calltype list.
7. Click Add to add a policy that allows the user to make local calls.
8. In the Policy name box, type allow-local-calls.
9. Select Allow from the Permission list.
10. Select local-call from the Calltype list.
11. Click OK to check your configuration and save it as a candidate configuration.
12. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To create the COR policy for the analog station:

1. Configure a policy for interbranch office calls.
   [edit services convergence-services]user@host# set class-of-restriction cor-for-admins policy allow-inter-branch-calls permission allow call-type inter-branch-call
2. Configure a policy for local calls.
   [edit services convergence-services]user@host# set class-of-restriction cor-for-admins policy allow–local–calls permission allow call-type local-call

Results

From configuration mode, confirm your configuration by entering the show class-of-restriction command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring an Analog Station for a User

CLI Quick Configuration

To quickly configure the analog station for a user, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the analog station for a user:

1. Select Configure > Convergence Services > Station, and click Add.
2. Define a new analog station.
   1. In the Name box, type alices-telephone.
   2. In the Extension box, type 65555.
   3. In the Caller ID box, type “Alice Marshall, 333 936-5555”.
   4. In the Direct Inward Dialing box, type “3339365555”.
3. Specify the station type.
   1. Click the Enable Analog check box.
   2. In the TDM Interface box in the Enable Analog pane, type fxs-0/0/10.
4. Click OK to check your configuration and save it as a candidate configuration.
5. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To configure the COR policy for the analog station:

1. Specify the name for the station.
   [edit services convergence-services]user@host# set station alices-telephone
2. Specify the extension number of the station.
   [edit services convergence-services]user@host# set station alices-telephone extension 65555
3. Specify the name of a preconfigured class-of-restriction configuration.
   [edit services convergence-services]user@host# set station alices-telephone class-of-restriction cor-for-admins
4. Specify caller ID information displayed to called parties.
   [edit services convergence-services]user@host# set station alices-telephone caller-id “Alice Marshall, 333 936-5555”
5. Specify the station type and the interface to be used for it.
   [edit services convergence-services]user@host# set station alices-telephone station-type analog tdm-interface fxs-0/0/10
6. Configure DID capability for the station.
   [edit services convergence-services]user@host# set station alices-telephone direct-inward-dialing “3339365555”

Results

From configuration mode, confirm your configuration by entering the show station command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring an Analog Station for a Lobby Phone

CLI Quick Configuration

To quickly configure the analog station for the lobby phone, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the analog station for the lobby phone:

1. Select Configure>Convergence Services >Station, and click Add.
   1. In the Name box, type lobby-Bldg2.
   2. In the Extension box, type 65655.
   3. In the Caller ID box, type “lobby building 2”.
2. Specify the station type and its interface.
   1. Click the Enable Analog check box.
   2. In the TDM Interface box on the Enable Analog pane, type fxs-0/0/11.
3. Click OK to check your configuration and save it as a candidate configuration.
4. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To configure the analog station for the lobby phone:

1. Specify the name for the station.
   [edit services convergence-services]user@host# set station lobby-Bldg2
2. Specify the extension number of the station.
   [edit services convergence-services]user@host# set station lobby-Bldg2 extension 65655
3. Specify caller ID information to display to called parties.
   [edit services convergence-services]user@host# set station lobby-Bldg2 caller-id “lobby building 2”
4. Specify the station type and the interface to be used for the station.
   [edit services convergence-services]user@host# set station lobby-Bldg2 station-type analog tdm-interface fxs-0/0/11

Results

From configuration mode, confirm your configuration by entering the show station command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Creating a Class-of-Restriction Configuration for SIP Stations

CLI Quick Configuration

To quickly configure the COR configuration for SIP stations, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To create the COR configuration for SIP stations:

1. Create the first COR policy.
   1. select Convergence Services>Station>Class of Restriction, and click Add.
   2. In the Class of restriction box, type cor-for-managers.
   3. Click Add.
   4. In the Policy name box, type allow-inter-branch-calls.
   5. Select Allow from the Permission list.
   6. Select inter-branch-call from the Calltype list.
2. Create the second policy.
   1. Click Add.
   2. In the Policy name box, type allow-local-calls.
   3. Select Allow from the Permission list.
   4. Select local-call from the Calltype list.
3. Create the third policy.
   1. Click Add.
   2. In the Policy name box, type allow-long-distance-call.
   3. Select Allow from the Permission list.
   4. Select long-distance-call from the Calltype list.
4. Create the fourth policy.
   1. Click Add.
   2. In the Policy name box, type allow-international-calls.
   3. Select Allow from the Permission list.
   4. Select international-call from the Calltype list.
5. Click OK to check your configuration and save it as a candidate configuration.
6. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To create the COR configuration for SIP stations:

1. Configure the first COR policy.
   [edit services convergence services]user@host#set class-of-restriction cor-for-managers policy allow-inter-branch-calls permission allow call-type inter-branch-call
2. Configure the second COR policy.
   [edit services convergence services]user@host#set class-of-restriction cor-for-managers policy allow–local–calls permission allow call-type local-call
3. Configure the third COR policy.
   [edit services convergence services]user@host#set class-of-restriction cor-for-managers policy allow–long-distance–calls permission allow call-type long-distance-call
4. Configure the fourth COR policy.
   [edit services convergence services]user@host#set class-of-restriction cor-for-managers policy allow-international-calls permission allow call-type international-call

Results

From configuration mode, confirm your configuration by entering the show class-of-restriction command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring a SIP Template

CLI Quick Configuration

To quickly configure a SIP template, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SIP template:

1. Select Convergence Services>Station>Station Template, and click Add.
   1. In the Template Name box, type sip-template-for-managers.
   2. Select the SIP button.
   3. From the Class of restriction list, select cor-for-managers.
2. Click OK to check your configuration and save it as a candidate configuration.
3. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To configure the SIP template:

1. Configure the COR.
   [edit services convergence-services]user@host# set station-template sip-template sip-template-for-managers class-of-restriction cor-for-managers

Results

From configuration mode, confirm your configuration by entering the show station-template sip-template command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring a SIP Station

CLI Quick Configuration

To quickly configure the SIP station, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SIP station.

1. Select Configure>Convergence Services> Station, and click Add.
   1. Type sip-station-1 in the Name box.
   2. Type the 861111 in the Extension box.
   3. Type cor-for-managers in the Class of Restriction box.
   4. Type Martin, 333 586–1111 in Caller ID box.
   5. Type sip-template-for-managers in the Template name box.
2. Click OK to check your configuration and save it as a candidate configuration.
3. If you are done configuring the device, click Commit>Options>Commit.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see “Using the CLI Editor in Configuration Mode”.

To configure the SIP station:

1. Configure the station.
   user@host#set services convergence-services station sip-station-1 station-type sip user@host#set services convergence-services station sip-station-1 extension 861111 class-of-restriction cor-for-managers caller-id “Martin, 333 555-5555”

Results

From configuration mode, confirm your configuration by entering the show station command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

To confirm that the configuration is working properly, perform these tasks:

• Verifying That the Peer Call Server Is Reachable
• Verifying That the SRX Series MGW Is Active

Verifying That the Peer Call Server Is Reachable

Purpose

Verify that the SRX Series MGW and the peer call server are communicating.

Action

From operational mode, enter the show services convergence-services sip peers command.

Verifying That the SRX Series MGW Is Active

Purpose

Verify that the SRX Series MGW is active. Display the length of time that the Integrated Convergence Services media gateway call routing engine has been executing.

Action

From operational mode, enter the show services convergence-services media-gateway uptime command.

Related Topics

• Understanding the SRX Series Integrated Convergence Services Media Gateway
• Understanding the Media Gateway Peer Call Server for SRX Series Integrated Convergence Services
• Understanding SRX Series Integrated Convergence Services Media Gateway Analog Stations Configuration
• Understanding Station Templates for SRX Series Integrated Convergence Services
• Understanding Class of Restriction Policies
• Understanding How the Media Gateway Peer Call Server Handles and Routes Calls Within the Branch for SRX Series Integrated Convergence Services
• Understanding How the Media Gateway Peer Call Server Handles and Routes Calls Outside the Branch for SRX Series Integrated Convergence Services
• SRX Series Integrated Convergence Services Media Gateway Overview