Administrator's Guide

Chapter 11. SIP Traffic
Static Registrations
You can specify that calls to a certain user address should also be redirected to another
address, or that calls to a non-person user name (like support@company.com) should be
redirected to one or more other addresses.
Static registrations only affect SIP requests addressed to Local SIP Domains.
Even if a call should be forwarded, the Telecommuting Module will try to put it through to
the original addressee.
Note that this table should not be used for your own XF or XF/Register accounts. Use the
User Routing table to forward calls for these accounts instead.
Requests To User
Enter the user address. Calls to this user are sent to the user, but also forwarded to users
listed under Also forward to. The address should be entered on the form user@domain.
Also Forward To
User
Enter the address to which the calls should be forwarded. The address should be entered on
the form user@domain. You can forward to more than one address by creating several rows
for the same Request to user name.
You can add parameters to the destination address to limit what is sent to that user. Parame-
ters are added after the address, separated by semicolon. The following parameters exist:
methods=: Enumerate the SIP methods that should be sent on to this user. If this parameter
is not used, all requests are forwarded regardless of which method is used.
audio: Audio calls are forwarded to the user. Audio calls are defined as requests with an
SDP where a "m=audio" line is present.
video: Video calls are forwarded to the user. Video calls are defined as requests with an SDP
where a "m=video" line is present.
+sip.message: Requests are forwarded to the user if the body contains a line with
"m=message" in it.
Example: If audio calls should be forwarded to adam@sip.ingate.com,
enter adam@sip.ingate.com;audio. If only the NOTIFY and SUB-
SCRIBE methods should be forwarded to emmie@sip.ingate.com, enter
emmie@sip.ingate.com;methods=NOTIFY,SUBSCRIBE.
207