CHAPTER 18 Core Entities
Mediant 4000 SBC | User's Manual
Parameter
Description
'SIP Connect'
sip-connect
[IPGroup_SIPConnect]
Defines the IP Group as representing multiple registering
servers, each of which may use a single registration, yet
represent multiple users. In addition, it defines how the
device saves registration information for REGISTER
messages received from the IP Group, in its registration
database. For requests routed to the IP Group's users,
the device replaces the Request-URI header with the
incoming To header (which contains the remote phone
number).
■
[0]
No
= (Default) Disables the SIP Connect feature.
No extra key based on source IP address is added to
the registration database and registration is done by
Contact and Address of Record (AoR).
■
[1]
Yes
= Enables the SIP Connect feature. For
initial registrations that are received from the IP
Group, the device attempts to add two
keys
representing the user to its registration database:
✔
Key 1: The first key contains the incoming
REGISTER message's source IP address, port
(only if UDP), and SIP Interface ID (e.g.,
"10.33.3.3:5010#1").
✔
Key 2: The second key contains the incoming
REGISTER message's URI (user@host) of the
Contact header, source IP address, port (only if
UDP), and SIP Interface ID (e.g., "user-
@host.com#10.33.3.3:5010#1").
If the device receives an initial registration request
that has the same IP address and Contact URI, or IP
address only, as an existing key (i.e., an existing
registration), the device rejects the request.
The device classifies incoming non-REGISTER SIP
dialog requests (e.g., INVITEs) from this IP Group,
by first using the regular user search method in the
registration database by Contact-AoR pair matching.
If unsuccessful, the device searches the registration
database for a matching Key 2 (i.e., Contact URI,
source IP address, and port if the transport type is
UDP). If no matching Key 2 exists, the device then
searches for a matching Key 1 (i.e., source IP
address only and port if the transport type is UDP). If
no key is found at all, the device continues with the
next Classification stage (e.g., by Proxy Set).
Note:
■
The parameter is applicable only to User-type IP
Groups.
■
The parameter is applicable only to the SBC
application.
'SBC PSAP Mode'
sbc-psap-mode
Enables E9-1-1 emergency call routing in a Microsoft
Skype for Business environment.
- 357 -
Содержание Mediant 4000 SBC
Страница 1: ...User s Manual AudioCodes Series of Session Border Controllers SBC Mediant 4000 SBC Version 7 2...
Страница 40: ...Part I Getting Started with Initial Connectivity...
Страница 48: ...Part II Management Tools...
Страница 113: ...Part III General System Settings...
Страница 118: ...Part IV General VoIP Configuration...
Страница 525: ...Part V Session Border Controller Application...
Страница 654: ...Part VI Cloud Resilience Package...
Страница 663: ...Part VII High Availability System...
Страница 685: ...Part VIII Maintenance...
Страница 759: ...Part IX Status Performance Monitoring and Reporting...
Страница 844: ...Part X Diagnostics...
Страница 888: ...Part XI Appendix...
Страница 1036: ...This page is intentionally left blank CHAPTER 62 Technical Specifications Mediant 4000 SBC User s Manual 1003...