Technical Documentation



new-transaction-policy policy-name {term term-name {from {contact {registration-state [ registered | not-registered ];regular-expression [ regular-expression ];uri-hiding [ hidden-uri | not-hidden-uri ];}method {method-invite;method-message;method-options;method-publish;method-refer;method-register;method-subscribe;}request-uri {registration-state [ registered | not-registered ];regular-expression [ regular-expression ];uri-hiding [ hidden-uri | not-hidden-uri ];}source-address [ ip-addresses ];}then {(accept | reject);admission-control admission-control-profile;message-manipulation {forward-manipulation {manipulation-rule-name;}reverse-manipulation {manipulation-rule-name;}}on-3xx-response {recursion-limit number;}}route {egress-service-point service-point-name;next-hop (request-uri | address ipv4-address <port port-number> <transport-protocol (udp | tcp)>);server-cluster cluster-name;}signaling-realm signaling-realm;trace;}}}

Hierarchy Level

[edit services border-signaling-gateway gateway gateway-name sip]

Release Information

Statement introduced in JUNOS Release 9.4.

message-manipulation option introduced in JUNOS Release 9.5.


Specify new transaction policies for out-of-dialog transactions including dialog-opening transactions. Transaction policies are useful when the policy does not need to differentiate between events. For example, you can use new transaction policies to route all transactions according to the same rules.

A new transaction event is raised when a new SIP request, 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.


policy-name—Identifier for the new transaction policy.

The remaining statements are explained separately.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Published: 2010-04-28