Using same VM box for two seperate stations 3

[kythri]

A user here has two desks in different buildings.

He wishes the phone at both desks (seperate extensions) to drop into the same VM box.

First question is, how do I arrange this?

Next question, how would I arrange it to ring at desk 1, then desk 2, and then drop into the VM box (which would automatically happen, if assigned to desk 2, yes?)

Thank you!

 

[phonepd]

You can make desk 1 the extension with voicemail and create a cover path for desk 1 that has the call ring a few times on desk 1 and the ring at desk 2 and if still not answered the call will go to the voice mail of desk 1.
If you want it to ring on both phones at the same time you could still setup desk 1 with the voice mail and put bridged appearances of desk 1 on the desk 2 phone. Make sure you mark bridged call alerting yes on desk 2 so the phone will ring.

 

[AvayaHelp]

Create a coverage path on the station 1 that points to the second station and still have another pointer in the same coverage path point to the VM hunt. On the second station have it's coverage path point to the Vm hunt and another pointer to the 1st station, basically the same set up as the 1st phone in reverse. Make sure the coverage path for both stations has the same VM hunt. Then regardless of which station he logs into the VM will always find it's way to the same mail box. Also depending on the phone type, ensure that the MWI extension reflects the VM number so that which ever phone he is on he will see the light appear when a VM is left.

I hope this is pointing you in the right direction if nothing else.

Avaya, Octel, AUDIX, CMS and other fun stuff.

"There is always a way, it may not be pretty but there is always a way."

P:-D

 

[avayaman]

There is a much better way to do this.

Go into the Audix programming & type "change auto-attendant business schedule 1". If its set as default, assign a name to it & leave it alone. If not try schedule 2 or 3.

Next type "change auto attendant routing table"

Under the incoming called number enter the extension that you want routed to a different voicemail. Enter the bus ness schedule under the next column. In the day, night & alternate service mailbox columns enter the destination mailbox number. Your done, just cover the extra extension to the voicemail hunt group.

As a matter of interest if you have a personal CO line, you can give it an access code the same lenght as your extensions. If you enter that access code in the incoming called number column, you can route a Personal CO into the same mailbox as the extension of the set.

Paul Beddows

Avaya Consulting, Implementation, One on One EAS & Definity Training for PBX Administrators.

Vancouver, Canada
E-mail avaya@vancouver.hm

 

[adminman3]

When we were moving our operation to a new building with new extensions, we programmed each mailbox to have both extensions (old and new) on the subscriber form as illustrated below, using the extension field and Secondary Extension field. We had DCS activated between both switches, but I'm not sure DCS made this happen. What did happen is that calls following coverage to VMail for 6128 and 6555 ended up in this same box. Make sense?

SUBSCRIBER

Name: ADMINMAN Locked? n
Extension: 6128 Password:
COS: custom Miscellaneous:
Switch Number: 1 Covering Extension: 8001
Community ID: 1 Broadcast Mailbox? n
Secondary Ext: 6555
Account Code:

 

[Bobg1]

Why not just bridge the extensions?
He would then have just one number to use and his calls can be had from either location.

 

[mdeeves]

Bingo Bob.

Ext A = 1234
Ext B = 4321

NO call apperances on ext B but rather bridges of ext A

Cov Path for Ext A = v-mail hunt group
Cov Path for Ext B = BLANK

Message lamp for ext A = 1234
Message lamp for Ext B = 1234

Bridge call alerting on Ext B =Y
per button ring control for Ext B = Y

Each bridge apperance should be set to r on Ext B


I have done this too many times for "needy" execs.

Hope this helps,

Mike

 

[highfive]

Mike,

Anyone who has converted from G2 to G3 will tell you not to do this, we have outlawed this process on our campus due to E911 issues that come up if you don't assign any of the buttons to have the actual extension of the station.

I know, easier said the done with whiny execs, just tell them they have to get a set with more buttons if there isn't any room for the real extension and the bridged appearances. I would recommend the steps that avayaman lists unless you have an Octel which you can fool.

 

[AvayaHelp]

Thats why I suggested my way as I have an Octel.
highfive - how can you fool the Octel 250?

Avaya, Octel, AUDIX, CMS and other fun stuff.

"There is always a way, it may not be pretty but there is always a way."

P:-D

 

[OldPhoneGuy]

If you have vectoring enabled do the following to have two or more extensions point to the same voicemail box:

1. The extension should have a coverage path that points to a VDN.
2. The vector for the VDN just needs one step:

01 messaging split xx for extension yyyy

Where Split xx = your Audix split, and extension yyyy = voicemail extension where you want to leave the message.