New to this digital communication. I am using an Yaesu FT3D and mostly there are no issues communicating using OS2. However I have noticed that I once in a while do not get any respons and need to change profile or completely disconnect in order to get out. The same when trying to use DTMF to control the OS2. I found that when the OS2 is not responding to DTMF it reports "got unknown radio code 30", which I suspect may be that it cannot read the DTMF code properly?

However, even when not using DTMF, and only using voice communication and not getting out at all, it reports the samme error as shown below:

(the below is from when connected to an YSF reflector, but I think the same occurs when in cross mode to DMR)

Any tips of what could be wrong?

Regards
Bjørnung

18:48:32 c4fmcalltracker: got header
18:48:32 c4fmcalltracker: got header
18:48:32 c4fmpacket: header
18:48:32 dst: YAF77EA6Xb src: LA9ULA
18:48:32 dl: ul:
18:48:32 c4fmcalltracker: voice call started, dst: YAF77EA6Xb dgid: 0 src: LA9ULA id: 0e727aca50d01892
18:48:32 nvmm-csd: looking up callsign YAF77EA6Xb
18:48:32 nvmm-csd: callsign YAF77EA6Xb not found
18:48:32 nvmm-csd: looking up callsign LA9ULA
18:48:32 nvmm-csd: dmr ids 2423084 call "LA9ULA" name "Bjornung" city "" state "" country ""
18:48:32 ysfref-c4fm: call started
18:48:33 ysfref: received poll
18:48:33 c4fmpacket: got unknown radio code 30
18:48:33 aprs-queue: added delayed msg type 2 to slot #3 LA9ULA-7
18:48:33 aprs-queue: processing delayed slot #3 LA9ULA-7 type 2
18:48:34 c4fmpacket: got unknown radio code 30
18:48:34 aprs-queue: added delayed msg type 2 to slot #4 LA9ULA-7
18:48:34 aprs-queue: processing delayed slot #4 LA9ULA-7 type 2
18:48:34 c4fmcalltracker: got terminator
18:48:34 c4fmpacket: header
18:48:34 dst: YAF77EA6Xb src: LA9ULA
18:48:34 dl: ul:
18:48:34 c4fmcalltracker: call ended, dur 1.9s ber 0.4% loss 0.0% rssi -47
18:48:34 ysfref-c4fm: call stopped
18:48:34 c4fmcall: tx confirm
18:48:35 ysfref: sending poll
18:48:36 ysfref: received poll