But far from being required. If you're putting the services in obvious locations there is no need to discover anything.
For example, if the SIP services for ke4rap.ampr.org were hosted at ke4rappbx.ampr.org, and we're working off the callsign@callsign.ampr.org schema, a SRV record (and lookup) is necessary, obviously, for the call to be delivered. But, I don't need a SRV record to tell the world I am hosting SIP at ke4rap.ampr.org when that's the de facto destination for a call for ke4rap.
Sent from my iPhone
On Apr 23, 2014, at 1:07 AM, K7VE - John k7ve@k7ve.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ SRV records help with discovery.
John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223
On Tue, Apr 22, 2014 at 9:49 PM, Danny Messano drmessano@gmail.com wrote: (Please trim inclusions from previous messages) _______________________________________________ There really is no need to get ENUM or DNS SRV records involved.
ENUM is a useless shim that redirects landline numbers to SIP (or IAX) addresses. DNS SRV records are only really necessary for failover or if your services are hosted at another location. (I know, thats a bit over-simplified. Keep going..)
Any softphone could dial a URI such as sip://ke4rap@ke4rap.ampr.org. I can easily build an extension on my PBX to place a call to sip://ke4rap@ke4rap.ampr.org when I dial any numeric string I desire from a numeric-only endpoint (269 for example). This numeric-to-URI translation for numeric endpoints easily takes place in the dialplan on the sending end, and should not rely on some new set of numeric addresses to further complicate things.
On the receive end, a call to ke4rap@ on my PBX (ke4rap.ampr.org) could be routed to any sort of endpoint, numeric or otherwise.
Now supposed AA4AA would rather not run a PBX? Well, if some nice guy wants to set up a shared system, we only need to know AA4AA is hosted on KB3AAs PBX or some shared AMPR PBX and can be reached at SIP://AA4AA@KB3AA.ampr.org or sip://AA4AA@asterisk1.ampr.org.
This is the very basis of peer-to-peer URI calling. All you really need is a standard DNS lookup and some idea who you are calling.
This also exists RIGHT NOW. If i know CALLSIGN has a PBX on here and is set up in DNS, I could call him right now at CALLSIGN@CALLSIGN.ampr.org and the call will route. No other acronyms other than DNS need to be harmed for this to take place. :)
Danny Messano KE4RAP
Sent from my iPhone
On Apr 22, 2014, at 10:32 PM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ Should be quite doable provided there isn't lots of firewalling or natting involved. If not this protocol, IAX2 within Asterisk for which there are already ham radio adaptations made to it (ie: app_rpt and other pieces) can easily make the connection. Some sort of e164/enum lookup based on callsigns would also be beneficial but that also requires DNS hackery [something to be added along with SRV records?]
On Tue, Apr 22, 2014 at 3:51 PM, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ actually making SIP work really well over amprnet would be cool.
On Tue, Apr 22, 2014 at 2:49 PM, Tom Hayward esarfl@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
On Tue, Apr 22, 2014 at 2:26 PM, Don Fanning don@00100100.net wrote: (Please trim inclusions from previous messages) _______________________________________________ ZeroConf depends on Multicast which doesn't work well over
tunnels/VPN's
unless specifically configured for such.
How about DNS SRV records? Does the AMPR DNS robot support that record type?
http://en.wikipedia.org/wiki/SRV_record
Tom KD7LXL _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net