AudioControl VERSION 6.2 SBC Registration Timers, IP Alert Timeout to SBC Outgoing INVITE Message

SIP Release Notes 1. What's New in Release 6.2

4.SBC Registration Timers:

	Product
Mediant 800 MSBG		Mediant 1000 MSBG
Mediant 3000/TP-6310		Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410		Mediant 3000 HA/TP-8410
	Management Protocol

Web

INI

SNMP

EMS

CLI

This feature now enables the device to retain the original value of the SIP Expires header received from the user or proxy. This feature also applies when the SBC is in “survivability” state (i.e., REGISTER requests cannot be forwarded to the proxy and is terminated by the SBC).

This feature is configured using the following new parameters:

•SBCUserRegistrationTime: This parameter replaces the now obsolete SBCRegistrationTime parameter. This parameter defines the duration of the periodic registrations between the user and the SBC. When set to 0, the SBC does not change the Expires value received in the user’s REGISTER request. If no Expires header is received in the REGISTER and SBCUserRegistrationTime is set to 0, the Expires value is set to 180 seconds (by default).

•SBCProxyRegistrationTime: This parameter replaces the RegistrationTime parameter. This parameter defines the duration for which the user is registered in the proxy database. When set to 0, the SBC sends the Expires value as received from the user to the proxy. (Note: The RegistrationTime parameter is still applicable to non-SBC applications.)

•SBCSurvivabilityRegistrationTime: This parameter defines the duration of the periodic registrations between the user and SBC when the SBC is in survivability state. When set to 0, the SBC uses the value of the SBCUserRegistrationTime parameter for the SBC response.

5.IP Alert Timeout to SBC Outgoing INVITE Message:

	Product
Mediant 800 MSBG		Mediant 1000 MSBG
Mediant 3000/TP-6310		Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410		Mediant 3000 HA/TP-8410
	Management Protocol

Web

INI

SNMP

EMS

CLI

This feature allows the configuration of a timeout (in seconds) for SBC outgoing (outbound IP routing) SIP INVITE messages. If the called IP party does not answer the call within this user-defined interval, the device disconnects the session. The device starts the timeout count upon receipt of a SIP 180 Ringing response from the called party. If no other SIP response (for example, 200 OK) is received thereafter within this timeout, the call is released. This feature is configured using the new parameter, SBCAlertTimeout.

Version 6.2 55 December 2010