atcomsystems.ca/forum Forums Active Threads Since Yesterday

I'm unfortunately in the middle of pulling out a nearly new Avaya Aura system to be replaced by Teams.

Digit dialing another phone is supported, but it's murky. By default the only way to call another phone is by dialing its entire 10 digit DID, or via a BLF button. Traditional 3 or 4 digit extensions are possible, but messy. The "easy" way is to assign an extension via an ActiveDirectory attribute. This will at least allow auto attendants to dial by extension, but it does not cover internal calls. For that you'd need to design a custom dial plan that will tack on the remaining 6-7 digits.

At least this is my understanding. We're very early in the process and this is what I recall from a very long 7 hour workshop that began at 3 AM my time (workshop was given by Microsoft in France).

I hesitate to call this a phone system. It's an instant messaging and conferencing platform that happens to have some physical devices attached to it. It seems like the focus for internal calls is really placed on the Teams app on a computer or cell phone, and calls to and from the PSTN. Traditional internal calling by number is more or a less a "nice to have" feature on this system.

I get the appeal for us since we have a significant amount of people working remotely, but I am worried about our plants that rely heavily on physical telephones and are heavy on internal calling. I'm also concerned about feature parody for our call centers. Going from Avaya CMS to some hobbled together PowerBI reports is going to be tough.

Rolm was one of the best until IBM got a hold of them!

There is a Network Emanager for windows 10 and IE did work in win10. I had it on a laptop and it worked fine. But the Network Emanager had to be installed correctly and the default browser had to be IE.