Definity Hunt Group

[nu2phone]

On the second page of the hunt group for the remote audix. The message center is: rem-audix this then allows you to enter something for AUDIX Extension.
The other possible choices for message center are: audix, fp-mwi, msa, qsig-mwi, and none.
Where do these choices come from? Are they programmable?

 

[ken07734]

What are you attempting to do?

 

[nu2phone]

The way I understand it the AUDIX Extension field re-directs them to the hunt group ext on the host PBX.
I need to do something similar only not for Audix, for Unified Messenger. I have posted exactly what I am trying to do on the message: Definity G3v7 Remote PBX Programming. I really need to come up with a solution ASAP. Thanks.

 

[ken07734]

Do you have the PBX link or mode code integration?

 

[nu2phone]

The intergration between UM and PBX is handled by the Calista PBXLink.

 

[ken07734]

then if you are replacing Audix that is already set up for centralized you shouldn't have a problem everything is already there.


Just replace the Audix hunt groups with the unified stuff

 

[nu2phone]

So I can just duplicate exactly what is there using rem-audix and just the different extension for the UM pilot number? I need to keep the existing audix set up for a while until the rest of the auto attendants are switched over. Thanks!

 

[BuckWeet]

When you're doing other types of voicemail you usually do it via bridged configuration. On the headend its done via a vector witch just a 'route-to' option and then all of the extensions in that vector.

As for the remote side like you're speaking about. I would assume you could make a VDN pointing to a vector that points to the headend. Then put that VDN in your coverage paths..


BuckWeet

 

[nu2phone]

The problem is that the remote switches do not have the capability of adding a VDN or Vector.

 

[ken07734]

If you are using PBX link and you already have a DCS enviroment and you replace the current setup with thenew one, there really should not be any problems, but, without seeing how you are currently setup it's hard to say if it will just work or you need to change some tramnslations.

 

[BuckWeet]

Most likley it won't work. Audix integrates into definity really well, whereas other vendor voicemails or octel doesn't integrate seamlessly.. The fact that you have to use a vector for voicemail instead of a huntgroup is pretty hoaky to me.. Its jsut this way because of how the PBXlink uses the display on the set to see who voicemail to be forwarded too.. Not to mention how you have to put the extension # into the name field with other vendor voicemails.. Just hoaky.. Wish AVAYA would change this..


BuckWeet

 

[BuckWeet]

IRS data that will remain here forever, to combat the liberals' tax-cuts-for-the-rich garbage...

 

[BuckWeet]

FYI:

Just found this out

if you program the set type to be 7434ND you don't have to put the extension #'s in the name field anymore, you must enabled the 7434ND in the "change sys features" on page 5


we've done this a few times, have yet to have problems...


PS forget that last post, accidentally pasted the wrong text, LOL!!!