User Registration And Internal Database - AudioCodes Mediant 800 MSBG User Manual

Notes:
8.4.4

User Registration and Internal Database

To allow registrations to traverse the SBC, the device must be configured with at least one
IP Group of type USER. USER IP Groups represent a group of user agents that share the
following characteristics:
Perform registrations and share the same serving proxy\registrar
Possess identical SIP and media behavior
Reside on the same Layer-3 network and are associated with the same SRD
Typically, the device is configured as the user agent's outbound proxy and the device is
configured (using the IP2IP Routing table) to route requests received from this IP Group to
the serving proxy and vice versa. Survivability can be achieved using the alternative
routing feature.
8.4.4.1 Initial Registration Request Processing
Registration requests have different processing policies than other SIP methods:
1. Determining source and destination URL's:
•
The source URL is obtained from the To header
•
The destination URL is obtained from the Request URI
2. Classification: The REGISTER classification process is the same as the general
classification process (described in previous sections). The source IP Group must be
of type USER. If classification fails or the source IP Group is not of type USER, the
registration is rejected.
3. Routing: The REGISTER routing is performed using the IP2IP Routing table:
•
The destination type can be an IP Group, specific IP address, Request-URI, or
ENUM query (can also use DNS queries).
•
If the destination IP Group is of type USER, then the registration is not be
forwarded. Instead, the device accepts (replies with 200 OK response) or rejects
(Reply with 4xx) the request according to the user group policy.
SIP User's Manual
•
Unknown SIP parts can only be added or removed.
•
SIP manipulations do not allow you to remove or add mandatory SIP
headers. Only the modify option is available for mandatory headers and
is performed only on requests that initiate new dialogs. Mandatory SIP
headers include To, From, Via, CSeq, Call-Id, and Max-Forwards.
Mandatory SDP headers include v, o, s, t ,c, and m.
•
When multiple manipulations rules apply to the same header, the second
rule applies to the result string of the first rule.
•
Manipulating any value in the message body causes a change to the
Content-length header automatically.
•
SDP body manipulations are currently not supported.
490
Mediant 800 MSBG
Document #: LTRT-12804