Limiting Sbc Call Duration; Sbc Authentication; Sip Authentication Server Functionality - AudioCodes Mediant 3000 User Manual

Fax configuration is done in the Coder Group Settings table and IP Profile table. The Coder
Group Settings table defines the supported coders, which is assigned to the IP Profile
associated with the SIP entity. The IP Profile table also defines the negotiation method
used between the incoming and outgoing fax legs, using the following fax-related
parameters:

SBCFaxBehavior: defines the offer negotiation method - pass fax transparently,
negotiate fax according to fax settings in IP Profile, or enforce remote UA to first
establish a voice channel before fax negotiation.

SBCFaxCodersGroupID: defines the supported fax coders (from the Coders Group
Settings table).

SBCFaxOfferMode: determines the fax coders sent in the outgoing SDP offer.

SBCFaxAnswerMode: determines the fax coders sent in the outgoing SDP answer.

IPProfile_SBCRemoteRenegotiateOnFaxDetection: You can also configure the device
to detect for faxes (CNG tone) immediately after the establishment of a voice channel
(i.e., after 200 OK) and within a user-defined interval. If detected, it can then handle
the subsequent fax renegotiation by sending re-INVITE messages to both SIP entities
(originating and terminating faxes). For more information, see the parameter in
''Configuring IP Profiles'' on page 391.
Note:
independent of the fax-related coder configuration, with the exception of the G.711
coder. If the G.711 coder is restricted by the Allowed Coders Group table, it is not
used for fax processing even if it is listed in the Coders Group Settings table for faxes.
However, support for G.711 coders for voice is not dependent upon which fax coders
are listed in the Coders Group Settings table.
28.7

Limiting SBC Call Duration

You can define a maximum allowed duration (in minutes) for SBC calls. If an established
call reaches this user-defined limit, the device terminates the call. This feature ensures
calls are properly terminated, allowing available resources for new calls. This feature is
configured using the MaxCallDuration parameter.
28.8

SBC Authentication

The device can authenticate SIP servers and SBC users (clients). The different
authentication methods are described in the subsequent subsections.

28.8.1 SIP Authentication Server Functionality

The device can function as an Authentication server for authenticating received SIP
message requests, based on HTTP authentication Digest with MD5. Alternatively, such
requests can be authenticated by an external, third-party server.
When functioning as an Authentication server, the device can authenticate the following
SIP entities:

SIP servers: This is applicable to Server-type IP Groups. This provides protection
from rogue SIP servers, preventing unauthorized usage of device resources and
functionality. To authenticate remote servers, the device challenges the server with a
user-defined username and password that is shared with the remote server. When the
device receives an INVITE request from the remote server, it challenges the server by
replying with a SIP 401 Unauthorized response containing the WWW-Authenticate
User's Manual
The voice-related coder configuration (Allowed and Extension coders) is
568
Mediant 3000
Document #: LTRT-89730