IPO Wish List 1

[ronromano]

I'm starting a feature/functionality wish list for future relaeses of the IP Office. Even though I think The IPO is great, flexible and stable (yes I said stable), I think there are important features and functionality missing from the system.

Since I'm pretty sure Avaya takes a frequent look at this forum, I'm start with a few I think are important.

Now I don't want this thread to get dropped so watch what you post about future releases, don't want anyone to violate an NDA.

Now these are in no particular order just one that come to mind.

1) A real VM transfer key, having to hit the transfer then # plus ext isn't ideal

2) A User Key that has BLF, coverage and voice announce intercom all at the same time (like the Panasonic DBS)

3) On transfer when using dial intercom, when hanging up to complete transfer, the reciving extension receives ring instead of the call be connected to the speakerphone.

4)When on a call appearence, when a second call comes in the phone continues to ring until forwarding destination.

5)State the name of the party before transfer in Auto Attendant.

6)Get rid of the drop option when using park.

7)FIFO LIFO option in playback of messages.

Like I said I think the IPO is great, amazing really. But I want it to be unbeatable.

 

[tlpeter]

1 just a normal on/off switch
2 when you use the directory in phonemanager and you use a 9 or 0 to dail out you have a problem with incomming calls
the phone doesn't display the callers name anyomore
there should be an option in phone manager to dail a 9 or a 0 for external call
then you can put the normal number (without the 9 or 0) in the directory
then the callers name is diplayed on the phones again

 

[mforrence]

My wish list items deal with intercom calls and transfers.

1. When a phone is set to auto answer on intercom, the announce should be more distinct than just a single standard ring. Two reasons: A) the caller doesn't know if the recipient's phone is set to auto answer, so they don't know to say 'hello' after one ring and B) the recipient doesn't know (without looking at their phone) if the call is an intercom call and they should begin speaking after first ring, or if it's an outside call that will continue to ring. A unique tone like the DialDirect tone would be great.

2. When performing a supervised call transfer, the person doing the transfer should be able to begin transfer, get unique voice announce tone (see #1 above), speak, then release call and have call ring on recpient's phone. (similar to ronramono's #3 above).

3. We'd also like IP Office to grow just a bit bigger..

Unfortunately for us, these have been show-stoppers for a couple of larger customers. These customers' view is that they shouldn't have to change to conform to the phone system, rather the phone system should conform to them.

Mike

 

[intrigrant]

Just some things i can think of right now...

1. When a user has a divert all set the diverted call comes back after the ring time-out. There should be a option to stop the time-out and leave the call ringing at the divert number, if the divert number is a group then the call should follow the settings of the group.
2. More advanced call routing.
3. More BLF information in PM and SC (logged-off users)
4. LDAP connection from PM Pro and SoftConsole
5. Button for number surpression before making a call
6. CallPickupGroupmembers does not work on a user who has logged out of the group.
7. a easy way to divert a group to external numbers
8. add users as overflow targets in the group
9. A action in VM Pro to test if a group is free and/or if there are any members logged into the group
10 a action in VM Pro to determine the choosen DID/DDI number
11 a systemvariable of the waiting time of the caller in a queue

 

[Rdy2Taxi]

I want the IMS integration with MS Exchange to mature into an efficient and reliable service. I want IMS to synchronize voicemails with the user mailbox without depending on a client-side application (kinda like my Blackberry Enterprise Server). This would solve the voicemail integration problem for OWA and Terminal Services environments.

I want .MSI installer files for PhoneManager and SoftConsole so I don't have to touch every single box in the organization. I want to be able to successfully upgrade over PhoneManager without having to uninstall it first.

I want all the installers to set all their own damn registry, security and DCOM settings like every other Windows application, thank you.

We use a dial-out digit (dial 9 for outside line). I want PhoneManager and Voicemail Pro to understand that fact, since having a dial-out digit breaks the call-pop feature in PhoneManager and defeats Caller ID and contact matching in Outlook.

When I call-in to check messages, I want VMPro to always present the newest message first, whether read or not, whether voice or email. This would be a huge improvement for folks (like my boss) who get 30 voicemails a day.

I want my IP Office system to know that I have Active Directory and that it should use AD to authenticate remote access dial-in.

 

[sizbut]

How about some field for setting the CLI to use with calls rather than having to experiment with shortcode, eg. User CLI, Line CLI, System Default CLI.

 

[telepaul]

These are some of my wishes.

-Mobile twinning with the possibility to transfer the call to a extension or external number. (Like the MultiVantage and Definity)

-Making a combination of internal and mobile twinning. If mobile twinning is enabled no internal number is possible to set. Combination of fix extension and dect or mobile is not possible for the moment)

-Pickup a call from a other extension with PhoneManager (right click on user icon and pickup call )

-Keep a list of mist calls in the PhoneManager even when the PhoneManager is not logged on

-More flexible in a Citrix environment. Remote sers are not able to use a PhoneManager.

-Same for RDP - remote desktop / terminal server

-Fiscal separated switch on 406V2 WAN/LAN (like SMO and IP412)

 

[dphoneguy24]

I agree that many of the above listed features would be a great additive. Here are some others that I can think of:

Bring back coverage to an analog extension - it was much easier in 2.1 when you could cover say a digital set to an analog port so you could ring a loud bell or some other alerting device

Definitely a "Direct VM" button feature is a must - especially when we are upgrading many of our customers from Avaya Partner or Merlin Legend/Magix - they hate that they have to hit TXFR-#-then dial the extension number-then TXFR to complete or hang-up immediately.

Some basic call vectoring capabilities would be nice-we have run into this with a boss-secretary scenario where the boss wants calls first handled by his secretary, then to a second person, then maybe a third, then finally vm. With the current coverage button, the problem we have is the secretary can't handle more than one call at a time for the boss.

When accessing the directory in VM Pro, if you input a name not found, it at least asks you to enter again, but it never says something like "or press just the # key to for assistance" so that the caller knows they can get out of the name directory and goto the destination you have setup in the False Action.

Be able to select in VM Pro that you want the names directory to be used system wide for either first or last-
If you are using first names in the AA and a caller gets to a users vm box and does an *8,*2 - they will be asked for the last name.

Dphoneguy24

 

[jasonmorrison]

One HUGE ONE ...
Bring back the COVERAGE TAB or create cover paths.
It's a pain in the neck to have to create overflowing hunt groups all the time a person wants multiple cover points!
The cover button just doesn't cut it. Example: one person covers 5 people (which is very common) and needs the extensions to ring and see if they are on the phone, that one person needs 10 buttons just to cover these people or all of those people need their extension with 2 hunt groups created. This has to be addressed!

 

[big70]

I would like things like staffed agents routing or available agents routing.

And a Nightservice button to change multiple incoming call route,s as you can do with a time profile.

Greets Peter

 

[ronromano]

I would also like to see dial by name directory for multiple companies I always hear different systems tout themselves as multi-tenant capable but never have this feature. I also can't stand the delay time on analog trunks here in the US. You have to play with it too much to get it close to what customers are used to.

I also want to to be able to change extensions without a reboot. It was like that for a while in 2.1 and 3.0 I think then it went away. This is big when you need to move people during business hours.

Also, a more streamlined VMPro capacity for holidays. The conditions editor is helpful but too much has to go into it for holidays.

Updates to VMPro need to be instant.

 

[kflounders]

1. Cascading Outcalling, I mean come on guys

2. Call forwarding that isn't call forwarding unless you don't get it fast enough.

3. Ability to have callers dial a 3 off of the AA as well as a 3xx extension.

4. Visual notification of # of VM messages, seriously you're Avaya, figure it out

5. Calling Party Status, such as the display telling you the person you are calling is on the phone or DND like on MICS

6. NATable IP Phones, set it and forget it

 

[mforrence]

kflounders - your #3 can be done today. Set 3 to go to another menu with ??. Transfer ?? to $KEY3??. Have no response timeout go to real digit 3 destination.
Mike

 

[telecomtekperson]

How about a better solution for powering the modules. Something rack mountable would be nice.

 

[ipo412]

I would like to second a few items here:

1. IMS integration with MS Exchange to mature into an efficient and reliable service. I want IMS to synchronize voicemails with the user mailbox without depending on a client-side application.

2. Calling Party Status, such as the display telling you the person you are calling is on the phone or DND. I can't believe you can't do this!

3. I would also like to see dial by name directory for multiple companies.

4. We use a dial-out digit (dial 9 for outside line). I want PhoneManager and Voicemail Pro to understand that fact, since having a dial-out digit breaks the call-pop feature in PhoneManager and defeats Caller ID and contact matching in Outlook.

 

[legendinmylunchtime]

I want to win lotto

 

[kavsagol]

Working in a company that installed around 100 IPO I have two wishes for IPO that should be addressed before any feature added:

1. No reboots unless somthing is terribly wrong.
2. No offline configuration. Why should I send all the configuration when I want to change one thing? Every PBX we installed had to be resetted at least once because of a bad send of the configuration. Make it online like any other PBX (through http or telnet).

Other than that those would also be nice:
- Internal power supply - you can not seriously rack mount devices with external power supplies. Where do you put them?
- Ability to add expansion units on the fly (not rebooting again) and hot swapping them.
- Don't let a DS port (or an entire DS unit) get stuck when I plug in somthing that is not a DS phone. At least give me a way to reset it without restting the entire system and an indicator that it is stuck.
- Make VM Pro handle its errors without crashing. Make IMS work. It's not our fault MS decided to secure DCOM. Use a different method - there are other server/client solutions available.
- Add AA capabilities to VM Lite. What Embedded VM has should be enough.
- Create a CTI interface that does not rely on TAPI.
- Let the PBX run scripts, this can save so much work with external programming.
- TAPI driver should indicate if the connection to the PBX is successful or not.
- We're still using 3.1, so this might have been already done: Allow Manager to change a specific attribute for a group of objects without having to change each one.
- Make phones with lots od buttons, or just bring back the 64xx series. Some people can't live without them and don't want to hear about a computer program. At least make something decnet instead of the EU24 and allow it to connect to 5410 and not only 5420. Also give us some decent ring sounds.
- Why do the phones forget their logs when the PBX resetts? Why can't I redial to a number if I called it for transferring or conferencing a call?

And the next features will never be implemented because Avaya does not want to make IPO an enterprise product:
- Add survivability. We don't need 99.999% online time, just give us a fallback PBX.
- Increase memory capacity on the 406.
- One VM Pro server should serve PBXs that are not tied in an SCN.

 

[Escorthosis]

Add a 3 digit number to the directory entries so that these numbers can be used as speeddials for extensions without a display. Storing them in the directory and as a shortcode makes maintenance more difficult.

 

[a0926]

1. Consolidated with kind of OnRelay(UK) function into IPO
2. a real FMC solution
3. over 550 extensions in one system
4. more VCM channel
5. allowed web conferencing participants upload file in any time
6. offer DISA function
7. SIP client and CSTA feature
8. MS-communicator
9. SOE-3, SOE-16 why not SOE-24/30
10. lower price in softphone

 

[1043]

voice interrupt on busy,
queing to users,
2nd call ringing on a busy phone.

Also I heard
cascading outcalling on R4
IP 500 module