Filter
Top Products
Version 6.2 61 December 2010
SIP Release Notes 1. What's New in Release 6.2
The “GATEWAY” type is necessary for requests representing multiple users, as the
existing options above are not suitable:
• The IP Group cannot be defined as a SERVER since its destination address is
unknown during configuration.
• The IP Group cannot be defined as a USER since the SIP Contact header of the
incoming REGISTER does not represent a specific user. The Request-URI user
part can change and therefore, the device is unable to identify an already
registered user and therefore, adds an additional record to the database.
The IP address of the “GATEWAY” IP Group is obtained dynamically from the host
part of the Contact header in the REGISTER request received from the IP Group.
Therefore, routing to this IP Group is possible only once a REGISTER request is
received. If a REGISTER refresh request arrives, the device updates the new location
(i.e., IP address) of the IP Group. If the REGISTER fails, no update is performed. If an
UN-REGISTER request arrives, the IP address associated with the IP Group is deleted
and therefore, no routing to the IP Group is done.
The IP Group table also has a new read-only field–“Gateway Group Location”– which
displays the current destination IP address of the IP Group.
14. Minimum Session Expires (SIP Min-SE Header):
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 provides support for configuring the minimum amount of time (in seconds)
between session refresh requests in a dialog before the session is considered timed
out. This value is sent in the SIP Min-SE header. This feature is configured using the
new parameter, SBCMinSE. When set to zero (default), the SBC does not limit
Session-Expires.
15. Multiple RTP Media Streams per Call Session:
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 provides support for multiple RTP media streams per SBC call session.
Up to five different media types can be included in a session - audio (m=audio), video
(m=video), text, (m=text), and fax (m=image). Therefore, this also allows the device to
provide transcoding of various attributes in the SDP offer/answer (e.g., codec, port,
and packetization time) per media type. If the device is unable to perform transcoding
(for example, does not support the codec), it relays the SBC dialog transparently.