@Moderator
I have observed a repeatable behaviour fault on the announcements for the widely used Return last call (1471) service. It is proven to occur on more than on line and has been observed independently on multiple calls. I will detail one instance to explain the problem. I would like this problem to be shared with the implementation team so that they can correct the behaviour.
I received a call on the 13th November at 0900 and on the 18th the Return Last Call (1471) announcement was correct shortly afterwards. The form it should take is as follows
Telephone number (TN)
called you (DT) at (TM).
To return the call press ’3’. There is normally a charge for this service.
where
(TN) is the full national telephone number released on behalf of the caller
(DT) is one of (1) today (2) yesterday (3) "on the nn st/th month name" e.g. "on the thirteenth November"
(TM) the time in the 24 hour e.g. "Oh nine hundred hours"
When I tested 1471 17 Nov at 22:31 The system returned:
(TM)
To return the call press ’3’. There is normally a charge for this service.
called you on the (DT) at telephone number (TN)
Then when I checked again on 18 Nov at 1124 the announcement was in the correct order once more.
Thus it appears to announce correctly on day 0,1 and 5 following the call and incorrectly on days 2, 3 and 4. Subsequent days are as yet unknown.
With the help of @Tim123 I have confirmed that this behaviour is not confined to my own service.
This appears to be an implementation error in the code of the IMS that runs part of the Digital voice service. In a former time one could call 150 and report such a fault but with the present customer facing service I fear it would not find its way past the computer trouble reporting system.
In the past such a report would have found its way on to an Exchange Incident Reporting form and be forwarded for the designers to investigate and fix. Would one of the Moderators please undertake to find out how to gat this report to the design team and hopefully get it fixed.