DGW Release Notes v2.0.38.717

IN 12439

The session-id present in the cookie is now regenerated systematically upon login. The session-id is also cleared in the cookie on logout.

IN 12045

The ptime attribute in SDP offers can now be added. Two new parameters were added to the Web interface:

• Include ptime Attribute : Specifies what value must be put in the ptime attribute of the SDP offers.
• Configured ptime Attribute : Specifies the configurable value to be put in the ptime attribute of the SDP offers provided the Include ptime attribute parameter is set to Declarative, Configured .

The Include ptime Attribute parameter can have 3 values:

• Disabled
• Declarative, Preferred Codec : Takes the ptime that the preferred codec would use.
• Declarative, Configured : Takes the value of the Configured ptime Attribute parameter.

IN 11925

The G.723.1 codec is now supported on the Sentinel, the Mediatrix C7, and the Mediatrix G7 units.

Each endpoint is statically bounded to a specific DSP on the unit. This may lead to call rejections even if some DSP resources are still available because of an unbalanced resource utilisation. Endpoints requesting DSP resources to process a call are now dynamically bounded to the DSP with the most available resources on the unit. At the end of the call, DSP resources are freed and are available to be used by other endpoints. This ensures a balanced resource utilisation and leads to more successful calls processed by the unit.

Dgw application now supports the Mediatrix Sentinel 100.

When a graceful restart is executed (either because a service is restarted or because of an automatic restart during a firmware installation) the Sbc service will refuse during the grace delay any new calls and will wait for all active calls to end before restarting the unit. If the grace delay expires, all active calls will be ended before restarting the unit.

All internal connections will be accepted when the Lfw Default Policy is Drop.

Go to Management\Firmware Upgrade. The following parameters were moved to a separate table at the bottom of the page:

• Automatic Restart Enable
• Default Settings On Restart
• Automatic Restart Grace Delay

IN 12439

The session-id is now regenerated upon login to prevent session fixation attacks.

The CAPS action in SBC ruleset now treats two INVITEs with the same alias as the same call attempt within 30 seconds. This ensures that re-INVITE won't be blocked.

The Sbc_Configuration.cfg script is used to configure a Mediatrix 3000 unit to run as an SBC. This script produced non-optimal values for the SipEp.UserAgents[].GatewayName parameters for FXO, BRI, and E1/T1 ports. The gateway name was set to "All". This was changed to "trunk_lines_gw" to be more consistent with these types of ports.

IN 12045

The ptime attribute in SDP offers can now be added under the SIP/Interop tabs of the Dgw Web interface.

The Dgw application now supports the Sentinel 100.

The Local Firewall drops all internal connections, so we add a default rule to accept these connections.

IN 12478

When the unit is restarted, the Telif service no longer changes from automatic to manual because of a timing issue.

IN 12606

The unit is no longer unreachable when a clear channel call fails to allocate the DSP channel on a 3000 Series unit.

Disabling the Conf Script Modifiers diagnostic traces no longer disables the Call Manager traces.

The HTTP User Agent field is now set when a firmware upgrade - multiple file update - is triggered via CWMP.

With the addition of single file update it was hard to get which parameter was needed for which transfer type. The page was re-ordered and re-divided so it is now easier to understand.

A call could be blocked after a re-INVITE because the call attempts per time unit (also known as CAPS) action in the SBC Ruleset was considering each INVITE as a separate calls, which is no longer the case.

The SBC was stopping RTCP XR packets and considering them as malformed packets. This was corrected and now the SBC properly relays the packets to the intended target. The SBC does not support RTCP XR, so it cannot make use of the packet itself.

IN 12517

This limitation was removed. The 4404 can now use all 8 channels, regardless of the configuration.

An issue in the logging subsystem has been identified and corrected.The SBC logging subsystem no longer triggers the Sentinel to be restarted.

The SBC was replacing the SDP crypto attribute in every 180, 183, and 200 responses, which was not supported by the unit receiving these responses. The SBC now reuses the same crypto attribute in these responses.

IN 12297

The port information was missing from the "Calling Host" call property for calls coming from SIP. Now, when the Contact in the SIP INVITE has a port, the port is appended to the Calling Host Call Property.

IN 12314

The SBC now handles Re-INVITEs with the alias received prior to the SIP challenge.

The RTP packets were not sent at a steady state rate on the Sentinel 400, causing poor audio quality if the jitter buffer of the other device was not of good quality. This has been solved.

The Sbc_Configuration.cfg script is used to configure a Mediatrix 3000 unit to run as an SBC. This script produced non-optimal values for the SipEp.UserAgents[].GatewayName parameters for FXO, BRI, and E1/T1 ports. The gateway name was set to "All". This was changed to "trunk_lines_gw" to be more consistent with these types of ports.

The calls are no longer dropped when the Mediatrix SBC routes an INVITE without SDP and receives a 183 provisional response with SDP followed by a 180 with the same SDP, or a 180 Ringing response with SDP followed by a 200 OK with the same SDP.

When using any codec with DTMF out of band and rtp, pressing several touch keys in a row could cause one of the DTMF tones to remain locked on a touch key tone causing call issues. This has been fixed and is no longer the case.

For the SBC to answer to authentification challenges correctly, a rulesets needs to be used. An issue was found that when the SBC received the challenge he would answer without any information on the username and password to use. This was is conflict with the rulesets and cause the connection to fail.