[App_rpt-users] Motorola Phone Patch (Bob - AF6D)

[Bob - AF6D]

I am very impressed with what you have done but must admit that you've scare
the stuffing out of me! I have built several complete hosting data centers
(behind a main providers infrastructure) and can get around Linux. All I
want for now are two mountain tops that will get public links (each repeater
can only see one control center) using Ubiquity. I am AT site one and will
provide internet. Site 2 can be seen by repeater 2 and he will use Ubiquity
to link up. At the end of the day they need to see the datacenter. I'll add
phone patching later. We intend to link/vote/simulcast.

 

Step one seems to be to get the RTC installed. But as far as a warm and cozy
data center? Ain't gonna happen! They are like refrigerators! LOL.

  _____  

From: Don Hackler [mailto:donh at sigma.net] 
Sent: Sunday, March 03, 2013 12:37 AM
To: Bob - AF6D
Cc: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] Motorola Phone Patch (Bob - AF6D)

 

In your situation, I would use Micro-Node RTCM modules on the repeaters to
minimize the computer hardware on mountain tops.

 

All they need is some internet (or private ethernet) connectivity back to
the server in the warm cozy datacenter.

The RTCM modules don't even need static or public IP addresses as long as
they have an IP address for the server in the datacenter..

 

The RTCM module is effectively a remote URI that uses ethernet instead of a
direct USB connection.

Ideally, you want the Allstar system to be the repeater controller for the
most flexibility, but 

the RTCM will also do basic repeater control if the internet connection
dies.

 

 

Personally, I have an AllStar server that just talks to local radios over
DMK URI modules, and it has an IAX connection to my "production" Asterisk
phone servers.

The radios can be dialed as extensions from my main phone servers, and I can
route an outside trunk directly to a radio if I want.

The radios can also dial extensions in my production servers.

 

You can setup dial plans in either the Allstar box (or the Asterisk server)
that will only allow certain numbers to be dialed from the radios or codes
that dial explicit numbers.

 

It's all very flexible.  The biggest issue is that the ACID/apt_rpt
distribution for AllStar is a fork of the main Asterisk distribution that is
frozen at Asterisk 1.4

It is minimalist command line driven system with very steep learning curve.

 

I use PBX in a Flash Distributions of more modern Asterisk versions to
connect to the outside world and do the heavy lifting.  It's still a handful
to learn, but it's mostly

a web GUI that is a lot easier to get things done, and it's a fairly secure
distribution (with a very minimal attack surface) if you put it behind a
firewall. 

 

 

 

On Mar 2, 2013, at 10:06 PM, "Bob - AF6D" <bob at af6d.com> wrote:





This is excellent news! To be clear on random connections, I'd like my own
private network, but I'd also like a public server. Can they be the same
server? Not a problem either way. I have rack space.

 

The reasons to use Allstar that you state are the reasons we've chosen it.
Snow has hampered us somewhat with another storm brewing mid-week. We're
getting about one foot a week at 6,400 feet in So. California. Just enough
to snow on my parade. For now then I need to configure each repeater and the
Thin Client.

  _____  

From: Don Hackler [mailto:donh at sigma.net] 
Sent: Saturday, March 02, 2013 9:40 PM
To: Bob - AF6D
Cc: <app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] Motorola Phone Patch (Bob - AF6D)

 

You won't have much trouble setting up what you want with some config file
hackage.

Most of the phone patch "secret sauce" is just Asterisk configuration.  If
you don't want random Allstar connections, you don't need to allow them.
The phone patch is easy to control.   You will need a sip trunk, either from
an external provider, or you can put a SIP adapter on a local POTS line.
You will find that a cheap SIP trunk costs less than a POTS line with
adapter and works much better.


Radios are simply extensions on the asterisk system.  This makes them very
flexible. 

 


On Mar 2, 2013, at 7:19 PM, "Bob - AF6D" <bob at af6d.com> wrote:

You have exposed my rookiness! LOL. I am aware that a thin client hooked up
acts like a controller. Fallback mode I guess. But I was under the
impression that there are open conference servers, or that others may call
our node if connected to the internet. I have much to learn.

 

Our plan remains the same. We intend to link both MSF's on different
mountain tops via our own server. I own the hosting company and have Tier 1
bandwidth at my beckon call. But we want to have our own phone patch and
have a phone line at our data center. Both nodes are true public safety
(ECS/ARES/SAR) and expenses come out of my wallet. It is my hope that there
is a way to add a phone patch that doesn't cost us a recurring fee.

 

With regards to our dedicated server I was under the impression that we
could have our own private network, and, a public network for others to use.
Giving back for fun and for free. But our phone patch would be for our
exclusive use. We envision macros that will telephone specific numbers. I am
Linux literate if I can create my own phone patch.

_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130303/a6204808/attachment.html>