As we've had some issues with people sending control codes into the system here and linking/unlinking major hubs I'm trying to figure out a better way than just prefixing the functions in rpt.conf with a code prefix (ie *3 becomes *443). Is there a way we can do this on a per user basis? Perhaps setting up a users file with a "PIN" and then requiring a user to "login" with this PIN prior to accepting any control codes? My ideal setup would be have one rpt_users.conf file (which should be changeable with out having to reload asterisk) [users] KB9MCI 12345 KQ4ERT 43567 KB8RET 54321 Then the users would key in #PIN, the system would auth them against the file, and upon authing them, it would respond "CALLSIGN authorized", the courtesy tone would change and the user would have 60 seconds to input the control codes. On the other hand I'd be happy with a way to do this on a per user basis for each command. For Example, *3 for kb9mci would become #12345*3. Anyone have ideas on how to script this sort of a setup? 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net
That sort of a thing was never implemented because of the open-interoperability nature of Allstar. That would prevent any user from going to any Allstar-linked system and be able to use it, which is one of the fundamental premises of Allstar. "Logins" are implemented to remote-base use, but not for general repeater use. Jim WB6NIL
Date: Sun, 21 Sep 2014 14:57:04 -0400 From: Bryan@bryanfields.net To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] user login prior to control codes?
As we've had some issues with people sending control codes into the system here and linking/unlinking major hubs I'm trying to figure out a better way than just prefixing the functions in rpt.conf with a code prefix (ie *3 becomes *443).
Is there a way we can do this on a per user basis? Perhaps setting up a users file with a "PIN" and then requiring a user to "login" with this PIN prior to accepting any control codes?
My ideal setup would be have one rpt_users.conf file (which should be changeable with out having to reload asterisk)
[users]
KB9MCI 12345 KQ4ERT 43567 KB8RET 54321
Then the users would key in #PIN, the system would auth them against the file, and upon authing them, it would respond "CALLSIGN authorized", the courtesy tone would change and the user would have 60 seconds to input the control codes.
On the other hand I'd be happy with a way to do this on a per user basis for each command. For Example, *3 for kb9mci would become #12345*3.
Anyone have ideas on how to script this sort of a setup?
73's -- Bryan Fields
727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Got my system working with the XIPAR install from the old Acid install that would hang every so often but had a question. Has anyone figured out a way to use web transceiver with the XIPAR install? I was just curious as it was nice to be able to turn that on at the Allstar site when I wanted to let others access it that way. Thanks Steve N4YZA
participants (3)
-
Bryan Fields -
Jim Duuuude -
The Rices