Hamshack Hotline Wiki

User Tools

Site Tools

Trace:
policies:covenant:equipment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
policies:covenant:equipment [2022/06/17 14:17] – Minor edit kg6bajpolicies:covenant:equipment [2024/03/22 19:01] (current) – [Security] kg6baj
Line 3: Line 3:
 HHUS, HHEU, and HHAP allow only devices listed in our Supported Endpoints document to connect HHUS, HHEU, and HHAP allow only devices listed in our Supported Endpoints document to connect
 to the network, to assure trouble-free and reliable provisioning. All other non supported endpoints can to the network, to assure trouble-free and reliable provisioning. All other non supported endpoints can
-be used on HHX or HHUX(Experimental). The HH Operator's Team (HHOPS) are a small group of volunteers+be used on HHUX (Experimental). The HH Operator's Team (HHOPS) are a small group of volunteers
 who dedicate some of their personal time to administrative duties and we want to ensure their burden is who dedicate some of their personal time to administrative duties and we want to ensure their burden is
 kept as low as possible. To achieve this, we will maintain a list of supported equipment.  kept as low as possible. To achieve this, we will maintain a list of supported equipment. 
Line 9: Line 9:
 As of March 5, 2018, HHUS, HHEU, and HHAP will no longer provide SIP accounts solely for softphones. In all As of March 5, 2018, HHUS, HHEU, and HHAP will no longer provide SIP accounts solely for softphones. In all
 cases, a member must have a provisioned and connected hardphone on HHUS, HHEU, and HHAP cases, a member must have a provisioned and connected hardphone on HHUS, HHEU, and HHAP
-network before HHOPS will allow that member to use a softphone on these listed servers(This does not +network before HHOPS will allow that member to use a softphone on these listed servers (This does not 
-apply to HHX or HHUX). The intention is to ultimately discourage the use of softphone-only users in general on the non-experimental network. The only exception to this is an IAX account issued solely for the purpose of trunking to another PBX that is member owned, in such case, the request will be granted by HHOPS.+apply to HHUX). The intention is to ultimately discourage the use of softphone-only users in general on the non-experimental network. The only exception to this is an IAX account issued solely for the purpose of trunking to another PBX that is member owned, in such case, the request will be granted by HHOPS.
  
 === A Note About End user PBX Trunks ===   === A Note About End user PBX Trunks ===  
Line 30: Line 30:
  \\  \\
 <font inherit/inherit;;#ffa500;inherit>Please note, that if at any time we detect that your trunk is in violation of this policy, we will terminate your trunk extension. </font> \\ <font inherit/inherit;;#ffa500;inherit>Please note, that if at any time we detect that your trunk is in violation of this policy, we will terminate your trunk extension. </font> \\
 + \\
 +Also, as a safety valve, Trunks will not be allowed to access RF links anymore. We have had too many instances of Trunk owners allowing PSTN connected callers onto their Trunks, as well as other users that HH can not vet as licensed amateur radio operators. Because of this potential for non-licensed persons to access RF connections, we had to take steps to dis-allow it. So, yes, a few bad apples have spoiled it for all Trunk extensions. \\
 + \\
policies/covenant/equipment.txt · Last modified: 2024/03/22 19:01 by kg6baj

Page Tools