Example: Configuring the SRX Series Survivable Call Server

This example shows how to configure the SRX Series SCS to provide call services and routing for SIP and analog stations at a branch office when the peer call server is unreachable. It shows how to configure trunks, trunk groups, a digit manipulation rule, the peer call server information, a dial plan that the SRX Series SCS refers to, and the SRX Series SCS.

• Requirements
• Overview
• Configuration
• Verification

Requirements

This example uses the following components:

• An SRX210 device with Integrated Convergence Services, which provides two onboard FXO interfaces.
• A 4 FXO-port voice analog Mini-PIM installed in the SRX210 device to allow for connectivity expansion.

Overview

This example configures the SRX Series SCS component of the Integrated Convergence Services to monitor the peer call server to determine if it becomes unreachable; to take control if it is unreachable and provide call services and routing for the branch office; and to return control to the peer call server when it becomes reachable again.

To determine how to route calls, the SRX Series SCS relies on a preconfigured dial plan to which it refers. Dial plan route pattern entries determine how a call is routed.

This example shows how to configure the following components:

• FXO trunks used to route calls.

  Table 11 shows the seven FXO trunks used and their interfaces.

  Table 11: FXO Trunks and Interfaces Used for Them

  FXO Trunks	FXO Trunk Interfaces
  fxoTrnk100	fxo-1/0/0
  fxoTrnk101	fxo-1/0/1
  fxoTrnk102	fxo-1/0/2
  fxoTrnk103	fxo-1/0/3
  fxoTrnk104	fxo-1/0/4
  fxo-1012	fxo-1/0/12
  fxo-1013	fxo-1/0/13

• SRX Series SCS trunk groups that include preconfigured trunks.

  In this example, one line is dedicated to emergency calls. Trunk fxoTrnk100 is assigned to trunk group scs-trunk-group1, which is included in the route pattern for 9-1-1 calls. Some trunk groups share lines (trunks), and some trunk groups are assigned to multiple route patterns.

  Table 12 shows the trunk groups, the trunks that are assigned to them, and how the lines are provisioned.

  Table 12: Trunks Groups and Their Trunks

  Trunk Groups	Assigned Trunks	Provisioned Lines
  scs–trunk–group1	fxoTrnk100	Used exclusively for emergency calls
  scs–trunk–group2	fxoTrnk101 fxoTrnk102 fxoTrnk104	Shared by: Local calls Interbranch calls
  scs–trunk–group3	fxoTrnk1012 fxoTrnk1013	Shared by: International calls to Japan International calls to India
  scs–trunk–group4	fxoTrnk104 fxoTrnk101 fxoTrnk103	Shared by: Long distance calls Interbranch calls
  scs–trunk–group5	fxoTrnk1012 fxoTrnk1013	Shared by: Long distance calls Local calls
  scs–trunk–group6	fxoTrnk103	International calls to India

• A digit manipulation rule.

  The example uses a rule called stripleading9 that strips the leading 9 from calls before they are routed out the PSTN.

  Note: Digit manipulation rules are assigned to trunk groups in a dial plan, not before a trunk group is added to it.

• A peer call server called peer-call-server-new-yorkHQ.

  The peer call server is configured with the minimum amount of information required for the SRX Series SCS to communicate with it. You can accept default values for all other options. 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 dial plan called PasadenaSCS-dialPlan used to determine how calls are routed.

  The dial plan uses the preconfigured trunk groups and their trunks. It includes route patterns for these call types:

  • emergency: 9911—This digit pattern specifies the emergency call number for the United States. (The digit 9 allows for outside calls.)
  • interbranch: 86xxxx—This digit pattern allows for all interbranch calls. (The branch code is 86.)
  • local: 9xxxxxx—This digit pattern allows for all local calls. (9-xxx-xxxx)
  • long-distance: 91xxxxxxxxxx—This digit pattern allows for calls anywhere in the United States. (9-1-xxx-xxx-xxxx)
  • international: 901181888111222—This digit pattern allows for calls to Kochi, Japan. (9–011–81–888–111–2222)
  • international: 90119111xxxxxxx—This digit pattern allows for calls to anywhere in India. (9-011-91-11-xxx-xxxx)
• An SRX Series SCS configuration called boston-branch-scs.

  The SRX Series SCS configuration specifies:

  • The name of the SIP peer call server that it monitors, peer-call-server-new-yorkHQ. The peer call server name must match the name specified in the peer call server configuration.
  • The SIP protocol, its port number (5060), and the transport used (UDP).
  • The registration expiry timeout (80 seconds).

    The registration expiry timeout parameter specifies how frequently a SIP phone should try to reach the peer call server after the peer call server has become unreachable to check if it is once again reachable.

  • The normal heartbeat interval (3 seconds) and its SIP timeout parameter (40 seconds).

    The SRX Series SCS uses this information to set up a watch period to monitor the peer call server while the peer call server is still active and in control.

  • Parameters that the SRX Series SCS uses to determine if the peer call server is reachable again and reliable. If both conditions exist, the SRX Series SCS returns control to the peer call server.
    • The survivable heartbeat interval (4000 milliseconds) when the SRX Series SCS sends messages to the peer call server to determine if it is reachable.
    • The monitor timeout period (12 seconds) and the response threshold (80 percent) that define the watch period that the SRX Series SCS uses to determine if the peer call server is responsive to survivable heartbeat messages.

      Monitor timeout defines the period when the peer call server must respond to a percentage of heartbeat messages that the SRX Series SCS sends it. The response threshold sets the percent of messages that the peer call server must respond to within that period.

  • The dial plan name, PasadenaSCS-dialPlan.

    The dial plan determines how the SRX Series SCS routes calls.

Configuration

• Configuring Trunks
• Configuring Trunk Groups
• Configuring a Digit Transform Rule
• Configuring the Peer Call Server
• Configuring a Dial Plan
• Configuring the SRX Series SCS

Configuring Trunks

CLI Quick Configuration

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

J-Web Quick Configuration

Step-by-Step Procedure

To configure the seven FXO trunks:

1. Configure the first FXO interface by selecting Convergence Services >Media Gateway >Trunks, and clicking Add.
   1. On the New Trunk Configuration page, type fxoTrnk100 in the Trunk name box to configure the first trunk.
   2. From the Trunk type list, select fxo.
   3. In the TDM interface box, type fxo-1/0/0.
   4. Click OK.
2. Click Add to add the second FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk101 in the Trunk name box.
   2. Select fxo from the Trunk type list.
   3. In the TDM interface box, type fxo-1/0/1.
   4. Click OK.
3. Click Add to add the third FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk102 in the Trunk name box.
   2. From the Trunk type list, select fxo.
   3. In the TDM interface box, type fxo-1/0/2.
   4. Click OK.
4. Click Add to add the fourth FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk103 in the Trunk name box.
   2. From the Trunk type list, select fxo .
   3. In the TDM interface box, type fxo-1/0/3.
   4. Click OK.
5. Click Add to add the fifth FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk104.
   2. From the Trunk type list, select fxo .
   3. In the TDM interface box, type fxo-1/0/4.
   4. Click OK.
6. Click Add to add the sixth FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk1012.
   2. From the Trunk type list, select fxo .
   3. In the TDM interface box, type fxo-1/0/12.
   4. Click OK.
7. Click Add to add the seventh FXO trunk.
   1. On the New Trunk Configuration page, type fxoTrnk1013.
   2. From the Trunk type list, select fxo .
   3. In the TDM interface box, type fxo-1/0/13.
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.”

1. Configure seven FXO trunks.
   [edit services convergence-services]user@host# set trunk fxoTrnk100 trunk-type fxo tdm-interface fxo-1/0/0user@host# set trunk fxoTrnk101 trunk-type fxo tdm-interface fxo-1/0/1user@host# set trunk fxoTrnk102 trunk-type fxo tdm-interface fxo-1/0/2user@host# set trunk fxoTrnk103 trunk-type fxo tdm-interface fxo-1/0/3user@host# set trunk fxoTrnk104 trunk-type fxo tdm-interface fxo-1/0/4user@host# set trunk fxoTrnk1012 trunk-type fxo tdm-interface fxo-1/0/12user@host# set trunk fxoTrnk1013 trunk-type fxo tdm-interface fxo-1/0/13

Results

From configuration mode, confirm your configuration by entering the show services convergence-services trunk trunk-name command for each configured trunk. This example shows the output for the fxoTrnk100 trunk.

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

Configuring Trunk Groups

CLI Quick Configuration

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

J-Web Quick Configuration

Step-by-Step Procedure

To configure six trunk groups containing preconfigured trunks:

1. Cerate the first trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration page, type scs-trunk-group1 in the Trunk group name box.
   3. From the Available trunks section, move fxoTrnk100 to the Selected trunks section.
   4. Click OK.
2. Create the second trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration pane, type scs-trunk-group2 in the Trunk group name box.
   3. From the Available Trunks section, move fxoTrnk101, fxoTrnk102, and fxoTrnk104 to the Selected trunks section.
   4. Click OK.
3. Create the third trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration page, type scs-trunk-group3 in the Trunk group name box.
   3. From the Available trunks section, move fxoTrnk1012 and fxoTrnk1011 to the Selected trunks section.
   4. Click OK.
4. Create the fourth trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration page, type scs-trunk-group4 in the Trunk group name box.
   3. From the Available trunks section, move fxoTrnk104, fxoTrnk101, and fxoTrnk103 to the Selected trunks section.
   4. Click OK.
5. Create the fifth trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration page, type scs-trunk-group5 in the Trunk group name box.
   3. From the Available trunks section, move fxoTrnk1012, and fxoTrnk1013 to the Selected trunks section.
   4. Click OK.
6. Create the sixth trunk group.
   1. Select Convergence Services>Media Gateway>Trunk groups, and click Add.
   2. On the New Trunk Group Configuration page, type scs-trunk-group6 in the Trunk group name box.
   3. From the Available trunks section, move fxoTrnk103 to the Selected trunks section.
   4. Click OK.
7. Click OK to check your configuration and save it as a candidate configuraiton.
8. 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 six trunk groups:

1. Create the trunk groups and add their trunks to them.
   [edit services convergence-services]user@host# set trunk-group scs-trunk-group1 trunk fxoTrnk100user@host# set trunk-group scs-trunk-group2 trunk fxoTrnk101 trunk fxoTrnk102 trunk fxoTrnk104user@host# set trunk-group scs-trunk-group3 trunk fxoTrnk1012 trunk fxoTrnk1013 user@host# set trunk-group scs-trunk-group4 trunk fxoTrnk104 trunk fxoTrnk101 trunk fxoTrnk103user@host# set trunk-group scs-trunk-group5 trunk fxoTrnk1012 trunk fxoTrnk1013 user@host# set trunk-group scs-trunk-group6 trunk fxoTrnk103

Results

From configuration mode, confirm your configuration by entering the show services convergence-services trunk-group trunk-group-name 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 a Digit Transform Rule

CLI Quick Configuration

To quickly configure the digit transform rule, copy the following command and paste it into the CLI.

J-Web Quick Configuration

Step-by-Step Procedure

To create the digit transform rule:

1. Select Configure>Convergence-Services>Dial Plan>Digit Manipulation and click Add.
   1. On the New digit manipulation configuration page, type stripleading9 in the Digit Transform box.
   2. In the Regular Expression box, type s/^9//.
   3. Click OK.
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 digit transform rule:

1. [edit services convergence-services digit-manipulation]user@host# set digit-transform stripleading9 regular-expression s/^9//

Results

From configuration mode, confirm your configuration by entering the show services convergence-services digit-manipulation digit-transform stripleading9 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 the peer call server’s IPv4 address, 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 Dial Plan

CLI Quick Configuration

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

J-Web Quick Configuration

To configure the dial plan:

Step-by-Step Procedure

1. Select Configure>Convergence Services>Dial Plan, and click Add.
2. In the Dialplan name box, type PasadenaSCS-dialPlan.
3. Configure the first route pattern.
   1. Click Add.
   2. In the Route pattern box, type 9911
   3. From the Call type list, select emergency-call .
   4. From the Available trunks list, select scs-trunk-group1.
   5. From the Digit manipulation list, select stripleading9.
   6. Click OK.
4. Configure the second route pattern.
   1. In the Route pattern box, type 86xxxx.
   2. From the Call type list, select inter-branch-call.
   3. From the Available trunks list, select scs-trunk-group2.
   4. Click OK.
5. Configure the third route pattern.
   1. Click Add.
   2. In the Route pattern box, type 9xxxxxxx.
   3. From the Call type list, select local-call.
   4. From the Available trunks list, select scs-trunk-group5.
   5. From the Digit manipulation list, select stripleading9.
   6. Click OK.
6. Configure the fourth route pattern.
   1. Click Add.
   2. In the Route pattern box, type 91xxxxxxxxxx.
   3. From the Call type list, select long-distance-call.
   4. From the Available trunks list, select scs-trunk-group4.
   5. From the Digit manipulation list, select stripleading9.
   6. From the Available trunks list, select scs-trunk-group5.
   7. From the Digit manipulation list, select stripleading9.
   8. Click OK.
7. Configure the fifth route pattern.
   1. Click Add .
   2. In the Route pattern box, type 901181888111222.
   3. From the Call type list, select international-call.
   4. From the Available trunks list, select scs-trunk-group3.
   5. From the Digit manipulation list, select stripleading9.
   6. Click OK.
8. Configure the sixth route pattern.
   1. Click Add.
   2. In the Route pattern box, type 90119111xxxxxxxx.
   3. From the Call type list, select international-call.
   4. From the Available trunks list, select scs-trunk-group3
   5. From the Digit manipulation list, select stripleading9.
   6. From the Available trunks list, select scs-trunk-group6.
   7. From the Digit manipulation list, select stripleading9.
   8. Click OK.
9. Click OK to check your configuration and save it as a candidate configuraiton.
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.”

1. To configure the dial plan:
   [edit services convergence-services dial-plan PasadenaSCS-dialPlan]user@host# set route-pattern 9911 trunk-group scs-trunk-group1 digit-transform stripleading9user@host# set route-pattern 9911 call-type emergency-calluser@host# set route-pattern 86xxxx trunk-group scs-trunk-group2user@host# set route-pattern 86xxxx trunk-group scs-trunk-group4user@host# set route-pattern 86xxxx call-type inter-branch-calluser@host#set route-pattern 9xxxxxxx trunk-group scs-trunk-group5 digit-transform stripleading9user@host#set route-pattern 9xxxxxxx call-type local-calluser@host#set route-pattern 91xxxxxxxxxx trunk-group scs-trunk-group4 digit-transform stripleading9user@host# set route-pattern 91xxxxxxxxxx trunk-group scs-trunk-group5 digit-transform stripleading9user@host# set route-pattern 91xxxxxxxxxx call-type long-distance-calluser@host# set route-pattern 901181888111222 trunk-group scs-trunk-group3 digit-transform stripleading9user@host# set route-pattern 901181888111222 call-type international-calluser@host# set route-pattern 90119111xxxxxxxx trunk-group scs-trunk-group3 digit-transform stripleading9user@host#set route-pattern 90119111xxxxxxxx trunk-group scs-trunk-group6 digit-transform stripleading9user@host# set route-pattern 90119111xxxxxxxx call-type international-call

Results

From configuration mode, confirm your configuration by entering the show services convergence-services dial-plan PasadenaSCS-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 SRX Series SCS

CLI Quick Configuration

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

J-Web Quick Configuration

Step-by-Step Procedure

To configure the SRX Series SCS:

1. Select Configure>Convergence Services>Call Service, and click Add.
   1. In the Call service name box, type boston-branch-scs.
   2. In the Transport box, type UDP.
   3. In the Port number box, type 5060.
   4. In the Registration expiry timeout box, type 80.
   5. In the SIP timeout box, type 40.
   6. In the Monitor timeout box, type 12.
   7. In the Heartbeat normal box, type 3.
   8. In the Heartbeat survivable box, type 4000.
   9. In the Response threshold box, type 80.
   10. In the Call server box, type peer-call-server-new-yorkHQ.
   11. In the Dialplan box, type PasadenaSCS-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 create the SRX Series SCS configuration:

1. Specify a name for the SRX Series SCS configuration and refer to the peer call server that it monitors.
   [edit services convergence-services survivable-call-service]user@host# set boston-branch-scs peer-call-server peer-call-server-new-yorkHQ
2. Specify the SIP protocol, its port number, and the transport to be used.
   [edit services convergence-services survivable-call-service boston-branch-scs]user@host# set protocol sip port 5060 transport udp
3. Specify the normal heartbeat interval and its SIP timeout parameter.
   [edit services convergence-services survivable-call-service boston-branch-scs]user@host# set heartbeat-normal-interval 3 sip-timeout 40
4. Configure the survivable heartbeat interval, monitor time-out period, and the response threshold.
   [edit services convergence-services survivable-call-service boston-branch-scs]user@host# set heartbeat-survivable-interval 4000 monitor-timeout 12 response-threshold minimum 80
5. Refer to the dial plan used for call routing. Specify the name of the dial plan given when you configured it.
   [edit services convergence-services survivable-call-service boston-branch-scs]user@host# set dial-plan PasadenaSCS-dialPlan
6. Configure the registrar expiration timeout parameter.
   [edit services convergence-services survivable-call-service boston-branch-scs]user@host# set registration-expiry-timeout 80

Results

From configuration mode, confirm your configuration by entering the show services convergence-services survivable-call-service boston-branch-scs 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 SCS Is in Control
• Verifying That the SRX Series MGW Is Active

Verifying That the SRX Series SCS Is in Control

Purpose

Verify that there is an active session between the SRX Series SCS and the peer call server that it is monitoring. Display information about the peer call server.

Action

From operational mode, enter the show services convergence-services survivable-call-services sessions 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

• Junos OS Feature Support Reference for SRX Series and J Series Devices
• Understanding the SRX Series Survivable Call Server
• Understanding Trunk Precedence and Trunk Group Preference for SRX Series Integrated Convergence Services
• Understanding Digit Transform Rules and Digit Manipulation
• Understanding Trunk Reusability for SRX Series Integrated Convergence Services
• Understanding Route Patterns and Their Digit Patterns
• Understanding SIP Station Configurations
• Understanding SRX Series Integrated Convergence Services Media Gateway Analog Stations Configuration
• Understanding SRX Series Integrated Convergence Services Features and Functions