Cisco Cisco Unified SIP Proxy Version 8.6 Release Notes

and users are responsible for compliance with U.S. and local country laws. By using this product you 
agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local 
laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at: 

.

If you require further assistance, send an email to export@cisco.com.

Voice and router functions may co-reside in the same router with Cisco Unified SIP Proxy with two 
exceptions:

Cisco Unified SIP Proxy may not co-reside in the same router when Cisco Unified Communications 
Manager Express (Cisco Unified CME) or Cisco Unified Survivable Remote Site Telephony (Cisco 
Unified SRST) are configured for SCCP phones.

Cisco Unified SIP Proxy may not co-reside in the same router with time division multiplex (TDM) 
gateways or configuration of H.323 dial peers (including Cisco Unified Border Element).

Cisco Unified CME, Cisco Unified SRST, and Cisco Unified Border Element configured for SIP 
may co-reside in the same router.

These caveats describe unexpected behavior in Cisco Unified SIP Proxy software releases. Severity 1 
caveats are the most serious caveats. Severity 2 caveats are less serious. Severity 3 caveats are moderate 
caveats, and only selected severity 3 caveats are included in the caveats document.

If you have an account on Cisco.com, you can use Bug Toolkit to find caveats of any severity. The Bug 
Toolkit is at: 

CSCsw97690

There are two symptoms of this bug. The first is that pinging of all elements 

(TCP/TLS/UDP) will be delayed. Therefore, their status may not be accurately 
reflected by the show server-group status command. The second is that committing 
a configuration can cause the CLI to hang for several minutes.

Invalid or down TCP elements are listed in server-group status.

Only use UDP or TLS elements in server-group configurations.