Version 7.2 377 Mediant 500L Gateway & E-SBC
User's Manual 17. Control Network
Parameter Description
Authenticates SIP servers. This is applicable only to Server-type IP
Groups.
Authentication Method
List
authentication-method-
list
[IPGroup_MethodList]
Defines SIP methods received from the IP Group that must be challenged
by the device when the device acts as an Authentication server. If no
methods are configured, the device doesn't challenge any methods.
By default, no value is defined. To define multiple SIP methods, use the
backslash ( \ ) to separate each method (e.g., INVITE\REGISTER).
Note: The parameter is applicable only if the 'Authentication Mode'
parameter is set to SBC as Server [2].
Username
username
[IPGroup_Username]
Defines the shared username for authenticating the IP Group, when the
device acts as an Authentication server.
The valid value is a string of up to 51 characters. By default, no username
is defined.
Note:
The parameter is applicable only to Server-type IP Groups and when
the 'Authentication Mode' parameter is set to SBC as Server (i.e.,
authentication of servers).
To specify the SIP request types (e.g., INVITE) that must be challenged
by the device, use the 'Authentication Method List' parameter.
Password
password
IPGroup_Password]
Defines the shared password for authenticating the IP Group, when the
device acts as an Authentication server.
The valid value is a string of up to 51 characters. By default, no password
is defined.
Note:
The parameter is applicable only to Server-type IP Groups and when
the 'Authentication Mode' parameter is set to SBC as Server (i.e.,
authentication of servers).
To specify the SIP request types (e.g., INVITE) that must be challenged
by the device, use the 'Authentication Method List' parameter.
Gateway
SIP Re-Routing Mode
re-routing-mode
[IPGroup_SIPReRoutin
gMode]
Defines the routing mode after a call redirection (i.e., a 3xx SIP response is
received) or transfer (i.e., a SIP REFER request is received).
[-1] = Not Configured (Default)
[0] Standard = INVITE messages that are generated as a result of
Transfer or Redirect are sent directly to the URI, according to the Refer-
To header in the REFER message or Contact header in the 3xx
response.
[1] Proxy = Sends a new INVITE to the Proxy. This is applicable only if a
Proxy server is used and the parameter AlwaysSendtoProxy is set to 0.
[2] Routing Table = Uses the Routing table to locate the destination and
then sends a new INVITE to this destination.
Note:
When the parameter is set to [1] and the INVITE sent to the Proxy fails,
the device re-routes the call according to the Standard mode [0].
When the parameter is set to [2] and the INVITE fails, the device re-
routes the call according to the Standard mode [0]. If DNS resolution
fails, the device attempts to route the call to the Proxy. If routing to the
Proxy also fails, the Redirect / Transfer request is rejected.