Some groups have local mesh networks with VoIP provision. Some time ago it was asked whether we would provide a central exchange where these VoIP systems might be brought together in an interoperable manner. This will probably be provisioned through an Asterisk server and a common dial plan based on the private DMR server talkgroup listing,
Some groups have local mesh networks with VoIP provision. Some time ago it was asked whether we would provide a central exchange where these VoIP systems might be brought together in an interoperable manner. This will probably be provisioned through an Asterisk server and a common dial plan based on the private DMR server talkgroup listing,
Looking to achieve something similar to the C*Net. Their setup information is at https://www.ckts.info/#installation . That uses ENUM DNS entries to route calls?
Something we can achieve by a private DNS server and maybe an Asterisk centrally for those groups who just want to connect directly?
Looking to achieve something similar to the C*Net. Their setup information is at https://www.ckts.info/#installation . That uses ENUM DNS entries to route calls?
Something we can achieve by a private DNS server and maybe an Asterisk centrally for those groups who just want to connect directly?
Using IAX2 Trunking would likely be the best way to arrange the interlinking.. This would allow for Mesh interlinking, which might be preferable rather than routing though a single point of failure.
Using IAX2 Trunking would likely be the best way to arrange the interlinking.. This would allow for Mesh interlinking, which might be preferable rather than routing though a single point of failure.
“For example, here we use the unix dig command to lookup up information stored in the DNS system rooted in e164.org for the phone number 1-800-555-5555, i.e. a random US toll free number. We ask for any records stored for this number.
What we get back describes to ways to reach that number using different transport schemes, using SIP and one using IAX2.
That information was actually stored in the NAPTR records associated with the domain 5.5.5.5.5.5.5.0.0.8.1.e164.org; so we would probably actually have done this to get this info:
I wasn’t thinking a single DNS server. More a pair of authoritative servers at the top and caching servers in each local ‘exchange’ to accommodate failures.
I don't think the two are mutually exclusive.
"For example, here we use the unix dig command to lookup up information stored in the DNS system rooted in e164.org for the phone number 1-800-555-5555, i.e. a random US toll free number. We ask for any records stored for this number.
$ dig +short 5.5.5.5.5.5.5.0.0.8.1.e164.org any
100 10 “u” “E2U+SIP” “!^\\+1800(.*)$!sip:1800\\1@216.234.116.184!” .
100 10 “u” “E2U+IAX2” “!^\\+1800(.*)$!iax2:guest@216.234.116.184/1800\\1!” .
What we get back describes to ways to reach that number using different transport schemes, using SIP and one using IAX2.
That information was actually stored in the NAPTR records associated with the domain 5.5.5.5.5.5.5.0.0.8.1.e164.org; so we would probably actually have done this to get this info:
$ dig +short 5.5.5.5.5.5.5.0.0.8.1.e164.org NAPTR
100 10 “u” “E2U+SIP” “!^\\+1800(.*)$!sip:1800\\1@216.234.116.184!” .
100 10 “u” “E2U+IAX2” “!^\\+1800(.*)$!iax2:guest@216.234.116.184/1800\\1!” ."
I wasn't thinking a single DNS server. More a pair of authoritative servers at the top and caching servers in each local 'exchange' to accommodate failures.
Some groups have local mesh networks with VoIP provision. Some time ago it was asked whether we would provide a central exchange where these VoIP systems might be brought together in an interoperable manner. This will probably be provisioned through an Asterisk server and a common dial plan based on the private DMR server talkgroup listing,
Looking to achieve something similar to the C*Net. Their setup information is at https://www.ckts.info/#installation . That uses ENUM DNS entries to route calls? Something we can achieve by a private DNS server and maybe an Asterisk centrally for those groups who just want to connect directly?
Using IAX2 Trunking would likely be the best way to arrange the interlinking.. This would allow for Mesh interlinking, which might be preferable rather than routing though a single point of failure.
I don’t think the two are mutually exclusive.
“For example, here we use the unix dig command to lookup up information stored in the DNS system rooted in e164.org for the phone number 1-800-555-5555, i.e. a random US toll free number. We ask for any records stored for this number.
$ dig +short 5.5.5.5.5.5.5.0.0.8.1.e164.org any 100 10 “u” “E2U+SIP” “!^\+1800(.)$!sip:1800\1@216.234.116.184!” . 100 10 “u” “E2U+IAX2” “!^\+1800(.)$!iax2:guest@216.234.116.184/1800\1!” .
What we get back describes to ways to reach that number using different transport schemes, using SIP and one using IAX2. That information was actually stored in the NAPTR records associated with the domain 5.5.5.5.5.5.5.0.0.8.1.e164.org; so we would probably actually have done this to get this info:
$ dig +short 5.5.5.5.5.5.5.0.0.8.1.e164.org NAPTR 100 10 “u” “E2U+SIP” “!^\+1800(.)$!sip:1800\1@216.234.116.184!” . 100 10 “u” “E2U+IAX2” “!^\+1800(.)$!iax2:guest@216.234.116.184/1800\1!” .”
I wasn’t thinking a single DNS server. More a pair of authoritative servers at the top and caching servers in each local ‘exchange’ to accommodate failures.
Another source for Asterisk config information https://npstn.us/docs/#mw