Dear
Sir,
You
might want to re-state your previous comment..
"I guess this group quickly assumes the ->lowest
common denominator<- when responding to technical inquiries.
:( "
While many of the folks who frequent this list are
professional engineers working in the industry, be it Broadcast or LMR. I
might dare say the vast majority of us consider ourselves to be hams
first. In my own mind it is nice to be paid to enjoy my hobby for a
living.. not the other way around!
Just a thought to consider... good luck in your
efforts.
-----------------------------------------------------------------------------------------
Mike
Perryman Cavell, Mertz
& Davis, Inc.
[EMAIL PROTECTED]
Consulting
Engineers
<http://www.cmdconsulting.com>
7839 Ashton Avenue
K5JMP
Manassas, VA 20109 USA
(703) 392-9090; (703)
392-9559 fax; DC Line (202) 332-0110
-----------------------------------------------------------------------------------------
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of NonProfit Radio
Sent: Saturday, April 08, 2006 8:04 AM
To: [email protected]
Subject: Re: [Repeater-Builder] Connecting a repeater to a PBX
The repeater is a commercial repeater, not ham, of course. Sorry I didn't spell it out. Didn't think it was necessary given the described situation of the proposed access. This group caters to all repeater types and is not limited to just ham repeaters.
Many (most?) PBXs can restrict access to certain extensions so that we can control who can access the repeater. This is an internal only extension that is limited so that only a few internal extensions can call it.
Rather than set up a number of tone remotes, I'd prefer to use our existing PBX because it affords us greater flexibility.
I guess this group quickly assumes the lowest common denominator when responding to technical inquiries. :(
YAHOO! GROUPS LINKS
- Visit your group "Repeater-Builder" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
