Just come across a strange problem since upgrading to 3.2.17
If a user with an analogue (or DS) handset gets a call and wishes to park it, they used to "transfer it" to *60X (where X is 1-9 (but I guess 0 would do too)) and would hear the "beep-beep" confirmation tone, and the call would be parked.
You could go to another phone and dial 60X and the call would be retrieved.
Short codes in use are:
*60X
Park Call
60N
0
60X
Retrieve Call
60N
0
The problem since upgrading to 3.2.17 (from 3.1.65) is that the analouge user presses Recall and gets dial tone, dials *601 and gets the confirmation beep, and hangs up; however instead of the call being Parked, it is only on Hold at that extension; the same is true for the DS users (but obviously using the transfer key (twice)). The call does not occupy a Park slot (confirmed in Call Status), and recalls to that extension under the hold timer (rather than the Park timer) - which given the status under Call Status is what you would (now) expect.
This has worked since we had the IPO (v2.0), without any change, so I'm guessing that it's a bug. Can anyone else confirm this, or suggest an alternative (other than using Phone Manager) for parking calls; we do know that the retrieve short code works correctly still, as the receptionist parks to these slots using Soft Console.
If a user with an analogue (or DS) handset gets a call and wishes to park it, they used to "transfer it" to *60X (where X is 1-9 (but I guess 0 would do too)) and would hear the "beep-beep" confirmation tone, and the call would be parked.
You could go to another phone and dial 60X and the call would be retrieved.
Short codes in use are:
*60X
Park Call
60N
0
60X
Retrieve Call
60N
0
The problem since upgrading to 3.2.17 (from 3.1.65) is that the analouge user presses Recall and gets dial tone, dials *601 and gets the confirmation beep, and hangs up; however instead of the call being Parked, it is only on Hold at that extension; the same is true for the DS users (but obviously using the transfer key (twice)). The call does not occupy a Park slot (confirmed in Call Status), and recalls to that extension under the hold timer (rather than the Park timer) - which given the status under Call Status is what you would (now) expect.
This has worked since we had the IPO (v2.0), without any change, so I'm guessing that it's a bug. Can anyone else confirm this, or suggest an alternative (other than using Phone Manager) for parking calls; we do know that the retrieve short code works correctly still, as the receptionist parks to these slots using Soft Console.