You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Back to Table of Contents

Back to SIP Services

The 

Unable to show "metadata-from": No such page "_space_variables"
supports SIP message that include the maddr parameter in the following scenarios by enabling the SIP Trunk Group signaling flag honorMaddrParam:

  • maddr is received in 3xx response's Contact Header

  • maddr is present in 18x or 200 OK response's Contact Header

  • maddr is present in incoming request’s Contact Header
  • maddr is present in Refer-To Header

The

Unable to show "metadata-from": No such page "_space_variables"
supports a maddr value of IPv4, IPv6 and FQDN (resolving to either IPv4 or IPv6).

When maddr is present in the received SIP request’s Contact Header or in the Contact header of 18x, 20x, and 3xx, the

Unable to show "metadata-from": No such page "_space_variables"
uses it as the remote target.

When routing based on the maddr value,

Unable to show "metadata-from": No such page "_space_variables"
uses the port information present in the received Contact (or Refer-To) header. Additionally, the
Unable to show "metadata-from": No such page "_space_variables"
uses the transport parameter present in the Contact as the new request's transport parameter.

For configuration details, see:

  • No labels