Search results for query: *

If you want to use the Mobile Workplace client, you need Power User

My installation guide from the R12 document pack says to use a generation 1 VM. Page 52

4 years aga there was no 46xxspecials.txt support so you had to create a manual 46xxsettings.txt. "The 46xxspecials.txt file is supported for the Avaya Workplace Client for IP Office R11.1.2.4 and higher." Now you should use the 46xxspecials.txt, this leaves the 46xxsettings.txt...

Instead of demanding someone download and share it for you, why not go back to the vendor and get the file from them or the sold to number?

First up, do you have only 2 appearance buttons set up for the user, and "reserve last CA" ticked in telephony/multi line options/? Also, are the users logged into both the desk phones and Workplace at the same time? If so, they will not get busy when putting a call on hold in Workplace. The...

I'm not aware of any setting that would control this behaviour, not even in the extended advanced settings (shift click) or the "toggle features" within that menu. I would raise an SR with Avaya support and get Xima to look into it for you.

Try this one

Does http://acr_ip_address:9080/web/login work?

It can be downloaded from the Avaya support site, you need the Admin CD zip file that matches the version of IP Office you are running

The number you are assigning to the group conflicts with the analogue extension, use a different number. Don't worry about the duplicate extension warning, that is because you can have the same extension more than once in groups other than "Collective" so it will remove them when you change the...

You have a 2 port analogue extension card, you won't be able to "add" another port as it's a physical limitation. Add another analogue card or swap out the 2 port card for an 8 port card.

From the Windows start button under "IP Office" or from the Admin app under <file/advanced/system status>.

We use Azul OpenJDK - https://www.azul.com/core-post-download/?endpoint=zulu&uuid=3b6fcd2d-79d6-4960-a428-e137aad90ac6 It's supported for IP office, just make sure to enable the "Add to Path" when installing

Speak to your SIP provider, they are sending the "486 Busy Here" response, they will have to let you know why, assuming the number is valid and not busy.

The only upgrade reference I can find is in the R12 IP500V2 Installation PDF on P.177:

To be safe, I would take the IP500V2 to the latest release of R11.1 following any recommendations in the R11 release notes for the version you are starting from. Once on R11.1 then go to R12. There are no cost implications other than an upgrade licence for R12. You will not be running on R11.1...

Anything in a monitor trace or SSA alarms? Also check security settings on the expansions especially around the HTTP, HTTPS and TLS settings.

Have you followed the deployment guide? You need to connect to the 500V2 and initialise it, add the expansion unit, then assign the licences. Chapter 10 on Page 76

Good FTP setup guide here from Chronicall: https://ximacare.ximasoftware.com/hc/en-us/articles/360018466772-How-do-I-configure-the-FTP-built-into-VMPRO-for-Chronicall-Linux-to-Windows Sounds like a key issue.

"The wide RTP range is for the ingress by the provider through the firewall" No, the ports the provider uses is for the EGRESS through the firewall. Inbound (Ingress) ports are the ones the IP Office uses (40675-50754 UDP). Simple mistake but can have significant impact if the provider ports...