MWI on Audix

If you're just looking for the abbreviated-dial code to get into Audix, program this as a dial-string:
[Audix ext]~p[subscr ext][password]
So this should something like this:
5999~p20011234

Hope this helps

And for the MWI's: maybe you already knew, but the subscriber names should be EXACTLY the same as the station-names. Case sensitive, spaces, comma's and all.

Good luck and plz let me know. Kind Regards,
Maarten Copini


-Please let fellow members know if their post was of any help-

Shait,
forgot the pounds. Disregards previous Reply.
Programm your abbreviated list position like this:
[Audix ext]~p[subscriber ext]#[password]#
For instance:
5999~p2001#1234#

Let me know. Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let fellow members know if their post was of any help-

Hi Maarten,

Thanks for your kind reply.

We had actually tried this method and you're absolutley correct that this does indeed work, however, it only works in this fashion if we have the mail box on the opposite Audix/switch. What we've therefore found is that when the script is used for the ACD station that is using the local Audix on the ACD switch, the script doesn't actually work whreby Audix simply sits there ignoring the script saying "this call is being answered by Audix...for help at any time press star 4....please enter extension and hash" -then Audix waits indefinitely.

Sorry to be the bearer of bad news however your help is greatly appreciated.

Many thanks and kind regards

Tony

Sounds like a problem with a setting in the Audix-hunt group. Check the message center settings on page 2. This should be msa on the local Audix. If this is the case and it doesn't work anyway, try the other options and test it. Usually this setting causes problems mixing up the login-message and the call-answer message.
Sorry for the vague description, but in most cases experimenting with this setting solves the problem.
Plz let me know what happened. Be sure to test BOTH the call-answering ànd the login-procedure, or Audix may not be reached by your customers anymore. Good luck. Kind Regards,
Maarten Copini


-Please let fellow members know if their post was of any help-

Thanks for that Maarten.

We just tried various settings but didn't get a different result.
One thing I did find though is that the ACD's hunt group page 2 was set as follows:

display hunt-group 1 Page 2 of 41 SPE A
HUNT GROUP

Message Center: none

LWC Reception: none
AUDIX Name: acd
Messaging Server Name: acd1

First Announcement Extension: Delay (sec):

Whereby the pbx is set per:

change hunt-group 1 Page 2 of 41 SPE B
HUNT GROUP

Message Center: none

LWC Reception: none
AUDIX Name:
Messaging Server Name:

First Announcement Extension: Delay (sec):

Your thoughts on this would be really appreciated.

Kind regards

Tony

I'm sorry to say that I'm kind of at a loss here...
Some questions that might help you and me think:

Are your Audix subscribers administered in Community-ID's?

How are the two Definity's and Auxix-systems connected?

Check the field MWI Served User Type for mwi-fp or mwi-qsig in the station forms. (Ìf your Definity's are connected via Qsig or ISDN to the Audix systems).

Is LWC-reception set for msa-spe in the Audix-station forms on both your Definity's?

Hmmm...these were about all the things I could think of that often cause problems like yours...
Kind Regards,
Maarten Copini


-Please let fellow members know if their post was of any help-