Search results for query: *

Because the unlicensed RF Spectrum that WiFi uses can be interrupted by anything. I have a location where the wireless (not WiFi!) handicapped-door open-button will cause the WiFi credit card machine closest to it to temporarily go offline for a few seconds. A door button.... Web browsing...

I only do this for home users, or those who want to use their own personal Bluetooth headset. I would never do a multi-endpoint rollout of WiFi phones.

My guess is that your VPN client credentials (username) don't permit access to the vLAN the IPO is on. Have whoever manages that Palo Alto fix that and I'm sure you'll be fine.

I can say that with 12.0.56 Time Profiles added are completely ignored. (observed on 3 different systems). 12.0.55 didn't do license checks, which is why it's gone from download availability completely.

If you mean on the IPO Linux server itself, just don't. Whether a virtual machine or bare-metal, just don't. Once you do, it all becomes unsupported by both your Avaya BP and Avaya Support themselves. Any update(s) can replace system files, and if an XDR product changes ANYTHING about those...

Where do your phones get their addressing from? The IPO, or an external DHCP server?

Page 9 it literally says "• Avaya only supports IP Office virtual machines created using the virtualized server images supplied by Avaya." I see it does show updating via ISO, but It's been my experience that v12.0 is actually v11.notreallyworking.1.goodluck I had to create a backup and deploy...

You don't use ISOs for virtual machines....

First off- when did this begin? How long did they work beforehand? Second- in SSA, Go to: System->VoIP Security->Blacklisted Addresses and see if the public IP of that location is listed, also check Blacklisted Extensions right above that. If a user or phone hammers the call server with...

Beyond not trusting hardware that old for something business-critical, I'd keep the following in mind: -It would be unsupported by Avaya in all ways. -can't install as a virtual machine on vmware, as the required version of vmware would be too new to have hardware support for that server -you...

I've found the newest version of Workplace will only work if TLS is setup with a proper 3rd party certificate. It will *mostly* work if TLS is completely disabled (including the appropriate lines of 46xxsettings.txt edited)

Discover x.x.x.x is always a routing/firewall issue. What device is routing between the vLANs? Are there any NAT/firewall/security rules between these vLANs? What's your "IP Route" look like in the IP Office?

You have zero administered channels. Give both sides some channels to work with and reconnect that line/path.

You've definitely got some network misconfigurations here. So your Voice vLAN your phones live on is 10.0.15.x (I assume it's a /24 subnet), of which LAN1 of the IPO lives on. If yes, the main IP Route should look like this: IP Address= 0.0.0.0 Mask= 255.255.255.0 Gateway= 10.0.15.1 (again...

@derfloh has the correct way Also, it only works in slot 4

I don't use Meraki, but for what I do use (using one DHCP server for everything), I have to have one DHCP Option 242: L2Q=1,L2QVLAN=10,VLANTEST=0 (this tells the phones to reboot and jump on vLAN10) ...and then another DHCP Option 242 specifically for vLAN10...

Do you have an IP Route setup for LAN2?

I'm kind of stuck on an issue and request the assistance of the group here. I have a few IPO systems in an SCN, all 500v2 chassis, v12.0. All phones are IP, mostly J179s with some 9600s still hanging about. I am attempting to move users from the remote systems to the "main" system at HQ...

what happens when you change the Primary's WebLM server's IP address to "127.0.0.1" instead of 172.17.0.x ?

Not supported means they won't support it. It *may* work. But if it doesn't, then it's all up to you to figure out why. If this is for any regulated industry, they you need to update those ESXi servers anyway.