Example: Configuring Integrated Convergence Services Support for Separate Registrar and Peer Call Server Functions

This example shows how to configure the SRX Series media gateway (SRX Series MGW) peer call server to support separate peer call server and registrar functions when these functions are managed by separate entities.

• Requirements
• Overview
• Configuration
• Verification

Requirements

This example uses an SRX210 device with Integrated Convergence Services, but you can also use an SRX240 device.

Overview

For some SIP networks, the peer call server and the registrar are managed by separate entities. When this is the case, you can configure the SRX Series MGW to recognize them as such. This example shows how to configure separate addresses for them.

Configuration

CLI Quick Configuration

To quickly configure separate addresses for the peer call server and the registrar, copy the following commands and paste them into the CLI.

Step-by-Step Procedure

To configure separate addresses for the peer call server and the registrar:

1. Configure the peer call server address.
   [edit services convergence-services]user@host set peer-call-server los-angeles-HQ address ipv4-addr 10.12.1.2
2. Configure the registrar address.
   [edit services convergence-services]user@host set peer-call-server los-angeles-HQ registrar-address ipv4-addr 112.10.10.254
3. If you are done configuring the device, enter commit from configuration mode.

Verification

To verify that the configuration is working properly, enter the show services convergence-services peers and the show services convergence-services registry commands.

Related Topics

• Understanding Integrated Convergence Services Support for SIP Networks with Separate Peer Call Server and Registrar Functions
• Understanding the Media Gateway Peer Call Server for SRX Series Integrated Convergence Services