Version 7.2 665 Mediant 800B Gateway & E-SBC
User's Manual 29. SBC Overview
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 'Configuring IP-to-IP Outbound Manipulations' on page 745.
9. 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.
10. The call is sent to the configured destination.
29.4 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.
29.4.1 Initial Registration Request Processing
A summary of the device's handling of registration requests (REGISTER messages) is as
follows:
The URL in the To header of the REGISTER message constitutes the primary
Address of Record (AOR) for registration (according to standard). 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.
If registration succeeds (replied with 200 OK by the destination server), the device
adds a record to its' registration database, which identifies the specific contact of the
specific user (AOR). The device uses this record to route subsequent SIP requests to
the specific user (in normal or survivability modes).
The records in the device's registration database include the Contact header. The
device adds every REGISTER request to the registration database before
manipulation, allowing correct user identification in the Classification process for the
next received request.
You can configure Call Admission Control (CAC) rules for incoming and outgoing
REGISTER messages. For example, you can limit REGISTER requests from a
specific IP Group or SRD. Note that this applies only to concurrent REGISTER dialogs
and not concurrent registrations in the device's registration database.
The device provides a dynamic registration database that it updates according to
registration requests traversing it. Each database entry for a user represents a binding
between an AOR (obtained from the SIP To header), optional additional AORs, and one or
To Next Page
Loading...
