Remote Rig

RRC 1258 Support in English => General discussion forum => Topic started by: VO1HP on 2015-12-24, 12:18:56

Title: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-24, 12:18:56
We are in Ottawa for Xmas and have  K3 mini with me.   Using a strong wifi signal in the house and am connected to the network.  I have a web cam at my remote site in VO1 land and I can see that the K3 turns on but after a few seconds turns off again and I get the audible alarm here at control end.   Also have flashing yellow light on the AUX/MIC jack....the  connection does not complete.

Have not tried hard wired Ethernet connection here as there is no jack in the furnace room!!

What do I look for on the router here assuming I can get into the menu....can anyone help ....just here for a few days.

Frank VO1HP
Title: Re: VO1HP.....in new location....cannot connect
Post by: sm2o on 2015-12-24, 12:58:48
 Check that SIP ALG is Disabled, If you use port 5060 for SIP it can be reserved for IP telephony at this location

/mike
Title: Re: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-24, 15:04:43
Mike

Tnx for fast reply.....cannot find SIP ALG anywhere in the modem .....looked at both Control and Remote RR boxes as well....I did port forwarding here at the new modem for the ports range 13000 - 13002 directed to RR Control IP but no change. 

Unclear about I know this is not supposed to be required at CONTROL end of the link but did it anyway....where is SIP ALG parameter located....could it be known by another name.

Frank VO1HP
Title: Re: VO1HP.....in new location....cannot connect
Post by: sm2o on 2015-12-24, 21:23:33
As you had a working setup before you should not change anything in the RRCs. SIP ALG is a router setting.
I assume you have set the control RRC in DHCP mode, the router at the new location may have a different LAN setup.
Portforwarding is never needed in Control end

/mike
Title: Re: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-25, 04:17:04
I have tried again to connect to my remote in Nfld. VO1  from new router in Ottawa VE3.  The new router has no selection  under the WAN menu to disable SIP ALG.  It is either not a feature of this modem or it is hard coded and cannot be disabled hence no selection.   I tried placing the RR Control box in DMZ but that did not result in a fix.  The rig turned on at the remote end I though it was going to connect but after few seconds the K3 shut  down and alarm tone came on at Control.

Also tried turning on DHCP in the CONTROL end but that did not work either.  I have always used static IP when I had the system working while at home in Nfld. and DHCP has always been NO.

The  REMOTE RR unit is seeing the correct IP for the router at control end and populates the OTHER PARTY line item correctly.

I have not changed any settings in either RR box.   Was hoping to get the system working for Stew Perry contest but likely will not happen as I am at a loss re what to do.

The FIBE Modem is called HOME HUB 2000 from Bell Canada but it has very limited setup options under all its menu selections.  Looks like it has been dumbed down to the lowest level.
Title: Re: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-25, 18:39:56
Re above connect issue ...still investigating.
Both routers at each end can ping each other with round trip 65msec.
Title: Re: VO1HP.....in new location....cannot connect
Post by: Jan (Microbit) on 2015-12-25, 19:04:25
Have you checked what the connection status is on their Status web pages?
Title: Re: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-25, 21:26:48

Jan

Thanks for your reply on Xmas Day!!

Here are the status pages for CONTROL and REMOTE ends

Can you see anything there that I can check furtherÉ

VO1HP
Merry Xmas


CONTROL end

Name   Value
Control panel   ON
Radio   ON
Connection status   Disconnected
SIP status   Unknown(1)
Last SIP error   None
RTP/UDP audio status   Disconnected
UDP cmd status   Disconnected
SIP command timeout   3
Rx Jitter buffer size   4
Rx Jitter delay   3
Dual Rx   0
SIP Out port   13000
SIP In port   13000
Audio Out port   0
Audio In port   0
Command Out port   13002
Command In port   13002
External SIP In port   13000
External Audio In port   13001
External Cmd In port   13002
Other party   47.55.xx.xx
Input 0   High
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
DNS status   OK, remoterig.com = 213.180.92.20
Active profile   Nov 28 2015
PTT status   OFF
Common network settings   No



Remote End

Name   Value
Radio   OFF
Connection status   Disconnected
SIP status   Idle
Last SIP error   None
RTP/UDP audio status   Disconnected
UDP cmd status   Disconnected
SIP command timeout   0
Rx Jitter buffer size   12
Rx Jitter delay   8
Dual Rx   0
External IP    47.55.xx.xx
SIP Out port   13000
SIP In port   13000
Audio Out port   0
Audio In port   0
Command Out port   0
Command In port   13002
External SIP In port   13000
External Audio In port   13001
External Cmd In port   13002
Other party   0.0.0.0
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
Dynamic DNS status   OK
Ping status (watchdog)   OK [70 ms]
DNS status   OK, remoterig.com = 213.180.92.20
Active profile   Nov 18 2015 07:50
PTT status   OFF
Antenna-Switch (IP)   not connected
Common network settings   No
Title: Re: VO1HP.....in new location....cannot connect
Post by: Jan (Microbit) on 2015-12-25, 21:48:18
You could also take a snapshot of those pages immediately after attempting to connect as those listings seems to be when the RRCs are idle.

A Merry Xmas to you too!
Title: Re: VO1HP.....in new location....cannot connect
Post by: VO1HP on 2015-12-31, 03:39:30
It seems that problems were mainly that I was attempting to use a static IP address for the RR Control.
The static IP matched the range for the router but it did not connect to RR Remote .  I ran setup  manager and changed to DHCP....that solved the problem.  Was able to connect from two different networks at different locations in Ottawa.  I was also able to plug into Ethernet jacks at both locations.  Wifi at the two locations did not initially work probably due to the DHCP setting....I did not have an opportunity to try Wifi after solid connection using direct Ethernet cable connection.

So for me the new rule is ALWAY USE DHCP WHEN TRYING TO CONNECT TO UNKNOWN NETWORK