Introduction
This document describes how to disable the Unreachable Destination table tracking in Cisco Customer Voice Portal (CVP) Call Server.
Contributed by Janeth Leija-Beltran, Cisco TAC Engineer.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- CVP Call Server
- CVP Operations, Administration, Maintenance and Provisioning (OAMP)
Components Used
CVP Call server 8.5 or higher
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.
Problem
When CVP Call Server configuration has multiple SIP (Session Initiation Protocol) Elements in a SIP Server group, CVP sends out the INVITE to the server with the highest priority. If the SIP element is down, CVP adds the SIP Element to an Unreachable Destination table. Once the SIP element is in the Unreachable Table, CVP will not send any more requests to the element. If SIP heart beats(OPTIONS Ping) are not enabled, then SIP element stays in the Unreachable table for 180 seconds.
Call Server Log Analysis
SIP Element 10.10.10.5 added to Unrachable Table
250274141: 10.7.3.15: Jul 24 2012 09:21:13.244 -0500: %_ConnectionManagement-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.ConnectionManagement: UnreachableDestinationTable - add (10.10.10.5:5060:2). Current count: 2
Error Message displayed when Call Server tries to route call to Down SIP Element
254024258: 10.7.3.15: Aug 12 2015 10:27:05.940 -0500: %_Resolver-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.Resolver: DsSipTransactionManager.m_useDsUnreachableTable: is set to :true // Unreachable table is enabled
254024259: 10.7.3.15: Aug 12 2015 10:27:05.940 -0500: %_Resolver-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.Resolver: using ServerLocator resolver
254024260: 10.7.3.15: Aug 12 2015 10:27:05.940 -0500: %_Resolver-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.Resolver: DsSipServerLocator.tryConnect() returning binding info = null ret_connection == null
254024261: 10.7.3.15: Aug 12 2015 10:27:05.940 -0500: %_client-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.LlSM.client: tryNextServer(DsSipRequest) returning false because (m_connection_ == null).
254024262: 10.7.3.15: Aug 12 2015 10:27:05.940 -0500: %_client-4-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.LlSM.client:
com.dynamicsoft.DsLibs.DsUtil.DsException: ConnectionWrapper.check: can't establish connection
at com.dynamicsoft.DsLibs.DsSipLlApi.DsSipClientTransactionImpl$ConnectionWrapper.check(DsSipClientTransactionImpl.java:2543)
at com.dynamicsoft.DsLibs.DsSipLlApi.DsSipClientTransactionImpl.start(DsSipClientTransactionImpl.java:485)
at com.dynamicsoft.DsLibs.DsSipDialog.DsSipReinvitation.start(DsSipReinvitation.java:271)
at com.dynamicsoft.DsLibs.DsSipDialog.DsSipInviteDialog.reinvite(DsSipInviteDialog.java:1116)
at com.cisco.cvp.sip.SIPCallController$CvpSipDialog.reinvite(SIPCallController.java:4309)
(3 minutes later)
SIP Element 10.10.10.5 removed from Unreachable Table
250285352: 10.7.3.15: Jul 24 2012 09:24:13.244 -0500: %_ConnectionManagement-7-com.dynamicsoft.DsLibs.DsUALibs.DsSipLlApi.ConnectionManagement: UnreachableDestinationTable - remove (10.10.10.5:5060:2). Current count: 2
Disable Unreachable Destination Table Tracking
Caution: Setting SIP.UseDsUnreachableDestinationTable = false might not help to detect actual SIP endpoint outage or congestions. This is a workaround. Add OPTIONS ping in order to investigate the root cause of the problem.
The UnreachableTable Destination tracking can be disabled by editing the sip.properties file on the CVP Call Server.
Step 1. Open a remote desktop session into the CVP Call Server.
Step 2. Browse to %CVP_HOME%\conf (usually C:\Cisco\CVP\conf).
Step 3. Open sip.properties file in a text editor.
Step 4. Search for 'SIP.UseDsUnreachableDestinationTable'.
Step 5. Change the configuration line to 'SIP.UseDsUnreachableDestinationTable = false' .
Step 6. Restart the Call Server from OAMP (or use Windows services.msc to restart the Call Server service) .
Feedback