Fortinet FortiGate Series Administration Manual page 516

Hide thumbs Also See for FortiGate Series:
Table of Contents

Advertisement

Configuring SIP
Support for RFC 2543-compliant branch commands
516
By default, open-register-pinhole is enabled and the FortiGate unit opens pinholes
for register requests. You can disable open-register-pinhole so that the FortiGate
unit does not open pinholes for register requests.
By default, open-contact-pinhole is also enabled and the FortiGate unit opens
pinholes for non-register requests. You can disable open-contact-pinhole so that the
FortiGate unit does not open pinholes for non-register requests.
Usually you would want to open these pinholes. Keeping the closed may prevent SIP from
functioning properly through the FortiGate unit.They can be disabled, however, for
interconnect scenarios (where all SIP traffic is between proxies and traveling over a single
session). In some cases these settings can also be disabled in access scenarios if it is
known that all users will be registering regularly so that their contact information can be
learned from the register request.
You might want to prevent pinholes from being opened to avoid creating a pinhole for
every register or non-register request. Each pinhole uses additional system memory,
which can affect system performance if there are hundreds or thousands of users, and
requires refreshing which can take a relatively long amount of time if there are thousands
of active calls.
To stop the FortiGate unit from opening register and non-register pinholes:
config application list
edit <list_name>
config entries
edit 1
set category voip
set application SIP
set open-register-pinhole disable
set open-contact-pinhole disable
end
end
FortiGate units support SIP
RFC 2543. However, some SIP implementations may use RFC 2543-compliant SIP calls.
The rfc2543-branch CLI keyword of the config application list command has
been added to support RFC 2543-complaint SIP calls involving branch commands that
are missing or that are valid for RFC 2543 but invalid for RFC 3261.
config application list
edit <list_name>
config entries
edit 1
set category voip
set application SIP
set rfc2543-branch enable
end
end
RFC
3261. RFC 3261 is the most recent SIP RFC, it obsoletes
FortiGate Version 4.0 MR1 Administration Guide
SIP support
01-410-89802-20090903
http://docs.fortinet.com/
Feedback

Advertisement

Table of Contents
loading

Table of Contents