Sip Definitions; Configuring Sip Parameters; Configuring Registration Accounts - AudioCodes Mediant 1000B User Manual

User's Manual
18

SIP Definitions

This section describes configuration of various SIP-related functionalities.
18.1

Configuring SIP Parameters

Many of the stand-alone SIP parameters associated with various features can be
configured in the following pages:

SIP General Parameters page: Provides SIP parameters for configuring general SIP
features. To access this page, use the following path: Configuration tab > VoIP menu
> SIP Definitions > General Parameters.

SIP Advanced Parameters page: Provides SIP parameters for configuring advanced
SIP features. To access this page, use the following path: Configuration tab > VoIP
menu > SIP Definitions > Advanced Parameters.
For a description of these parameters, refer to the section corresponding to the feature or
see 'Configuration Parameters Reference' on page 881.
18.2

Configuring Registration Accounts

The Account table lets you configure up to 102 Accounts. An Account defines registration
information for registering and authenticating (digest) Trunk Groups (e.g., PBX) or IP
Groups (e.g., IP PBX) with a "serving" IP Group (e.g., ITSP).
The device initiates registration with a "serving" IP Group on behalf of the "served" Trunk
Group or IP Group. Therefore, Accounts are typically required when the "served" Trunk
Group or IP Group is unable to register or authenticate itself for whatever reason.
Registration information includes username, password, host name (AOR), and contact user
name (AOR). The device includes this information in the REGISTER message sent to the
serving IP Group. Up to 10 Accounts can be configured per "served" Trunk Group or IP
Group. A Trunk Group or IP Group can register to more than one IP Group (e.g., multiple
ITSPs). This is done by configuring multiple entries in the Account table for the same
served Trunk Group or IP Group, but with different serving IP Groups, username/password,
host name, and contact user values.
Authentication is typically required for INVITE messages sent to the "serving" IP Group. If
the device receives a SIP 401 (Unauthorized) in response to a sent INVITE, the device
checks for a matching "serving" and "served" entry in the Account table. If a matching row
exists, the device authenticates the INVITE by providing the corresponding MD5
authentication username and password to the "serving" IP Group.
Note:
username and password is taken from:
•
FXS interfaces: Authentication table (see Configuring Authentication on page 558
per Port)
•
'UserName' and 'Password' parameters on the Proxy & Registration page
The following procedure describes how to configure Accounts through the Web interface.
You can also configure it through ini file (Account) or CLI (configure voip > sip-definition
account).
Version 7.0
If no match is found in the Account table for incoming or outgoing calls, the
357 Mediant 1000B Gateway and E- SBC
18. SIP Definitions