New VM Pro Feature in 9.1: MWI for other users 4

[94astro]

Found this on the knowledgebase, didn't hear about this earlier, might be useful to people. I've been wanting this feature.

On VM Pro (probably Embedded also), you can enable MWI for other users now, not just hunt groups. Under a user's source tab enter U followed by the user name or extension. Once done, your MWI will light up when the other user has a message, and your visual voice menu will let you check the other user's messages by selecting their name.

 

[Westi]

Something we all wanted for a long time. I guess Avaya got sick of us to complain about this to them.

Joe W.

FHandw, ACSS (SME), ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[tlpeter]

Another nice new option is the huntgroup fallback destination which now also can be a user or shortcode.

BAZINGA!

I'm not insane, my mother had me tested!

 

[IPGuru]

Thanks guys
those are both going to be quite useful (especially the HG fall-back - no more phantom users for off switch divert )

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[IPGuru]

Now if they could just add "Busy Last Ca" to user rights (& preferably enable it by default) I may finally get rid of this RSI

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[tlpeter]

IPGuru, create a user with this option enabled and save it as a template.
Then create your users with this template.
Saves a lot of RSI

BAZINGA!

I'm not insane, my mother had me tested!

 

[IPGuru]

That is great if you are installing (although it would still have been better if Avaya had done the job properly with user rights & sensible defaults, how difficult could it be?)

it is not so great if the system was installed by another engineer who "forgot" & you now have to remotely correct 100+ users.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Gunnaro]

There are plenty of new features in Voicemail Pro R9.1
(Still a misleading name, Voicemill Pro would be much more fitting...Can I have that, Avaya? No?
Alright then, moving on

Security User Access Control
Access to the voicemail server configuration can now be assigned to IP Office service users.

Database and VBScript features are now included in Preferred Edition license.
Existing Advanced Edition license still enables 8 generic TTS port for use with Speak Text actions and VRL support.
(So don't delete the "obsolete" Advanced Lic)

Support for A-Law/U-Law Recordings
The voicemail server now supports and stores recording from the telephone system using the companding format.

Outcalling Control
The option to enable or disable Intuity mailbox outcalling system-wide is now available to all systems.

Mailbox Password Control
Control of the minimum mailbox password length and complexity requirements

Message Waiting Indication for Other User Mailboxes (Covered by OP already)

Visual Voice Button for Other Mailboxes
Dedicated Visual Voice buttons for another user or hunt group mailbox can be programmed.
(I know someone wanted this badly)

Not so well documented are the New System Variables
I've compared the old VMPro help files with the new, and it looks like we got almost twice as much to play with now.

$ACCOUNT_CODE		The account code associated with the call.
$ANS_PARTY		Number of party who answered the call.
$ANS_PARTY_NAME		Name of the party who answered the call.
$CALL_DATE		The call date (UTC).
$CALL_TIME		The call time (UTC).
$CALLED			The called number.
$CALLED_NAME		The name, if available, of the called party.
$CALLED_TZOFFSET	The called parties time zone offset.
$CALLERS_TZOFFESET	The callers time zone offset.
$CLI_NAME		The name, if available, of the caller.
$DATE			The date associated with the call. 
$DAY			The current day.
$DISPLAY		The phone display text.
$FALLBACK_NUM		The fallback number associated with the call.
$HOUR			The current hour.
$ISDST			Indicates whether the system is currently using daylight saving or not.
$REC_ORIGINATOR		The recording originator.
$REG[name]		Returns the current value of the named user variable. Allows user variables to be used as call variables.
$SEC			The current seconds.
$TAG			The tag text currently associated with the call.
$TARGET_NAME		The name of the target.
$TARGET_TZOFFSET	The targets time zone offset.
$TIME			The current system time.
$USER_DATA	
$WEEKDAY		The day of the week.
$YEAR			The current year.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[derfloh]

Nice... I can't wait for Linux based VMPro systems being able to connect to databases too.

 

[pkdev]

Nice... I can't wait for Linux based VMPro systems being able to connect to databases too.

I've asked Avaya about this and the response is : "it may never happens, workaround is to use Avaya Contact Center Select (ACCS) to connect database is IPO Server environment".

 

[Gunnaro]

What a silly thing to say! (Not you personally pkdev )
To connect a simple DB, spend $$$$$ on extra server(s), licenses and configuration for Server Edition + IPOCC...?

What about: Get Win2K8 Foundation license for $230, reinstall existing server, done.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[IPGuru]

What about Avaya simply install & support for one of the many open-source Database engines that already run on Linux or install the necessary software to enable connection to a Microsoft DB engine.

It is not rocket surgery!


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Gunnaro]

You would think they could, but..no.

How hard could it be, seriously, two-three hours job?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[derfloh]

I heard about it is planned for R10 but as always... Not sure so far.

I agree it should not be a big deal to connect to different database engines from Linux systems. But perhaps it is a bigger deal to connect VMPro to the DB connectors.

It is for sure possible to use a Windows Server to host VMPro. But... In Server Edition you must use the Linux based VMPro. And - I'm not sure about the details - with the new features like WebCollaboration, Conferencing and to use the new CA you have to have a Linux based Application server.

I don't wand to defend the ways Avaya goes because they are sometimes strange enough but I also see some hard words about bad implemented and not working new features here. Don't we want Avaya to finish implementation of new features before they are released?

 

[derfloh]

And what I forgot... I was told a few weeks ago that IPOSS only covers "pure" Avaya systems. So Application Server is covered as long as we don't install packages that are not delivered by Avaya. Avaya applications installed on Windows servers are not covered. So in the IPOSS conditions there will be CCR excluded.

 

[Gunnaro]

That would be VMPro on Windows too, I guess.
Lets see what R10 gives, I'm not in a hurry to go all Linux

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[IPGuru]

Gunnie
[ I'm not in a hurry to go all Linux]

Why not?
instillation is easier
it means you have a fully tested & configured solution with no 3rd party dependencies that need to be reinstalled (Microsoft).
No danger of 3rd party updates breaking operation (Microsoft again)
No Demarcation disputes between you & the IT dept. (Ok it is YOUR problem but that is usually far easier to resolve than convincing the IT guy it is his).
With the current Avaya offerings NO specialist Linux knowledge is normally required (perhaps you forget how much windows specific knowledge you need because you are now familiar with it).

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Gunnaro]

Installation is easier
- Agree, it's more "fire & forget". Still it would be more work to run around transforming existing equipment.

It means you have a fully tested & configured solution with no 3rd party dependencies that need to be reinstalled (Microsoft).
- Lately things that goes GA is far from "fully tested".

No danger of 3rd party updates breaking operation (Microsoft again)
- Knock on wood, I've not had any issues since I kicked out CCR (ironically on of the biggest reasons for running Windows in the first place)

No Demarcation dispute between you & the IT dept. (Ok it is YOUR problem but that is usually far easier to resolve than convincing the IT guy it is his).
- We are a peace loving nation, no feuds or disputes . Most of my installs are on physically separated networks.
In cases where I have to mingle with the IT guy, it's been a all good (except for the firewall guys ).
That's why I in most cases put in my own stuff.

With the current Avaya offerings NO specialist Linux knowledge is normally required (perhaps you forget how much windows specific knowledge you need because you are now familiar with it).
- I do run Linux in 50% of my lab, mainly to prevent being caught with my pants down. Linux was just a wet dream when I got my Windows knowledge.

Apart from the above, I'm not moving anything over until the VMPro is equal or better on Linux (that in particular means DB functionality)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[IPGuru]

OK I wouldn't change an existing set-up without good reason either

GA from Avaya far from fully tested - true but that is equally valid for the windoze version as well at least with Apps server Avaya have nowhere to run.


generally I prefer to go Apps server for new installs whenever possible but we will also install windows versions if that is better suited to the customers environment (recently had one where the Apps server would not run in the customers hosted environment so we went windows instead)

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[soflaphoneguy]

I also would like database support in the Linux version. They are already installing the unixodbc package in the server install, so someone must know how to use it.