Connected to sip - but Connection status Faulty ?

[dl2nd]

Hello,

the connection between two RRC-1258 works.

I have a problem with the connection between the PC Client and the RRC-1258.

The RRC Client shows: Connected to sip: ...... and the RTP lights green but the RRC-1258 Radio Status Homepage shows:

Radio   ON
Connection status   Faulty(See below)
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(60)
UDP cmd status   Error(0)
SIP command timeout   0
Rx Jitter buffer size   7
Rx Jitter delay   5
Dual Rx   0
Current audio packet size   40
Current audio quality   0 - alaw 8 kHz
SIP Out port   61389
SIP In port   13000
Audio Out port   61392
Audio In port   13001
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   79.252.241.174
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
Dynamic DNS status   Unknown
Ping status (watchdog)   Off
DNS status   OK, remoterig.com = 193.202.110.185
Active profile:   Default
PTT status:   OFF
Antenna-Switch (IP)   not connected

The router ports (NAT) should be ok, I have tried the connect also in my own network but I got the same problem.
I have made 2 Files in the debug mode: external connection and connection in my own network.
In both files there are a entry with ...unauthorized ...., I have double checked my sip password, should be ok.

Thank you for your help.

Uwe

[dj0qn]

Uwe,

It looks like a port forward problem. You may have forwarded TCP instead of UDP, for
example.

If you send me a short mail to dj0qn (at) darc.de then I can send you my networking
checklist if you don't find the forwarding problem first.

73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

Yes, when you see "Connection status   Faulty(See below)" the lines below will tell which part is faulty. In this case it is the UPD port transferring the commands which has no contact as it says "UDP cmd status   Error(0)":

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

The numbers inside () are showing a timeout value and when they reach 0 there is a communication fault which was not just temporary.

[dl2nd]

Okay, thanks.
To exclude a problem with my router configuration, I have tried the connection in my own network (without the router)
but got the same error.
In matching with the ports at the 1258 status homepage, I think I have the correct settings in the RRC Client:
SIP Port: 13000
Command Port: 13002
Audio Port: 13001

Should be ok ?
By the way, when I disconnect the connection, the radio (TS-2000) switched off.

What strikes me, the outgoing ports of the RRC-1258 are allways different (not the command port, it is zero) which each new connection. I that correct ?

I took a look with wireshark and there are following records in the capture file; answer from RRC-1258:
Status: 401 unauthorized
Status: 403 forbidden

Uwe

[dl2nd]

Okay,

Mitch told me, I have to use RRC-COM2 instead off RRC-COM0 with Kenwood TS-2000.
I will try it ...

Uwe

[dj0qn]

Jan,

I suggest that the setup instructions for the RRC Micro Client should be improved.
This is at least the 5th or 6th one I have seen in the last few months that were
confused by the way it is written.

There are (hard to believe) many users of the RRC's that never set their station up
to use CAT. Then they don't understand why this won't work with the PC Client.
It needs to be clearer that one must use the CAT COM port. If this is a rig such as
a Kenwood, Yaesu or Elecraft, they must install a serial cable between the RRC and
rig to make this work.

Thanks & 73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

Mitch,

Thanks for your advice about how to improve the RRC Micro's setup instructions. Those "in charge" of it will surely follow your advice 

[roland]

I agree that it could be better. Just a thought. Would video instructions be better than written?

[dj0qn]

Thanks, video is always better, but has two drawbacks:

1) Is hard to modify, you usually need to redo for any changes
2) Can't be printed out.

73,
Mitch DJ0QN / K7DX

[roland]

Thanks for the input.
Guess PDF is to prefer then

[dl2nd]

Hello @ALL,

I have new results, looks better but not hundred percent.
With Mitchs help I am a step forward now 

COM0 and COM2 (RRC) connected to TS-2000.
- PTT works
- RX works
- TX works, I think

The debug file looks better but still with error "401 unauthorized".
The communications between COM2 and HRD fails.
The RRC Hompage still shows "connection faulty".

@Jan
Maybe, the debug file could help you ?

Uwe

[Jan (Microbit)]

Does the RRC status page still show "UDP cmd status   Error(0)"?

[dl2nd]

Yes

[Jan (Microbit)]

Then there is still something which prohibits the UDP Cmd data from being transferred between the RRC and the RRC Micro. You are 100% sure that the port forwarding is ok for that port?

[dl2nd]

Yes, for sure.
I am using the same ports with the combination RRC (Remote) - RRC (Radio) and it works.
Port forwarding settings: UDP -> 13000 - 13002 for 192.168.1.228 (RRC Radio)

If you like to try it I can send you the RRC radio url via private mail.

Uwe