Configuring a New Transaction Policy
New transaction policies control how requests related to new transactions are handled. A new transaction event is raised when a new SIP request message, such as an INVITE, either opens a new dialog or is not related to any dialog. If the event does not match a new transaction policy, the BSG rejects the SIP request and returns a 403 (Forbidden) message.
The actions that you can take on requests that match conditions in new transaction policies include accepting, rejecting, or tracing traffic; routing of SIP requests; or applying CAC (call admission control). Using new transaction policies to route SIP requests or to apply CAC is described separately.
To configure a new transaction policy:
- Create a new transaction policy, and assign it
a name.[edit services border-signaling-gateway gateway bsg-1 sip]user@host# edit new-transaction-policy peer-to-core
- Configure a term for the policy.[edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy peer-to-core]user@host# edit term block_presence
- Configure match conditions for the term.
For example, to match incoming traffic based on the type of SIP method:
If you have multiple values for the same field in a from clause, there is an OR function between the values. In this case, the term must match one of the method values defined.
- Configure actions to be taken on messages that
match the term conditions. For example:[edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy peer-to-core term block_presence]user@host# set then reject
