User Registration; Initial Registration Request Processing - AudioCodes E-SBC User Manual

CHAPTER 30 SBC Overview
10. Applying Call Setup Rules for Various Functions: If configured, the device can run Call
Setup Rules to apply various functions to the call. The Call Setup Rule is configured in the Call
Setup Rules table (see
IP Routing table.
11. Applying Inbound SIP Message Manipulation: Depending on configuration, the device can
apply a SIP message manipulation rule (assigned to the IP Group) on the incoming dialog. For
more information, see Stage 3.
12. Applying Outbound Manipulation: Depending on configuration, the device can apply an
Outbound Manipulation rule to the outbound dialog. This manipulates the user part of the
Request-URI for source (e.g., in the SIP From header) or destination (e.g., in the SIP To
header) or calling name in the outbound SIP dialog. The manipulation rule is associated with
the dialog, by configuring the rule with incoming matching characteristics such as source IP
Group and destination host name. The manipulation rules are also assigned a Routing Policy,
which in turn, is assigned to IP-to-IP routing rules. As most deployments require only one
Routing Policy, the default Routing Policy is automatically assigned to manipulation rules and
routing rules. For more information, see
13. Applying Outbound SIP Message Manipulation: Depending on configuration, the device
can apply a SIP message manipulation rule (assigned to the IP Group) on the outbound dialog.
For more information, see Stage 3.
14. The call is sent to the configured destination.

User Registration

The device provides a registration database for registering users. Only users belonging to a User-
type IP Group can register with the device. User-type IP Groups represent a group of SIP user
agents that share the following characteristics:
■ Perform registrations and share the same serving proxy\registrar
■ Same SIP and media behavior
■ Same IP Profile
■ Same SIP handling configuration
■ Same Call Admission Control (CAC)
Typically, the device is configured as the user's outbound proxy, routing requests (using the IP-to-
IP Routing table) from the user's User- type IP Group to the serving proxy, and vice versa.
Survivability can be achieved using the alternative routing feature.
The device forwards registration requests (REGISTER messages) from a Server-type IP Group,
but does not save the registration binding in its' registration database.

Initial Registration Request Processing

A summary of the device's handling of registration requests (REGISTER messages) is as follows:
■ The URL in the SIP To header of the REGISTER message constitutes the primary Address of
Record (AOR) for registration (according to SIP standards). If the To header's URL includes
the "user=phone" parameter, then only the user part of the URL constitutes the AOR. If the To
header's URL does not include the "user=phone" parameter, then both the user part and host
part of the URL constitutes the AOR.
■ The device can save other AORs in its registration database as well. When the device
searches for a user in its' registration database, any of the user's AORs can result in a match.
■ The device's Classification process for initial REGISTER messages is slightly different than
for other SIP messages. Unlike other requests, initial REGISTER requests can't be classified
according to the registration database.
Configuring Call Setup Rules
Configuring IP-to-IP Outbound
- 725 -
Mediant 1000 Gateway & E-SBC | User's Manual
on page 482) and is assigned to the IP-to-
Manipulations.