This is more of 2 problems with 3 solutions
Since custom AWAY messages were done away with AND Vmails will not release without a QSY unless AWAY is active I have to choose; To have a custom welcome message (never away), or let people collect their Vmails.
1. Enable custom away messages again
1a. Send extended away message only after recieving an SNR report of -10 or better
Or whatever SNR supports a speed level that will transfer the EAWAY in 2 packets
2. Add option to release Vmails without QSY when no CAT control or Auto QSY is not allowed
You could have a popup on the active user side to let them decide if they want to retrieve the Vmail and have a chart with
SNR recommendations for when to retrieve and when to try again later
3. Do both with protocols for sending extended data once an acceptable SNR is received to ensure speedy transfer
Here are my comments :
AWAY messages used to add lot of congestion to the CF. even in reasonable conditions. Therefore they will not be supported at the moment. I might add them later as an option to send only after a successfully QSY
This is already available. If you are not in AUTO-QSY or have no CAT control, and you have vmails waiting for someone and they connect you, it will be transferred on the CF as there is no other options to make those Vmails sent out.
Going back to item #1 - CF is a CF. Therefore is should remain available for callings. all data transfers should take place away from the CF when possible. especially "extended data" such as files and other long transmissions. From the moment we have implemented this ideology, the CF became much more available and I hear much less complains about CF congestions.
Another idea might be able to pre-setup a Auto-QSY before connecting. That way we could leave the CF open, but still pass mail. or have a slot just for mail?