Hi Walt,
I still find it hard to believe that these ports are blocked by public WiFi. I have never experienced
any problems, and I have connected back from 20+ countries, including the U.S. many times.
The problem with port 80 was probably not a block, but a port conflict. Your router most likely is
already using port 80 for configuration. It is therefore always a must to forward the HTTP port.
I also recommend always to change the SIP port, because many routers have a VoIP function built-in
(especially in Europe). You may find a conflict with port 5060 on a router where you are visiting, if
not at home.
I am not sure if I understand what you mean about the library changing your DynDNS address. The user
side does not use DynDNS, only the radio side. This is an automatic process that is transparent to the
user, except for a few minutes wait until it updates if you happen to be using it at the time the address
is changed by the ISP. The user needs to enter the DynDNS address (SIP contact) and correct port (SIP port)
on the user side, and the box will find the radio itself. The IP address where you are located at the time is irrelevant.
You didn't mention if you were using an RRC 1258 box, or the RRC PC Client. If you are using the box, I am wondering
how you are connecting its ethernet port up to the WiFi. There are methods, e.g. routers, bridges and PC internet
sharing, but I am curious how you are doing this if you are indeed using the box.
73,
Mitch DJ0QN / K7DX