Years ago, the allstarlink.org website hosted a Java Applet communicator to interoperate with standard nodes on the AllStarLink Network. In the intervening years, the authentication method developed for this applet named "Web Transceiver" became the de facto standard for authenticating mobile and desktop applications to the AllStarLink network. These terms are used today: "WebTransceiver mode", "WT auth", "WT Mode", etc. However this method has numerous flaws and must be replaced.
WebTransceiver is what applications such as Repeater Phone, DVSwitch, etc. all use on mobile devices or apps such as Transceive or QSOone - and used for authentication. Note this does not mean that these applications will be going away, only that they will be updated to the new App Authentication ("AA") model at some point before the old WT authentication is removed. It is also important to note that "WebTransceiver" is not a separate "mode" for AllStarLink connections - they all use IAX2 - only that how the connection authenticates is different (i.e. "nodeless").
Standard ASL002 has been developed to replace deprecate and replace "WebTransceiver" authentication to modernize the process of authenticating users. The document can be found here:
https://github.com/AllStarLink/Standards/blob/main/ASL002-App_Authentication.md
This document is being made available now for a "fatal flaw" review while the new API is in development. (See this description for what this is.) This topic in Community can be used to ask any clarifying questions. This document will be open for fatal flaw review through October 2nd.
Of particular note, the standard includes the transition mechanisms and deprecation timelines for "Web Transceiver". Currently the expected implementation date is somewhere around the first or second week of November but a formal date will be announced in the coming weeks. I expect the API to be available for testing in mid- to late-October.
Thanks.
Jason