AudioCodes Mediant 500 E-SBC, User Manual

Page: 284 / 920

User's Manual 284 Document #: LTRT-10437
Mediant 500 E-SBC
Parameter Description
Application Type
CLI: application-type
[Account_ApplicationType]
Defines the application type:

[0] GW/IP2IP = (Default) Gateway and IP-to-IP application.

[2] SBC = SBC application.
18.2.1 Regular Registration Mode
When you configure the registration mode in the Account table to Regular , the device
sends REGISTER requests to the Serving IP Group. The host name (in the SIP From/To
headers) and contact user (user in From/To and Contact headers) are taken from the
configured Account table upon successful registration. See the example below:
REGISTER sip:xyz SIP/2.0
Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac1397582418
From: <sip:ContactUser@HostName>;tag=1c1397576231
To: <sip: ContactUser@HostName >
Call-ID: 1397568957261200022256@10.33.37.78
CSeq: 1 REGISTER
Contact: <sip:ContactUser@10.33.37.78>;expires=3600
Expires: 3600
User-Agent: Sip-Gateway/v.6.00A.008.002
Content-Length: 0
18.2.2 Single Registration for Multiple Phone Numbers using GIN
When you configure the registration mode in the Account table to GIN , the Global
Identifiable Number (GIN) registration method is used, according to RFC 6140. The device
performs GIN-based registration of users to a SIP registrar on behalf of a SIP PBX. In
effect, the PBX registers with the service provider, just as a directly hosted SIP endpoint
would register. However, because a PBX has multiple user agents, it needs to register a
contact address on behalf of each of these. Rather than performing a separate registration
procedure for each user agents, GIN registration mode does multiple registrations using a
single REGISTER transaction.
According to this mechanism, the PBX delivers to the service provider in the Contact
header field of a REGISTER request a template from which the service provider can
construct contact URIs for each of the AORs assigned to the PBX and thus, can register
these contact URIs within its location service. These registered contact URIs can then be
used to deliver to the PBX inbound requests targeted at the AORs concerned. The
mechanism can be used with AORs comprising SIP URIs based on global E.164 numbers
and the service provider's domain name or sub-domain name.
The SIP REGISTER request sent by the device for GIN registration with a SIP server
provider contains the Require and Proxy-Require headers. These headers contain the
token 'gin'. The Supported header contains the token 'path' and the URI in the Contact
header contains the parameter 'bnc' without a user part:
Contact: <sip:198.51.100.3;bnc>;