policies:covenant:equipment
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| policies:covenant:equipment [2021/09/10 04:34] – k1wiz | policies:covenant:equipment [2023/03/25 19:19] – [Allowed Equipment] 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' | + | be used on HHUX (Experimental). The HH Operator' |
| 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 === | ||
| We WILL NOT issue or provide support for SIP trunks. | We WILL NOT issue or provide support for SIP trunks. | ||
| + | |||
| + | |||
| + | === Security Note About PBX Trunks === | ||
| + | |||
| + | ===== Security ===== | ||
| + | |||
| + | <font inherit/ | ||
| + | \\ | ||
| + | In other words, if your trunk allows others a means to connect or call into your PBX (from a source not HH) those callers are not allowed onto our system, as we have no means to positively identify them as a properly licensed amateur radio operator. \\ | ||
| + | \\ | ||
| + | HH trunks fully support bi-directional traffic with this rule in mind. HH users may call your trunk to reach you. You, as an HH user, may use your trunk to call other HH users. You are not allowed to have others use your trunk to call HH users. \\ | ||
| + | \\ | ||
| + | This is to eliminate the potential of unauthenticated traffic (we try to do our best to keep traffic compliant since we have interconnected RF systems - we take that responsibility very seriously). \\ | ||
| + | \\ | ||
| + | <font inherit/ | ||
policies/covenant/equipment.txt · Last modified: 2024/03/22 19:01 by kg6baj