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

[Don Hackler]

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/20130302/d943329a/attachment.html>