Table of Contents
Advertisement
SIP User's Manual
5.
The Contact of the outgoing REGISTER is populated with a unique Contact generated
by the device and associated with this specific registration.
Note:
9.2.4.2
Internal Database
The device manages a dynamic database that is updated according to registration requests
that traverse the SBC. Each database entry represents a binding between an AOR and one
or more contacts. Database bindings are added upon successful registration responses.
For specific registrations, the AOR is obtained from the SIP To header and the contact is
taken from the SIP Contact header.
Database bindings are deleted in the following cases:
Successful de-registration responses (REGISTER with Expires header that equals
zero)
Registration failure responses
Timeout of the Expires header value (in scenarios where the user agent did not send a
refresh registration request)
The database has the following limitations:
Maximum registered users is 200
Maximum of five contacts per AOR
The same contact cannot belong to more than one AOR
Contacts with identical URIs and different ports and transport types are not supported
(same key is created)
Multiple contacts in a single REGISTER is not supported
One database is shared between all USER-type IP Groups
9.2.4.3
Routing using Internal Database
Typically, routing using the database is applicable to all method types other than
registrations. To route to a registered user (using the internal dynamic database), the
following steps must be taken:
1.
An IP2IP Routing rule with the desired input parameters (matching characteristics) and
the destination type as IP Group (operation rule).
2.
The destination IP Group must be of type USER.
3.
To find a match for these specific rules, the device attempts to locate a match between
the incoming request URI and (according to the description order):
a.
Unique contact - the Contact generated by the SBC and sent in the initial
registration request to the serving proxy
b.
Registered AOR - the AOR of the incoming REGISTER request
c.
Registered contact - the Contact of the incoming REGISTER request
Version 5.8
Alternative routing and manipulations are not implemented for registrations.
467
9. IP Telephony Capabilities
October 2009
Advertisement
Table of Contents
Troubleshooting
