EasyManuals Logo

AudioCodes Mediant 8000 User Manual

AudioCodes Mediant 8000
924 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #765 background imageLoading...
Page #765 background image
Version 6.6 765 October 2014
Installation & Operation Manual 43. Session Border Controller (SBC) Application
43.14 User Registration
To allow registrations to traverse the SBC application, one of the IP Groups must be
configured with USER type. USER IP Groups represent a group of user agents that
share the following characteristics:
Perform registrations and share the same serving proxy\registrar
Identical SIP and media behavior
Reside on the same Layer-3 network and are associated with the same SRD
Typically, the Board functions as the user agent's outbound proxy and is configured
(using the SBC IP to IP 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.
43.14.1 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 the 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 only be an IP Group (i.e., no specific
address\Request URI).
If the IP Group is of type SERVER, the REGISTER is routed to the IP
Group's Proxy Set.
If the IP Group is of type USER, then the device replies with a 200 OK
response (used for Survivability) and the REGISTER is not forwarded.
4. The Contact of the outgoing REGISTER is populated with a unique Contact
generated by the device and associated with this specific registration.
Note: Alternative route and manipulations are not implemented for registrations.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes Mediant 8000 and is the answer not in the manual?

AudioCodes Mediant 8000 Specifications

General IconGeneral
BrandAudioCodes
ModelMediant 8000
CategoryGateway
LanguageEnglish

Related product manuals