1. ACLI Reference Guide
  2. ACLI Configuration Elements A-M
  3. local-policy

local-policy

The local-policy configuration element determines where session signaling messages are routed and/or forwarded.

Parameters

from-address
Enter the source IP address, POTS number, E.164 number, or hostname for the local-policy element. At least one address must be set within this list, but it can include as many addresses as necessary. This parameter may be wildcarded, or entered with a DS: prefix (dialed string).
An IPv6 address is valid for this parameter.

Note:

This field adheres to the standard ACLI character limit of 1024, as documented herein.
to-address
Enter the destination IP address, POTS number, E.164 number, or hostname for the local-policy element. At least one address must be set within this list, but it can include as many addresses as necessary. This parameter may be wildcarded.
An IPv6 address is valid for this parameter.

Note:

This field adheres to the standard ACLI character limit of 1024, as documented herein.
source-realm
Enter the realms used to determine how to route traffic. This list identifies incoming traffic on a realm and is used for routing by ingress realm via the local policy element. Source-realm entries must be a valid realm.
  • Default: *
description
Provide a brief description of the local-policy configuration element
activate-time
Set the time when selected local-policy becomes valid
activate-time yyyy-mm-dd hh:mm:ss or
activate-time yyyy-mm-dd-hh:mm:ss
y=year; m=month; d=day h=hour (24-hour clock) m=minute; s=second
deactivate-time
Set the time when selected local-policy becomes invalid
deactivate-time yyyy-mm-dd hh:mm:ss or
activate-time yyyy-mm-dd-hh:mm:ss
y=year; m=month; d=day h=hour (24-hour clock) m=minute; s=second
state
Enable or disable the local-policy element
  • Default: enabled
  • Values: enabled | disabled
parallel-forking
Enable or disable parallel forking on this local-policy.
  • Default: disabled
  • Values: enabled | disabled
policy-priority
Set the policy priority parameter for this local policy. It is used to facilitate emergency sessions from unregistered endpoints. This value is compared against a policy priority parameter in a SIP interface configuration element.
  • Default: none
  • Values: none | normal | non-urgent | urgent | emergency
next-hop

Note:

This attribute is only present when the Routing entitlement is disabled.
Enter the next signaling host IP address, SAG, hostname, or ENUM config; ENUM is also an accepted value. You can use the following as next-hops:
  • IPv4 address or IPv6 address of a specific endpoint
  • Hostname or IPv4 address or IPv6 address of a configured session agent
  • Group name of a configured session agent group
The group name of a configured session agent group must be prefixed with SAG: For example:
  • policy-attribute: next-hop SAG:appserver
  • policy-attribute: next-hop lrt:routetable
  • policy-attribute: next-hop enum:lerg
realm

Note:

This attribute is only present when the Routing entitlement is disabled.
Enter the egress realm, or the realm of the next hop. If traffic is routed using the local policy, and the selected route entry identifies an egress realm, then this realm field value will take precedence. This value must be a valid entry in a realm configuration.
action

Note:

This attribute is only present when the Routing entitlement is disabled.
Set this parameter to redirect if you want to send a redirect next-hop message back to the calling party with the information in the Contact. The calling party then needs to send an INVITE using that information.
  • Default: none
  • Values:
    • none—No specific action requested
    • replace-uri—To replace the Request-URI with the next hop
    • redirect—To send a redirect response with this next hop as contact
terminate-recursion

Note:

This attribute is only present when the Routing entitlement is disabled.
Terminate route recursion with this next hop
  • Default: disabled
  • Values: enabled | disabled
app-protocol

Note:

This attribute is only present when the Routing entitlement is disabled.
Select the signaling protocol used when sending messages to the configured next-hop. When the SBC receives an ingress signaling message and uses local policy to determine the message’s destination, it will interwork the signaling between protocols (H.323<—>SIP or SIP<—>H.323) if the signaling type does not match the value configured in the app-protocol field.
  • Default: ""
  • Values: "" | SIP | H323 | MGCP | H248 | BGF | BFD | SCF | RTSP | DD | DIAMETER | IKE | NONE
methods

Note:

This attribute is only present when the Routing entitlement is disabled.
Enter the SIP methods you want to use for matching this set of policy attributes. Use a double-quoted string with space-separated items.
  • Values: INVITE | REGISTER | PRACK | OPTIONS | INFO | SUBSCRIBE | NOTIFY | REFER | UPDATE | MESSAGE | PUBLISH
lookup

Note:

This attribute is only present when the Routing entitlement is disabled.
Enable multistage local policy routing, or leave the parameter at the default single for single stage local policy routing.
  • Default: single
  • Values: single | multi
next-key

Note:

This attribute is only present when the Routing entitlement is disabled.
Select the key to use for the next stage of local policy look-up.
  • Values: $TO | $FROM | $PAI

Path

local-policy is an element under the session-router path. The full path from the topmost ACLI prompt is: configure terminal , and then session-router , and then local-policy.

Note:

This is a multiple instance configuration element.