ā08-06-2012 07:33 AM - edited ā03-16-2019 12:33 PM
I have discoverd a problem with the night-service date command on CME.
I have 3 CME's configured with the following commands;
telephony-service
night-service date Aug 6 09:01 09:00
!
ephone-dn 31
no call-waiting beep generate
number 121 no-reg primary
label Line 1
description BT line 1
call-forward busy 122
call-forward night-service 9xxxxxxxxxxx
call-forward noan 113 timeout 20
night-service bell
!
!
This should have enabled night-service this morning on the CME, so all calls to the main number would be forwarded to the number we have configured on the ephone-dn. This did not happen, when calls were made to the main number the call just rang out and eventualy were forwarded to ext 113 which is an external answer machine.
If I added the following command then the call was forwarded;
night-service day mon 10:00 09:00
this enabled night-service at 10am this morning and calls to the main number were forwarded to the number configured in the ephone-dn as expected.
The timezone and clock were configured correctly so I do not see this as being an issue.
We had this happen on 3 different CME's two of which were running IOS 12.4(15)T8 and one running 15.0(1)M3
Does anyone have any idea as to why the night-service did not enable with the night-service date command?
Solved! Go to Solution.
ā08-06-2012 08:42 AM
Hi.
You may be hiiting this bug
Your 12.4.15T8 is included in the affected IOS list.
Cisco claim that it is fixed in
12.4.20T3
Regards,
Alex.
Please rate useful posts.
ā08-06-2012 08:42 AM
Hi.
You may be hiiting this bug
Your 12.4.15T8 is included in the affected IOS list.
Cisco claim that it is fixed in
12.4.20T3
Regards,
Alex.
Please rate useful posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide