Document ID: 50260 |
Introduction
This document describes how to configure the IP address used in the Via and Record-Route path headers on the Cisco Session Initiation Protocol Proxy Server (Cisco SPS).
Note: This information has only been validated for Cisco SPS versions 2.1 and later.
Prerequisites
Requirements
Readers of this document should have knowledge of these topics:
-
The "How to Configure Proxy-Server DNS Behavior" section of Configuring Cisco SPS
Components Used
The information in this document is based on these software and hardware versions:
-
Cisco SPS version 2.1
-
Sun Solaris 8 Operating System
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Background Information
When the Cisco SPS application is started, a number of different processes are started sequentially that complete the entire SPS application. After starting the application, the primary configuration file, called sipd.conf, is created. This creation happens based on the information coming from the MySQL database of the Cisco SPS. This database is installed separately during the installation of the Cisco SPS. All parameters that are not in the MySQL database when the Cisco SPS is restarted are lost.
How to Use the IpAddrInPathHeaders Variable
The primary purpose of the IpAddrInPathHeaders variable is to control which source IP address the Cisco SPS inserts into the Via and Record-Route path header fields, on multi-homed servers, when the ProxyAddressResolutionType variable is set to IP. If not configured, then the first value returned from issuing the gethostbyname command is used.
Permanent Changes to the Variable
It is not difficult to configure this variable, but it needs to be provisioned in the correct way. This means that unless the variable is entered using the GUI, it is not saved in the MySQL database. Every attempt to change the sipd.conf file manually is not saved when the Cisco SPS is restarted.
Locating the IpAddrInPathHeader variable field in the GUI may be tricky because it is not logically placed in the Cisco SIP Proxy Server Core of the GUI, where you might expect to find it.
Find and Alter the Variable in the GUI
Complete these steps to locate and make changes to the IpAddrInPathHeader variable field:
-
Start the Cisco SPS provisioning GUI.
-
Go to Farm/Proxies > Advanced > Farming.
-
Choose Show Additional Fields under Farm Members.
-
Insert the source IP address into the IpAddrInPathHeaders variable field.
-
Click Submit to save any changes.
Cisco SPS: Sequence of Processes
This section shows the order in which the processes of the Cisco SPS are started and the application structure of required processes that run after startup.
-
This is the sequence of processes running during the startup of the Cisco SPS application:
./opt/sip/bin/sip start # ./sip start Starting pserver... /opt/sip/bin/pserverctl start: pserver started Starting license manager... /opt/sip/bin/lmctl start: licenseMgr started Starting spa... /opt/sip/bin/spactl start: spa started /opt/sip/bin/spactl start: Waiting for sipd.conf from spa.... /opt/sip/bin/spactl start: sipd.conf written Starting sipd... Version of CSPS : 2.1.1.1 - Official Release Version in Config file : 2.1.1.1 - Official Release Software release version of CSPS validated successfully with your license License validated successfully This is Permanent license, with Infrastructure functionality
-
These are the processes running after the Cisco SPS application has started:
ps -ef | grep -i sip csps 13413 1 0 10:59:09 pts/3 0:00 /opt/sip/bin/Sip_Services -z -y 52931 csps 13460 1 0 10:59:20 pts/3 0:02 /opt/sip/bin/sipd csps 13433 1 0 10:59:12 ? 0:01 /opt/sip/bin/spa /opt/sip/conf/spa.conf csps 13467 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13465 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13415 1 0 10:59:10 ? 0:02 /opt/sip/bin/pserver -c /opt/sip/conf/ps.conf csps 13466 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13468 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13463 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13464 13460 0 10:59:22 pts/3 0:00 /opt/sip/bin/sipd csps 13423 1 0 10:59:11 ? 0:00 /opt/sip/bin/licenseMgr /opt/sip/conf/lm.conf
How to Check the MySQL Database
In order to examine the content of the MySQL database for the purpose of configuring the IpAddrInPathHeaders variable, use this procedure to connect to the MySQL database to check the variable content.
-
Enter the ./mysql -p sip command at the prompt.
#./mysql -p sip Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1164 to server version: 3.23.54-classic-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
-
At the mysql> prompt, issue the show tables; command.
mysql> show tables; +-----------------------+ | Tables_in_sip | +-----------------------+ | CSPS | | ControlCSPS | | DBAuthenticationTable | | DBSubscriberTable | | License | | PersistentTCP | | TempLicense | | subscriber | +-----------------------+ 8 rows in set (0.00 sec)
-
At the mysql> prompt, issue the select Farm from CSPS; command.
mysql> select Farm from CSPS; +----------------------------------------------------------------------+ | Farm | | +----------------------------------------------------------------------+ | <table><row><Host>10.48.80.149</Host><Port>5060</Port> <IpInPathHeaders /> <InRegFarm>On</InRegFarm><InRouteFarm>On</InRouteFarm></> | +----------------------------------------------------------------------+ 1 row in set (0.00 sec)
Cisco Support Community - Featured Conversations
Related Information
- Voice Technology Support
- Voice and Unified Communications Product Support
- Troubleshooting Cisco IP Telephony
- Technical Support & Documentation - Cisco Systems
| Updated: Nov 20, 2007 | Document ID: 50260 |