After verifying the error from RRC to RRC I had a friend connect with his RRC. He got the RTP failure just like I did and it seem to take about a minute to reset and reconnect. The interesting thing is this happens like clockwork every 15 minutes. The 15 minute rule carries over even between connection sessions. I was seeing drop outs at :11, :26, :41, and :56. If I disconnect and wait to reconnect at :10 it will fail within two minutes. If I connect at :28 it won't fail until :41. I'm not sure if this indicates something in the network resetting on a fixed interval but it certainly isn't random.
When it does fail the status page of the local RemoteRig says "RTP/UDP audio status Stalled(18)". The number varies between failures. When the connection is good the status page says "RTP status Excellent(60)".
I used a Telnet client to connect to my local RemoteRig to monitor the connection and it shows the failures and reset as
rtp disable
duplex: New Audiocoding 103 (12 KHz)
CP-> Radio ON(Idle)
duplex: New Audiocoding 103 (12 KHz)
duplex: New Audiocoding 103 (12 KHz)
duplex: New Audiocoding 103 (12 KHz)
New UDP CmdTxPort=13002
rtp enable [162.254.66.19/13001 162.254.66.19/13001]
CP-> Sending 8V: 0 Mute spk: 0
CP-> audioQuality=3
duplex: New Audiocoding 103 (12 KHz)
mode14: master-init-start
ELECRAFT K3 [ID017;]
mode14: master-init-done
The Telnet connection let's us know if the failure is happening without having to sit and listen to the connection constantly. It's too bad it doesn't timestamp the messages.
Is there something in the radio RRC that could be responsible for this? I would be more than happy if you want to contact me off line at w0jm at ARRL.Net and I will be happy to give you SIP address and password for you to look further into this if you would like.