Table Of Contents
Release Notes for the Cisco SIP Proxy Server Version 1.0 on Solaris
Known Problems in this Release
Admendments to the Documentation
Installing the Cisco SIP Proxy Server Software
Obtaining Technical Assistance
Release Notes for the Cisco SIP Proxy Server Version 1.0 on Solaris
December 18, 2000
This document lists the known problems in the Cisco SIP Proxy Server Version 1.0 and contains information about the Cisco SIP Proxy Server that was not included in the Cisco SIP Proxy Server Administrator Guide.
Sections in this document include the following:
•
Known Problems in this Release
•
•
Related Documentation
In addition to this release note, use the following publications to learn how to install and use the Cisco SIP Proxy Server:
•
•
Recommended Sun Platforms
The following two Sun Microsystems' platforms are the recommended platforms on which to run the Cisco SIP Proxy Server:
•
–
–
–
–
–
•
–
–
–
–
Known Problems in this Release
This section lists the currently known problems in the Cisco SIP Proxy Server, Version 1.0.
Problem: shmem segment tmpnam files are not deleted (CSCdr61706)
Problem Description: Each time the Cisco SIP Proxy Server is started, a file named filexxxxx.sem (where xxxxx is a random string) is created in the /tmp directory. These files do no cause any operational problems but one might want to occasionally delete the files to eliminate clutter.
Recommended Action: None.
Problem: The Cisco SIP Proxy Server does not support SIP and HTTP simultaneously (CSCdr67142)
Problem Description: The Cisco SIP Proxy cannot establish a TCP connection or initiate a HTTP transfer regardless of the specifications for Apache-specific configuration directives that would allow it to do so.
Recommended Action: None. If HTTP support is required, a separate copy of Apache Web Server must be loaded. However, to provide adequate performance and ease of administration, we recommend that you run the Apache Web Server (httpd) and the Cisco SIP Proxy Server (sipd) on separate machines.
Problem: Server Internal Error might be returned in response to a REGISTER request (CSCds02480)
Problem Description: Occasionally, the Cisco SIP Proxy Server returns a "500 Server Internal Error" response to a REGISTER request. This problem occurs primarily during periods of heavy CPU loads and receiving REGISTER requests at a rate equal to or greater than 10 per second. Also, this problem is more likely to occur when running a server farm because the registration information is being updated on multiple machines. This condition is temporary.
Recommended Action: Reissue the SIP REGISTER request.
Problem: Static Registry entry configuration problems (CSCds07314)
Problem Description: Specifying parameters in the Static_Registry_Contact directive of a Static Registry entry causes misreadings by the code. For example, specifying a "12345678@username-solaris.company.com;action=redirect" will cause the code to read the value as "sip:12345678@username-solaris.company.com;action=redirect;user=phone" in because the entry is read as though it is specified as user@host.
Additionally, misspelling the value in the Contact_Age directive of a Static Registry entry might cause the Registry Entry to not be added. For example, if the value for the Contact_Age directive is specified as "Permat" instead of "Permanent" (a valid value), the Static Registry entry will not be added.
Recommended Action: Only enter a Static_Registry_Contact as user@host. Do not add any additional parameters. Also, verify the spelling of the value specified in the Contact_Age directive.
Problem: Cisco SIP Proxy Server does not support SIP message lines that exceed 1024 bytes (CSCds22652)
Problem Description: If an incoming SIP message has a header or Request-URI that exceeds 1024 bytes, the message might be rejected by the server with a "400 Bad Request" response.
Recommended Action: Ensure that messages with headers or Request-URIs greater than 1024 are not sent.
Problem: Parsing problems occurring with sipd.conf directives (CSCds32514)
Problem Description: Various sipd.conf file directives are not properly range checked. When configuring these parameters, care must be taken to configure them correctly.
Please be aware of the following when configuring the sipd.conf file:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Recommended Action: None.
Problem: TCB age-off timer bug might exist during requests or response retransmission (CSCds42804)
Problem Description: During the retransmission of requests or responses, a sipd child process with a Transaction Control Block (TCB) lock could crash after the age-off timer for that TCB has started. While this problem has never occurred, it is possible. If this problem should occur, the process that handles the age-off timer for the TCB will hang until it is restarted by the child process. There is no method of identifying a process that is in this state.
Recommended Action: None.
Problem: The Cisco Proxy Server requires the /etc/irs.conf to properly function (CSCds51189)
Problem Description: If the irs.conf file does not exist in the /etc/ directory, the Cisco SIP Proxy Server will hang without displaying an error message.
Recommended Action: Verify that the irs.conf file /etc/irs.conf file exists and if not, create the file and ensure that it includes the following contents:
passwd nispasswd nispasswd nispasswd nisgroup local continue,mergegroup nisservices localprotocols localhosts local continuehosts dnsnetworks local continuenetworks irpnetgroup localProblem: Syntax error message line number is incorrect and only the first syntax error is reported (CSCds52504)
Problem Description: When a syntax error occurs in the sipd.conf file, the line number reported in the syntax error message is incorrectly reported. The number that appears in the syntax error message is always the last line of the sipd.conf file and not the line in which the error occurred. In addition, only the first syntax error in the sipd.conf file is reported.
Recommended Action: None.
Problem: Certain configurations cause the Cisco SIP Proxy Server to erroneously return a SIP 400 response instead of a SIP 404 response (CSCds70275)
Problem Description: sipd.conf file directives configured as follows, ServerType Redirect, Cisco_Registry Off, and SipResolveLocalContactsInRedirectMode Off, cause the Cisco SIP Proxy Server to send a "400 Bad Request" with a "Server mode conflicts with request-Disposition" request line response when it should send a "404 Not Found" response.
This problem occurs because when a SIP INVITE request is received by the proxy and fails a registry lookup (for example, the module is disabled). The proxy attempts to do a route lookup and sees that SIPResolveLocalContactsInRedirectMode is set to Off.
Recommended Action: None.
Problem: Static routes targets that are not resolvable are not processed (CSCds73342)
Problem Description: If a static route entry is not resolvable, it is not processed. For example, if two static routes to a target are configured as gw1.domain.com and gw2.domain.com and the gw1.domain.com route has a higher priority and weight, it is selected. However, if the attempt to resolve gw1.domain.com fails, the Cisco SIP Proxy server does not try the second route, gw2.domain.com. However, if gw1.cisco.com is resolvable but down, the Cisco SIP Proxy Server will try the route until it has exhausted its retransmission attempts and then it will try gw2.domain.com.
Recommended Action: Ensure that the static route target entries are resolvable. Static routes should be IP address or FQDNs that can be resolved via a DNS lookup.
Problem: The "include" directive does not work for some block configuration directives (CSCds73530)
Problem Description: Block configuration directives (for example, <StaticRouteID> and <StaticRegistryID>) cannot be placed in a separate file and "included" in the sipd configuration file. Static routes and static registry entries must be defined in the main sipd.conf file.
Recommended Action: None.
Problem: On rare occasions, the Cisco SIP Proxy Server might fail to send some messages (CSCds74923)
Problem Description: When running on the Solaris 2.6 Operating Environment, on rare occasions the Cisco SIP Proxy Server might fail to send some messages during periods of heavy retransmission and retransmission timers simultaneously expiring. If this condition occurs, the following message is logged in the error_log file "Error trying to create UDP socket." This condition indicates that either the next hop server is down or the network is overloaded.
Recommended Action: None.
Problem: Starting the Cisco SIP Proxy Server (sipd) process directly can cause multiple sipd processes to start (CSCds82140)
Problem Description: Not using the sipdctl script to start the Cisco SIP Proxy Server can cause problems if another copy of sipd is already running. If another set of sipd processes are already running, directly starting the Cisco SIP Proxy Server will start additional sipd processes. The additional sipd processes will then consume memory and might impact the original sipd processes.
Recommended Action: Always start the Cisco SIP Proxy Server using the sipdctl script (issue ./sipdctl start from the server directory).
Admendments to the Documentation
This section contains information that was not included in the Cisco SIP Proxy Server Version 1.0 Administrator Guide or the CD Installation Guide for the Cisco SIP Proxy Server on Solaris.
Installing the Cisco SIP Proxy Server Software
The installation procedure documented in the "Installing the Cisco SIP Proxy Server Software" section describes how to install the Cisco SIP Proxy Server in such a manner that it will run as root when started. The user id will be landv and the group will be 25.
For security purposes, create a user ID and group under which to run the Cisco SIP Proxy Server before installing the software. If you have already installed the Cisco SIP Proxy Server software as root user, change the ownership of the directory and ensure that you have write privilege to the logs directory.
Also, the Cisco SIP Proxy Server on Solaris image name as it appears on the product CD is sip-server-1.0-solaris.tar.gz.
Obtaining Documentation
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•
•
•
–
–
You can e-mail questions about using CCO to cco-team@cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Access Registrar, AccessPath, Are You Ready, ATM Director, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, Cisco Powered Network logo, Cisco Systems Networking Academy, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, iQ Logo, iQ Readiness Scorecard, Kernel Proxy, MGX, Natural Network Viewer, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, WebViewer, Workgroup Director, and Workgroup Stack are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert Logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Collision Free, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0010R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Guest