Hi Jeffrey,
There is nothing special about making "outbound" P2P connections with Pat. You just enter the remote target call and the rest is handled automatically. You shouldn’t need to add the -0 suffix. Messages in your outbox addressed to the remote node will be transferred. Make sure the the message is ONLY addressed to the remote station, otherwise the message won’t be sent.
Regarding your issue that Pat just "sat idle». It sounds like you dialed a connection to a remote node that didn’t expect an incoming connection. WInlink Express will keep you in this idle state if the user didn’t select the proper «P2P session». You could also end up in this state if the remote TNC is not connected to any Winlink host application at the time.
I hope you’re able to resolve your issues.
PS: You enable listening for incoming packet connections by adding «ax2» to the list of listeners, either in your config or via the command line option. Then the remote will be able to connect to you as long as Pat is running. I.e. no «P2P session» needed as with Winlink Express.
—
73 de LA5NTA / Martin