|
|
Joined: Sep 2006
Posts: 139
Member
|
Member
Joined: Sep 2006
Posts: 139 |
Hi folks, On our Axxess v11, I'm trying to swap extensions for a number of people. The old extension must continue to work to reach the new phone extension. That's the actual goal I want to achieve, so the change is transparent to callers.
To do this I changed the extension on one of the phones, let's say from 1150 to 1250. Then I created a phantom of 1150 - the old extension, remotely programmed call forward to 1250 - the new extension.
Then in the voice processor I created an Extension ID for 1150.
Now you can dial the old extension internally or externally and it rings the user's phone on the new extension. But when the call goes to voice mail you get the generic system voice mail menu, not the user's mailbox greeting. I know why, because the old extension isn't associated with the new extension / mailbox in the voice processor. Don't know how to resolve this!
HALP!
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Sep 2006
Posts: 139
Member
|
Member
Joined: Sep 2006
Posts: 139 |
I found a solution. It seems a little complex. If there is an easier way, I'd appreciate some suggestions.
I unforwarded the phantom. I created a CRT that times out to the user's mailbox. I created a system forward path with the user's new extension as the first forward point and the CRT as the second forward point. For the phantom extension, I put in the forward path setting the internal call flag to yes and DND, Busy, No answer, immediate to no.
Now I call the old extension (phantom) internally or through AA and it rings the new extention for a while then hits the CRT which sends the call to the new voice mail.
Now I have to do this for about a dozen more people. YAY!
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
Delete the current station/endpoint. This leaves the mailbox unassociated. Create a Phantom with the same extension number. You should be alerted of a mailbox with the same number. You then have an option of associating the mailbox with the new phantom extension.
|
|
|
|
Joined: Sep 2006
Posts: 139
Member
|
Member
Joined: Sep 2006
Posts: 139 |
So the phantom will have a mailbox (the original one) and the new extension on the new extension number will have a new mailbox?
So each user will have two mailboxes - one for their old exension which is now a phantom and one for their new extension?
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
This will associate mailbox with the phantom. So any calls to the phantom will go to voicemail. It appears that is your first goal. I guess I don't understand why you are using phantoms if they are staying at the same physical phone.
We use phantoms to hot desk our agents. The endpoints don't have a mailbox or extension ID. If they want to receive calls, they must be logged in. We use Xarios for our hot desking.
|
|
|
|
Joined: Sep 2006
Posts: 139
Member
|
Member
Joined: Sep 2006
Posts: 139 |
The reason is that we are changing a bunch of extensions to match DID numbers. The users want their old extensions to continue to work, ringing on the new extensions. For both internal and external calls. And when forwarded to voice mail go to the same voice mailbox used by their new extension.
I did speak finally to an Inter-Tel remote tech who confirmed that my workaround way is the best way to handle it. Although she suggested I might like to put the phantom and the new extension in a hunt group instead of using forwarding path.
|
|
|
Forums84
Topics94,532
Posts640,045
Members49,853
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
263
guests, and
21
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|