Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - es3at

Pages: [1]
1
Nice to heard that I'm not alone :)

I think only developers can help us.
Mike say in other topic "...the RRC-Micro and the RRC  do not add, remove or interfere it just opens up a channel..."
I agree and understand. But how we can be sure that something is not lost in the way?
Maybe this is my obsession, but I still think that highspeed serialconnection over UDP is not a good idea.
It's ok when we use this setup in same LAN, or over really good connection. But over long Wlan hops, 3G networks ..., I prefer TCP.

Is there some reason why we cant use TCP for this? For audio is clear, UDP is better.

73,
Kuido ES3AT

2
Hi, sometimes I lost connection between TS-2000 and RC-2000
Or better say that info transfer is only from TS-2000 to RC-2000 direction.

As example:
I can swich on my radio over network, all working, and in one moment  I can only receive audio and see moving S-meter and freq if scanning. From remote side to radio side nothing working.
No audio level, no squelsh, no poweroff. Only what I can do is switch off RRC in remote side and after restart all working again (from some min to several hours).

And in this time Remote side thinking that radio is off:
Quote
Control panel   ON
Radio   OFF
Connection status   OK
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(60)
UDP cmd status   OK(45)
SIP command timeout   0


I think (but not sure), that with 57600 speed is easy to lost some bits when connections is over UDP.
Dont remember similar situation when working/testing in my home with local network.

Any ideas what I can do with this problem?

Quote
Product   1258
Hardware   4
Software   2.46
Bootloader   <= 1.7



3
Nothing special.
Just configure home side, I recommend move SIP port to somewere high.
I use all ports 12000 and up.
And if Your router in homeside can then configure a vpn as backup.
Is possible, that some networks have some limitation and You cant connect directly.
Then You can try via notebook/VPN.

4
RRC uses 5 ports, telnet, web, SIP, UDP CMD, UDP AUDIO.
Only SIP, UDP CMD and UDP AUDIO is needed for remote control.
I never open/forward webserver/telnet port to internet. And I can work with without problem, I dont have PC client.
If I need change something in my radioside config then anyway I need some PC/notebook for this and
then vpn/ssh tunnel for this is no problem.

5
Chris, you are right with regard to the communication itself, but I'm concerned about the rig that is exposed on internet without any type of protection and you know there are guys, which hobby is to penetrate firewalls. basically the web pages, also if you change the port 80 are completely exposed (password without encryptions is not very strong) and they can easily access your rig. this is my real concern.
any suggestion?
cheers.
Why You need open web port to internet? If setup is done then You dont need it. Or if for some reason it is needed then I use ssh tunnel for this.

6
General discussion forum / Re: Cannot access control RRC
« on: 2011-01-18, 17:53:00 »
It is apparent, something is corrupt in the LAN connection to the RRC. I tried to refresh the firmware with both 30 and 32, and it failed to load.
Starting from ver 30 firmware is zipped. You unzip archive before update?

7
General discussion forum / Re: RC2000 and TS2000
« on: 2010-10-01, 10:53:23 »
Yes, I use RC2000 with TS2000. What is problem?

8
General discussion forum / Re: Drop Outs - Red Led comes on
« on: 2010-04-22, 16:40:40 »
Can you recommend how to do Network testing?

With command traceroute (tracert in Windows) You can see path. And then You try ping every router/host. Then You can see what hop is problematic.

9
General discussion forum / Re: Lost packets - lost CMD
« on: 2010-04-19, 19:52:31 »
Hi, I have same problems. 3-4 times press power button on RC-2000 before rig switch it on or off.
Sometimes rig switch off but RC-2000 is still connected.

All working ok in LAN. Problem exist if i work over internet. 2M/768k ADSL in rig side and 5M/5M in remote side.

I think that TCP for commands is good solution.

Pages: [1]