DRG11/22 SW R2L Release Notes

Transcription

1 DRG11/22 SW R2L Release Notes

2 DOC-DRG-11/22-R2L-RN Rev B Printed October 8, 2008

3 Contents Contents 1 INTRODUCTION Supported Platform Released Images NEW FUNCTIONALITY CR293: Support for Port mode settings via INI CR970: INI/configuration file can be uploaded CR1947: Call waiting tone played from SIP INFO CR2100: Use Hostname as the DRG identity for CDSP CR13851: TCP Throughput improvement on DRG 11/ CR14524: Support for two early media streams carried in SDP in both 180 and 183 messages CR15533: Support for Call Forwarding Indication/Reminder by NOTIFY CR15715: DRG configuration to send SIP requests to the proxy server even though there is no Record-Route inserted by the server FIXED BUGS TR2135: Record-Route header in INVITE is not properly handled TR14071: No RTP when Packet size was set to 30ms TR14245: One way speech with DRG22i on MD IPLU when incoming call to group extension TR15178: Fallback to RTP during T.38 FAX renegotiation KNOWN BUGS TR1132: The parameter of BEARERCAP is invalid TR1274: No Routing protocol observed when enable "Dynamic Routing" TR1998: SIP INVITE hacker attacks according to CA makes DRG stuck/dead after certain amount of run testcases TR2131: Always sending ACK to dialog unmatched 200OK TR2137: "500 Server Internal Error" shall be responded to requests with sequence number lower than or equal to previous request TR2140: BYE without tags not rejected TR13596: Wrong report while INI file upgrading with unavailable FQDN

4 2 DRG11/22 SW R2L Relase Notes

5 Introduction 1 Introduction This release notes describes the DRG 11/22 R2L software maintenance release. 1.1 Supported Platform Unless stated otherwise, new functionality and fixed bugs apply to all DRG11/22 products. 1.2 Released Images Image revision DMA0021-R2L465 Protocol SIP DMA0022-R2L466 H.323 3

6 DRG11/22 SW R2L Release Notes 2 New Functionality 2.1 CR293: Support for Port mode settings via INI The DRG supports the configurable speed and duplex mode settings on both the WAN and LAN ports. The parameter configuration is described as follows: Parameter name: PORTMODE Format: PORTMODE= [AUTO AUTO10 100FD 100HD 10FD 10HD OFF], [AUTO AUTO10 100FD 100HD 10FD 10HD OFF] The first value presents the setting of the WAN interface, and the second value presents that of the LAN interface. Values: - AUTO: The port uses IEEE802.3u negotiation with its link partner to determine the correct mode of operation. The port advertises 100FD, 100HD, 10FD and 10HD modes, and will select one of these modes based upon the modes advertised by the link partner. - AUTO10: The port uses IEEE802.3u negotiation with its link partner to determine the correct mode of operation. The port advertises 10FD and 10HD modes, and will select one of these modes based upon the modes advertised by the link partner FD: The port speed is 100Mbps and the mode is full duplex - 100HD: The port speed is 100Mbps and the mode is half duplex - 10FD: The port speed is 10Mbps and the mode is full duplex - 10HD: The port speed is 10Mbps and the mode is half duplex - OFF: The port is disabled. Note: It is not recommended to set the WAN port to OFF as this will result in connectivity loss. Default value: AUTO,AUTO Example: Configuration to set WAN port into 10Mbps half-duplex mode and to set LAN port into 10Mbps full duplex mode PORTMODE=10HD,10FD 2.2 CR970: INI/configuration file can be uploaded The DRG now supports uploading of all configuration information, i.e. config, INI, DEF, and network related information, to a designated HTTP server. A "CFG Upload" item in the System submenu is added to provide the feature. The item requires the user to provide the uploading URL indicating the designated HTTP server, CGI and config filename. Note: Information about passwords, e.g. the VoIP user and PPPoE user passwords, is removed from the uploaded configuration for security reason. 4

7 New Functionality 2.3 CR1947: Call waiting tone played from SIP INFO The DRG plays the Call Waiting tone when it receives Broadsoft-specific SIP-INFO from the server. When the user presses the flash, the DRG sends Broadsoft specific SIP-INFO to inform the server of the flashhook event. To enable this feature, the External Class 5 service must be enabled and the keypad type for the corresponding line must be set to "SIP INFO". 2.4 CR2100: Use Hostname as the DRG identity for CDSP2 Hostname is used instead of MAC Address if the Hostname is defined in CDSP2 clients. MAC Address is also supported by CDSP2 clients using the GetParameterValue method. Items Identity and Hostname are added on the WAN Status page of the Web GUI. If the Hostname is set, the content of the Identity is the Hostname. Otherwise, Identity is the MAC Address. 2.5 CR13851: TCP Throughput improvement on DRG 11/22 The TCP throughput performance on the DRG is improved. Both the downlink and the uplink volumes are increased by providing a rate limit function, and by adding the feature to manually configure the WAN/LAN port by setting the parameters RATELIMIT to YES and PORTMODE to AUTO. Please refer to the release notes for CR293 for the details of the parameter PORTMODE. 2.6 CR14524: Support for two early media streams carried in SDP in both 180 and 183 messages In previous releases, the DRG is not able to handle two early media streams at the same time in both SIP 180 and 183 messages. When the parameter LOCAL_RINGING is set to ON, sometimes the ring back tone sounds OK and sometimes it is just imtermittent noise (one tone, then intermittent noise, then ring back one continues). If the parameter LOCAL_RINGING is set to OFF, two behaviors are observed: - 1 ring back tone once and then a different ring back tone - 1 ring back tone once and then silence This problem is solved by playing the first incoming media stream and ignoring the other stream in the early dialog stage. A related issue is also solved in this release. In the previous release, the RTP packet is only supported when it is 12 bytes. This causes the intermittent noise, because the last 2 bytes in a RTP header is treated as the voice data. This issue is fixed by recognizing the extension field in the RTP header. 5

8 DRG11/22 SW R2L Release Notes 2.7 CR15533: Support for Call Forwarding Indication/Reminder by NOTIFY The DRG supports two new features: 1) Call Forwarding Indication If Call Forwarding is enabled for the phone line, a stuttering Dial-Tone is played when the handset of the connected phone is taken off the hook, 2) Call Forwarding Reminder If there is an incoming call on the phone line, a special ringing signal is played when the handset of the connected phone is on-hook, 2.8 CR15715: DRG configuration to send SIP requests to the proxy server even though there is no Record-Route inserted by the server The DRG can be configured to send SIP requests to the proxy server even though there is no Record-Route inserted by the server. 6

9 Fixed Bugs 3 Fixed Bugs 3.1 TR2135: Record-Route header in INVITE is not properly handled The DRG alters the values of the unknown parameters received in the Record-Route header. 3.2 TR14071: No RTP when Packet size was set to 30ms When the RTP packet size is set to a volume bigger than 20ms, speech cannot be heard. Speech is delivered normally when the RTP packet is set to be bigger than 20ms in this release. 3.3 TR14245: One way speech with DRG22i on MD IPLU when incoming call to group extension The DRG sends OpenLogicalChannel when the TerminalCapabilitySetExchange is completed but the MasterSlaveDetermine is uncompleted. This causes one way speech on the DRG. 3.4 TR15178: Fallback to RTP during T.38 FAX renegotiation When voice calls are established successfully and the DRG detects FAX, a SIP INVITE is sent to renegotiate T.38 capability. The session content is changed from voice call to T.38 FAX, but the session version is not increased. It results in a failed capability negotiation for FAX. 7

10 DRG11/22 SW R2L Release Notes 4 Known Bugs 4.1 TR1132: The parameter of BEARERCAP is invalid The support of parameter BEARERCAP is currently missing. Configuring the parameter in the ini file or via HDD does not take any effect. 4.2 TR1274: No Routing protocol observed when enable "Dynamic Routing" When the DRG WAN port is connected to the hub, the LAN port is connected to the PC and the DRG works in routed mode with LAN routing configuration Dynamic Routing Tx and Rx enabled, routing packets such as the RIP on the WAN side cannot be observed. 4.3 TR1998: SIP INVITE hacker attacks according to CA makes DRG stuck/dead after certain amount of run testcases The DRG becomes stuck/dead when the DRG is under SIP INVITE hacker attack according to CA (Multiple vulnerabilities in implementations of the Session Initiation Protocol (SIP)). 4.4 TR2131: Always sending ACK to dialog unmatched 200OK The DRG always sends ACK to 200OK regardless of whether the 200OK is the correct response to INVITE or not. This is because it may have a different Call-ID header other than that for the INVITE request. If the Call-ID header of 200OK to INVITE is different from that requested by the INVITE request, the DRG should not acknowledge the 200 OK with ACK. Instead, the DRG should discard the 200 OK silently. When a 200 OK is sent to the DRG, the DRG also acknowledges it with ACK. This is incorrect. 8

11 Known Bugs 4.5 TR2137: "500 Server Internal Error" shall be responded to requests with sequence number lower than or equal to previous request If the remote sequence number is empty, it must be set to the value of the sequence number in the CSeq header field in the request. If the remote sequence number is not empty and the sequence number of the request is lower than the remote sequence number, the request is out of order and must be rejected with a "500 Server Internal Error" response. If the remote sequence number is not empty and the sequence number of the request is higher than the remote sequence number, the request is in order. It is possible that the CSeq sequence number can be higher than the remote sequence number by more than one. This is not an error condition, and a UAS should be prepared to receive and process requests with CSeq values more than one higher than that of the previously received request. The UAS must then set the remote sequence number to the value of the sequence number in the CSeq header field in the request. If a proxy challenges a request generated by the UAC, the UAC has to resubmit the request with credentials. The resubmitted request then has a new CSeq number. The UAS never sees the first request, and therefore, a gap in the CSeq number space is noticed. The DRG should respond a "500 Server Internal Error" response, but instead, a "400 Bad Request" message is responded by the DRG. 4.6 TR2140: BYE without tags not rejected A UAS processes the BYE request according to the general UAS processing. The UAS checks if the BYE request matches an existing dialog. If the BYE request does not match an existing dialog, the UAS core should generate a "481 Call/Transaction Does Not Exist" response and pass that onto the server transaction. This rule means that a BYE request sent without tags by a UAC will be rejected. However, the DRG accepts all the BYE requests with or without tags and the 200 OK responses are sent by the DRG. 4.7 TR13596: Wrong report while INI file upgrading with unavailable FQDN The DRG incorrectly reports the download status while upgrading an existing INI file with a non-existent FQDN (Fully Qualified Domain Name). 9

12 DRG11/22 SW R2L Release Notes Copyright and Legal Notices Copyright 2008 PacketFront. All rights reserved. DRG is a trade name of PacketFront. All other trademarks, service marks and trade names are proprietary to their respective owner. 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. 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 administered 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 acknowledge 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. 10