Example: Configuring an Integrated Convergence Services Media Gateway and Trunks

This example explains how to configure an Integrated Convergence Services SRX Series MGW for a medium-size branch with up to 24 users. It includes how to configure SRX Series MGW trunks for the peer call server to use and a dial plan that defines route patterns for these trunks and how calls are routed. The example also shows how to configure the SRX Series MGW, a peer call server, class-of-restriction configurations, and stations for phones.

• Requirements
• Overview
• Configuration
• Verification

Requirements

This example uses the following components:

• An SRX210 device with Integrated Convergence Services.
• A 4-port FXO voice Mini-PIM added to the SRX210 device to allow for connectivity expansion.
• An analog phone attached to an FXS interface on the device and a SIP phone at the branch office.

Overview

When the Integrated Convergence Services SRX Series MGW is active, the peer call server provides call handling and routing services for the branch office. It routes calls from the branch office using its own telephony trunks. However, it can also route calls out SRX Series MGW trunks at the branch office, if any are configured.

This example shows how to configure the following components to create an SRX Series MGW deployment that uses SRX Series MGW trunks:

• SRX Series MGW trunks.

  Table 6 shows the six FXO interfaces for telephony service provider trunks that the configuration uses, including those onboard the SRX210 device and the 4-port FXO voice Mini-PIM. The peer call server routes calls out these trunks based on the SRX Series MGW dial plan. The configuration for each trunk specifies the trunk name, the trunk type, and the interface used for it.

  Table 6: Trunks and Interfaces Used for Them

  FXO Interfaces	Trunk Configured for the Interface
  fxo-1/0/12 fxo-1/0/13 fxo-1/0/0 fxo-1/0/1 fxo-1/0/2 fxo-1/0/3	fxoTrnk1 fxoTrnk2 fxoTrnk3 fxoTrnk4 fxoTrnk5 fxoTrnk6

• SRX Series MGW trunk groups.

  Table 7 shows the two trunk groups, their trunks, and the trunk interfaces that the configuration uses. Each trunk group is composed of three preconfigured trunks that are shown in Table 6. The trunks are specified for a trunk group in the order of precedence that they are used to route a call.

  Table 7: Trunk Groups, Trunks, and Their Interfaces for the SRX Series Media Gateway Example

  Trunk Groups	Trunks Used in the Trunk Groups (and Their Interfaces)
  mgTrnk1	fxoTrnk1 (fxo-1/0/012), fxoTrnk2 (fxo-1/0/13), fxoTrnk3 (fxo-1/0/0)
  mgTrnk2	fxoTrnk4 (fxo-1/0/1), fxoTrnk5 (fxo-1/0/2), fxoTrnk6 (fxo-1/0/3)

• An SRX Series MGW dial plan.

  The mg1-dialPlan dial plan contains two route patterns whose digit patterns specify trunk access codes.

  The peer call server routes calls in this way:

  • It routes some calls out its own telephony trunks.
  • It routes calls whose numbers specify the trunk access code 9 as their prefix out trunks configured for the route pattern that specifies 9. as its digit pattern. These calls are routed out local SRX Series MGW PSTN trunks.
  • It routes calls whose numbers specify the trunk access code 34 out trunks configured for the route pattern whose digit pattern specifies 34XXXXXXXXXX. These trunks are reserved for calls destined for the Bangalore site’s PBX.
• A peer call server.

  The peer-call-server-new-yorkHQ peer call server configuration specifies the minimum required information, including the peer call server name and IPv4 address 13.14.16.14, so that the SRX Series MGW and the SRX Series SCS can communicate with it.

• An SRX Series MGW.

  The LA-media-gateway SRX Series MGW specifies peer-call-server-new-yorkHQ peer as its peer call server. It specifies that the mg1-dialPlan dial plan is used for call routing.

• Class of restriction configurations for analog and SIP phones.

  The configuration includes the following COR configurations:

  • The cor-for-admins COR configuration to allow administrators to make interbranch, local, and long-distance calls.
  • The cor-for-managers COR configuration to allow managers to make interbranch, local, long-distance, and international calls.
• A SIP template.

  The standard-sip-template SIP template specifies the cor-for-managers COR configuration. The following default values are assumed for the SIP template parameters not specified in the template:

  • caller-ID transmit, which is enabled by default.
  • The codec set, G711–A | G711–MU | G729AB, whose codecs are proposed to the peer call server in that order.
  • The standard DTMF specified in rfc-2833.
• An analog station.

  The analog station configuration for Alice, an administrator, allows her to make the types of calls specified by the cor-for-admins COR configuration. The station configuration specifies the phone number (DID number) for users outside the company to dial to reach Alice directly and caller ID information that is displayed to called parties.

• A SIP station.

  The SIP station configuration for Martin, a manager, specifies the cor-for-managers COR configuration that allows the manager to make interbranch, local, long-distance, and international calls. It specifies the extension number for Martin’s station and caller ID information. The configuration specifies a DID number for outside parties to call Martin directly.

Configuration

• Configuring SRX Series MGW Trunks
• Configuring Trunk Groups
• Configuring the SRX Series MGW Dial Plan
• Configuring the Peer Call Server
• Configuring the SRX Series MGW
• Configuring Class-of-Restriction Policies for Stations
• Configuring the SIP Template
• Configuring the Analog Station
• Configuring the SIP Station

Configuring SRX Series MGW Trunks

CLI Quick Configuration

To quickly configure the SRX Series MGW trunks, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SRX Series MGW trunks:

1. Select Convergence Services>Media Gateway>Trunks, and click Add to add a new trunk.
2. In the New Trunk Configuration pane, type fxoTrnk1 in the Trunk name box.
3. Select fxo from the Trunk type list.
4. In the TDM interface box, type fxo-1/0/12 .
5. Follow the preceding set of steps to configure five additional trunks using the information in Table 8

   Table 8: Additional Trunks to Be Created

   Trunk Name	Trunk Type	TDM Interface
   fxoTrnk2 fxoTrnk3 fxoTrnk4 fxoTrnk5 fxoTrnk6	fxo fxo fxo fxo fxo	fxo-1/0/13 fxo-1/0/0 fxo-1/0/1 fxo-1/0/2 fxo-1/0/3

6. Click OK to check your configuration and save it as a candidate configuration.
7. 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 6 FXO SRX Series MGW trunks:

1. Configure six trunks.
   [edit service convergence-services]user@host# set trunk fxoTrnk1 trunk-type fxo tdm-interface fxo-1/0/12 user@host# set trunk fxoTrnk2 trunk-type fxo tdm-interface fxo-1/0/13 user@host# set trunk fxoTrnk3 trunk-type fxo tdm-interface fxo-1/0/0 user@host# set trunk fxoTrnk4 trunk-type fxo tdm-interface fxo-1/0/1 user@host# set trunk fxoTrnk5 trunk-type fxo tdm-interface fxo-1/0/2 user@host# set trunk fxoTrnk6 trunk-type fxo tdm-interface fxo-1/0/3

Results

From configuration mode, confirm your configuration by entering the show trunk command for each trunk. 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 Trunk Groups

CLI Quick Configuration

To quickly configure two trunk groups, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure two trunk groups:

1. Create the first trunk group and add three trunks to it.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add to add a new trunk.
   2. In the New Trunk Group Configuration pane, type mgTrnk1 in the Trunk group name box.
   3. From the Available trunks section, move the following trunks to the Selected trunks section: fxoTrnk1, fxoTrnk2, and fxoTrnk3.
2. Create the second trunk group and add three trunks to it.
   1. Select Convergence Services >Media Gateway>Trunk groups, and click Add.
   2. In the New Trunk Group Configuration pane, type mgTrnk2 in the Trunk group name box.
   3. From the Available Trunks pane, move the following trunks to the Selected trunks section: fxoTrnk4, fxoTrnk5, and fxoTrnk6.
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”.

Configure two trunk groups:

1. Create the first trunk group and add three trunks to it.
   [edit services convergence-services]user@host# set trunk-group mgTrnk1 trunk fxoTrnk1 trunk fxoTrnk2 trunk fxoTrnk3
2. Create the second trunk group and add three trunks to it.
   [edit services convergence-services]user@host# set trunk-group mgTrnk2 trunk fxoTrnk4 trunk fxoTrnk5 trunk fxoTrnk6

Results

From configuration mode, confirm your configuration by entering the show trunk-group command for each trunk group. 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 the SRX Series MGW Dial Plan

CLI Quick Configuration

To quickly configure the SRX Series MGW dial plan, copy the following commands and paste them into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SRX Series MGW dial plan:

1. Configure the first route pattern.
   1. Select Configure>Convergence Services>Dial Plan>Dial Plan, and click Add to begin configuring the new dial plan.
   2. Type mg1-dialPlan in the Dialplan name box and click Add.
   3. Type 9.in the Route pattern box.
   4. In the Call type box, select trunk-call from the list.
   5. In the Trunk Group Information pane, select mgTrnk1 from the Available trunk groups list and move it to the Selected Trunk Groups list.
   6. Click OK.
2. Configure the second route pattern.
   1. Click Add.
   2. Type 34xxxxxxxxxx in the Route pattern box.
   3. In the Call type box, select trunk-call from the list.
   4. In the Trunk Group Information pane, select mgTrnk2 from Available Trunk Groups list and move it to the Selected Trunk Groups list.
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 SRX Series MGW dial plan:

1. Configure the first route pattern.
   [edit services convergence-services]user@host# set dial-plan mg1-dialPlan route-pattern 9. trunk-group mgTrnk1 user@host# set dial-plan mg1-dialPlan route-pattern 9. call-type trunk-call
2. Configure the second route pattern.
   [edit services convergence-services]user@host# set dial-plan mg1-dialPlan route-pattern 34XXXXXXXXXX trunk-group mgTrnk2 user@host# set dial-plan mg1-dialPlan route-pattern 34XXXXXXXXXX call-type trunk-call

Results

From configuration mode, confirm your configuration by entering the show dial-plan mg1-dialPlan 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 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 the minimum required information:

1. Specify the peer call server name and 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 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 the SRX Series MGW

CLI Quick Configuration

To quickly configure the SRX Series MGW, copy the following command and paste it into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SRX Series MGW:

1. Define the SRX Series MGW.
   1. Select Configure>Convergence Services>Media Gateway>Media Gateway, and click Add.
   2. In the Media Gateway box, type LA-media-gateway.
   3. In the Call server port box, type peer-call-server-new-yorkHQ.
   4. In the Dial Plan box, type mg1-dialPlan.
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 SRX Series MGW:

1. Specify the SRX Series MGW name and associate the peer call server with it.
   [edit services convergence-services]user@host# set media-gateway LA-media-gateway peer-call-server peer-call-server-new-yorkHQ
2. Specify the name of the SRX Series MGW dial plan.
   [edit services convergence-services]user@host# set media-gateway LA-media-gateway dial-plan mg1-dialPlan

Results

From configuration mode, confirm your configuration by entering the show media-gateway 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 Class-of-Restriction Policies for Stations

CLI Quick Configuration

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

J-Web Quick Configuration

Step-by-Step Procedure

To configure two COR policies for stations:

1. Create the first COR policy by selecting Convergence Services>Station>Class of Restriction, and clicking Add.
   1. In the Class of restriction box, type cor-for-admins.
   2. Click Add to add the first policy that allows a user to make interbranch calls.
   3. In the Policy name box, type allow-inter-branch-calls.
   4. Select Allow from the Permission list.
   5. Select inter-branch-call from the Calltype list.
   6. Click Ok.
2. Create the second COR configuration by clicking Addon the Class of Restriction pane.
   1. In the Policy name box, type allow-local-calls.
   2. Select allow from the Permission list.
   3. Select local-call from the Calltype list.
   4. Click Ok.
3. Click Add to add the third policy that allows users to make long-distance calls.
   1. In the Policy name box, type allow-long-distance-calls.
   2. Select allow from the Permission list.
   3. Select long-distance-call from the Calltype list.
   4. Click Ok.
4. Create the second COR configuration by clicking Add on the Class of Restriction pane.
   1. In the Class of restriction box, type cor-for-managers.
   2. Click Add to add the first policy that allows a user to make interbranch calls.
   3. In the Policy name box, type allow-inter-branch-calls.
   4. Select Allow from the Permission list.
   5. Select inter-branch-call from the Calltype list.
   6. Click Ok.
5. Click Add to add the second policy that allows a user to make local calls.
   1. In the Policy name box, type allow-local-calls.
   2. Select allow from the Permission list.
   3. Select local-call from the Calltype list.
   4. Click Ok.
6. Click Add to add the third policy that allows a user to make long-distance calls.
   1. In the Policy name box, type allow-long-distance-calls.
   2. Select allow from the Permission list.
   3. Select long-distance-call from the Calltype list.
   4. Click Ok.
7. Click Add to add the fourth policy that allows users to make international calls.
   1. In the Policy name box, type allow-international-calls.
   2. Select allow from the Permission list.
   3. Select international-call from the Calltype list.
   4. Click Ok.
8. Click OK to check your configuration and save it as a candidate configuration.
9. 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 two COR policies for stations:

1. Create the COR configuration that allows a user to make interbranch office, local, and long-distance calls.
   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
   3. Configure a policy for long-distance calls.
      [edit services convergence-services]user@host# set class-of-restriction cor-for-admins policy allow-long-distance-calls permission allow call-type long-distance-call
2. Create the COR configuration that allows a user to make interbranch office, local, and long-distance calls.
   1. Configure a policy for interbranch office calls.
      [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 a policy for local calls.
      [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 a policy for long-distance calls.
      [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 a policy for international calls.
      [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 services convergence-services class-of-restriction cor-for-managers and the show services convergence-services class-of-restriction cor-for-admins 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 the SIP Template

CLI Quick Configuration

To quickly configure the SIP template, copy the following command and paste it 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 standard-sip-template.
   2. Select the SIP button.
   3. From the Class of restriction list, select cor-for-managers.
   4. Click Ok to check your configuration and save it as a candidate configuration.
2. 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”.

1. Configure the SIP template.
   [edit services convergence-services]user@host#set services convergence-services station-template sip-template standard-sip-template 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 the Analog Station

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:

1. Select Configure>Convergence Services>Station, and click Add.
2. In the Name box, type alices-telephone.
3. In the Extension box, type 65555.
4. In the Class of Restriction box, type cor-for-admins.
5. In the Caller ID box, type “Alice Marshall, 333 936-5555”.
6. In the Direct Inward Dialing box, type “3339365555”.
7. Click Enable Analog .
8. In the TDM Interface box of the Enable Analog pane, type fxs-0/0/10.
9. Click OK to check your configuration and save it as a candidate configuration.
10. 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:

1. Specify the station name.
   [edit services convergence-services]user@host# set station alices-telephone
2. Specify the station’s extension number.
   [edit services convergence-services]user@host# set station alices-telephone extension 65555
3. Specify the 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 to be displayed to called parties.
   [edit services convergence-services]user@host# set station alices-telephone caller-id “Alice Marshall, 333 936-5555”
5. 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 the SIP Station

CLI Quick Configuration

To quickly configure the SIP station that uses the SIP template, copy the following command and paste it 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 861111 in the Extension box.
   3. Type cor-for-managers in the Class of Restriction box.

      Type “Martin, “555 986-1111” In the Caller ID box.

      Type 5559861111 in the Direct Inward Dialing box.

   4. Type standard-sip-template in the Template name box.
   5. Click Enable SIP.
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. Specify the SIP station.
   [edit services convergence-services]user@host# set station sip-station-1
2. Specify the station’s extension number.
   [edit services convergence-services]user@host# set station sip-station-1 extension 861111
3. Specify the preconfigured class of restriction configuration.
   [edit services convergence-services]user@host# set station sip-station-1 class-of-restriction cor-for-managers
4. Specify caller ID information displayed to called parties:
   [edit services convergence-services]user@host# set station sip-station-1 caller-id “Martin, 555 986-1111”
5. Configure DID capability for the station.
   [edit services convergence-services]user@host# set station sip-station-1 direct-inward-dialing “5559861111”
6. Configure the station type.
   [edit services convergence-services]user@host#set station sip-station-1 station-type sip

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 SRX Series MGW Is Active
• Verifying That the Peer Call Server Is Active

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.

Verifying That the Peer Call Server Is Active

Purpose

Verify that the peer call server is reachable.

Action

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

Related Topics

• Understanding Integrated Convergence Services Media Gateway Trunks and Dial Plans
• Understanding the SRX Series Integrated Convergence Services Media Gateway
• Understanding SRX Series Integrated Convergence Services Media Gateway Analog Stations Configuration
• Understanding Trunk Precedence and Trunk Group Preference for SRX Series Integrated Convergence Services