Quick Start

This chapter provides the procedure for configuring the Application Server as a SIP server.

Network Configuration

The following IP addresses should be configured:

  • A public IP address for all traffic is required.

  • A public IP address for management is recommended.

  • A private IP address for communication from NIU to Application Server is recommended.

  • If configuring an HA pair, a private IP address for communication between the NIUs is required.

  • If configuring an HA pair, all IP addresses on the secondary NIU must be consecutive from the primary NIU addresses. For example, if the primary NIU address is 100.10.100.1, the secondary must be configured as 100.10.100.2.

  • If configuring an HA pair, the host name must resolve to the SIP IP HA address.

Note

All host names must be resolvable.

We recommend that, unless specifically mentioned in this chapter, configuration attributes should remain as the default values until application requirements dictate additional configuration changes.

Platform Configuration

This section provides the steps for making the minimum configuration changes to have the Application Server up and running in your network. For more information about configuration files, see Configuration and Sample Configuration Files.

Important

A basic knowledge of XML is required to make changes to the configuration files.

Log in to each machine that makes up your Application Server and follow the steps in this procedure for each one.

  1. Make the following changes in the ps_master_config.xml file:

  • Replace all instances of my_ip_address with the host name of this machine or the IP address of the interface through which the traffic is routed.

  • Set these attributes to the following values:

<console local-ip-addr="hostname"></console>
<ps-httpd local-ip-addr="hostname"></ps-httpd>
<ps-sip-agent local-ip-addr="hostname"/>
<ps-softms-pcs local-ip-addr="hostname"></ps-softms-pcs>

In this example, “hostname” refers to a globally resolvable host name, but this value can also be an explicit IP address.

  • If you are configuring the machine as an NIU, add the following sections to identify the AS machines:

<ps-proxy
        local-ip-addr="my_ip_addr"
        initiate-connect="true">
                <proxy-queue>name="ps_eventdispatcher@hostname-aps1"</proxy-queue>
                <proxy-queue>name="ps_sip_agent@hostname-aps1"</proxy-queue>
                <proxy-queue>name="ps_eventdispatcher@hostname-aps2"</proxy-queue>
                <proxy-queue>name="ps_sip_agent@hostname-aps2"</proxy-queue>
</ps-proxy>

Where the variable hostname-aps# is the host name of the AS.

<ps-sip-redirect-server local-ip-addr="my_ip_addr">
                <app-server ip-address="hostname-aps1" />
                <app-server ip-address="hostname-aps2" />
</ps-sip-redirect-server>

Where my_ip_addr is the HA address if the NIU is in a cluster. Where the variable hostname-aps# is the host name of the AS.

  • On all NIUs, remove or comment out the lines that refer to any AS that is not present.

  • If you are configuring the NIU as part of an HA pair, replace the ps_proxy2 process configuration with the following:

<process>
        name="ps_proxy2"
        control-queue="ps_proxy"
        restart="1"
        critical="1"
</process>

  • If you are configuring the NIU as part of an HA pair, add the following line:

<cluster file="cluster_config.xml" />

  1. If you are configuring for a specific application, you may also have to set up application-properties and ps_routing_rules within the ps_master_config.xml file.

For more information, refer to Description of ps_routing_rules and the specific application User’s Guide.

  1. Save the changes to the ps_master_config.xml file.

  2. If configuring the NIUs as an HA pair, edit the /usr/sipxpress/config/cluster_config.xml file to enter the IP address of the primary NIU.

For more information about HA configuration, see High Availability Services.

  1. Save the changes to the cluster_config.xml file.

  2. Reboot the Service Delivery Platform after changes have been made to all registered machines.

The ps_init process runs at startup. This process is responsible for reading from the ps_master_config.xml file and running all that is required on the Application Server. This includes starting all the user applications that have been pushed to the Application Server and mentioned in the ps_master_config.xml file.