Actually, there are some SIP servers on AMPRNet already; and I'm capable of standing up a SIP server at my station. The only problem personally is that there's not much of a reason to stand up multiple SIP servers. Even if we did, it would be a good idea to standardize the call scheme to interconnect them, so we could dial those with SIP registrations on the various servers.
To deploy this kind of infrastructure we can use a SIP Server like ("OpenSer"). This server will be a login server and a router server (enroute call to the endpoints), and the mailbox and the rest of services (echo test, text to speech, etc.) can be in individual Asterisk Servers. With SIP we can implement Voice, presence and IM services.
In the other hand with SIP we can deploy RoIP (radio over IP) services. for example HYT repeaters has a SIP interface to link to a PABX services (like asterisk) using SIP protocol.
A few years ago, I was deploying a similar infrastructure into the guifi.net network (Spanish wireless network).
I have more ideas to deploy services (cross-link DMR repeater to SIP servers to make direct calls, for example), and I know that my spanish colleague Alberto Sagredo will be interested in participate in this project.
Kind regards Alex Casanova (EA5HJX)
Regarding announcing services:
What exactly do those who want services announced wish to accomplish by having services announced over the network (and to the world if added to the DNS)?
My idea was more-so that those who don't mind informing the AMPRNet at-large that they have a service to share (and don't mind sharing that information) could post it to the list.
-KB3VWG _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net