Skip to content
This repository has been archived by the owner on Feb 27, 2020. It is now read-only.

Commit

Permalink
Merge pull request #270 from Metaswitch/change_default
Browse files Browse the repository at this point in the history
[Reviewer: Krista] Change default value
  • Loading branch information
eleanor-merry committed Jul 3, 2017
2 parents 1d14942 + e076e7c commit ee0944a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/Clearwater_Configuration_Options_Reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,7 @@ This section describes optional configuration options, particularly for ensuring
* Without an I-CSCF there is no way to prevent it from registering as different user accounts.
* `disable_tcp_switch` - when set to 'Y', Clearwater disables UDP-to-TCP uplift on SIP messages. This is useful when creating a deployment where all SIP is sent over UDP. This option only affects Sprout nodes.
* `sprout_impi_store` - this is the location of Sprout's IMPI store. It has the same format as `sprout_registration_store`. If not provided, Sprout uses the same value configured in `sprout_registration_store`.
* `request_shared_ifcs` - when set to 'Y' Clearwater requests Shared iFC sets from the HSS. This option is enabled by default. Shared iFC sets can be configured on Clearwater in the `/etc/clearwater/shared_ifcs.xml` file.
* `request_shared_ifcs` - when set to 'Y' Clearwater requests Shared iFC sets from the HSS. Shared iFC sets can be configured on Clearwater in the `/etc/clearwater/shared_ifcs.xml` file. This option is not enabled by default.
* `apply_fallback_ifcs` - when set to 'Y' Clearwater will apply any fallback iFCs specified by the operator in the `/etc/clearwater/fallback_ifcs.xml` file to initial requests who have no applicable iFCs associated with them. This option is not enabled by default.
* `reject_if_no_matching_ifcs` - when set to 'Y' Clearwater will reject any initial requests that don't have any matching iFCs that can be applied to them. This option is not enabled by default.
* `dummy_app_server` - this field allows the name of a dummy application server to be specified. If an iFC contains this dummy application server, then no application server will be invoked when this iFC is triggered.
Expand Down

0 comments on commit ee0944a

Please sign in to comment.