Messages

1

Hardware, Cabling, Installations / Re: 706 powers up, no control

« on: 2013-04-01, 04:29:21 »

Hi, Mike... here's an update...

The Aux/Mic light indicating the SIP connection is good comes on when I press the power button and I see the following status for the radio controller:
Radio   ON
Connection status   OK
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(60)
UDP cmd status   OK(18)

The control status shows:
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)

Notice the "Radio" status; this is as you explained before... the radio appears to be on but I am not able to see or control it. If the hardware is good, is it a port issue? I suspect it is something simple, but...

Thank you!

2

Hardware, Cabling, Installations / Re: 706 powers up, no control

« on: 2013-04-01, 03:05:54 »

Thanks, as always, Mike.

I checked the jumpers and they are all solid. I reseated each, just to be sure.

One thing has become apparent since I first posted this morning; the DSL router at the radio end took a hit of some sort and I think some of the port configurations were affected. I will re-do all of those, and I did confirm continuity on each of the radio/controller cable pins. I suspect routing issues now as nothing has changed at the control end and I am now seeing what I think are connectivity issues below:

Name   Value
Radio   OFF
Connection status   Disconnected
SIP status   Idle
Last SIP error   None
RTP/UDP audio status   Disconnected
UDP cmd status   Disconnected

I am correct in assuming the RTP/UDP audio is on 11000 and the command is 12000 (I used the defaults for those)? Would you agree it looks like there is now a firewall/routing issue in play?

It may be that the I lost partial control as the ports were being fouled in the DSL router today, as physically, the box looked fine.

You thoughts? Again, thank you...

3

Hardware, Cabling, Installations / 706 powers up, no control

« on: 2013-03-31, 17:06:18 »

Thanks for any thoughts/help in advance.

Everything was working fine, but, suddenly, the control head for my 706 is only able to turn the rig on and off. It will stay on for a few minutes, then turn itself off. It's as if it has partial control. The status information at the radio end is copied below; all looks normal.

Variables: The cable from the control head to the controller has just been redone. This is a new installation with many new pieces of equipment between the controllers (DSL, WiFi, bridge).

My feeling is that some critical piece of control information has quit being passed between the controllers and, sensing it has lost control, one or both of the controllers shut down the connection. And, it happened all of a sudden.

Is it possible to only be able to turn the radio on and off and not have other control? If so, does that indicate the cable at the control end? As the cable is delicate (which is why it has recently been redone), I don't want to stress it out any more than needed, so am reluctant to go at it with a VOM... but, will be happy to do so if that is where I need to look.

Any thoughts?

73,

Gary

===============================

Name   Value
Radio   ON
Connection status   OK
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(59)
UDP cmd status   OK(40)
SIP command timeout   0
Rx Jitter buffer size   10
Rx Jitter delay   9
Dual Rx   0
Current audio packet size   20
Current audio quality   0 - alaw 8 kHz
External IP   50.0.XXX.XX
SIP Out port   5061
SIP In port   5061
Audio Out port   11000
Audio In port   11000
Command Out port   12000
Command In port   12000
External SIP In port   5061
External Audio In port   11000
External Cmd In port   12000
Other party   75.111.XX.XX
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
Dynamic DNS status   OK
Ping status (watchdog)   Off
DNS status   OK, remoterig.com = 193.202.110.185
Active profile:   Default
PTT status:   OFF

4

General discussion forum / Re: Codec 12 - IMA ADPCM 8 KHz

« on: 2013-01-07, 15:32:49 »

Thank you! That would explain the random nature of the problem. Yes, please, if there is anything you can do to be proactive to help the codec "right" itself again it starts distorting, it would be greatly appreciated.

Are there any settings I can optimize to guard against this, that would not eat more bandwidth?

73

5

General discussion forum / Codec 12 - IMA ADPCM 8 KHz

« on: 2013-01-07, 04:36:41 »

I am moving to a 3G connection where I will have to count every kB and need to run codec 12, IMA ADPCM 8 khz.

I have been running it for a few days and have noticed it begins to distort quite a bit after some period of time. I can clean it up by powering off the local controller, but not by restarting it. I am running software 2.57 and an Icom-706MKIIG. Codec 0 is solid as a rock, but, now, with limited bandwidth, I need Codec 12.

I haven't figured out what triggers it into distortion (very difficult to explain, almost like harmonic bursts on voice peaks with low frequency components), nor does it start at a regular interval. But, when it works, it is perfect,

Has anyone else encountered this behavior? Anything I can do at this end to help isolate the cause?

Many thanks and 73,

Gary

6

General discussion forum / Re: DDNS issue

« on: 2012-08-04, 19:30:53 »

HA!!! Thank you for helping me see the obvious. I am so used to putting in a secondary DNS server address in normal configurations, that is exactly what I had done with the remote unit for the DNS Server address. Once I saw that, I knew that was the problem. I would have looked at that for days and not realized it. All better now! Thanks and 73...

7

General discussion forum / DDNS issue

« on: 2012-08-04, 02:53:10 »

My remote box is not updating when a new IP address is assigned. It still shows the old IP address and is unavailable via RemoteRig's DDNS service. If I set the current remote IP address and port in the calling unit, the remote unit comes right up and works fine, so it is working fine in that regard. To clarify:

External IP is the old address
Dynamic DNS status    is "Unknown"
DNS status is "Querying status"

I have restarted the box a number of times and reset the DNS interval hoping to force a look for a new IP address, but no luck.

Any other parameters you'd like me to check, or have any ideas? I think it failed on August 1, at the start of the new month, when the ISP hands out new addresses.

Thanks and 73,

Gary, WA6HZT

8

General discussion forum / Re: Best strategies for dealing with packet loss

« on: 2012-06-03, 02:23:07 »

Thanks Mitch and Mike!

I have been running codec 0, and have experimented with 12, as well. Sometimes I find 12 gets raspy-sounding after a while, but have not noticed that with 0.  I agree, 0 is fine for everything I have tried it with, which has been FM and digital modes.

Bandwidth at the radio end is 768 K up and 10 MB down, and I have enabled QoS to the RRC to the highest priority.

Bandwidth at the control end is almost 4 MB up and 25 MB down. QoS enabled at that end, too. Both are cable internet services.

Even running 16/15 buffers and 20 ms packets, I still get hiccups at times. I know bandwidth isn't the issue, and suspect ISP problems at the radio end. The direct path is about 200 miles (322 km). I have verified bandwidth isn't too pinched in the evening via speed tests.

There are no external devices attached and I have been watching the actual bandwidth during operation as I have changed parameters. Nothing over about 150 K in a worst-case scenario, typically 90 to 100 K with the current 16/15 buffers with 20 ms packets.

Thanks again!

73

9

General discussion forum / Re: Help with RRC Radio web access

« on: 2012-06-02, 02:16:10 »

All is working fine now, thank you. For whatever reason, the port reassignment seems to have made the difference. Ah, the joys of networking...  :-)

73

10

General discussion forum / Best strategies for dealing with packet loss

« on: 2012-06-01, 04:50:29 »

I'd appreciate everyone's thoughts on this. I have seen two schools of thought on how best to deal with packet loss; one says to increase the packet size while keeping buffer/delay values lower while the exact opposite is also touted as being more robust.

To put it in RRC terms, at one extreme you might have buffer and delay values of 16 and 15 with a packet size of 5 ms, with the other extreme being buffer and delay values of 6 and 5 with a packet size of 40 ms.

I am plagued by very bad packet loss at times, especially in the evening, and some expert advice would be greatly appreciated. Bandwidth concerns aside, which of these two approaches... or is there another... that works best?

Thanks & 73

11

General discussion forum / Re: Help with RRC Radio web access

« on: 2012-06-01, 03:58:05 »

Some success has been had, but still an issue.

I wound up trying port 8090 for the web server and it still would not connect via the xxxxxxxx.ddns.remoterig.com address. However, when I tried the IP address of the remote location with the port number appended, XX.XXX.XX.XX:8090, I got right to it. This has been working reliably for a couple hours now, but I still cannot connect using the ddns.remoterig.com route. The Radio RRC is now back behind the firewall, out of the DMZ, with only proper port forwarding, as it should be. All is well, except for the ddns resolution issue, if that's what it is.

Maybe you could look into this for me?

Many thanks...

12

General discussion forum / Re: Help with RRC Radio web access

« on: 2012-06-01, 02:27:09 »

Hi, Jan... firmware is current for the model. I also had the idea to put the RRC in the DMZ, which *should* eliminate any port forwarding issues, but I still can't access it. I'll reboot everything one more time, but, beyond that, I'm stumped. I agree... if the RRC is serving locally, it should be serving externally. I'll post a solution if I find one, for anyone who may have a similar issue down the road.

73,

Gary

13

General discussion forum / Re: Help with RRC Radio web access

« on: 2012-05-31, 03:10:05 »

One more thing... I am able to telnet into the box. I could see the RRC menus no problem.

14

General discussion forum / Re: Help with RRC Radio web access

« on: 2012-05-30, 19:33:45 »

Hi, Jan... some answers for you...

The connection times out, always. There are no partial or slow loads. It's as if the port is not open, no matter if it's 80 or not.

I have a helper at the other end that can change things locally, and I have the ability to do so, as well, using CrossLoop.

If you enter the Radio RRC local IP address you can get right to it. I have configured it with and without user ID and password and it works flawlessly inside the LAN.  The problem is only from the outside.

Do you think a release/renew forcing a new IP address might help? What other information can I provide to help?

Thanks!

15

General discussion forum / Help with RRC Radio web access

« on: 2012-05-30, 04:26:59 »

Thanks in advance for any suggestions. I have the RRC's talking happily over the Internet with no issues... they work and sound great! But, the Radio RRC web access has been problematic. It did work a few days ago when I originally installed the system, but has now gone away.

I have tried changing ports to 8000, 8081, etc. to no avail. The other ports involved are 2300, 11000, and 12000. I left 80 back as the default after trying various other ports without success. It's a Linksys router that has been rock solid and I can blast holes in the firewall predictably with it for anything else.

I have confirmed the checklist items and verified it is set for the 10 minute interval, is set to ddns with the generated information showing from the initial registration. I have tried different browsers with different DNS servers (to eliminate resolution problems) and tried the known-correct IP address at the radio end with :80, :8000, etc. appended, and it still times out.

Now, here's a clue: I ran a status just now and found this-
ID   
Zone   ddns.remoterig.com
Host   xxxxxxxx
Link   xxxxxxxx.ddns.remoterig.com
Ip   XX.XXX.XX.XX
Last update   2012-05-26 06:57:44
Update count   2

Can the web server just freeze up and refuse to play along? Short of a reset, which isn't feasible at the moment, any suggestions? Looks like it has quit calling the mother ship and has been booted many times since then. The IP address is still the same as that shown in the status report.

Thanks and 73,

Gary, WA6HZT