Recent content by tylamb19

Also looking for an answer on this, I don't have access to Avaya's KB but would like to know if it's safe to delete, or if there is a new certificate that needs to be installed.

Yep, make sure if they want to use 172.xxx.xxx.xxx that it's within the range of 172.16.0.0/12. Expressed in a generic range and not in CIDR that's 172.16.0.0 – 172.31.255.255

That address space needs to be changed. The problem will be solved when you aren't creating routes to public IPs on a private network.

Was not IPv6 only - definitely had an IPv4 address, just something along the path was not working. The VPN solution should work fine. Since we're still behind the user's cellular modem/router providing NAT, I couldn't do a normal IPSec site to site VPN, which is why I had to find a solution to...

Yep, all H.323 and SIP helpers are disabled in the UniFi firewall. The end user's router is a really dumb cellular modem. They have no normal cable or fiber internet. No options to change, no way to log into it. Even if I could log in, I can't imagine that it has the ability to do NAT...

Just gave that a try and no luck. It still gets a login screen but after logging into the extension, nothing. Another solution I’m thinking of is to put the phone behind a router with an always-on VPN. The UniFi VPN server is L2TP over IPSec. Anyone out there know a router or other device that...

Yes the public IP is populated when I run STUN.

Yep - STUN as of Friday was coming back with "Full Cone NAT" but for whatever reason as of today comes back with "Unknown" but I know for a fact the firewall is open from the destination IP. It might just be the STUN server I'm using, if anyone has any recommendations on one to try I'd be happy...

Nope - same responses still on the phone, just "Discover <External IP>" on the phone (only after logging in) and the repeating message of Recv GRQ in Monitor.

Hey Tim - thanks for the reply! I'm not using VPN to connect this phone. It's just a port forward to the IPO directly which is locked down to only be accessible by the end user's external IP. This solution is documented in Avaya's literature here. The IPO doesn't have any VPN licenses so even...

Hi all, Having trouble with setting up a basic remote extension for a single user, working from home due to an injury for the next few months. IPO is running 9.1. There is no VPN licenses on the system, which is why I'm going down the standard H.323 port forward route. Forwarded TCP 1720, UDP...

That screen is under the “SIP URI” tab in R8.1

Remove the Incoming Number field if you want the system to answer all calls on the SIP trunk.

Tommy, you are a g**d***** genius, I would have never thought about that. Pink for the theorized workaround alone.

It isn't great to run VM Pro on a separate release but it will work fine. I have an R9.1 system in my home that is using VM Pro R11.1 running on the Linux app server. Sometimes it freaks out but 99% of the time it works perfectly fine. If you have server 2019 with HyperV or any other hypervisor...