-
Notifications
You must be signed in to change notification settings - Fork 87
Peer to Peer (P2P) messaging
This article will cover P2P messaging. This example setup will use the web GUI and ax25 transport. It is based on KM4ACK's video demo of this topic.
This article assumes you have already set up the web GUI and the ax25 transport.
In order to receive P2P messages, Pat must be configured to listen for them. This can be set in the listen field in the config file, like so:
{
"listen": ["ax25"]
}This configuration would have Pat listen for messages on the configured ax25 transport.
After Pat has been configured, simply run pat http to start the HTTP server. Pat will report in the console which address and port it is listening on for HTTP requests. Open the web GUI and verify at the top of the screen that Pat is "Listening on ax25". If that message is present, you are ready to receive a P2P message. So long as Pat is running, if your station is called with a message, Pat will receive it and save it to your inbox.
In the web GUI, under the Action menu, choose Compose to begin composing a new message. Enter the recipient's call sign in the "To:" field as usual and a subject if desired. Check the box for "P2P Only" to make sure the message is not routed to Winlink CMS servers. Finally, type your message and add any attachments you may wish to send, and click Post.
After posting a message, it is saved to the outbox and needs to be transmitted. Under the Action menu, choose Connect. For the transport, choose AX.25, and for the target, enter the call sign of your recipient with an SSID of -0. For instance, if your intended recipient is W1AW, you should target W1AW-0. With that, you're ready to send!