Version 7.0 1031 Mediant 3000
User's Manual 58. Configuration Parameters Reference
Parameter Description
ï‚§ For the parameter to take effect, a device reset is required.
ï‚§ The maximum number of SUBSCRIBE sessions can be increased by
reducing the maximum number of SBC channels in the Software
License Key. For every reduced SBC session, the device gains two
SUBSCRIBE sessions.
[SBCInDialogSubscribeRo
uteMode]
Enables the device to route in-dialog, refresh SIP SUBSCRIBE requests
to the "working" (has connectivity) proxy.
 [0] = (Default) Disable – the device sends in-dialog, refresh
SUBSCRIBES according to the address in the Contact header of the
200 OK response received from the proxy to which the initial
SUBSCRIBE was sent (as per the SIP standard).
 [1] = Enable – the device routes in-dialog, refresh SUBSCRIBES to
the "working" proxy (regardless of the Contact header). The "working"
proxy (address) is determined by the device's keep-alive mechanism
for the Proxy Set that was used to route the initial SUBSCRIBE.
Note: For this feature to be functional, ensure the following:
ï‚§ Keep-alive mechanism is enabled for the Proxy Set ('Proxy Keep-
Alive' parameter is set to any value other than Disable).
ï‚§ Load-balancing between proxies is disabled ('Proxy Load Balancing
Method' parameter is set to Disable).
[SBCMaxForwardsLimit]
Defines the Max-Forwards SIP header value. The Max-Forwards header
is used to limit the number of servers (such as proxies) that can forward
the SIP request. The Max-Forwards value indicates the remaining
number of times this request message is allowed to be forwarded. This
count is decremented by each server that forwards the request.
The parameter affects the Max-Forwards header in the received
message as follows:
ï‚§
If the received header’s original value is 0, the message is not passed
on and is rejected.
 If the received header’s original value is less than the parameter's
value, the header’s value is decremented before being sent on.
 If the received header’s original value is greater than the parameter's
value, the header’s value is replaced by the user-defined parameter’s
value.
The valid value range is 1-70. The default is 10.
SBC Session-Expires
[SBCSessionExpires]
Defines the SBC session refresh timer (in seconds) in the Session-
Expires header of outgoing INVITE messages.
The valid value range is 90 (according to RFC 4028) to 86400. The
default is 180.
Minimum Session-Expires
[SBCMinSE]
Defines the minimum amount of time (in seconds) between session
refresh requests in a dialog before the session is considered timed out.
This value is conveyed in the SIP Min-SE header.
The valid range is 0 (default) to 1,000,000, where 0 means that the
device does not limit Session-Expires.
[SBCSessionRefreshingP
olicy]
Defines the SIP user agent responsible for periodically sending refresh
requests for established sessions (active calls). The session refresh
allows SIP UAs or proxies to determine the status of the SIP session.
When a session expires, the session is considered terminated by the