DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

Use this flag to allow the SBC to process (and make routing decisions) the maddr parameter present in the Contact header of the incoming request/response or in the Refer-To header.

When this flag is disabled, the SBC does not perform any special processing for maddr parameter in the SIP message.

The following behavior is supported with this feature:

  • When maddr is present in the received SIP request’s Contact Header or in the Contact header of 18x, 20x, and 3xx, SBC uses it as the remote target.
  • When routing based on maddr value, the SBC uses the port information present in the received Contact (or Refer-To) header.
  • When routing based on maddr value, the SBC uses the transport parameter present in the Contact as the new request's transport.
Note

 The SBC supports this feature when maddr value is IPv4, IPv6, or even FQDN (resolving to either IPv4 or IPv6).

 

Command Syntax

% set addressContext <name> zone <name> sipTrunkGroup <name> signaling honorMaddrParam <disabled | enabled>

Command Parameters

Honor Maddr Param Parameter

ParameterDescription

honorMaddrParam

Enable this flag to allow the SBC to process (and make routing decisions) the maddr parameter present in the Contact header of the incoming request/response or in the Refer-To header.

  • disabled (default)
  • enabled
 

  • No labels