DRG SW R2N30 Release Notes

Transcription

1

2

3

4 PF-DOC-DRG_R2N30-RN. Published August 31, Copyright and Legal notice Copyright 2011 PacketFront International AB. All rights reserved. DRG, the DRG bootloader, program models and other software, software content and this documentation ( the Intellectual Property Rights ) are protected by the Swedish Copyright Act (Sw: Upphovsrättslagen) and, if applicable, the Swedish Patents Act (Sw: Patentlagen). All and any copying and distribution of the Intellectual Property Rights, without authorization by PacketFront is prohibited. The prohibition includes every form of reproduction and distribution. Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change without notice. PacketFront assumes no liability for damages incurred directly or indirectly from errors, omissions or discrepancies between the software and this document. DRG is a tradename of PacketFront. All other trademarks, service marks and trade names are proprietary to their respective owner. Purchasers, licensees and users accept and acknowledge that the products contain components (including components carrying certain firmware) and combinations of components that constitute trade secrets protected by PacketFront or its partners. Purchasers, licensees and users warrant that the delivered products will not be opened or dismantled, copied, altered or in any other way modified. Furthermore, purchasers, licensees and users agree not to attempt to reverse engineer, disassemble, modify, translate, create derivate works, rent, lease, loan, or without written permission distribute or sublicense the software, in whole or in part. The products and its hardware, firmware and software, including technical data, may be subject to EU and U.S export control laws, including the U.S Export Administration Act and its associated regulations and the International Traffic in Arms Regulations administrated by the US Department of State, and may be subject to export or import regulations in other countries. Purchasers and licensees agree to comply strictly with all such regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import hardware, firmware and software. Purchasers and licensees are not entitled to, and PacketFront is not in any event liable to pay, compensation for damages which delivered products or software has caused to other property or to persons or any other consequential damages, including but not limited to loss of profit, loss of production or any other indirect damages.

5 Contents DRG SW R2N30 Release Notes Introduction Supported Platform Released Images New Features in DRG SW R2N Resolved issues in DRG SW R2N Known issues in DRG SW R2N i

6 ii

7 Introduction This release notes describes the DRG SW R2N30 software release. Supported Platform If not otherwise defined, the new features, resolved issues and known issues apply to the products specified in Released Images on page 1. Some issues may be dedicated to a specific image or protocol as indicated in the descriptions. Released Images Table 1 shows the supported hardware platforms and corresponding software images in this release. Table 1 Released Images Hardware platform Image revision Protocol DRG 11/22 DMA0021 SIP DRG 100 DMA0202 SIP DRG 340/540 DMA0101 SIP DRG 560/580 DMA0081 SIP DRG 600T DMA0121 SIP 1

8 New Features in DRG SW R2N30 No new features are introduced in DRG SW R2N30. Resolved issues in DRG SW R2N30 The following issues are resolved in this release. Table 2 Bug number Resolved issues Description Using SNMP to reconfigure access VLANs breaks connection Using SNMP to configure VLANs may cause VLAN configuration to be corrupted H.323 call fails during media capability negotiation When the DRG makes calls over H.323, in rare cases some calls might fail due to incompatibility between the DRG and the terminal device on the other end of the call. If the H.245 terminalcapabilityset message received by the DRG contains some unrecognized capabilities in one entry, the DRG cannot negotiate a correct voice codec with the called party and thus fails to send Open Logical Channel (OLC) messages. If the called party happens to be the slave, the called party cannot send Open Logical Channel (OLC) messages either. Both parties hang in OLC waiting status. When timeout occurs, the call fails DRG crashes behind NAT when server side keep-alive is enabled The DRG crashes after receiving approximately 500 OPTION messages with extensions in the "Via" field. 2

9 Known issues in DRG SW R2N30 The following issues are known in this release. Table 3 Known issues Bug number Discovered Description R2N Parameter values insufficient for COUNTRY param for CLIP Parameter values are insufficient for COUNTRY parameter for CLIP. The parameter value ETSI_DURING_RINGING should be removed, and the following values should be added: 1. ETSI_DURING_DT-AS 2. ETSI_DURING_RP-AS 3. ETSI_DURING_LR+DT-AS R2N TV freezes when multiple STBs are watching the same channel When using multiple STBs connected to DRG560/580, the TV picture may freeze R2N DHCP Option 225 cannot configure SIP server port When using DHCP option 225 for configuring SIP server details, non-default settings for ports are used as the local port, not the SIP server port. Workaround: Always use default ports R2N Echo Cancellation causes loss of voice Under some conditions, when both sides talk, the DRG may stop sending voice traffic for up to 30 seconds. Workaround: Disabling echo cancellation has been shown to stop this issue from occurring R2N H.323: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N H.248: DRG stops polling HDD when IF1 does not have an IP address If the virtual interface is enabled, and the VoIP interface fails to get an IP address via DHCP, the DRG stops polling HDD R2N DMA0083: DRG stops responding Following configuration changed by HDD, a DRG may become unresponsive and disappear from the network. It must be rebooted to become active again. 3

10 Table 3 Known issues Bug number Discovered Description R2N Multicast streams do not stop If a multicast client leaves a group without sending a leave message, the multicast stream will not time out and be removed R2N Turning off IGMP Snooping stops all multicast If IGMP snooping is disabled for one port, all multicast traffic flows are stopped and cannot be restarted R2N DMA0027: SIP registration problem after WAN outage If the path between DRG and SIP proxy is interrupted long enough for the registration to expire, then the DRG may fail to register with the proxy when the disruption is removed R2N DMA0027 R2N14 only sends End Event at Flash Hook Flash Hook, enabled either tapping the receiver or using the R button, only produces an RTP Flash End event. Because no Start event packets are sent, the certain External Class 5 service will not work in customer switches R2N SIP stops working after a final REGISTER response matching transaction but not matching dialog If the DRG receives a response to a REGISTER message where the URI does not match the request, the SIP application may stop working R2N H.323: DRG incoming calls failure Incoming H323 calls may fail on DRG R2N Not able to configure ports on DRG600-Access through HDD For the DRG600, it is not possible to configure ports using HDD R2N SNMP get/set not matching configurations On DRG600A, some SNMP objects may not match the actual device configuration R2N Contact-URI is used for CLIP instead of display name The Contact-URI may be used for CLIP information instead of From-URI. Under normal conditions, these values are the same and this has no effect. 4

11 Table 3 Known issues Bug number Discovered Description R2N CLIP presentation of number does not work when dial plan contains reverse substitution which includes "+" If the dial plan contains a reverse substitution rule that includes "+", the caller ID value used will not contain the reverse substitution, but will use the value from SIP "from uri" context R2N GUI stops responding after a while after being upgraded to R2N18 The web server is not accessible. But other network applications such as ping and SNMP are not affected R2N No respond to MGCP request when "Max. delay before RSIP" set to 0 If the value of maximum delay before RSIP is set to zero, the DRG will register with the MGCP agent, but will then stop communicating with the agent. Workaround: Use a non-zero value for max delay before RSIP R2N DRG Web GUI does not support Google Chrome The DRG does not fully support Google Chrome. If the user makes some configuration changes on the GUI using Chrome and restarts the DRG, the configurations are not updated. 5

12 6

13

14