View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
enable-strict-location-match
Default Value: No default value (empty string)
Valid Values: msml (or true), softswitch, trunk, all
Changes Take Effect: For the next call
Related Feature: Geo-Location for MSML-Based Services: Strict Matching
Controls the SIP Server behavior in cases where an MSML service that matches a call by geo-location or overflow-location is not available, or, if during an attempt to apply a treatment, the matching service responds to the INVITE message with a SIP error, as follows:
- If this option is not present or not configured, SIP Server tries other available services for a call.
- If this option is set to msml (or true), SIP Server tries other available services that match a call by geo-location or overflow-location. If there is no match, SIP Server does not apply a service to the call with a different geo-location. (A value of true is supported for compatibility with previous releases of this feature.)
- If this option is set to trunk or softswitch, SIP Server tries other available trunks or softswitches that match a call by geo-location. This applies to calls directed to an external destination or DNs located behind the softswitch. If there is no match, SIP Server does not send a call to a device with a different geo-location.
- If this option is set to all, SIP Server applies the msml setting for calls to GVP and the trunk/softswitch setting to other cases.
If the enable-strict-location-match option is set to msml or true, it is possible to specify an alternative geo-location using the Application-level option overflow-location-map, or using the overflow-location key in AttributeExtensions of TRouteCall and TApplyTreatment client requests.
Draft Option
No draft option
