Cisco Bug: CSCup02333 - SNR timer issue
Last Modified
Nov 14, 2015
Products (1)
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
10.0(2.99991.7)
Description (partial)
Symptom: SNR timer issue Conditions: While adding SNR timer am seeing few changes from 9.0 CUCM In cucm 9.0 , for SNR timer there was answer too late timer, but now with CUCM 10.0 it has been changed to ?Stop ringing this phone after?, values now need to be entered in seconds and the validation says that the accepted values are 0, 10 to 30 (seconds). If I set the value to 300 000 milliseconds then it populates the value of 300 seconds which is correct but if you try save the value on CUCM the validation rejects it as it only support up to 30seconds. On viewing the help page for this on CUCM 10 the name of this field is still listed as the old name i.e, Answer too late with the old millisecond value i.e, 300000 milli seconds so it seems the help page has not been updated and also From version 9.0 and 10.0 the maximum value has decreased from 300 seconds down to 30 seconds which does not allow to take 300000 milliseconds
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)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases