Rules for mapping SIP addresses Contains one or more hostMatch elements. Each hostMatch element is evaluated until one matches. A hostMatch may contain multiple hostPattern elements, followed by a userMatch element. The host part of the target URI is compared with each hostPattern until one matches. Despite the name, the contents of a hostPattern is not a pattern; The host part of the target URI must match the content of a hostPattern exactly. Matches a DNS name (which includes an IPv4 address), with an optional port number. This is a permissive match, in that it allows names that are not fully qualified. The host part of the target URI is compared with each hostPattern until one matches. Despite the name, the contents of a hostPattern is not a pattern; The host part of the target URI must match the content of a hostPattern exactly. Contains a set of match specifiers for the user part of a SIP address and then other rules to be applied to any address that matches at least one of the specified userPattern specifiers. Matches all characters valid in a SIP user part. A pattern expression used to match the user part of a SIP URL. The contents of a userPattern is a sequence of characters that is matched against the entire user part of the target URI. The following characters are special in a userPattern: x matches any single character . matches any sequence of characters [] encloses a set of characters that match a single character Any other character matches only if it exactly matches the character in the target URI. Any of the special characters may be escaped by prefixing with a backslash (\), in which case it matches only if it exactly matches the character in the target URI. Any other use of backslash is invalid, and is ignored. The pattern is implicitly anchored at both ends. Contains a set of match specifiers for the user part of a SIP address and then other rules to be applied to any address that matches at least one of the specified user patterns. A string that must match an existing permission token. This applies to the permissions of the target URI, not the caller, so it can be used to create matches based on the capabilities of the called address. Contains elements to construct the output address. In each of the output elements, these special strings are replaced as follows: {digits} the full user part of the original URI {vdigits} the the right substring of the orignial URI that begins at the first non-constant character in the userPattern that matched. {host} the host part of the orignial URI (including the port, if any) {headerparams} the full header parameters of the original URI {urlparams} the full URL parameters of the original URI {uri} the full original URI The following special strings are deprecated - they are allowed now, but may not be in the future; use is strongly discouraged: {localhost} the URI of the local host {voicemail} the host configured for the voicemail server {mediaserver} the host configured for the media server This specifies the complete Contact address. These elements allow substitution of or addition to the existing address any parts not explictly specified are copied from the input address. The complete output SIP URL. In this element only, the value must be escaped as it would be when transmitted in a SIP message. The user portion of the output SIP URL. The value should not be escaped as it would be when transmitted in a SIP message; only escaping needed to make it valid XML should be used. The host portion of the output SIP URL. The value should not be escaped as it would be when transmitted in a SIP message; only escaping needed to make it valid XML should be used. A field parameter to be appended to the output SIP URL. It is not valid to specify a 'tag' field parameter. An 'expires' parameter, if specified, replaces any existing 'expires' parameter rather than being appended. The value should not be escaped as it would be when transmitted in a SIP message; only escaping needed to make it valid XML should be used. A header parameter to be appended to the output SIP URL. Certain parameters are not allowed (see SipMessage::SipMessageFieldProps::initDisallowedUrlHeaders). A Route header, if specified, is pushed as the topmost route (rather than being appended, which would cause it to be the last route). The value should not be escaped as it would be when transmitted in a SIP message; only escaping needed to make it valid XML should be used. A URL parameter to be appended to the output SIP URL. The value should not be escaped as it would be when transmitted in a SIP message; only escaping needed to make it valid XML should be used. Used to describe the rule in the user interface.