Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed header, formatting of call_policy.md #740

Merged
merged 1 commit into from
Jul 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions content/uc-doc/administration/call_policy.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Sound Files
title: Call Policy
tags: administration,call,policy,api
slug: linear-ring-group-preview
slug: call-policy
---

There exists multiple ways to constrain calls performed through the Wazo platform.
Expand Down Expand Up @@ -35,14 +35,16 @@ endpoints configuration.

SIP endpoint options can be configured in two ways:

1. through SIP templates, which apply to all or a subset of SIP endpoints in a tenant Each tenant
has a global SIP template which represent common options which can apply to all SIP endpoints.
Other templates can specify options for a specific subset of SIP endpoints. See
[SIP templates documentation](/uc-doc/administration/sip_templates) for information on how to
1. through SIP templates, which can be applied to all or a subset of SIP endpoints in a tenant;
each tenant has a `global` SIP template which represent common options which can apply to all SIP
endpoints. Other templates can specify options for a specific subset of SIP endpoints.
See [SIP templates documentation](/uc-doc/administration/sip_templates) for information on how to
query and configure SIP templates.

2. directly through a SIP endpoint's individual configuration. Individual endpoint configuration can
be changed through the `/api/confd/1.1/endpoints/sip/{sip_uuid}` REST API endpoint. See
2. directly through a SIP endpoint's individual configuration;
individual endpoint configuration can be changed through the
`/api/confd/1.1/endpoints/sip/{sip_uuid}` REST API endpoint.
See
[API reference](/documentation/api/configuration.html#tag/endpoints/operation/update_endpoint_sip)
for details.

Expand Down