Cisco Cisco Unified SIP Proxy Version 8.6 Release Notes

Page of 8
 
5
Release Notes for Cisco Unified SIP Proxy Release 1.1.3
 OL-19828-01
  Caveats
CSCsx10996
Symptom
Cisco Unified SIP Proxy DNS SRV based call routing does not work after 
rebooting Cisco Unified SIP Proxy.
Workaround
There are two workarounds. The first is to toggle off, then on the sip 
dns-srv command. The second is to configure route tables with server-group based 
routing.
CSCsx18654
Symptom
When multiple IPs are configured on Cisco Unified SIP Proxy, SIP messages 
source from wrong source ip.
Conditions
Cisco Unified SIP Proxy is configured with multiple IP interfaces.
CSCsx38761
Symptom
When trying to make a call to the SRV defined device, Cisco Unified SIP 
Proxy cannot establish a connection and issues a 502 message to the calling device.
Conditions
This problem only occurs if the network is of type NAT.
Workaround
Use a different network type, standard, for example.
CSCsx48124
Symptom
The maddr parameter in the request-uri is not handled properly.
Conditions
Cisco Unified SIP Proxy fails to remove the maddr parameter if it is 
pointing to Cisco Unified SIP Proxy on incoming requests. Cisco Unified SIP Proxy 
fails to forward the message based on the maddr address on outgoing requests.
CSCsx62364
Symptom
Invites from the Avaya PBX are rejected with a 404 “no matching algorithm 
found” message.
Conditions
An Avaya PBX is used.
Workaround
Use a different model PBX.
CSCsx65522
Symptom
Normalization on user portion of request-uri fails, NullPointerException is 
thrown during normalization operation. (This can be seen by looking at the trace.log 
file.)
Conditions
The user portion of the request-uri is empty.
Workaround
Normalize the entire request-uri to add/update the user portion.
CDETS
Description