infrastructure:services:yate
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
infrastructure:services:yate [2024-09-08 19:52 UTC] – Created from the form at infrastructure:services:form echtnurich1 | infrastructure:services:yate [2024-09-08 20:49 UTC] (current) – [Data entry] add vm host as server echtnurich1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== yate ====== | ====== yate ====== | ||
---- dataentry service ---- | ---- dataentry service ---- | ||
- | service-urls_urls: | + | service-urls_urls |
- | other-service-fqdns: | + | other-service-fqdns |
- | host-fqdn: @@Host-FQDN@|@ | + | host-fqdn |
- | netbox-link_url: | + | netbox-link_url |
- | server_page: | + | server_page |
- | maintainers: | + | maintainers |
- | ccchh-id-integration_yesno: | + | ccchh-id-integration_yesno : false |
---- | ---- | ||
+ | |||
===== Description ===== | ===== Description ===== | ||
- | what does this service | + | This service |
- | what do I need to know as a user?\\ | + | |
===== Configuration ===== | ===== Configuration ===== | ||
- | how is this service configured? (especially: what interesting specific configuration choices were made?) | + | The service |
+ | Additionally is pulls the service config from [[https:// | ||
+ | |||
+ | The most stable way currently to do call routing is by setting aliases or " | ||
+ | |||
+ | Routing is supposed to do the following: | ||
+ | * Receive calls from EPVPN and our landline | ||
+ | * Only route outgoing calls to EPVPN | ||
+ | * Internal routing with an easy number scheme |
infrastructure/services/yate.1725825173.txt.gz · Last modified: 2024-09-08 19:52 UTC by echtnurich1