RMS Express not initiating SCS Modem to P3.
Svar
I have discussed with Steve Waterman recently and he has advised me that a fix is being sought for sessions not being accepted as P3. No longer a forum issue. Thank you.
This issue has been fixed by Vic. Tested over several days and this bug is now gone. Thansk to WL2K for finding the problem as reported.
The logs were of no value in this instance. As they did not show the other sides problem. Vic has corrected it at the server side. Now a done and fixed aspect. RMS Express is reliabnle on P3 connects!
It is kind of the other way around if a PTCII with no more trial P3s is linked to a RMS allowed by sysop running P1,P2, P3, or P2,P3.
RMS Express 1.1.1.3 still do force the PTCII into MYLevel P3 mode, and then TNC stops TX.
Not a problem with Airmail. Session level is automatically detected, allowed and automatic limited to P2 and thus working.
This is part of Pactor protocol, so possible. A possibility of choosing MYLevel 2 would solve the problem. No help in doing this with HYPERTERM first. It is overrun during initialization.
Can now hook for limit to P2.
This solves both Norwegian problem of 1000HZ BW by Law on 30m towards EU.
This also solves all world using old non P3 enabled PTCIIs linking to Servers allowing P1,2,3.
No more forcing into P3 which stop the TNC from any TX at all.
73 la7um Finn
Kundesupport af UserEcho