Cisco Bug: CSCtd60595 - UCxn should not send 486 Busy Here when no ports available
Jan 08, 2010
- Cisco Unity Connection
Known Affected Releases
Symptom: Unity Connection publisher and subscriber failover pair integrated via SIP trunks to CIsco Unified Communication Manager (CUCM) 7.1.3. When all ports are busy on the subscriber (assuming Top Down call routing in CUCM where the subscriber is first in the Route Group and the publisher second), the next caller gets a busy tone. No call is ever presented to the publisher server by CUCM. Conditions: Unity Connection cluster integrated via CUCM 7.1.3 or later via SIP trunks. In CUCM, CSCsz93063 (RouteListExhausted Alert is raised ignoring Stop Routing Service Params) was integrated in 7.1(3), so that now CUCM no longer will continue routing the call when a 486 Busy is sent by Unity Connection.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases