Can't solve UDP error

[wq1k]

I've almost got RRC-Micro running, but I could sure use a bit of help.  Setup is an IC-7100, Firmware 2.85, RRC-Micro version 1.7.0  With the control and radio RRC-1258, everything works perfectly (Mode 2).  Then I try to connect RRC-Micro.  It appears to connect normally (screen shot attached) and receive an audio stream with RTP activity, steady buffer use. A faint hiss from the speakers.  But within 2 seconds of starting, I note the following status changes from the Radio Web UI.

Just before starting RRC-Micro:

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

... then IMMEDIATELY after starting - the radio is powered on, and audio is streaming, but a UDP error at 0 immediately occurs:

Radio   ON
Connection status   Faulty(See below)
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(60)
UDP cmd status   Error(0)

.. then, about two seconds later:


Status
Name   Value
Radio   OFF
Connection status   Disconnected
SIP status   Error
Last SIP error   SIP Error
RTP/UDP audio status   Disconnected
UDP cmd status   Disconnected

... and it stays that way until I stop RRC-Micro, when it returns to idle/normal.

What is strange is that UDP commands are clearly making it when I run in mode 2 with the control RRC.  I have double checked jumpers.  Firewall and antivirus on the RRC-Micro host machine are disabled.  CI-V is connected on COM2 with an Icom CT-17 and brand new serial cable; baud rate at 4800/N/8/2.  COM0 and COM1 are inactive on Micro RRC, and audio, command, and SIP ports are the same between RRC-Micro and the Radio RRC (and work fine from the Control RRC).  After scouring this forum, I also tried setting RTP transmission mode to continuous, that didn't help.  Audio quality to 0 on the Radio end as I understand the RRC-Micro requires.

One possible clue from debug mode on Micro RRC (I won't replicate the whole file here), but can send it:

[normal initialization... then:]

VERSIONS
17:42:58 Stored=1.7.0.0
17:42:58 RRC=1.7.0.0
17:42:58 Rtp=1.2.0

COM PORTS
17:42:58 Microbit 2.0 AB Virtual COM 2.6.2
17:42:59 FabulaTech Virtual Serial Port Bus

AUDIO DEVICES
17:42:59 Integrated Microphone Array (ID
17:42:59 External Mic (IDT High Definiti
17:42:59 Stereo Mix (IDT High Definition
17:42:59 Line (2- Microbit 1274A)
17:42:59 Microphone (2- Microbit 1274A)
17:42:59 Speakers and Headphones (IDT Hi
17:42:59 Communications Headphones (IDT
17:42:59 Speakers (2- Microbit 1274A)

17:42:59 RTP version 1.1.0
17:42:59 Checking Network Interface
17:42:59 Network is Realtek PCIe GBE Family Controller
17:42:59 Checking authorization
17:42:59 Dongle is present
17:42:59 This is a valid installation
17:42:59 Initalizing CW Page

[end excerpt]

Note the conflicting version reports for the RTP version...  Not much happens in the log at the moment the disconnect happens, it looks like this:

17:43:3 [RTP] IP=192.168.1.56, Port=13001, SizeSpk=80, SizeMic=40, J-Delay=6, J-Size=8, MicID=Integrated Microphone Array (ID, SpkID=Speakers (2- Microbit 1274A)
17:43:3 [RTP] Voip started
17:43:3 RTP Connected
17:43:3 [RTP] RTPCNTRL_CREATE_SESS
17:43:3 COM2{2} listening on TCP port 11184
17:43:3 COM: UDP Listening on port 13002
17:43:3 UDP/COM Manager Started
17:43:4 [RTP] WaveIn::Open SUCCESS
17:43:4 [RTP] RTPCNTRL_MIC_ON
17:43:4 [RTP] RTPCNTRL_AUDIO_ON
17:43:4 [RTP] Start Playback
17:43:5 [RTP] waveOutRestart           <<<<<<<==== THIS IS WHERE THE ERROR SEEMS TO OCCUR - what follows is just me shutting down a minute later
17:44:19 COM listener stop.
17:44:19 UDP/COM Manager Stopped
17:44:19 Connection closed in comAcceptCallback
17:44:19 [RTP] RtpClose

I'm stumped.  UDP commands get there fine with the control RRC - though it is interesting to see the countdown get as low as 17 or so before resetting to about 45.  I do have several routers and a WiFi link between the two ends, but ping times are short, signals strong, and again - it works fine from the Control RRC at the same point in the network that the Windows 7 machine running Micro-RRC fails.

Can anyone please help?

Thanks,
Dave WQ1K

[Jan (Microbit)]

Dave,

We have spotted an issue in version 2.85 of the RRC firmware which might be the cause to the problems you are facing. We hope to have a fix for it in the near future. Meanwhile you could try to downgrade to 2.84 and see if it works, if you can do without the other things we changed in 2.85. If you try to downgrade please report the outcome here as it would help us confirm we are on the right track 

[wq1k]

Jan, thanks so much for the update.  Good luck with the issue, and I'll try a downgrade as soon as I can.

[Jan (Microbit)]

It has been confirmed that downgrading to 2.84 solved a similar problem, so you could try the new 2.86(Beta) and see if it solves your problems too:

http://www.remoterig.com/forum/index.php?topic=3642.msg16792#msg16792

[wq1k]

Jan, 2.86 no longer reports a SIP error in the UI, but UDP cmd status is still Error(0).

Also, using 2 RRC-1258s, when you power down the IC-7100 (with 2.85 firmware on the control end and 2.86 beta on the radio end) the session no longer shuts down cleanly - the IC-7100 doesn't show "Power off" on the display and an error tone occurs.

 Here is a telnet debug2 transcript from an RRC-Micro session, in case it's helpful...

=========================
a: audio
c: codec
d: debug
f: flash
h: hwtest
i: sip
l: led
q: audio quality
p: power
r: radio
s: sys
u: usb
=========================
'
d

debug
=========================
+-:debuglevel
q: exit
0: com0-debug on/off
1: com1-debug on/off
2: com2-debug on/off
3: com3-debug on/off
4: com0-ascii on/off
5: com1-ascii on/off
6: com2-ascii on/off
7: com3-ascii on/off
8: debug2 on/off
i: icom-mic debug on/off
m: mode-10 debug on/off
t: comx time-stamp on/off
w: winkeyer on/off
8
debug2 = 1

debug
=========================
+-:debuglevel
q: exit
0: com0-debug on/off
1: com1-debug on/off
2: com2-debug on/off
3: com3-debug on/off
4: com0-ascii on/off
5: com1-ascii on/off
6: com2-ascii on/off
7: com3-ascii on/off
8: debug2 on/off
i: icom-mic debug on/off
m: mode-10 debug on/off
t: comx time-stamp on/off
w: winkeyer on/off
duplex: New Audiocoding 100 (8 KHz)
duplex: New Audiocoding 100 (8 KHz)
SIP: PC Client, packetlen=40
duplex: New Audiocoding 100 (8 KHz)
duplex: New Audiocoding 100 (8 KHz)
duplex: New Audiocoding 100 (8 KHz)
SIP: PC Client, packetlen=40
duplex: New Audiocoding 100 (8 KHz)
R-> Radio ON requested (2)
rtp enable [192.168.1.81/13001 192.168.1.81/13001]
R-> Connection established, radio ON, audioQuality=0
duplex: New Audiocoding 100 (8 KHz)
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
Skipping SIP msg 8 due to different Call-Id:
'11e98cdc4ac24841800c37139486ed77'
'19011140@192.168.1.56'

R-> Sending '8V on'
R-> Radio power ON detected (2)
sendIC7100PowerCmd: Sending pwr on cmd with 7 FEs
Skipping SIP msg 8 due to different Call-Id:
'11e98cdc4ac24841800c37139486ed77'
'19011140@192.168.1.56'

COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
rtpTx UDP
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
rtpRx UDP
rtpTx UDP
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
rtpRx UDP
rtpTx UDP
rtpRx UDP
rtpTx UDP
rtpRx UDP
rtpTx UDP
rtpRx UDP
rtpTx UDP
rtpTx UDP
rtpRx UDP
rtpTx UDP
rtpRx UDP
rtpTx UDP
rtpRx UDP
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
COM0-RX: SOM
rtpTx UDP
rtpRx UDP
rtp disable
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
duplex: New Audiocoding 100 (8 KHz)
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
R-> Radio OFF - SIP Idle
duplex: New Audiocoding 100 (8 KHz)
webserverPeriodics100ms: Connection timeout, closing connection 0
webserverPeriodics100ms: DoClose periodic clean, connection=0
duplex: New Audiocoding 100 (8 KHz)

[Jan (Microbit)]

Did you notice that you have to use 2.86 at both ends?

Jan

[wq1k]

Sorry, no; I was doing 2.85 to 2.86.  So I guess forget what I mentioned about the 1258 to 1258 connection, but still no luck with the RRC-Micro...

[Jan (Microbit)]

I assume that you no longer see disconnections due to SIP error when using version 2.86? If so, what does the RRC-micro look like now?

Also, do you still see log entries like:
'Skipping SIP msg X due to different Call-Id:' etc in the RRC Telnet log when either connecting with the RRC or the RRC-micro? Those entries should not appear when using 2.86 in both control and radio RRC.

[wq1k]

Jan, that's right, no disconnections due to SIP error, but still the UDP Error.  And yes, the skipping SIP message log entries do still appear.  Attached are fresh transcripts from the telnet debug interface - one from an RRC-Micro session with 2.86 on the radio side (along with the corresponding complete RRC-Micro debug log) and one from and one from 2.86 Control 1258 to 2.86 Radio 1258, both show that message.

However, even with the message, 1258 to 1258 mode 2 sessions work normally with "OK" UDP cmd status, but RRC-Micro sessions do generate the UDP error(0)

Hope this helps.  Thanks so much for working actively on this.
Dave WQ1K

[Jan (Microbit)]

This looks strange:

Skipping SIP msg 8 due to different Call-Id:
'19011141@192.168.1.50'
'19011140@192.168.1.56'

It's like there are two RRCs simultaneously accessing the radio-RRC. Which units have IP 1.50 and 1.56?

[wq1k]

Hmm.  .50 is the control, .56 is the radio unit.  The RRC-Micro Windows machine IP is .81. 

When I did the testing from the RRC-Micro, the Control unit at .50 was still on the network, but the last thing I had done with it was power down the IC-7100 front panel with the power button, making the assumption that the control unit would not hold any sessions open or interfere in any other way once that had been done. 

But the IC-7100 "run with console disconnected" option was enabled, so perhaps that kept something alive with the control unit that was interfering with the UDP commands from the RRC-Micro?   I'll test this theory if you think it has merit by either unplugging the control unit from the network and/or changing that IC-7100 option, then try RRC-Micro again?

[wq1k]

>>>> SOLVED!! <<<<<

I set the IC-7100 option (using the IC-7100 panel connected to the RRC-Control) so that the option "Power OFF (With No Controller)" to ON.  Then I pressed and held the power button until I saw a "Power off" indication on the IC-7100, and then unplugged the RRC-Control unit from power.  At that point, the RRC-Micro was able to start a normal session to the radio unit, with no UDP errors.

>>> EDIT <<
However, I later discovered that the Power-off mode problem may have been related to the TRX program I was using to control the IC-7100.  I have now switched to Ham Radio Deluxe, and it works fine with the "Power off )With No Controller)" setting OFF. 

One other note that may be helpful to others: I didn't realize that the radio mode of the RRC-1258 radio automatically switches to mode 0 when used with RRC-Micro.  It can be manually set to something different (when operating, as I do, alternately between detached front panel mode and CI-V via COM2) and will still work with RRC-Micro.

Thanks, Jan, you figured it out.

Maybe it would be good to add a note in the IC-7100 documentation about this option...

[Jan (Microbit)]

>>>> SOLVED!! <<<<<

I set the IC-7100 option (using the IC-7100 panel connected to the RRC-Control) so that the option "Power OFF (With No Controller)" to ON.  Then I pressed and held the power button until I saw a "Power off" indication on the IC-7100, and then unplugged the RRC-Control unit from power.  At that point, the RRC-Micro was able to start a normal session to the radio unit, with no UDP errors.

>>> EDIT <<
However, I later discovered that the Power-off mode problem may have been related to the TRX program I was using to control the IC-7100.  I have now switched to Ham Radio Deluxe, and it works fine with the "Power off )With No Controller)" setting OFF. 

One other note that may be helpful to others: I didn't realize that the radio mode of the RRC-1258 radio automatically switches to mode 0 when used with RRC-Micro.  It can be manually set to something different (when operating, as I do, alternately between detached front panel mode and CI-V via COM2) and will still work with RRC-Micro.

Thanks, Jan, you figured it out.

Maybe it would be good to add a note in the IC-7100 documentation about this option...

Great that it works now! 

About the automatic switching of modes etc when using the RRC-Micro it is mentioned here:

http://www.remoterig.com/wp/?page_id=28