Release Notes for the Cisco SIP Proxy Server (SPS) Version

Transcription

1 Release Notes for the Cisco SIP Proxy Server (SPS) Version November 9, 2004 OL Rev. A1 This document lists the known problems in the Cisco SIP Proxy Server (SPS) Version and contains information about the Cisco SPS that was not included in the Cisco SIP Proxy Server Administrator Guide. Contents These release notes describe the following topics: Related Documentation, page 2 Recommended Platforms, page 2 New and Changed Information, page 4, page 6 Obtaining Documentation, page 37 Obtaining Technical Assistance, page 38 Corporate Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA Copyright Cisco Systems, Inc. All rights reserved.

2 Related Documentation Related Documentation In addition to this release note, use the following publications to learn how to install and use the Cisco SIP Proxy Server: Cisco SIP Proxy Server CD Installation Guide Version 2.2 Describes how to install the Cisco SIP proxy server (Cisco SPS) software on a a Linux or Solaris platform and how to do preliminary configuration tasks. This document ships with the product CD and is available online at: Cisco SIP Proxy Server Administrator Guide, Version 2.2 Describes how to configure a Cisco SIP proxy server (Cisco SPS) to be operational in a voice-over-ip (VoIP) network. This document ships with the product CD and is available online at: Recommended Platforms The following platforms are the recommended platforms on which to run the Cisco SPS: Linux IBM xseries 335: 2 x 2.0 GHz or higher Memory - 1 GB or more Disk - 40 GB or larger OS Version - RedHat Enterprise Linux 3.0, Versions AS, ES, or WS Solaris High End Netra 20 Memory - 1 GB or more Disk - 40 GB or larger OS Version - Solaris 8 (2.8 kernel) Solaris Low End SunFire V120 Memory MB or more Disk - 40 GB or higher OS Version - Solaris 8 (2.8 kernel) Note Cisco SPS requires the use of one of the operating systems listed above. Cisco SPS will not run on operating systems other than those listed. The per platform performance summary may be used to help determine which platform is best suited for your needs. 2

3 Recommended Platforms Cisco SPS Version 2.2 Performance Cisco SPS Version 2.2 performance is shown in Table 1. Table 1 Cisco SPS Release 2.2 Performance Platform CPU Registers / Sec Calls / Sec Maximum UDP TCP UDP TCP Registered Users 1 Sun Fire V120 1 x 550 MHz ,000 Netra 20 2 x 900 MHz ,000 IBM xseries x 2.0 GHz , Based upon 20,000 users, at 10 cps, and on UDP only, using the performance factors in the following list. Table 2 lists the current limitations of SPS 2.2 functionality. Table 2 Current Limitations of SPS 2.2 Functionality Object Value Maximum Routes 20k Maximum Subscribers 20k 1 Maximum Registrations Refer to Table 1. Maximum Forks (Contacts per AOR) 6 Maximum Next Hops per Dial Pattern 100 Maximum RADIUS preauth servers 10 Maximum RADIUS accounting/authentication 2 servers Maximum Virtual Proxy Domains 10 (registration, authentication, and accounting per domain, cannot do number expansion or routing per domain) Maximum GK's per cluster 5 Maximum servers per farm 2 Maximum MySQL dbs 2 Maximum persistant TCP connections 1000 Maximum persistant TLS connections 1000 Maximum external ENUM servers 2 Maximum number of Sipd's on one machine tested See Table 1 for hardware specific numbers Up to 1000 Transmission Control Protocol (TCP) Connections per Server Performance assumptions Redundant servers Record route used 3

4 New and Changed Information Maximum number of dynamic registrations TCP connections not reused. (Reuse will improve performance.) 30% overhead allowed for other features For Solaris servers with concurrent registrations and calls, a conservative engineering guideline is: X = (expected peak registers per second (rps) / value in table) * 100% Y = (expected peak calls per second (cps) / value in table) * 100% X + Y <= 80% Linux servers can sustain peak rps and cps concurrently New and Changed Information The following sections list the new hardware and software features supported by the Cisco SIP Proxy Server, Version New Hardware Features in Cisco SIP Proxy Server, Version Cisco SPS is software based and does not support hardware features. New Software Features in Cisco SIP Proxy Server, Version This section documents new software features supported by the Cisco SIP Proxy Server, Version Note A cumulative list of all new and existing features supported in this release, including platform and software image support, can be found in Cisco Feature Navigator at the following link: To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank to cco-locksmith@cisco.com. An automatic check will verify that your address is registered with Cisco.com. If the check is successful, account details with a new random password will be ed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL: Functional Enhancements for Cisco SIP Proxy Server, Version Upgrade support Linux OS to Red Hat Enterprise Linux 3.0. Improved privacy Configurably add and remove P-Asserted-Identity headers to authenticated INVITE requests received from or sent to trusted or untrusted addresses. Configurably add and remove Remote-Party-ID headers to authenticated INVITE requests received from or sent to trusted or untrusted addresses. Diversion headers 4

5 New and Changed Information Configurably validate and rewrite Diversion headers in 3xx Redirection responses received prior to sending the corresponding INVITE requests. Configurably remove Diversion headers from INVITE requests received from untrusted addresses Configurably, per subscriber, add "privacy=full" token in locally generated Diversion headers in call forwarding scenarios, and anonymize such Diversion headers before sending to untrusted addresses. Rewrite Diversion headers before sending to untrusted addresses. Support additional wildcard usage in static routes. Support embedded '*' characters in static routes Handle wildcard routes as a single route rather than expanding as a set of routes with variable number of trailing '.' characters. TLS security patch. MySQL upgrade to incorporating latest security patches. Administrative Enhancements for Cisco SIP Proxy Server, Version Provide a Privacy page in graphical user interface (GUI) to support configuration of CLIR features for the proxy. Modify the Access Control page to add information for Trust Lists. Subscriber database and GUI support for CLIR field per subscriber. Represent registration expiration time as a date, and color red if registration has expired. Simplified log file rotation configuration with checkbox enable/disable and menu for rotation units. 5

6 Open Caveats Cisco SIP Proxy Server, Version This section documents possible unexpected behavior by the Cisco SIP Proxy Server, Version Open Caveats for the Cisco SIP Proxy Server, Version 2.2 CSCdr26023 Comments not supported in header value Problem : SPS doesn't support comments embedded in sip header. However, from SIP RFC: Comments can be included in some SIP header fields by surrounding the comment text with parentheses. Comments are only allowed in fields containing comment as part of their field value definition. In all other fields, parentheses are considered part of the field value. comment = LPAREN *(ctext / quoted-pair / comment) RPAREN ctext = %x21-27 / %x2a-5b / %x5d-7e / UTF8-NONASCII / LWS ctext includes all chars except left and right parentheses and backslash. A string of text is parsed as a single word if it is quoted using double-quote marks. In quoted strings, quotation marks (") and backslashes (\) need to be escaped. quoted-string = SWS DQUOTE *(qdtext / quoted-pair ) DQUOTE qdtext = LWS / %x21 / %x23-5b / %x5d-7e / UTF8-NONASCII Examples: Retry-After: 120 (I'm in a meeting) 6

7 CSCdr26025 Headers inside SIP URL are not supported Problem : SPS doesn't support headers in sip URL. From RFC 3261, headers are an option component of a SIP URI.: Headers: Header fields to be included in a request constructed from the URI. Headers fields in the SIP request can be specified with the "?" mechanism within a URI. The header names and values are encoded in ampersand separated hname = hvalue pairs. The special hname "body" indicates that the associated hvalue is the message-body of the SIP request. SIP-URI SIPS-URI = "sip:" [ userinfo ] hostport uri-parameters [ headers ] = "sips:" [ userinfo ] hostport uri-parameters [ headers ] headers = "?" header *( "&" header ) header = hname "=" hvalue hname = 1*( hnv-unreserved / unreserved / escaped ) hvalue = *( hnv-unreserved / unreserved / escaped ) hnv-unreserved = "[" / "]" / "/" / "?" / ":" / "+" / "$" Example: sip:user@host?subject=foo&call-info=< CSCdr61706 CSCds52504 CSCds53849 shmem segment tmpnam() files are not deleted Problem : Each time the server is started a file named "filexxxxx.sem", where XXXXX is a random string is created in the "/tmp" directory. This causes no operational problems but the administrator may want to occasionally delete them to eliminate clutter. Misleading syntax error message when sipd.conf is wrong Problem : When there is a syntax error in the sipd.conf config file, the line number is reported incorrectly. It always shows the last line of the config file instead of the line number where the error actually occurred. An example of such a config error would be an illegal value given for a valid directive. A related problem is that only the first syntax error in the configuration file is reported. Recommended Action: There is no workaround other than correcting the misconfiguration. CSPS: sipdctl configtest does not detect all syntax errors Problem : The sipdctl configtest command does not accurately detect all syntax errors. Also an incorrect line number is reported when a syntax error is detected. Possible errors that are not detected include illegal values given in non-boolean directives. Conditions: Run./sipdctl configtest with an invalid sipd.conf file. Recommended Action: The sipd.conf configuration file can only be verified by successfully loading the server. 7

8 CSCds56981 CSCds75715 CSCdt35155 CSCdt35294 CSCdt50814 CSPS: Start Sip_Services after a Farm DBs Old entries are deleted Problem : If the proxy server has been down for more than the Cisco_Routing_Max_DB_Age_on_Boot or Cisco_Registry_Max_DB_Age_On_Boot, the ServerRoot/logs/*.db files will be removed/cleaned. Otherwise, these values might actually get re-used if a farm member tries to sync. CSPS: sipdctl start: sipd started message is misleading Problem : When starting SPS from the graphical user interface (GUI) or command line, it is possible to see sipdctl start: sipd started when in reality sipd was not able to start correctly. Conditions: This can happen for a number of reasons, including a failure to allocate enough shared memory or corrupted databases. Recommended Action: Manually check that sipd started successfully by looking at the error_log file and/or running the command ps -ef grep sps to make sure there are the correct number of sipd processes running (the default is 7). CSPS: External entity failure causes reduced performance : Server child processes have no means to communicate failures of external entities to the other child processes. Conditions: A failure of an external entity (e.g., RADIUS, DNS, subscriber db), is not communicated to all child processes. Problem : Server performance can drop significantly, depending on the number of child processes executing. Recommended Action: Reducing the number of child processes is the only was to alleviate this problem. Add Registry/Routing Code changes to support TEL URL Problem : Proxy parses tel Urls completely based on the rules specified in RFC At this point, there are no routing changes based on tel: url additional fields. Conditions: For example, in "tel:1111;phone-context=919;phone-context=456", only 1111 is used for routing the call like in sip: url, not the additional fields. And tel url is transformed to a sip: Url as follows: sip:1111@whatever-proxy.com SIP/2.0 RecordRoute:<sip:1111@whatever-proxy.com;parameters including phone-context> Recommended Action: At this point, there is no intelligence to change the number from "tel:555xxxx;phone-context=919" to "tel: xxxx". CSPS: Log file check and verification needed for proxy server Problem : When the CSPS is started, it writes the logs to the error_log and access_log files in the logs subdirectory by default. The log files can be deleted manually while the server is still running, the CSPS will continue to run but no logs will be logged due to the deletion of the log files. Recommended Action: After the deletion of the log files, one can (graceful) restart the server so new log files can be created and server can then continue the logging process. 8

9 CSCdt87934 CSCdu00398 CSCdu69703 CSCdu82119 CSCdv34778 CSPS: Proxy will crash if SharedMemorySize too little for call rate Problem : The CSPS proxy can crash if it is not configured with enough shared memory to handle the call rate. Recommended Action: This problem can be resolved by increasing the value of SharedMemorySize directive in sipd.conf file. To configure the total usable shared memory segment size on Linux or Solaris platform, please follow the instructions in the README.cisco file. User agents on same box/different port disallowed Problem : Proxy will not terminate calls to a user agent running on the same box but different port. Conditions: Setup a testcase when there is another SIP entity running on same box where SIP proxy is running (on different port), and try to make a call that has that SIP entity in the call path. Recommended Action: User agents should be running on a different machine than the proxy. CSPS: Accounting with XACCT Radius not working properly Problem : If accounting is enabled on CSPS, the session-id for START and STOP records is populated with SIP Call-Id, which is needed so that it is possible for the Radius/billing server to correlate the STOP with the appropriate START. For accounting to work correctly, the back end Radius/billing server must be able to accept and correlate START/STOP records with duplicate session-id values. In the case of the XACCT Radius server, XACCT does not respond at all to records with duplicate session-ids. As a result, CSPS blocks waiting for a response. Eventually, CSPS times out and continues processing the call; however, if enough concurrent calls are placed, it is possible that all of CSPS's processes will be blocked waiting for Radius responses and call processing will effectively stop. Conditions: Accounting is enabled and the backend Radius server does not respond to RADIUS request records with duplicate session-ids. Recommended Action: Disable accounting or use a backend Radius server, such as Livingston, which supports the reception of multiple Radius records with the same session-id. CFLAGS does not cover all include directories CSPS: CFNA timers not reset if BYE sent instead of CANCEL Problem : When a call is made to a IP phone registered to CSPS which has a Call Forward No Answer (CFNA) entry in MySQL, if the caller hangs up on the call during the ringing phase before it is answered, the behavior of CSPS is dependent on the IP phone sending a CANCEL before/instead of sending a BYE. 1. If CANCEL is sent when the caller hangs up, the call is terminated without any problems. 2. If BYE is sent instead of CANCEL, CSPS keeps the CFNA timer running and this leads to an INVITE being sent by CSPS to wherever the user has CFNA configured after the timer expires. This may lead to a phone ringing suddenly out of the blue when no call is being made. Conditions: This is an issue only in the following circumstances: 1. CFNA is being used 2. The SIP client originating the call does not send a CANCEL when aborting an attempted call, but sends only a BYE instead. 9

10 CSCdv54154 CSCdw94123 CSCdx61275 CSPS: Proxy returns 400 Req-URL is bad when rec tel url w/cic parm Problem : When handling a SIP INVITE with a tel URL containing the cic parameter, the proxy returns "SIP/ Request-URI is bad". If should convert the tel URL to its equivalent sip URL. For example, the following INVITE: INVITE tel: ;cic=1234 SIP/2.0 results in a 400 response from the proxy. Conditions: This problem occurs whenever the proxy receives a tel URL containing a parameter it does not explicitly support. CSPS: Cannot rename MySQL db fields if using provisioning Problem : In sipd.conf, it is possible to re-map the MySQL subscriber database field names from the default names used by the MySQL installation script to new values which may be preferred. One reason to do this is perhaps because the customer already has an existing MySQL subscriber database and wants CSPS to use it. In this case, CSPS will read and use the new field names specified in sipd.conf. The problem is that if the customer is using provisioning, the provisioning graphical user interface (GUI) will not read sipd.conf, nor will it use the new field names. Rather, it will ignore any new field names and use the default names which match those used by the MySQL install script. Conditions: This is an issue only if the customer is using CSPS with Provisioning and has an existing MySQL database which they wish to use rather than using the MySQL installation script to create a new database. If the existing database has different names for the MySQL table fields than those used by the Provisioning system, new subscriber information entered using the provisioning GUI may not be accessible by CSPS. CSPS: SNMP: Error message in csps_ciagent_install Problem : When installing ciagent, error messages are displayed setany $Version $Agent $User \ smlaunchcontrol.$lowner.$lname abort Error code set in packet - INCONSISTENT_VALUE_ERROR: 1. setany $Version $Agent $User \ smscriptadminstatus.$sowner.$sname disabled Error code set in packet - INCONSISTENT_VALUE_ERROR: 1. setany $Version $Agent $User \ smscriptrowstatus.$sowner.$sname destroy smscriptrowstatus = destroy(6) These error messages logged from running the script smpopscript when installing CIAgent for the first time on a system are benign and are due to the fact that it is trying to remove an item that does not exist in the script MIB table. As far as all the other subsequent setany commands are executed successfully, the smpopscript is considered to finish its job well. 10

11 CSCdx66179 CSCdx67593 CSCdx78228 CSCdx83047 CSCdx88304 CSPS: SNMP: sappagt is taking 100% cpu for a few minutes at startup Problem : sappagt is taking 100% CPU when starting ciagent. This is fine, since we don't plan to restart ciagent frequently. Response from vendor: Both the sappagt subagent and the hostagt subagent show high CPU utilization upon startup because they both must retrieve a large amount of information from the system, to initialize the tables they support. Once these tables are initialized, the utilization will go down. This is not abnormal behavior. Recommended Action: On a Linux machine that has a lot of packages or softwares installed, the System Applications Monitor (sappagt) may take 100% CPU for a few minutes at startup. If you think this is not acceptable, you can disable this subagent from being invoked by removing its name, sappagt, from the ciagent script file under /usr/local/ciagent directory on your Linux machine and restart ciagent. CSPS: MySQL Suscriber table needs to be CASE SENSITIVE to USER info Problem : MySQL sees "tdeleon" and "TDELEON" as the same. As a result, CSPS accesses MySQL for Authentication & Call Forwarding info for a single entry which is incorrect. And MySQL will not allow another entry. Conditions: I was testing our SIP products for CASE Sensitivity to the USER portion of the SIP URI and I have noticed that the CSPS, Phones, and Gateways recognize the differences between "tdeleon" and "TDELEON". One issue that I did see was with MySQL. CSPS: TCP on solaris using too many fds for reuse=off Problem : Transmission Control Protocol (TCP) calls are not accepted/connected by proxy Conditions: When TCP services are not configured to reuse the TCP connections, the proxy can run out of file decriptors because OS may not free the file descriptors immediately. this happens when proxy is connected with other SIP entity on Solaris or Linux, however with Cisco gateways the connections are closed immediately. Recommended Action: When configuring the system, if proxy is expected to connect with Solaris or Linux based SIP entities, it should be configured to reuse the TCP connections. SNMP critagt sends trap with sipds child process id Problem : The Solaris version of the critagt (Critical Applications Monitor) subagent sometimes reports critappup traps with one of sipd children's process id. The vendor explained that is because the critagt always try to get and monitor the first process id in the process table that matches the specified application name. However, since on Solaris the first process id that matches sipd is not always the master/parent sipd, but rather likely one of the child sipd's. We really want to monitor master sipd's status, so we want the vendor to fix/improve their handling of process ids in critagt. This doesn't seem to be a problem on Linux, since the first process id seems always to be the master sipd's, and the traps correctly report that. CSPS: GUI does not allow input of &, >, < in any field Problem : Data entered into any field through the graphical user interface (GUI) may not not contain any of the characters &, < or >. The GUI will reject any data with these characters and prompt for it to be re-input. 11

12 CSCdx91876 CSPS does not convert a tel: url to a sip: url correctly Problem : CSPS provides only limited support for the tel URL. Essentially, it translates the tel: URL into a sip: URL, then handles the message based on the sip: URL. The translation performed is as follows: tel:<global-phone-number> SIP/2.0 is converted to sip:<global-phone-number>@<proxydomain>;user=phone SIP/2.0 If there are additional parameters in the tel URL, they are not handled correctly. For example: tel: ;phone-context=408;subject=hello SIP/2.0 CSPS converts the tel: URL to the following sip: URL: sip: @ :5060;user=phone;phone-context=408 SIP/2.0 The sip: URL should be: sip: ;phone-context=408;user=phone SIP/2.0 CSCdx95989 CSCdy01790 Conditions: The tel to sip URL conversion will be a problem if the URL contains additional parameters other than a global phone number. CSPS: sysadmin_csps_regroute takes 97% CPU when window closed Problem : Closing the window in which the sysadmin_sps_regroute is running, rather than exiting cleanly using the 'Q', 'q', or 'Ctrl-C' command, will cause the sysadmin_sps_regroute to take 97% CPU time. Recommended Action: The workaround is to not close the window prior to exiting the tool, however, once in this state, you can stop the process with either SIGINT or SIGQUIT signal. CSPS: CIAgent: Dr-Web on Linux Make Changes button not working Problem : On Linux, when using dr-web to make changes to the critical application monitor and clicking on Make Changes button, sometimes the change does not take place until the user clicks on the Reload button on the web browser. Recommended Action: Click on the Reload button on the web browser to make the changes reflected in CIAgent. 12

13 CSCdy02296 CSCdy05591 CSCdy05850 CSPS: when recovering from a split netwrok, some registrations lost Problem : In the event of a split network, it is possible that each farm member will separately accept new registrations. When the networks join, a sync is performed; however, the sync is performed based which member accepted the most registrations rather than as a merge. As a result, some registrations may be lost. For example, if there are farm members P1 and P2: The registration database prior to let split contains entries for a,b,c. A network split occurs. P1 accepts new registrations for d,e,f P2 accepts new registrations for g,h The networks join. P1's view of the world is inherited by P2, so the registry is: a,b,c,d,e,f; and g,h are lost. Conditions: 1. 1) There must be a farm of 2 or more servers with registration farming enabled. 2. Clients must be configured to load balance or failover between the servers. 3. A split network must exist for a period of time, and during that time more than one server must accept one of more registrations. Recommended Action: Configure the servers as primary and secondary such that all clients register with the same server at any point in time. This requires that the clients do not experience the split with some seeing only the primary and some seeing only the secondary. This may or may not be possible. CSPS: Too many open files with persistent TCP connection Problem : Transmission Control Protocol (TCP) calls may fail with error message socket: Too many open files. Conditions: When proxy is connecting with other Solaris or Linux based SIP entities, it may run out of file descriptor even with the persistent connections concurrent TCP connections is the supported limit. CSPS: MySQL wont install if SNMP just started Problem : MySQL installation fails with the error message: cannot get exclusive lock on /var/lib/rpm/packages Conditions: This happens when MySQL installation is started just after starting ciagent. The problem is that when ciagent starts, it gets an exclusive lock on /var/lib/rpm/packages. MySQL installation also needs this lock, therefore MySQL installation will fail. Recommended Action: When starting ciagent, wait for about 30s before installing MySQL. 13

14 CSCdy07416 CSPS: escaped characters in URIs are not handled Problem : A customer ran into a problem with this specifically when dealing with tech prefixes. The problem was that the '#' character was inserted in the Request URI and To headers by the GW in the INVITE is sends to SPS. SPS can strip the '#' from the Request URI, but not from the To. SPS also includes the '#' in its Record-Route header. The fix is to have the GW escape the '#' as %23 wherever it appears. Now SPS needs to be able to translate from escaped to non-escaped for the LRQ. Currently SPS treats escaped characters within URIs no differently than any other character. It parses them fine, and is able to store them (e.g. in the registry db) and pass them along, but it doesn't convert them from escaped to non escaped when it should. At a minimum to solve this problem, a solution is to have the GW makes code changes to escape the '#' character in all urls before sending the INVITE to the proxy. SPS will need to modify the remote access server (RAS) module to unescape the %23 before constructing the LRQ. As for fixing this in general, it is legal for URLs to escape any characters it likes, meaning that SPS could receive %31%32%33%34 in the username which should be interpreted as 1234 for number expansion, accounting, routing, etc. CSCdy29642 CSPS: Regroute cannot parse DOS formatted sipd.conf file Problem : Open a valid sipd.conf file using Wordpad and save it. This will reformat it into DOS format. Try to use sysadmin_csps_regroute tool and you will get the following error: : No such file or directory Recommended Action: Convert sipd.conf back to UNIX format, or use the graphical user interface (GUI) to create a new sipd.conf. CSCdz20402 CSPS: tcp to udp translation is not Problem : The call success rate for Transmission Control Protocol (TCP) to UDP translation calls is not % Conditions: When proxy is doing translation of transport between TCP and UDP, some of the calls may fail. CSCdz23707 CSPS: proxy retransmits non-local non-2xx over TCP Problem : SPS retransmits non-local non-2xx responses over Transmission Control Protocol (TCP). According to the standards, this retransmission is not supposed to happen; however, it will not cause any problems. Conditions: If the client on the TCP connection does not send an ACK for non-200 response, then SPS starts to retransmit the final response, similar to UDP behavior., but the retransmission may be safely ignored. 14

15 CSCea25188 CSCea30173 CSPS: Add/upgrade w/ GUI resets farm member specific data Problem : 1. CSPSConfConvertor does not push the original member specific data for each farm member into MySQL, because CSPSConfConvertor reads from only one sipd.conf file and does not have access to the member specific data in the other sipd.conf files. So all member specific data is reverted back to their default values. 2. csps_setup always writes the per farm member specific data with defaults. Therefore any original member specific data will be replaced with defaults. Conditions: 1. When adding the GUI to configure sipd.conf. 2. When upgrading to SPS 2.1 and currently using the GUI to configure sipd.conf. Conditions: The farm data is an xml blob that contains a list of Farm members plus the member specific data such as "host", "port" (default 5060), "ip in path headers" (default <empty>), "in registry farm" (default On), and "in routing farm" (default On). Recommended Action: Write down the old farm member specific data before adding a GUI or upgrading to SPS 2.1. After adding the GUI or upgrading to SPS 2.1, manually reset the farm member specific data accordingly. CSPS: not found Problem : When using "/etc/init.d/mysql stop start", the following error appears: not found This occurs when directly running this command, or indirectly running this comand via csps_setup (and install_mysql_db), uninstall_mysql_db, and after a reboot. Recommended Action: None. However, you can simply ignore this error message, since it does not affect anything. 15

16 CSCea58230 Static routes do not support. in middle of dest pattern Problem : SPS allows wildcarded digits in the destination pattern of static routes in the form of a '.' character. For example, 5... as a destination pattern means any 4-digit number beginning with a 5. However, SPS does not support wildcarded digits followed by non-wildcarded digits. For example, the following are not supported: Recommended Action: There are two options: 1. Use a less restrictive destination pattern which does not require embedded wildcard digits. For example, each of the problematic destination patterns above could be made less restrictive as follows: > > > >... CSCea Use multiple more restrictive destination patterns which do not require embedded wildcarded digits. For example:.555 -> 0555, 1555, 2555, etc. SPS: error handling after receiving data from DNS request Problem : SPS receives an INVITE for a number for which it is configured with a static route: next-hop: sip-gateway.foo.bar port : 0 So SPS appropriately performs an SRV query for sip-gateway.foo.bar. Then, the SPS performs an A query as expected and gets information back from the DNS Server, but fails to forward the message: [Mon Mar 31 15:49: ] sip_sm.c(2001) "SRV" Query for sip-gateway.foo.bar successful,got 1 records. [Mon Mar 31 15:49: ] sip_sm.c(2030) "A" Query for sip-gateway.foo.bar successful, Got But then SPS does not send forward INVITE, and instead prints the following error in the error log: [Mon Mar 31 15:49: ] PID(32608) apr_socket_write() failed, Error string Invalid argument The problem is the SRV query returns the hostname of the gateway with the port of 0, rather than 5060 or some other valid port. As a result, the sender of the INVITE is left waiting until the request times out. Rather, SPS should return a 503 for the transport error. Recommended Action: None, however, if DNS is configured correctly, this issue can be avoided altogether. 16

17 CSCea66342 RFC 3261 compliance, do not send CANCEL if no provisional response Problem : A proxy should not send a CANCEL for an INVITE for which it has not received a provisional response, but SPS sends CANCEL for all branches associated with the INVITE regardless of whether or not a provisional response has been received. Conditions: SPS received an INVITE and forwarded it to one or more downstream entities. It then receives a CANCEL and forwards the CANCEL to any downstream entities from which it has not received a final response, including those from which it has not received any provisional response. According to RFC 3261, the CANCEL should not be sent unless a provisional response has been sent. This bug does not effect the functionality of SPS. This was allowed in RFC 2543 but leads to potential race conditions. CSCea82993 Cannot redirect output of sysadmin_csps_regroute to a file Problem : Attempts to redirect the output to a file fail. Example: > # cat input-file > d > s > e 5000 > q > > #./sysadmin_csps_regroute < input-file > output-file Afterwards, output file is empty. Recommended Action: Use expect scripts rather than redirecting the output. CSCea91984 ControlCSPS on 2 servers checked only unchecks one Problem : In certain situations in the Proxy Control screen, only one of two servers becomes unchecked after a Graceful Restart. Conditions: This has only been observed on Windows. In the ProxyControl screen check both servers in the farm and make sure the bottom one is highlighted. Click the Graceful button. Only one of the servers becomes unchecked. The other one stays checked. Note that if the top server is highlighted, both servers become unchecked. Also note that the Graceful Restart will have been performed. Recommended Action: Make sure that the top server in the table is highlighted instead of the bottom one to prevent the situation. Should the scenario occur, the checkmark will be cleared if the window is redrawn. Simply minimize and reopen the window or the user can click on the affected row. CSCeb05010 SIP client diverts not working properly (double diverts not working) Problem : Multiple redirects not working properly. When inserting Diversion headers SPS does not order them properly. New Diversion headers are always added last rather than first. This may cause undesired or unexpected results with respect to call completion, voice mail, and/or billing for calls involving multiple diversions. Conditions: Using SPS with the following feature set: SPS configured as a stateful, recursive proxy CFNA, CFB, CFUNV features enabled AddDiversionHeader enabled A call flow involving multiple call forward invocations by SPS on the same call. 17

18 CSCeb05745 CSCeb21352 CSCeb27053 CSCeb27117 CSCeb38768 SPS: pserverctl needs to stop Sip_Services Problem : If using pserverctl rather than the sip script to stop or restart the pserver, the Sip_Services process will not be restarted or stopped, but will continue to run. Conditions: For custom setups where pserver is the only Cisco SPS process running on the farm member, and pserver is being restarted in order to change the farming configuration. If the farm configuration is changed, and Sip_Services continues to run without itself being restarted, then that Sip_Services can seriously degrade the performance of the farm, either by trying to connect to a missing farm member, or by causing unnecessary data synchronization between farm members. Recommended Action: If possible, use the /etc/init.d/sip script to restart and stop SPS. Otherwise, when you need to restart the pserver via pserverctl, do a pserverctl stop first, then kill the Sip_Services process, the issue a pserverctl start. With reuse off and record route on, run out of tcp connections Problem : Under high Transmission Control Protocol (TCP) traffic SPS may run out of TCP connection limit of 1000 soon. Conditions: When AddRecordRoute flag is On, and the SipTcpReuseConnection flag is Off, then some of the TCP connections take longer to get freed. Recommended Action: Decrease the value of SipMaxT3InMs, which is used to detect timeouts for idle connections. CSPS: Wait Timer remains after edit multiple entries Problem : After performing an Edit or Add within a table in the Cisco SPS graphical user interface (GUI), the wait cursor does not change back to the default cursor. Conditions: Can occur when editing multiple records at once. Recommended Action: The user need only move the mouse cursor to the top menu bar of the GUI or off of the GUI completely and back on to restore the default cursor. SPS: proxy does not handle failover for ACK messages Problem : When the next hop in the ACK's route list is not reachable, proxy is not able to failover to the alternate DNS records, unlike other SIP requests. Conditions: This happens when the next hop is not reachable from the default n/w interface, but it uses the alternate n/w interface to retransmit the 200 OK, which result in the upstream user retransmitting the ACK. Error seen when exiting CiscoSPS GUI on Windows OS Problem : When closing the graphical user interface (GUI) installed on a Windows 2000 PC, the following log is generated in./logs/pserver_log: # tail -f./logs/pserver_log ERR : transport/connection.cxx:257 Failed to read data, reason:connection reset by peer This error is not seen when using the GUI installed on Linux or Solaris. Recommended Action: The error message is non service affecting and can be ignored 18

19 CSCeb44311 CSCeb49412 CSCeb61814 Client side STOP not generated if no 487 is received Problem : When a 200 to CANCEL is received on a branch but no 487 ever comes back from the downstream, SPS will not be able to generate a client side STOP record for that branch. Recommended Action: If the canceled branch is the only branch or the best branch to return response upstream, a 408 response will be returned upstream when the original INVITE request finally times out in SPS, and the user can gather some information from the server side STOP record instead. CSPS: Toggling Virtual Proxy Host on/off can cause duplicate records Problem : Cisco SPS has virtual proxy host enabled, and two registrations with the same user id but different domains have been entered, i.e. user id: 3000, domain: foo.com and user id: 3000, domain: bar.com. If virtual proxy host is then disabled in SPS, it appears as if there are duplicate records for the 3000 user. If one of these records is then changed, the database starts behaving badly. Recommended Action: Once virtual proxy host is enabled, do not disable it. GUI dynamic column resize sometimes fails Problem : One column of a table can stretch across the entire viewable area of the graphical user interface (GUI). The user must move the slider bar to see the other columns. Conditions: Sporadically, after performing an action in the GUI, a column may fill up the viewable area of the GUI and cause the other columns to be pushed to the side. Recommended Action: Click on the Refresh button or click on the column header to resize the columns. 19

20 CSCeb71070 CSPS: Changing UseVirtualProxyHost from Off to On causes conflicts Problem : Turning the 'Use Virtual Proxy Host' directive from On to Off can cause several problems. 1. Phones using entries with a Domain Name previously set to a Virtual Proxy Host before the 'Use Virtual Proxy Host' directive was turned Off can no longer be called. 2. Entries with a Domain Name previously set to a Virtual Proxy Host before the 'Use Virtual Proxy Host' directive was turned Off can no longer be edited or deleted via the graphical user interface (GUI). 3. Entries which were unique before the directive was turned Off may no longer be unique. 4. The Domain Name column is empty. Conditions: The database uses the Registry entry's 'Domain Name' as one of the key fields for identifying unique registry records. When the directive is On, the database stores the value of each Registry record's domain name and retrieves it when requested. When the directive is turned off the database no longer uses the stored value, but instead, uses the current value of the 'Proxy Domain' directive. When attempting to access records, the Proxy Domain is used. Since this does not match what is stored in the database, the records which have domains which do not match the Proxy Domain can not be accessed. Recommended Action: Recommendation is that you leave 'Use Virtual Proxy Host' set to On. If you no longer wish to have any Virtual Proxy Hosts, delete all of them from the table, but leave 'Use Virtual Proxy Host' set to On. If you must turn it Off for some reason, follow the steps below. Before turning 'Use Virtual Proxy Host' Off, the user should prepare the existing Registry records. Manually change the Domain Name for each Registry Record to match the Proxy Domain. Verify that this does not cause two records to become the same. If so, assign a new user ID to one of them or change one of the other values such that the records remain unique. If a record is no longer needed, delete it. If the database is large, this can be done more quickly using the export/import functions under the GUI's Operations menu. Export the Registry database into a comma separated value (CSV) file using the GUI's export command. Open the saved file in Microsoft Excel and modify the Domain Name column so that all entries are set to the Proxy Domain. Import the modified CSV file back into Cisco SPS using the GUI's import command. If these steps were not followed before turning 'Use Virtual Proxy Host' from On to Off, simply turn it back on and follow the steps above before turning it off again. CSCec03170 Support multiple Proxy-Authorization headers in INVITE Problem : When multiple Proxy-Authorization headers are present in an INVITE and authentication is turned on, SPS can't handle these Proxy-Authorization headers and sends back 407. Recommended Action: Only configure one SPS do authentication so that only one Proxy-Authorization header is present and necessary to pass authentication check. CSCec24660 SPS: Timestamps in error_log do not correspond to servers date & time Problem : The timestamps in the log files are always in GMT rather than in the time format configured on the machine. 20

21 CSCec24701 CSCec61373 CSCed21297 SPS: Registry Cleanup Interval does not remove expired registration Problem : The Registration database is not periodically purged of expired registrations regardless of the value set in the Registry Cleanup Interval directive. Conditions: Allow a registration to expire or manually change a registered entry's registration time so that it is expired. It will not be removed from the database unless it is called or manually removed. Recommended Action: 1. Calling a registered user who's registration has expired will cause the registration to be aged out and removed from the database. 2. Manually run the sip/bin/sysadmin_sps_regroute tool. Follow the menus and list all of the registry entries. This will cause the expired registrations to be removed from the database. This can also be done on the command line by typing./sysadmin_sps_regroute -l -m registry To have this be performed automatically, set up a cron job on the machine the proxy is running on to run the following command:./sysadmin_sps_regroute -l -m registry 3. Using the provisioning graphical user interface (GUI), display all of the registrations. The expired registrations will have their Expiration time shown in the color red. Click on the column header to sort on the expiration time. Manually delete the expired entries. Note, make sure the time and date on the machine running the GUI matches the time and date of the machine running the proxy as this is used to change the expire time color to red. Need to validate contents of Contact_Age Problem : Entering an invalid value for the Contact_Age field of a static registration results in the Contact being added to the database without any error message; but then when the associated user is called the Contact is treated as if it has expired and the call fails. The correct behavior would be to flag the invalid value when the Contact was being entered. Conditions: This is applicable to static registrations via the graphical user interface (GUI) or CLI only. An example of an invalid contact is misspelling the word Permanent. Recommended Action: Re-enter the Contact with a valid Contact Age value. SPS does not support complete Remote-Party-ID syntax Problem : SPS supports only that portion of the Remote-Party-ID syntax that is required for and parallels that of the P-Asserted-Identity header as used to facilitate Privacy in a network consisting of other Cisco SIP endpoints. Conditions: PrivacyWithRPID is enabled and SPS receives an INVITE from a trusted entity with the following Remote-Party-ID header: Remote-Party-ID: <user@domain>;privacy=name;privacy=full When forwarding to an untrusted entity, SPS should and will remove the header. However, if instead the header is as follows: Remote-Party-ID: <user@domain>;privacy="name,full" When forwarding to an untrusted entity, SPS will not recognize that privacy was requested since it does not support quoted strings as privacy values, so it will not remove the header. Recommended Action: Use the semicolon separated syntax for rpi-privacy tokens rather than the quoted string syntax. 21

22 CSCed27525 CSCed40792 CSCed83101 CSCee24124 CSCee27711 Linux GUI install gives spurious warnings Problem : Upon installation of the SPS graphical user interface (GUI), the user will see several warning messages. Conditions: The messages may be due to the version of InstallAnywhere currently used to create the installer. Recommended Action: Ignore the messages as they are harmless. RAS Gatekeeper Cluster Host/Port pairs need to be made required Problem : The proxy fails to restart correctly after modifying the remote access server (RAS) Gatekeeper Clusters via the graphical user interface (GUI). Conditions: When a GK or port is added without giving a value to the corresponding port or Gk. For example, if a value is added to the GK1 column, a value must be added to the Port1 column for the same row. Recommended Action: Always add both GK and port data when modifying or creating RAS Gatekeeper clusters. Multiple registrations do not all show up in provisioning Problem : At times, registrations by independent UAs to the same number will appear to overwrite each other when using provisioning to view the registrations. When a call is made to the number both sets ring. Also, when using the CLI tool in ACE mode, both registrations appear. Conditions: This may occur if the Contact in the Register message does not contain a User portion of the URL. Recommended Action: Use the sysadmin_sps_regroute CLI tool to view the registrations with the same number. Slow export of registry/routing entries in sysadmin_sps_regroute Problem : The export function of the sysadmin_sps_regroute tool takes a long period of time when compared to doing an export when in ACE mode or through the graphical user interface (GUI). Conditions: Perform an export of the registry or routing databases via the sysadmin_sps_regroute tool. Process completes, but takes longer than if done by other methods. Recommended Action: Use the ACE mode of the sysadmin_sps_regroute tool when performing an export of the routing or registry database. Another option is to export from the GUI. sipd processes die if log file can not be written Problem : sipd processes abort with 'File size limit exceeded' errors. This error indicates that log files can not be written to. Condition: Either the filesystem log file exist on must be full, or at least one log file must have reached the maximum file size allowed by the operating system. Recommended Action: Manually remove the log file and remove any unnecessary file to recover disk space. Then gracefully restart the SPS. 22

23 CSCee29382 CSCee29399 CSCee32712 CSCee35557 CSCee41389 Radius accounting record time format always GMT Problem : There is a RADIUS accounting directive for time format that accepts the values of GMT or Local; however, the accounting record times are always in GMT regardless of how this is configured. Conditions: Accounting enabled, Time Format changed from GMT (default) to Local Recommended Action: None MaxRequestsPerChild is misleading Problem : MaxRequestsPerChild is not the max number of SIP requests a sipd child process an handle. A sipd process handles SIP traffic, IPC traffic, and timeouts. Timeouts happen every 50 ms (regardless of an running timer for that slot) and a per child MaxRequestsPerChild counter is incremented each time. As a result, sipd child processes die much more frequently than might be expected when MaxRequestPerChild is set to some non 0 value. Conditions: MaxRequestPerChild changed from default value of 0. Recommended Action: Try a value of the order of to see sipd child processes die in a more expected pattern. StateMachine debug option ignores LogLevel Problem : The value of LogLevel is not taken into account when StateMachine debugs are enabled. Full StateMachine debugs are written to the error_log file regardless of the LogLevel value if StateMachine debugs are enabled. Condition: StateMachine debugs On, LogLevel set to something other than debug Recommended Action: None. It is recommended that StateMachine debugs are not enabled on a heavily loaded system. Log rotation by file size using rotatelogs does not work Problem : The admin guide (SPS 2.1 and later) and GUI (SPS 2.2 and later) describe using rotatelogs to rotate the access_log and error_log by time or by size. If you configure SPS to rotate based on size, for example: /opt/sip/bin/rotatelogs /opt/sip/logs/error_log 500M it rotates every 500 seconds rather than every 500M. Recommended Action: None GUI allows unsupported dot wildcards in middle of route pattern Problem : Calls can not be resolved to a route that was provisioned using dot wildcards Condition: The route pattern contains an embedded dot wildcard at the beginning or middle of the pattern Recommended Action: Dot wildcards must exist at the end of a route pattern. Replace the embedded dot with a '*' wildcard or re-write the route pattern. 23