Your comments
We have tried in the intial testing of RMS WINMOR to integrate both Pactor and WINMOR into the same server. The results due to scanning requirements and busy channel detection were always unsatisfactory even with much effort. The problme has to do with the time needed for accurate signal type detection and the requirement for channel scanning. Using more stations and having them scan more limited frequencuies (e.g. Time of day scanning etc.) is the only practical solution found to date. The minimal additional cost of RMS WINMOR (no expensive TNC) will in time result in additional WINMOR stations coming on line.
The unattended station is always the Server and the station operator/owner of this server needs to have the ability to set the bandwidth. It is also necessary so that very limited wide band segments (e.g. US autoforward sub bands) are not used by low bandwidth stations making poor use of these limited spectrums. The station INIATING the connection (the client) KNOWS before hand the bandwidth of the station he is calling (e.g. the server is P3 or WINMOR 1600) and if this illegal for his location THE CLIENT is the one responsible for not making the illegal connection.
Customer support service by UserEcho
I am open to this but I think we need to see real analysis with detailed examples worked out to show how it would work and where the most likly problems are. When you allow only one frequency you dramatically simplify this problem though dual Pactor and WINMOR operation is still a bit of a challenge to insure absolute interlocking.
KN6KB