Using New Transaction Policies to Manipulate SIP Headers or to Reject SIP Messages
You can use new transaction policies to modify information in SIP headers or to reject SIP messages based on information in the SIP header.
To configure a new transaction policy to manipulate SIP headers or to reject SIP messages:
- Access the configuration of a new transaction
policy.[edit services border-signaling-gateway gateway bsg-1 sip]user@host# edit new-transaction-policy tr_accept
- Configure a term for the policy.[edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tr_accept]user@host# edit term accept_all
- Access the message manipulation configuration. [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tr_accept term accept_all]user@host# edit then message-manipulation
- Add forward manipulation rules to the
policy. Forward manipulation rules are applied to messages going from
the user agent client (UAC), or the caller, to the user agent server
(UAS), or the call recipient. It is applied to the original transaction
request. [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tr_accept term accept_all then message-manipulation]user@host# set forward-manipulation hm-ruleuser@host# set forward-manipulation mod-to
- Add reverse manipulation rules to the
policy. Reverse manipulation rules are applied to messages going from
the UAS (the call recipient) to the UAC (the caller).[edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tr_accept term accept_all then message-manipulation]user@host# set reverse-manipulation no-subscribe
