Driver Information
Showing 1 to 5 of 13 (Show All)
|
Date
|
Version
|
Notes
|
|
19 Mar 2010
|
8.4.2
|
New products:
CANT-3 TG870 (POTS only) r8.4.2.I
DANT-F TG797(i)n v2 r8.4.2.I
DANT-J TG784Bn (POTS only) r8.4.2.I
Platform CANT-3, CANT-7, CANT-8, CANT-G, CANT-W, CANT-Y, DANT-F, DANT-J
GoMP BLI-image - CANT-3 SIPS/SIP : TG870: ZXRGAA8.42I.bli
GoMP BLI-image - CANT-3 SIPS/SIP : TG870: ZXRGAA8.42N.bli
GoMP BLI-image - CANT-3 SIPS/SIP : TG870: ZXRGAA8.42Q.bli
GoMP RBI-image - CANT-3 SIPS/SIP : TG870: ZXRFAA8.42I.rbi
GoMP RBI-image - CANT-3 SIPS/SIP : TG870: ZXRFAA8.42N.rbi
GoMP RBI-image - CANT-3 SIPS/SIP : TG870: ZXRFAA8.42Q.rbi
GoLinux BLI-image - CANT-7 : TG585(i)nv2: ZYEYAA8.42I.bli
GoLinux BLI-image - CANT-7 : TG585(i)nv2: ZYEYAA8.42N.bli
GoLinux BLI-image - CANT-7 : TG585(i)nv2: ZYEYAA8.42Q.bli
GoLinux RBI-image - CANT-7 : TG585(i)nv2: ZYEXAA8.42I.rbi
GoLinux RBI-image - CANT-7 : TG585(i)nv2: ZYEXAA8.42N.rbi
GoLinux RBI-image - CANT-7 : TG585(i)nv2: ZYEXAA8.42Q.rbi
GoMP BLI-image - CANT-8 : TG587(i)nv2: ZYEKAA8.42I.bli
GoMP BLI-image - CANT-8 : TG587(i)nv2: ZYEKAA8.42N.bli
GoMP BLI-image - CANT-8 : TG587(i)nv2: ZYEKAA8.42Q.bli
GoMP RBI-image - CANT-8 : TG587(i)nv2: ZYEJAA8.42I.rbi
GoMP RBI-image - CANT-8 : TG587(i)nv2: ZYEJAA8.42N.rbi
GoMP RBI-image - CANT-8 : TG587(i)nv2: ZYEJAA8.42Q.rbi
GoMP BLI-image - CANT-G SIPS/SIP : TG787(i): ZXLLAA8.42I.bli
GoMP BLI-image - CANT-G SIPS/SIP : TG787(i): ZXLLAA8.42N.bli
GoMP BLI-image - CANT-G SIPS/SIP : TG787(i): ZXLLAA8.42Q.bli
GoMP RBI-image - CANT-G SIPS/SIP : TG787(i): ZXLKAA8.42I.rbi
GoMP RBI-image - CANT-G SIPS/SIP : TG787(i): ZXLKAA8.42N.rbi
GoMP RBI-image - CANT-G SIPS/SIP : TG787(i): ZXLKAA8.42Q.rbi
GoMP BLI-image - CANT-G MGCP : TG787(i): ZYCQAA8.42I.bli
GoMP RBI-image - CANT-G MGCP : TG787(i): ZYCPAA8.42I.rbi
GoMP RUI-image - CANT-G MGCP : TG787(i): ZXLMAA8.42I.rui
GoLinux BLI-image - CANT-W SIP Server : TG782(i): ZXQEAA8.42I.bli
GoLinux BLI-image - CANT-W SIP Server : TG782(i): ZXQEAA8.42N.bli
GoLinux BLI-image - CANT-W SIP Server : TG782(i): ZXQEAA8.42Q.bli
GoLinux RBI-image - CANT-W SIP Server : TG782(i): ZXQBAA8.42I.rbi
GoLinux RBI-image - CANT-W SIP Server : TG782(i): ZXQBAA8.42N.rbi
GoLinux RBI-image - CANT-W SIP Server : TG782(i): ZXQBAA8.42Q.rbi
GoMP BLI-image - CANT-Y SIPS/SIP : TG784(i): ZYCZAA8.42I.bli
GoMP BLI-image - CANT-Y SIPS/SIP : TG784(i): ZYCZAA8.42N.bli
GoMP BLI-image - CANT-Y SIPS/SIP : TG784(i): ZYCZAA8.42Q.bli
GoMP RBI-image - CANT-Y SIPS/SIP : TG784(i): ZYCYAA8.42I.rbi
GoMP RBI-image - CANT-Y SIPS/SIP : TG784(i): ZYCYAA8.42N.rbi
GoMP RBI-image - CANT-Y SIPS/SIP : TG784(i): ZYCYAA8.42Q.rbi
GoMP BLI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUEAA8.42I.bli
GoMP BLI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUEAA8.42N.bli
GoMP BLI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUEAA8.42Q.bli
GoMP RBI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUDAA8.42I.rbi
GoMP RBI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUDAA8.42N.rbi
GoMP RBI-image - DANT-F SIPS/SIP : TG797(i)nv2: ZXUDAA8.42Q.rbi
GoMP BLI-image - DANT-J SIPS/SIP : TG784Bn: ZXP3AA8.42I.bli
GoMP RBI-image - DANT-J SIPS/SIP : TG784Bn: ZXP2AA8.42I.rbi
GoMP BLI-image - DANT-J MGCP : TG784Bn: ZXNGAA8.42I.bli
GoMP RBI-image - DANT-J MGCP : TG784Bn: ZXNFAA8.42I.rbi
GoMP RUI-image - DANT-J MGCP : TG784Bn: ZXL6AA8.42I.rui
New Features
Note before: unless marked otherwise, all new features were introduced at r8.4.2.I.
- Unified 3-party phone call conferencing:
VoIP gateways now support full-blown unified 3-party conferencing calls involving any DECT handsets and/or FXS phones connected to the Gateway in mixed codec scenarios.
- Extended shared address book support:
The shared phonebook (as introduced in the previous Main Track Slotted Release R8.4.1) has been extended in this release with following features:- It now supports up to 1000 phonebook contact entries.
- A contact entry can be shared over all phonebooks or can be non-shared, meaning that it is only accessible for phones connected to the phonebook (backwards compatible).
- Contact entries are stored in UTF-8 encoding (offering support for entries in all possible alphabets).
- 8 SIP accounts supported:
Up to eight SIP accounts are supported. A SIP account will be identified by a VoIP account ID.
- CAT-IQv2 specified DECT handset profile-selective calling:
The TG870 supports high-end DECT handsets to select a specific VoIP profile to be used for outgoing calls. If the off-hook button is pressed long on the DECT handset, a menu is shown to select which VoIP profile is to be used for the outgoing call.
- TDD support:
VoIP gateways now comply to the requirements for tone detection for hearing impaired phone users as stipulated in TIA 1001.
- Extended US Hookflash support:
The hookflash action assigned to the Switching Order Commands (SOC) (functions) are configurable as follows:- Hold active call and enable call setup (
HoldActiveCallAndEnableCallSetup).
- If no active call: retrieve the held call (
NoActiveCallRetrieveHeld)
Establish3PartySwitchBetweenActiveAndHeldSwitchBetweenActiveAndWaitingDropLastPartyFrom3Party
The SOCs that are configurable are HF, HF1, HF2, HFTO, HFTO or HF2and HF3.
- Unified Call barge-in regardless of interface:
When a call is ongoing and another party locally picks up the phone (any DECT handset and/or FXS phone connected to the Gateway), that party automatically joins the call in a 3-party setup. This compares best to the ‘old’ analog situation where you had multiple phones attached to the same analog interface.
- Persistent and per call/suspend-based Cancel Call Waiting (CCW) support:
The Gateway supports to cancel a waiting call on a per call, or persistent basis:- To cancel Call Waiting persistently,
#43# is the service code
- To cancel Call Waiting for a single, or on suspend,
#43* followed by the number to call, cancels call waiting for the duration of that call.
- Call Hold (CH) support for local DECT calls:
The Gateway supports call hold requests from local DECT handsets connected to the DECT base station.
- Provisioning and activation of supplementary VoIP services through TR-104:
The Gateway supports provisioning and activation of supplementary call services, such as 3-party calling support, call waiting support, ... through TR-104.
- Number translation extensions:
For phonebook matching purposes, the original calling party number is taken, the non-digits are removed, and the last x (configurable) digits are used to scan the phonebook for a match.
Based on a global configuration:- The caller ID sent to the phone is the original, or the translated number.
- The Call log / call list will use the original, or the translated number.
- The input for phonebook matching are the last x (configurable) digits of the original number.
- Echo Cancellation timing (ECAN) has been changed from 48ms to 64ms for G.168 compliancy:
To further improve voice quality in extreme echo-prone environments, and/or when using echo-prone phone devices, the 64ms G.168 compliant echo canceller is used from now onwards in favour of the previously applied 48ms echo canceller.
- SIP Server extensions for advanced Connection Admission Control (CAC) configuration:
The SIP server configuration has been extended to allow configuration of the maximum number of external session configuration, and configuration of response codes with customized values.
This allows to - for example - support a set maximum number of external calls and a customized code in the response when more call sessions are requested.
The default value for CAC has been changed to 2 to allow a maximum of two external (incoming/outgoing) calls per Gateway. In this behaviour, a third caller (incoming/outgoing) will receive busy tone (486 “Busy” SIP message) instead of a temporarily unavailable
tone (480 “Temporarily Unavailable” SIP message).
- OSGi Software Development Kit:
Selected products support the Open Services Gateway initiative (OSGi) Java-based service platform, which allows third-party service, API and application component development for Thomson Gateway platform software. These are the current supported models:- TG587(i)n v2
- TG784(i)
- TG784Bn
- TG787(i)
- TG797(i)n v2
- TG870
The OSGi framework provides:- A new generation framework (as compared to deployment provided in the previous Main track Slotted R8.4.1 DEMO framework).
From this Main Track Slotted Release onwards, the framework used is Felix. Felix is a community effort to implement the OSGi R4 Service Platform, which includes the OSGi framework and standard services, as well as providing and supporting other interesting OSGi-related technologies. Felix currently implements a large portion of the OSGi release 4 specification, but additional work is necessary for full
compliance. Despite this fact, the OSGi framework functionality provided by Felix is very stable.
- Secure Transport connections (TLS/SSL) with peer authentication by trusted certificates.
This is an implementation that provides an extension of the Execution Environment with a subset of the Java package javax.net.ssl API that builds on the Native Communication and System services of the Gateway Service Platform, among its TLS capabilities, while adhering to the Gateway product’s security and QoS policies.
- Use with pre-installed OSGi components bundles.
The OSGi framework can handle pre-installed bundles, i.e. bundles that are pre-installed on the Gateway platform software by integrating them during creation of the platform software at THOMSON.
Note: Remote management, installation and execution of OSGi bundles on a running Gateway platform software is possible, yet not recommended.
- WebUI Software Development Kit:
Selected Gateways support full design of new, or ultra-flexible customization of existing, GUI pages via the Lua scripting language.
- Remote access to Thomson Gateway shared content:
(Note: GUI page not available by default; depends on ISP integration) The Gateway supports secured (remote) access via HTTP and/or HTTPS (with integrated authentication via the Multi-Level Access Policy (MLP) framework) to shared content stored on one or multiple disks connected via the product’s USB port(s) to allow the user to browse, delete, download and upload files on disk(s) connected to the Gateway.
- NTFS and/or HFS+ file systems now supported under USB Content Sharing:
(Note: GUI page not available by default; depends on ISP integration) Upon request and feasibility, the Gateway can be customized to support Content Sharing for hard disk media using the New Technology File System (NTFS) and/or the Hierarchical File System Plus (HFS+) file system on top of the already supported File Allocation Table 32 (FAT32) file system.
- Optimized power consumption control & management:
This unique feature allows the Gateway to constantly monitor user activity and to instantly use this information to optimize it’s power consumption and peripheral connections; i.e when there is no or low user activity, the Gateway can automatically:- Reduce the clock frequency of the central processor (thus lower power consumption)
- Reduce the Ethernet functionality to mere link detection when there are no devices connected to the Ethernet port
- Switch the wireless interface to a reduced power mode in which the access point is available for connection, yet while other functions are turned off.
- Policy-controlled firewall behaviour:
(Note: GUI page not available by default; depends on ISP integration) The Gateway provides a framework to support time-based Internet access control through time-dependant configuration of the Stateful Inspection Firewall (SIF) rules policy.
- Wireless: Adjacent Channel Interference mechanism:
(Note: off by default as it may impact Wireless reach) ACI is a method to allow Wi-Fi deployment in RF-overcrowded areas (for example, apartment buildings with more than 10 wireless APs in the air). Under normal conditions (without ACI) there are too many collisions and interfering packets being broadcast, preventing the deployment of a good Wi-Fi link, due to the collision avoidance nature of the 802.11 protocol. The ACI mechanism will now make radio on the AP more robust by ignoring most of the irrelevant (low-power) background noise. Hence it is possible to set up a wireless network in areas where otherwise no Wi-Fi could be established.
- System Services Manager extension for individual IP interface Access Control Lists:
The Gateway System Service Manager has been extended to support individual IP interface Access Control Lists (ACL) in addition to existing IP interface groups (such as ‘LAN’, or ‘WAN’,...) ACLs. With this extension, multiple IP addresses can now be specifically configured to allow access to a certain service, while the IP addresses can be located on different interfaces.
- GUI: Improved login page:
The Gateway GUI pages feature an improved login page that pro-actively redirects every access attempt to an embedded authentication cycle.
- GUI: Embedded Help:
An improved Firmware Embedded Help (FEH) is included in the platform software.
This FEH:- Introduces a further improved single-sourced, conditionalized XML sources for FEH content, facilitating customization and localization.
- Fixes various issues found in earlier versions (such as missing coverage for example).
- Backwards compatible with existing language packs.
- 802.11n wireless LAN certification:
All new introduced wireless-n capable products are IEEE802.11n certified by the Wi-Fi Alliance.
- WPS certification:
All new introduced wireless-n capable products are Wi-Fi Protected Setup (WPS) certified by the Wi-Fi Alliance.
- DLNA certification:
Selected Thomson Gateway products are certified by the Digital Living Network Alliance (DLNA). This DLNA certification guarantees that the UPnP AV Media Server seamlessly integrates in the DLNA home environment to interwork with and share media content with other certified products, such as televisions, computers, gaming devices or PDAs.
These are the current certified models:- TG587(i)n v2
- TG784(i)
- TG784Bn
- TG787(i)
- TG797(i)n v2
- TG870
- UPnP certification:
The following products have been UPnP certified by the UPnP Forum:- TG585(i)n v2
- TG587(i)n v2
- TG782(i)
- TG784(i)
- TG784Bn
- TG787(i)
- TG797(i)n v2
- TG870
BugFixes:
Note before: unless marked otherwise, all BugFixes were introduced at r8.4.2.I.
- GUI interoperability with Internet Explorer 8, Safari, and Google Chrome:
The Gateway GUI framework has been updated to include seamless support when browsing GUI pages with Internet Explorer 8 or with Google Chrome.
This enables the following functionality on these web browsers:- Switching user via the GUI using Internet Explorer 8.
- It is possible to log to the GUI as Administrator with Safari
- Phone call pass-through not possible by Thomson Gateway due to SIP ALG:
The issue where the product’s SIP ALG does not correctly handle address translation of call forward RTP coming from a local SIP PBX on the local network, has been solved.
- SIP Server doesn’t correctly handle Call transfer:
The issue where during a call (PSTN calling a phone registered to the SIP server), if the call is transferred to another phone registered to the Gateway SIP server, this will fail (as the REFER message is forwarded to the VoIP softswitch with the private IP @ and mapping, instead of being handled locally by the Gateway SIP Server, has been solved.
- SIP Server GUI internal registration issue:
The issue where configuring Internal SIP UAs via the GUI may cause registrations to fail, has been solved.
- No tone is generated when the active party hangs up during incoming call while busy:
The issue where an FXS phone is not supplied with the release tone accompanied by polarity reversal back to ‘I’ state after disconnecting an active call on this phone while an incoming call to this phone was received during the call, has been solved.
- Packet loss on video bridged connections when PPPoA is in retrying state:
The issue where packet loss has been observed on upstream video bridged connections (IGMP queries) when the PPP connection is retrying (in scenarios with PPPoA data/voice connections next to bridged connections for video, has been solved.
- Gateway cannot handle incoming calls to an off-hook phone that is not involved in a call:
The issue where, when call waiting service is active and an incoming call is received for a local phone that is off-hook, yet not involved in an active call, the caller doesn’t get a busy tone immediately, has been solved.
- SIP ALG does not add the NAT-ted port to the contact header when the received contact header doesn’t contain a port number:
The issue where the SIP ALG does not add the translated proxy port within the contact header of SIP messages, in situations where the proxy port was not present in the original contact header of the SIP message, has been solved.
- Voice LED behaviour extensions to take SIP account status into account:
When independent profiles are created for individual VoIP connections, the Voice LEDs for the particular VoIP connection now takes the individual status of the profile into account instead only basing the LED status on the COMMON profile.
- Voice parameter lengths compliancy to TR-104:
The maximum supported lengths of the user name, password, proxy addresses, user agent domain, registrar address, ... for a SIP UA configuration are now compliant to TR-104.
- Two simultaneous incoming calls not handled correctly:
The issue where, during an incoming call that is not yet answered (phone is ringing), and a second incoming call to this phone is received, will not result in a busy signal to the calling party and will ultimately fail due to no phone alerting, has been solved.
- Internal SIP Server registration failure:
The issue where it has been observed that after some time the internal SIP Server registration of the voice profile list is not registered anymore, has been solved.
- TR-104 compliant Voice Session Information parameters available via TR-069 are not aligned with TR-104:
The issue where some Voice Session Information parameters available via TR-069 were missing, not compliant to, or aligned with TR-104, has been solved.
- The first IP address of the IPCP pool is always reserved for virtual unnumbered PPP interface:
The issue where, in an IPCP scenario with PPP set to unnumbered and DHCP to numbered, the Gateway doesn’t take the expected IP address from the DHCP pool as gateway IP address, has been solved:- By default with PPP-Public-Subnet, and PPP-Public-Subnet Passthrough, the last IP address of the received IPCP pool is used for configuring the PPP interface (i.e. virtual IP address) and the first IP address to configure the LAN interface (i.e. DHCP gateway IP address).
- The assignment of the virtual IP address to be used by the PPP interface is made configurable by the
subnetfirstip parameter (which allows to specify if the first or the last IP address from the received range is to be used to configure the PPP interface).
- Wireless security cannot be used with MSSID:
The issue where wireless clients can only associate on the virtual access points without encryption (i.e. WEP, nor WPA(2) are possible) when the Gateway is configured with multiple SSID and the virtual access point is assigned to a VLAN with separate DHCP pools, has been solved.
- Legacy front-panel button functionality unable to disable the wireless interface after restart:
The issue where, once the legacy front-panel button functionality is enabled, the button cannot be used for disabling the integrated wireless interface after a restart, has been solved.
- GUI Vulnerability issue:
A vulnerability issue of the GUI, where a malicious user can access the Gateway, has been solved.
- Improved GUI page loading:
The issue where loading the GUI home page was slowed down due to extensive and redundant Device Discovery actions, has been solved.
- IPoE WAN connections not shown on the Broadband Connections GUI page:
- IGMP proxy membership database gets corrupted with multiple Set-Top Boxes:
The issue where the IGMP proxy membership database (the group list that keeps track of what STB clients are using which stream) may become corrupted after some time when multiple STB clients are connected, has been solved.
- RTSP NAT ALG doesn’t handle RTSP from ADB Set Top Box and Alcatel-Lucent video server:
The issue where the Gateway RTSP NAT ALG does update the payload of the RTSP packets to pass NAPT, but does not open a connection and pinhole for the UDP stream to be received from the video server, has been solved.
- Separated authentication trigger point in AAA framework (r8.4.2.N):
The issue where local telnet and serial access to a Business Gateway product is impossible when AAA is enabled while the remote server does not support authentication for telnet and serial access, has been solved by descoping the telnet and serial trigger points authentication from the AAA module.
- PPTP session not possible through the Gateway (r8.4.2.N):
The issue where it is not possible to setup a PPTP connection from an MS Windows XP host computer through the Gateway, has been solved.
- Restart due to parental control (r8.4.2.N):
The issue where the Gateway has been observed to restart when surfing to a number of different web sites while URL-based or content-based web site filtering is enabled and configured to block one or more sites (or URLs), has been solved.
- It is not possible to use and configure a pre-shared key authentication on the IPSec/VPN Expert GUI page. (r8.4.2.N):
- Segmentation issue in IPSec scenarios with NAT-Traversal (r8.4.2.N):
The issue where the Business Gateway products have a segmentation problem in IPSec scenarios with NAT-Traversal (in case firewall UDP checks are enabled, the second segment is always dropped), has been solved.
- Differentiated Service Delivery (DSD) intercepts all traffic once the default WAN connection goes down, yet other WAN connections are OK (r8.4.2.N):
The issue where in multiple WAN scenarios, the DSD intercepts all traffic once the default WAN connection goes down, including the traffic coming from other WAN connections that are OK, for example HTTP traffic towards a STB, has been solved by adding transparent NAPT portmap support.
- Game TCP connection is going idle and is killed, even if traffic is active on the connection (r8.4.2.Q):
The issue where the TGateway wrongly brings online game TCP connections in idle state, and eventually kills them, even if traffic is flowing on the connection, has been solved.
General Fixes:
Note before: unless marked otherwise, all General Fixes were introduced at r8.4.2.I.
- Bridge / VLAN / Bridge Filter / Ethernet:
- The issue where the ‘no_WAN_broadcast’ Ethernet bridge filter does not work in EFM and Ethernet WAN scenarios, has been solved.
- The issue where VLAN membership configuration of virtual wireless access points (mssid) was not saved correctly (and hence was lost on restart) has been solved.
- CWMP / Datamodel:
- The issue where extensions to the IGD datamodel do not fully support adding new IP Set-Top Boxes (STBs) (using DHCP vendor class, or possibly MAC address) to the flexiport functionality, has been solved.
- The issue where, when the Gateway detects an incompatible or corrupted firmware image (for example when the firmware image is for another Thomson model), it will correctly detect this, but does not send a “Transfer Complete” error message to the ACSs to report this failure, has been solved.
- The issue where CWMP packets are still processed through queue 4 instead of through the queue corresponding to the new QoS class, even when changing the internal QoS class for CWMP to another value than the default value 12 (where the outgoing CWMP packets’ service class is 12 and the packets are processed through queue 4), has been solved.
- The issue where it is not possible to configure Ptrace through TR-069, has been solved.
- The issue where, when setting the value
InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.Name to another value via CWMP/TR-069, the VoIP proxy server (which should be in InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP.ProxyServer) is changed, has been solved (r8.4.2.N).
- The issue where it is not possible to modify the wireless security preshared key for WPA(2) through TR-069, has been solved (r8.4.2.N).
- The issue where a TR-069 platform software upgrade of the Thomson Gateway will fail when a disk is connected to the USB port and set as managed disk, has been solved (r8.4.2.Q).
- DHCP / IPCP / DNS:
- The issue where a Gateway, configured in a PPP unnumbered scenario sends TR-069 inform messages with correct virtual IP address but with incomplete path, and sets the wrong IP address in the
ExternalIPAddress IGD parameter, has been solved.
- The issue where it is not possible to simultaneously configure different dynamic DNS services on different interfaces, has been solved.
- GUI / Firmware Embedded Help / Embedded Easy Setup / Lua:
- The issue where, when enabling Remote Assistance or Remote Access, WAN access to the GUI (over HTTPS) should be provided using the defined default Internet connection, but where however, in cases where multiple routed WAN connections have been configured (but not necessarily used) the Remote Assistance WAN access may be assigned to a wrong connection or to a 0.0.0.0 IP address, has been solved.
- The issue where it is not possible to switch to another user directly via clicking the user name on the GUI when using Internet Explorer 8, has been solved.
- The issue where backing up and restoring configurations via the GUI using file names other than user.ini did not work, has been solved.
- The issue where it is not possible to restore configurations via the GUI pages using HTTPS, has been solved.
- The issue where not all existing configurations are reset and cleared before the new configuration is applied when restoring via the GUI using Internet Explorer 7, or Internet Explorer 8, has been solved.
- The issue where the Gateway restarts when browsing to the Routed Ethernet connections page in the Expert GUI (on supported products) via Connections » Routed Ethernet » dmz1 » guest1, has been solved.
- The issue where IPoE connections created on top of the VDSL2 interface are not shown on the GUI (on pages Home » Broadband Connection and Home » Broadband Connection » Internet Services), has been solved.
- The issue where the Search wireless devices task on the Wireless GUI page to register wireless clients when wireless access control is enabled, cannot be used when wireless security is enabled (WEP or WPA(2)); i.e. the registration window is actually only opened after the GUI progress bar is at 100%, has been solved.
- The issue where, when restoring Business product configurations via the GUI, not all existing configurations are reset and cleared before the new configuration is applied, has been solved (r8.4.2.N).
- The issue where the responsiveness of the GUI is degrading with high data rate and high amount of connections, has been solved (r8.4.2.N).
- Housing / LEDs:
- The issue where in a DHCP WAN scenario the Internet LED does not turn red when no DHCP lease is offered to the ETHoA WAN interface, has been solved.
- IGMP / Video:
- The issue where the Gateway could not handle fragmented multicast packets correctly, i.e. where some of the packets were not forwarded, or were dropped, has been solved.
- The issue where connection reservation could not be applied for IGMP multicast traffic connections, has been solved.
- The issue where a configured Last Member Query Interval (LMQI) setting is not taken into account by the Gateway (hence where the maximum time between two group-specific query messages will always comply to, thus less than the default LMQI being 1 second), has been solved.
- IP Acceleration / IP Forwarding / IP Routing:
- The issue where, in routed iTV scenarios, any action that triggers an update of the connection framework will trigger packets that are out of sequence, has been solved.
- The issue where it was observed that Accelerated IP causes ICMP traffic to be dropped by the firewall, has been solved.
- The issue where Accelerated IP may cause DSCP labelled UDP traffic to be queued wrongly, has been solved.
- IPSec / VPN (r8.4.2.N):
- When Accelerated IP and IP QoS are enabled (default setting) ACKs are dropped by IPQoS for IPIP, GRE and IPSec tunnelled traffic.
- The issue where unnecessary and unused accelerated connection sessions are created for ICMP pings over IPIP and GRE tunnels, has been solved.
- The issue where the Gateway may restart when experiencing high-load IPSec traffic over extended periods of time, has been solved.
- NAT ALG:
- In PPP-subnet-passthrough scenarios, no transparent NAT map is added for the public DHCP subnet. As a consequence address translation is applied on the public subnet lease addresses of local hosts instead of being transparently passed through the Gateway.
- The issue where registration attempts of Windows Messenger 5.1 are not handled correctly by the SIP ALG when UPnP is enabled on the Gateway, has been identified as an inconsistency in the behaviour of Windows Messenger 5.1. Therefore, THOMSON advises to upgrade to the
latest version of Windows Live Messenger.
- The issue where it is not possible to set up a call for two WAN User Agents (UA) when the SIP Server is in the LAN (because the
Record-Route field was not translated), has been solved.
- The issue where the SIP ALG does not properly close connections it previously opened, or connection-related traffic doesn’t follow the predicted flow as soon as it receives a
183 Session Progress message, has been solved.
- Physical Layer - ADSL/ADSL2+:
- The issue where ATM AAL5 tracing for debugging purposes cannot be enabled on an ATM interface, has been solved.
- Services - UPnP AV / Content Sharing:
- The issue where subsequently connecting and disconnecting a disk to/from the without unmounting the disk via the GUI causes the CIFS service to stop working and access to the disk content to be lost, has been solved.
- The issue where hard disks connected via a USB hub are not recognized well for content sharing, partitions on the hard disk are not reported correctly or invisible, has been identified as due to using USB hubs that are not independently powered. When using a USB hub to connect hard disks to the Gateway, always use self-powered hubs.
- The issue where overall performance is impacted when a Windows Media Center UPnP client (e.g. on Windows Vista Home Premium or Ultimate, or Windows 7) (re-)querying all media after each renewal of the computer’s DHCP address by the Gateway DHCP server, has been solved.
- The issue where content sharing CIFS parameters (CIFS server name, workgroup name, comment) cannot be configured with strings starting with “@#” or “@”, has been solved.
- The content sharing FTP server port has been moved from the default value 21 to 51021 at WAN-side (on LAN-side the ‘traditional’ 21 port on 192.168.1.253 is kept) to avoid conflicts with the standard FTP access to the Gateway file system (at port 21 of public WAN IP address or LAN IP address).
- The issue where it is not possible to assign the standard FTP server service to a local computer via the Gateway Game and Application Sharing service due to the fact that the port 21 is assigned to remote FTP content sharing, has been solved.
- Services - Printer Sharing:
- The issue where the Gateway may restart when configuring two or more very long queue names for printer sharing, when enabling printer sharing, has been solved.
- The issue where it is not possible anymore to configure valid printer sharing queue names, once an invalid queue name was configured before (for example with an illegal character in the name), has been solved.
- VoIP - General / DECT / SIP:
- The issue where, in a scenario where DECT handsets are mapped to individual SIP accounts, all missed calls and missed call notifications are shared among all DECT handsets, instead of individual per DECT handset, has been solved.
- The issue where 3-party calls are supported only when both call legs are setup using a separate SIP account, has been solved. Note that by this solution, internal 3-party calls involving DECT handsets are supported now.
- The issue where the caller ID is not correctly shown on a phone when receiving an INVITE with P-asserted-ID (due to the fact that the P-asserted-ID does not overrule the ID from the message header), has been solved.
- The issue where, when deleting the missed calls log on a DECT handset (
menu » calls list » options » Delete all calls), the missed calls entries in the voice statistics log are actually not deleted until restart, has been solved.
- The issue where the Call Waiting service on DECT handsets is not supported, has been solved.
- The Gateway will ignore voice profiles using non-ASCII characters (i.e. non a-z, A-Z, 0-9).
- To circumvent issues with T.38 faxing, the Gateway allows to configure to allow/deny faxing traffic completely, or T.38 faxing specifically.
- The issue where the configurable VoIP waiting timer (default is 0, i.e. re-register as soon as credentials have changed) to define a time-out to re-register after failed registration, was not taken into account, has been solved.
- The issue where a DECT handset that has been recently registered to the Gateway is wrongly reported as being ‘Not Subscribed’ after restarting the Gateway (due to which no calls were possible from this DECT handset), has been solved (r8.4.2.N).
- The issue where, when uploading a modified user configuration (user.ini) or when customizing the platform software with a modified default configuration, the tone mapping will not be taken over correctly as there will always be kept parts of the old tone mappings, has been solved (r8.4.2.N).
- The issue where the Gateway may restart when receiving packets with DHCP option 120, has been solved (r8.4.2.N).
- The issue where it has been observed that, after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI, has been solved (r8.4.2.N).
- The issue where the Gateway restarts if, during at least two active external VoIP calls the DSL line goes down, has been solved (r8.4.2.N).
- The issue where Call transfer requests from a DECT handset are not supported, has been solved (r8.4.2.N).
- The issue where the Gateway cannot register anymore after a VoIP registration attempt with credentials that fails due to receiving a “503 Service unavailable” SIP message, has been solved (r8.4.2.Q).
- The issue where, when a re-registration attempt fails due to a changed (wrong) password for the SIP proxy, subsequent registration attempts will continue to fail, even if the password is changed back again to its original (correct) value, has been solved (r8.4.2.Q).
- VoIP - SIP Server:
- The issue where, for SIP Server internal calls (i.e. from
intUA to intUA) an invite message with authentication isn’t sent after receiving a 407 “Proxy Authentication Required” SIP message, no calls are
possible anymore due to authentication failure, has been solved.
- The issue where reconfiguring an existing outboundproxy or outboundregistrar of the SIP Server via CLI returns errors, while modifying via TR-069 works fine, has been solved.
- The issue where the Gateway may restart when enabling or disabling the SIP Server while a SIP UA is enabled, has been solved.
- The issue where the ‘From’ header information in the
INVITE message is changed to an invalid, anonymous header when a call is made between two internal UAs (causing - for example - call transfers to fail), has been solved.
- GrandStream 3000 SIP phone: interoperability issues (inability to establish calls from this SIP phone to another internal UA or to a phone connected to the Gateway FXS port), has been solved.
- The issue where the default outbound proxy and registrar ports are set to 0 instead of the typical 5060 port number, has been solved.
- The issue where, if call waiting service is enabled, when during an incoming call a second incoming call is received and the first call is put on hold to answer the second call, after terminating this second call, the phone is alerted for the first call on hold, but with the CLIP number of the second call instead of the one of the call on hold, has been solved.
- Wireless:
- If the specific p-bit schemes used in VDSL2 scenarios are configured correctly, wireless performance will not be negatively impacted.
- The issue where, when MAC address-based access control is enabled, a wireless client cannot associate until the Gateway has been restarted first after successful registration into the ACL, has been solved.
- The issue where the Gateway may restart when enduring heavy local wireless traffic (for example an FTP session between a wireless client and a local computer), has been solved.
- TG121g wireless USB adapter: the issue of no connection if the Gateway is configured for WPA+WPA2 security, has been solved.
- Miscellaneous:
- The issue where the Gateway may restart in Fiber to the Home (FTTH) and (pure) VDSL2 scenarios with high-speed throughput while Ptrace is enabled, has been solved.
- The issue where errors are returned when adding ATM OAM loopback via the CLI, has been solved.
Modified Features and Optimisations:
- Wi-Fi Alliance IEEE802.11n wireless LAN certification does not allow 11n connection speed in case of WPA-TKIP, or WEP:
- When a wireless-n Thomson Gateway is configured to use WEP, or WPA-PSK, it will support both TKIP and AES. However, if a wireless-n host tries to associate using WPA-PSK TKIP, the Gateway will deny the host connection at full IEEE802.11n speeds, and allows only connection at 802.11g speed, as per the IEEE802.11n wireless LAN certification requirement by the Wi-Fi Alliance.
As a consequence, full IEEE802.11n wireless communication speed is only available for WPA-PSK with AES, or WPA2 wireless security.
- Wireless WPS button behaviour Changed:
- To avoid unintended Wi-Fi Protected Setup (WPS) actions and the consequential possibility of allowing unintended wireless hosts to join the Gateway secured local network, the wireless WPS button must at least be pushed for 600ms before the WPS pairing process is started.
- TG782(i): Reduced feature set:
The following standard features are either removed, reduced or changed to optimise memory:
- The tracelevel has been reduced to one.
- RIP is not supported.
- USB master functionality has been removed.
- SNMP and ILMI is not supported.
- Trace and debug commands for the Ethernet driver have been removed.
- KPML has been removed.
- Call logging is not supported.
- The Phone book GUI page has been removed.
ScheduleInform RPC is not supported.- Reduced Differentiated Service Delivery (DSD) functionality.
Open Issues:
Note before: unless marked otherwise, all Open Issues were reported at r8.4.2.I.
- Bridge / VLAN / Bridge Filter / Ethernet:
- The state of the bridge port is not propagated to higher layers in the Gateway. As a
consequence, in VDSL2 scenarios where the Gateway acts as DHCP client, if the VDSL2 line resynchronises, the corresponding bridge port goes down temporarily, yet this is not propagated to IP level, which means that the ARP table is not updated. When the VDSL2 line is then restored again, no traffic is possible anymore until the ARP entry to the old DHCP IP address is requested again (ARP time-out), and the ARP entries at the Central Office (CO) ISAM are updated again.
- Ethernet switch storm control and shaping (used for Ethernet switch flow control) cannot be configured and as a consequence does not work.
- Streams based on DTRC precedence do not follow the TOS precedence mapping table, mapping TOS field/precedence to an internal VBUF priority indirectly indirect to a VLAN user priority/PCP.
- The egress shaper speed can only be configured to 64kbps or 128kbps if the normalized relative speed calculation method is enabled.
- CWMP / Datamodel:
- If restarted during the delay period of a delayed platform software upgrade (indicated by the ACSs), after the restart the Gateway sends a ‘9010 Download Interrupted’ in the
transferComplete to the ACSs or simply nothing instead of resuming the platform software download. As a consequence the Gateway is not upgraded.
- Changing NAPT port mappings via the IGD data model is not possible; it is only possible to set the port mapping via TR-069 using the same internal and external port on the first attempt.
- The Gateway does not support TR-069 Upload RPC to a communicated destination via FTP/HTTP, to backup, or restore complete Gateway configurations (r8.4.2.N).
- Device Manager / Device Discovery / TR-111:
- When manually adding a local host entry to the device manager (formerly referred to as host manager) via the CLI, the device manager is unable to correctly detect the host’s IP addressing type, i.e. DHCP hosts are not recognized as such.
- The device manager (formerly referred to as host manager) sporadically reports the connection status and connection interface of local hosts incorrectly.
- DHCP / IPCP / DNS:
- It is not possible to simultaneously configure different dynamic DNS services on the same interface.
- ECO:
- Due to the fact that a Gateway may return in low-power mode too quickly after a voice call is finished, the “200 OK” SIP message cannot be sent anymore by the VoIP application. As a consequence, retransmissions of the “Bye” SIP message by the remote SIP server may be seen.
- Ethernet OAM:
- E-OAM does not work in bridged scenarios (r8.4.2.N).
- GUI / Embedded Help / Embedded Easy Setup / Lua:
- No statistics of transferred VDSL2 (i.e. only in case of VDSL2 line synchronisation) data are shown on the GUI.
- Creating port maps via the GUI with a range larger than 10000 requires a restart to be applied effectively.
- If local hosts have an unidentified IP address in Device Discovery (and hence identified with IP address 0.0.0.0) it is not possible to assign a Game, and/or Application to a user-defined IP address.
- IGMP / Video:
- High load on Gateways running GoLinux Multi-Processing (GoMP) platform software (for example, heavy LAN-to-LAN routed traffic) negatively impacts video routed zapping performance, such as too high zapping latencies and video stream errors.
- If IGMP snooping is disabled on all physical Ethernet ports of the bridge, after saving the configuration and restart, the Gateway is not able to start up anymore. If it is required to disable IGMP snooping, disable it on the bridge itself (via CLI:
:eth bridge igmpsnooping config state disabled) (r8.4.2.N).
- IP Acceleration / IP Forwarding / IP Routing:
- In routed iTV scenarios, packets are out-of-sequence on first connection creation.
- The connection reservation framework (requiring QoS labelling) and the current application-based labelling framework (for which labelling is only effective on initiated traffic from a host application) results in a situation where connections that are not initiated by a Gateway application (for example, VoIP) will not captured by the connection reservation function, hence are not guaranteed. As a workaround, labels can be created to capture incoming SIP and RTP traffic; however, make sure that the label rules for VoIP SIP and VoIP RTP traffic are lined up with the service manager configuration (i.e. the bound SIP port (typically but not necessarily 5060) and dynamic port range (by default 1024-1151, but can be configured otherwise)) are aligned at all times.
- IPSec / VPN / Tunnelling:
- Due to a missing LAN IP range, initially setting up a VPN client dial-in session manually (Use Manual Dialup) via the Expert VPN > VPN Client GUI page will fail. As a workaround, first force the LAN IP range to be updated by clicking “Use Automatic Start (Always On)”. From then on, using manual dial-in for VPN client sessions will work (r8.4.2.N).
- NAT ALG:
- File transfers using Windows Messenger during a chat session fail from internal to external site. No problems are seen for file transfers from external to internal site, or when using Live Messenger.
- The SIP ALG doesn’t interpret the “received” parameter correctly; for example, additional (incorrect) pinhole connections are created when a SIP application registers to an Asterisk SIP server.
- QoS:
- TG784(i): applying IPQoS to Internet and IPTV PVCs may cause a restart as soon as STBs connected to the Gateway are reset, or restarted.
- Services - DLNA:
- While playing a movie (located on Gateway shared content) with a DLNA client (for example, a television set), you cannot pause the movie (r8.4.2.N).
- Services - UPnP AV / Content Sharing:
- The maximum number of items the UPnP AV Media Server can profile is limited to 5000. Time and memory consumption is considerable if the full maximum of 5000 items need to be profiled by the UPnP AV Media Server.
- Services - Printer Sharing:
- When unplugging a shared printer during an ongoing print job, the Gateway may restart (r8.4.2.N).
- SNMP / Syslog:
- It is not possible to configure and/or modify the SNMPv3 access security groups.
- If the maximum number of Syslog rules (i.e. 16 rules) that have been configured are flushed via CLI, the Gateway stops responding.
- SNTP - Real Time Clock:
- The transmit timestamp is not set to 0 (zero) if the Gateway system time is invalid or unreliable.
- SNTP requests from the NTP client do not use the standard UDP port 123.
- VoIP - General / DECT / SIP:
- If CFNR is enabled for a local phone with authentication, when an external call is done to that phone, the last INVITE message using the new credentials for the forward phone number is not sent to this forward phone number but again to the original phone (r8.4.2.I only).
- It has been observed that after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI (r8.4.2.I only).
- Call transfer requests from a DECT handset are not supported (r8.4.2.I only).
- When restarting the Gateway after registering a DECT handset successfully, after the restart, the DECT handset is wrongly reported in the CLI as ‘Not Subscribed’. As a consequence, calls are not possible from this DECT handset, and it is not possible to unsubscribe the handset from the Gateway DECT base station. As a workaround, restarting the DECT handset will subscribe it again to the Gateway (r8.4.2.I only).
- The value of the SIP outbound proxy cannot be updated/overwritten by a received DHCP option 120 parameter (r8.4.2.N).
- It has been observed that the Gateway may generate and introduce a buzzing noise in the RTP stream towards connected phones (DECT and FXS phones) during three-party calls (r8.4.2.N).
- If more than one VoIP profile is configured, deleting one of the profiles may cause the profile mapping between profile and assigned phones to shift after restart (i.e. phones are not assigned to the profile as previously configured). If this happens, as a workaround, delete all profiles and recreate them one by one with correct profile mapping (r8.4.2.N).
- Pressing the DECT registration/paging button on the Gateway only launches DECT paging once every two times (r8.4.2.N).
- Via CLI it is possible to set the SIP
registerExpire value to 0 (zero); however changing this value to 3600 is not accepted via CLI, though it is possible to change the value via TR-069.
- In a scenario where DECT handsets are mapped to individual SIP accounts, all answered calls are shared among all DECT handsets, instead of individual per DECT handset.
- The following CLI commands will, if executed, flush all corresponding tone settings (to none), instead of returning them to factory default settings:
:voice tone patterntable flush:voice tone descrtable flush:voice tone eventtable flush:voice sip reponsemap flush
- If the DECT handset software upgrade file transferred during a DECT handset Software Upgrade Over The Air (SUOTA) is corrupted, the DECT handset will still accept it and perform the upgrade. As a consequence, the handset upgrade will fail, and the handset stops working after the corrupted upgrade.
- Due to the fact that the Gateway cannot distinguish internal calls from one DECT handset to another DECT handset, and identifies them as an external call, the DECT handset feature to assign a different ring tone for an incoming internal call is not functional.
- VoIP - SIP Server:
- During bootup, some values of the SIP Server are not, or not correctly loaded from default settings and/or user.ini. Affected values are:
- External UA configuration values
The order of configuring this is important due to the CLI over MBus implementation. Therefore, make sure that the external UA configuration is done after the outbound proxy and outbound registrar configuration (otherwise the external User Agent configuration is not loaded and applied).
- Registrar Bind
As a workaround, add the :mbus debug loadobjects dmtree atomic path IP.Intf CLI debug command before the registrar binding configuration (otherwise registrar binding are not configured).
- Wireless:
- Interoperability issues have been seen with the WiFi-certified WPS mechanism applied on Gateway products against the Windows 7 Native Wifi implementation.
- When using WEP encryption or WPA-TKIP wireless security, the throughput performance of the 802.11n wireless interface is lower than when using no wireless security or WPA2.
- Miscellaneous:
- No error is generated by the Thomson Gateway if a number of connections are reserved which exceeds the maximum number of connection reservations possible.
- When uploading a configuration file (user.ini), and loading this configuration via the CLI (
:config load), the SNTP configuration isn’t applied correctly.
- It has been observed that surfing to a number of different web sites while URL-based or content-based web site filtering is enabled and configured to block one or more sites (or URLs), may cause a restart (r8.4.2.I only).
- In multiple WAN connection scenarios with specific connections for specific traffic, if a particular WAN connection goes down, traffic designated for this WAN connection uses another WAN connection that may not be designed for that traffic or, in the case of (for example) a Dial-on-Demand PPP connection, continuously trigger this PPP connection to come up. In other words, the Gateway does not support configuring a service to only use a specific WAN connection and to block forwarding when that WAN connection is down (r8.4.2.N).
- Under extreme and enduring load (high, continued traffic) over a PPP connection, the Gateway has been observed to restart when the PPP connection goes down (r8.4.2.N).
|
|
02 Sep 2010
|
8.2.7
|
Platform CANT-G, CANT-J, CANT-O, CANT-W, CANT-Y, CANT-5, DANT-D
GoLinux BLI-image - CANT-G SIP : TG787(i): Z73AA8.277.bli
GoLinux RBI-image - CANT-G SIP : TG787(i): ZZ72AA8.277.rbi
GoLinux BLI-image - CANT-J : TG585(i)n: ZZBTAA8.277.bli
GoLinux RBI-image - CANT-J : TG585(i)n: ZZBSAA8.277.rbi
GoLinux BLI-image - CANT-O : TG587(i)n: ZZ1NAA8.277.bli
GoLinux RBI-image - CANT-O : TG587(i)n: ZZ1MAA8.277.rbi
GoLinux BLI-image - CANT-W MGCP : TG782(i): ZYUHAA8.277.bli
GoLinux RBI-image - CANT-W MGCP : TG782(i): ZYUGAA8.277.rbi
GoLinux BLI-image - CANT-W SIP : TG782(i): ZYUOAA8.277.bli
GoLinux RBI-image - CANT-W SIP : TG782(i): ZYUNAA8.277.rbi
GoLinux BLI-image - CANT-Y SIP : TG784: ZYU4AA8.277.bli
GoLinux RBI-image - CANT-Y SIP : TG784: ZYU3AA8.277.rbi
GoLinux BLI-image - CANT-5 SIP : TG712(i): YMHAA8.277.bli
GoLinux RBI-image - CANT-5 SIP : TG712(i): ZYMGAA8.277.rbi
GoLinux BLI-image - DANT-D SIP : TG782T: ZY6XAA8.277.bli
GoLinux RBI-image - DANT-D SIP : TG782T: ZY6WAA8.277.rbi
New Features
- Wi-Fi Alliance - IEEE802.11n 1x1 wireless LAN certification.
- IP-in-IP tunnelling support.
- TR-064 service extensions:
The TR-064 framework has been extended to allow configuration of the static WAN IP address via TR-064 with the WANIPConnection and LANHostConfigManagement parameter sets.
- Improved WPS interoperability with Windows 7:
The WiFi-certified WPS mechanism applied on all Gateway products has been extended to support the configured AP WPS functionality to improve the interoperability with MS Windows 7’s WPS implementation.
- Ethernet debug CLI command extensions:
The following expert CLI debug commands have been made available to support advanced debugging and monitoring of the Ethernet interface::ethd state
Show the state of the Ethernet interface:ethd trace
Enable ETHD tracing:ethd spool
Show memory pools:ethd sdata
Show driver data:ethd cdata
Clear driver data:ethd smode
Show interface mode:ethd stats
Show interface statistics:ethd clear
Clear interface statistics:ethd help
Display help info.
- Configurable Internet LED behaviour:
Internet LED behaviour has been made configurable via the :system config optional wanconnection=<IP interface> CLI command to decide its LED state according to not only the default WAN connection interface state, but also upon optional (fall-back, or second service) WAN connection interface states if these are configured.- By default, the behaviour is identical as before: only the default WAN connection is taken into account.
- Via defining optional WAN connections, the Gateway monitors the default WAN connection and all optional WAN connections, if configured.
- If more than one WAN IP interface is configured, the first interface that is “up” is used to affect the Internet LED.
- If both default WAN connection and optional WAN connection are not defined, the Internet LED follows the state of the Broadband LED (for example in case of bridged scenarios without Internet IP interface).
- On applicable products, if the WAN port auto-sensing feature is applied, the Internet LED behaviour based on the WAN port Auto-Sensing Lua script overrules the optional WAN connection configuration.
- ARP probing extensions:
By default, ARP probing remains RFC826 compliant. When the ARP process does initial broadcast probing and
only later on performs unicast probing, the ARP daemon has been extended and made configurable to force exclusively broadcast ARP probing.
- SIP: Busy tone when Call Waiting service enabled and phone off-hook:
When an INVITE SIP message is received for a SIP URI with an assigned voice port (i.e. UAmap exists), but the call cannot be answered (for example the phone is off-hook, yet not involved in a call), a “486 Busy” SIP message response is replied.
- TG782T: Support for wireless interface MAC address-based SSID:
TG782T platform software has been made aware of customer-specific platform flavour identification to allow setting the default wireless network name (SSID) to a value that is derived from the wireless interface’s MAC address via a new introduced _SSID_POSTFIX_LEGACY_OR_MAC environment variable.
BugFixes:
- Game & Application Sharing not supported for hosts with fixed IP address:
The issue where it is not possible to assign a Game & Application service to a local host configured with a static IP address via the GUI, has been solved.
- Cross-Site Scripting (XSS):
Various Cross-Site Scripting (XSS) flaws in the GUI have been fixed.
- ARP table overflow causes restart:
The issue where an overflow of the ARP table (for example, by DOS attack flooding the ARP table) may cause the Gateway to restart, or where due to a full ARP table, no new host connections are possible anymore, has been solved.
- UPnP port mapping too slow when port mapping list is big:
The issue where UPnP port mapping is too slow (particularly if the port map list is long, causing port mappings to fail on some applications due to a time-out), has been solved.
- The first IP address of the IPCP pool is always reserved for virtual unnumbered PPP interface:
The issue where, in an IPCP scenario with PPP set to unnumbered and DHCP to numbered, the Gateway doesn’t take the expected IP address from the DHCP pool as gateway IP address, has been solved:- By default for PPP-Public-Subnet, and PPP-Public-Subnet Passthrough, the last IP address of the received IPCP pool is used for configuring the PPP interface (i.e. virtual IP address) and the first IP address to configure the LAN interface (i.e. DHCP gateway IP address).
- The assignment of the virtual IP address to be used by the PPP interface is made configurable by the
subnetfirstip parameter (which allows to specify if the first or the last IP address from the received range is to be used to configure the PPP interface).
- IPSec / VPN / Tunnelling:
The issue where FTP transfers through a GRE, or IP-in-IP tunnel may fail because the Gateway does not forward the ACK acknowledgment packets, has been solved.
- CLI downstream transmit power wrong:
The issue where the downstream transmit power displayed via the :xdsl info expand=enabled CLI command is wrong (in fact always zero), has been solved.
- HTTP server not HTTP/1.1 compliant when using Download RPC:
The issue where the Gateway always included a host IP address 0.0.0.0 in the HTTP header in all its HTTP/1.1 request messages, causing interoperability issues with ACSs using Virtual Web hosting, has been solved.
- Dying Gasp, GoLinux-based platforms:
The issue where it was not possible to enable or disable Dying Gasp on products running a GoLinux-based platform software, has been solved. Furthermore, the following functionality has been added:- When Dying Gasp is enabled, the DSLAM is able to detect Loss-Of-Power (LOP) messages after putting down the Gateway.
- When dying gasp is disabled, the DSLAM does not detect any LOP messages after putting down the Gateway.
- ADSL1 annex B fast mode with Alcatel-Lucent NALT-D line card:
The issue where high frame loss rate (high Bit Error Ratio (BER)) in the downstream direction and many Code Violation (CV) packets have been observed if the Gateway operates in ADSL1 annex B fast mode against an Alcatel-Lucent NALT-D line card (while the problem is not seen if interleave mode is used), has been solved.
- Wireless: performance issues:
Wireless performance issues seen with the previous Main Track Slotted Release R8.2.6 (compared with
R8.2.5 performance), have been solved from this Main Track Slotted Release onwards.
- Wireless: SSID returns to the factory default:
The issue where the SSID returns to the factory default value or another unexpected value after a restart (when the SSID contains one or more spaces, or quotation marks), has been solved.
- Wireless: SSID prefix variables disappear:
The issue where the wireless SSID prefix variables disappear after running the embedded wizard has been solved.
- VoIP: Digits A-D not sent:
The issue where, when pressing digits A-D, a DTMF event is detected (and a syslog event is seen on CLI), but the event is not added in the SIP INFO message, has been solved.
- VoIP: No warning tone when dialling own number:
The issue where a caller that tries to call their own number doesn’t get a warning tone (in fact no tone at all), has been solved.
- VoIP: Call distribution changes via GUI only take effect after restart:
The issue where modifying incoming call distribution via the GUI (for example from ringing on one particular FXS phone to ringing on all FXS phones), only takes effect after restart, has been solved.
- VoIP: Ongoing reduced FXO calls cancelled on restart:
The issue where an ongoing phone call over the regular phone line via an FXO port (Reduced FXO call), set up while the Thomson Gateway is turned of (for example due to power failure), is broken off by the Gateway when registering its VoIP service after restarting (i.e. in the example when power is restored), has been solved.
- SIP: Restart when setting up a VoIP call:
The issue where the Gateway restarts whilst setting up a VoIP call (because ‘Connection Information’ comes after ‘Media Description’ in the message body of the SIP frame from the UA), has been solved.
- SIP: Interoperability extension of
NOTIFY SIP message XML body handling:In addition to ETSI ES 183 043 v1.1.1 compliant behaviour to support application/simservs+xml content type of a NOTIFY SIP message, it now also supports the text/xml content type to correctly handle non-compliant NOTIFY SIP messages. When receiving a NOTIFY SIP message, the Gateway will check the content type first and depending on this adapt its parsing to retrieve the tone to be generated.
- SIP Server: Restart required after adding/deleting an External UA:
The issue where, after adding or deleting an External UA, the Gateway must be restarted before the external UA is able to send its Register message, has been solved.
- TG782: MGCP VoIP does not support parallel G.729 calls:
The issue where there is no audio on the second call when two parallel G.729 calls are used, has been solved. Parallel calls with G.729 codec, as well as G.711 codecs are supported.
- TG782i: DSL synchronisation losses with Huawei 5100 DSLAM:
The issue where DSL synchronisation losses have been observed if a TG782i operates in ADSL2 or ADSL2+ in Interleave 16/2 mode against a Huawei 5100 DSLAM, has been solved.
- Bridge interface not shown on GUI if not in default VLAN:
The issue where a bridge interface is not shown on the GUI when this WAN-side bridge interface is not in the default VLAN, has been solved.
- TG782: restarts in certain customer-specific scenarios:
The issue where in certain customer-specific scenarios the TG782 restarts, has been solved.
General Fixes:
- DNS routing table sorting to support conditional DNS forwarding:
Sorting criteria and order is as follows:- DNS entries with domain labels are sorted first.
- If the source/source mask is specified, routes with a longer source mask have higher priority.
- When routes have an equal source mask, the routes with the lower metric are sorted first.
Changes:
- Wireless Distribution System removed from GUI:
From this Main Track Slotted Release onwards Thomson Gateway products no longer support the use of the deprecated non-standardized Wireless Distribution System (WDS) via the GUI.
Open Issues:
- Physical Layer - ADSL/ADSL2+:
- A large value of data rate spread that can exceed 5Mbps has been observed if the Gateway operates in ADSL2+ Interleave mode against an Alcatel-Lucent NVLT-C line card.
- ATM:
ATM loopback can’t work correctly and cannot capture any ATM cells at ax4000.
- Bridge / VLAN / Bridge Filter / Ethernet:
- Ethernet switch storm control and shaping (used for Ethernet switch flow control) cannot be configured and as a consequence does not work.
- VLANs are not properly configured on an Ethernet port that has been configured as non-bridge Ethernet WAN interface. This causes tagged packets to be dropped by the Thomson Gateway Ethernet switch. As a workaround, enable
unknownVLAN on the other (LAN-assigned) Ethernet ports of the switch so that the Ethernet switch is forced to flood the packets received on the WAN Ethernet port.
- When sending a unicast packet from an
unknownVlan LAN port, the learned MAC address is lost on the unknownVlan WAN port.
- CWMP / Datamodel:
- If restarted during the delay period of a delayed platform software upgrade (indicated by the ACSs), after the restart the Gateway sends a ‘9010 Download Interrupted’ in the
transferComplete to the ACSs or simply nothing instead of resuming the platform software download. As a consequence the Gateway is not upgraded.
- Changing NAPT port mappings via the IGD data model is not possible; it is only possible to set the port mapping via TR-069 using the same internal and external port on the first attempt.
- CWMP packets may not be forwarded according to QoS label rules.
- Some datamodel parameters of type ‘boolean’, ‘int’ and ‘unsignedint’ are empty in the IGD datamodel, which is not in line with TR-098 specification. This may cause problems with ACSs test scenarios.
- When the ACSs server’s DNS name is resolved by the Thomson Gateway DNS server to multiple IP addresses, the Thomson Gateway will only use the first resolved IP address to connect to the ACSs. As a consequence, CWMP actions may fail.
- It is not possible to reconfigure the Thomson Gateway DHCP server and DHCP pool configuration via the IGD datamodel with
SetParameterValues.
- DHCP / IPCP:
- The Gateway crashes when the assigned IP address of the PPP interface is part of the DHCP server’s DHCP pool range.
- Crashes have been observed when, with Device Discovery enabled (default setting), the DHCP leases are flushed whilst a high number of DHCP hosts are connected to the Gateway.
- When changing the default IP address of the Gateway via the GUI (for example from the factory default 192.168.1.254 to 192.168.1.1), the gateway IP address parameter of the Gateway DHCP server’s default DHCP pool configuration is not changed (i.e. the gateway IP address remains 192.168.1.254).
- GUI / Embedded Help / Embedded Easy Setup / Lua:
- When running the embedded Easy Setup wizard with multiple service templates (i.e. more than the standard set), when going back in the wizard (by clicking the ‘Back’ Button) until the service template list, not all templates are listed anymore.
- It has been observed that, when changing the state of a self-created firewall rule via the GUI, the actual state (enabled/disabled) may not be displayed correctly in the GUI anymore.
- Internet Explorer 8: It is not possible to switch to another user directly via clicking the user name. As a workaround, switch to another user via the User Management page (Toolbox > User Management).
- When one of the default IP addresses of the Thomson Gateway are deleted (192.168.1.254 or 10.0.0.138), running the embedded Easy Setup wizard may cause the Gateway to restart.
- On the Web Cameras GUI page (if supported and enabled) the MAC address is displayed and used instead of the camera’s IP address. As a consequence the web camera cannot be controlled via the GUI.
- The status of FXS and DECT phones is always shown as connected on the GUI Home Network page, regardless of whether phones are actually connected, or not.
- When only one LAN IP address assigned to the Gateway, it is not possible to change this IP address via the GUI.
- Once a wireless client has connected to the Gateway, it is not possible anymore to clear the ‘Allowed on WLAN’ check box on the Gateway Home Network > Devices > device’s Configure GUI page. As a consequence it is not possible to disallow that wireless client from connecting to the wireless network.
- Call logging figures shown on the Gateway Telephony > Telephony Statistics GUI page and the Telephony > Call log GUI page may not be consistent.
- IPSec / VPN / Tunnelling:
- The Gateway cannot relay IPSec packets when IKE and ESP connections are bound to a specific port in the connection bind list. As a workaround unbind IKE and ESP via the CLI.
- The IPSec VPN client cannot be configured via CLI, while it can be configured correctly via GUI pages.
- When multiple IPSec tunnels are configured, only one tunnel can be displayed as ‘running’ in the GUI, though more may actually be started.
- NAT ALG:
- In PPP-subnet-passthrough scenarios, no transparent NAT map is added for the public DHCP subnet. As a consequence, address translation is applied on the public subnet lease addresses of local hosts instead of being transparently passed through the Gateway.
- Subsequently connecting and disconnecting the Internet PPP interface may cause the Gateway to restart due to NAT template creations.
- The Gateway PPTP ALG erroneously deletes the NAT mapping after time-out expiry and no traffic passes, though the PPTP control connection exists. As a consequence, GRE data traffic from WAN cannot pass and the local PPTP client can not communicate with the WAN.
- QoS:
- Queue based rate limiting has no impact.
- PPPoE Active Discovery (PAD) messages (
PADI, PADO, PADR) do not respect the internal class setting assigned by PPP; as a consequence the derived P-bits are wrong.
- Services - UPnP AV / Content Sharing:
- Uploading files to a shared disk (with FTP WAN access enabled), connected to the Gateway fails, while downloading files is possible.
- SNMP:
- The
ifInOctets and ifOutOctets values of some interfaces (such as eth0, ethport2, ethport3, ethport4) will reset to 0 (zero) if their effective number exceeds 65535.
- UPnP / TR-064:
- The Internet connection state of VDSL2 products configured with IPoE, is unreliable and cannot be controlled via MS Windows’ Network Connection page.
- It is not possible to browse the UPnP AV Server.
- The Gateway does not support configuring WAN IP Interfaces and DNS server via TR-064.
- VoIP - General / DECT / SIP:
- The Gateway SIP ALG does not correctly handle the address translation of call forward RTP coming from a local SIP PBX on the local network.
- An FXS phone connected to the Thomson Gateway is not supplied with a release tone and polarity reversal back to “I” state after disconnecting an active call on this phone whilst an incoming call to the same phone was received during the call.
- It has been observed that after some time the VoIP configuration is returned to factory default settings, and the SIP profile settings are lost.
- When a remote platform software upgrade is triggered via TR-069, VoIP calls are terminated by sending a
BYE SIP message, which causes the SIP account to be deregistered. However, due to the fact that the Gateway is not responding to the subsequent digest authentication request of the voice platform (as it doesn’t take it into account), the other party to the call is kept hanging for several minutes, until the voice platform times out and sends a BYE SIP message to the other party.
- When
forcedFXO is provisioned, no corresponding dial plan entry added for forcedFXO calls. As a consequence, a forcedFXO call may be done over VoIP.
- When all phones (FXS phones and DECT handsets) are common and call waiting service is disabled, if a DECT handset is in a call when another incoming call is received, only the FXS phone(s) will start ringing (normal behaviour). If the DECT handset now terminates its call, it will start ringing as well for the incoming call (if still not picked up). However, when answering this call with the DECT handset, only the dial tone is heard and the FXS phone(s) will continue to ring, i.e. the call is actually not picked up at all.
- Call logs on the voice page of the GUI may not register calls correctly when an interrupted intended call (phone is picked up, no number is dialled and the phone is hung up again) from an FXS phone has been made.
- A Software Upgrade Over The Air (SUOTA) of a DECT handset is not possible when IPQoS is enabled on the Gateway.
- The voice of an ongoing call is interrupted (and not restored) on a DECT phone after a Call Waiting tone alert is received on that phone.
- The voice of an ongoing call is interrupted (and not restored) on an FXS phone after a Call Waiting tone alert is received on that phone.
- When the proxy port and/or the registration port of a voice profile are changed, after reconfiguration RTP streams are dropped.
- If, during a 3-party call, HF+0 is pressed the 3-party call is terminated.
- When, during a phone call, a second call attempt is done to the phone, generating the call waiting tone, after both the waiting call and the active calls are terminated, no release tone is generated.
- During a 3-Party call, if two of the three callers go on hook, the remaining caller does not hear a release tone (no remaining call) as expected.
- Caller Identification (CLIP) on receiving VoIP calls may not work after reducedFXO calls.
- It has been observed that after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI.
- No hold tone is generated on the called FXS phone (with call Hold service enabled) if the caller puts the call on hold.
- Subscribed DECT handsets are not listed in the DECT handset list (via the CLI command
:voice decthandset list), as well as are not listed in the datamodel. As a consequence, for example, Software Upgrade Over The Air (SUOTA) of the DECT handset may fail.
- Calls between a registered IP phone connected to the Gateway LAN and a registered FXS phone connected to the same Gateway are not possible as the dataflow is dropped by NA(P)T.
- VoIP - MGCP:
- When using the G.729 codec, setting up internal calls between two phones connected to the FXS ports is possible, yet no voice can be heard.
- Wireless:
- When using WEP encryption or WPA-TKIP wireless security, throughput performance of the IEEE802.11n wireless interface is lower than when using no wireless security or WPA2.
- Wireless clients can only associate without encryption (i.e. neither WEP nor WPA(2) are possible) on virtual access points configured on the WLAN interface when configured with multiple SSID and the virtual access point is assigned to a VLAN with separate DHCP pools.
- When the wireless hardware button is used for legacy MAC address based registration, if during the registration phase the wireless interface is disabled (e.g. via CLI), the button LED does not turn off.
- With certain wireless clients on Windows 7 it has been observed that setting up a wireless connection using the Windows 7 connect with wireless security key mechanism (as alternative to the WPS PIN method) may fail.
- Miscellaneous:
- In multiple WAN connection scenarios with specific connections for specific traffic, if a particular WAN connection goes down, traffic designated for that connection uses another WAN connection that may not be designed for that traffic or, in the case of a Dial-on-Demand PPP connection, for example, will continuously trigger the PPP connection to come up. In other words, the Gateway does not support configuring a service to only use a specific WAN connection and to block forwarding when that connection is down.
- In normal operating conditions (i.e. in cases where the Gateway is not overloaded with Ethernet WAN traffic processing), VoIP, Video, TR-069 gets prioritized over normal traffic.
- Physical layer version information cannot be read from the archive of some products.
- Unknown VLAN packets coming from the WAN are dropped when ingress filtering is enabled.
- Using Parental Control, i.e. URL-based, or content-based filtering, negatively impacts download performance.
- TG784:
- With a TG784, when an STS file is sent to the device to remove the default ATM interface (hence Ethernet WAN remains as WAN interface) and then the VLAN IDs are changed by a second STS file, if the WAN interface is attached before the LocalNetwork interfaces are attached, the IP interfaces are stopped and cannot be attached again.
- Due to the WAN auto-sensing feature added to the TG784, after upgrading from r8.2.2 to this release, LED behaviour may be incorrect in Ethernet WAN scenarios.
- TCP traffic from a TG784 configured in IPoA Routed mode, without NAT, and IP Acceleration enabled, is dropped on Alcatel-Lucent DSLAM (with ISAM version 3.6.02 or higher) because data packet length=0 is considered as bogus packets. As a workaround, disabling IP acceleration solves the issue.
- Packet loss in wireless traffic from LAN through a TG784 to the WAN may cause restart.
- Attaching, then detaching WAN interfaces on a TG784 used in an Ethernet WAN scenario, may cause the Gateway to stop responding on any management channel (telnet, FTP, GUI, UPnP).
|
|
23 Apr 2010
|
8.2.6
|
BCM6358: Platform CANT-5, CANT-G, CANT-J, CANT-O, CANT-W, CANT-Y, DANT-D
GoLinux BLI-Image - CANT-5 SIP : TG712(i): ZYMHAA8.267.bli
GoLinux RBI-Image - CANT-5 SIP : TG712(i): ZYMGAA8.267.rbi
GoLinux BLI-Image - CANT-G SIP : TG787(i): ZZ73AA8.265.bli
GoLinux RBI-Image - CANT-G SIP : TG787(i): ZZ72AA8.265.rbi
GoLinux BLI-Image - CANT-J : TG585(i)n: ZZBTAA8.265.bli
GoLinux RBI-Image - CANT-J : TG585(i)n: ZZBSAA8.265.rbi
GoLinux BLI-Image - CANT-O : TG587(i)n: ZZ1NAA8.265.bli
GoLinux RBI-Image - CANT-O : TG587(i)n: ZZ1MAA8.265.rbi
GoLinux BLI-Image - CANT-W MGCP : TG782(i): ZYUHAA8.267.bli
GoLinux RBI-Image - CANT-W MGCP : TG782(i): ZYUGAA8.267.rbi
GoLinux BLI-Image - CANT-W SIP : TG782(i): ZYUOAA8.267.bli
GoLinux RBI-Image - CANT-W SIP : TG782(i): ZYUNAA8.267.rbi
GoLinux BLI-Image - CANT-Y SIP : TG784: ZYU4AA8.267.bli
GoLinux RBI-Image - CANT-Y SIP : TG784: ZYU3AA8.267.rbi
GoLinux BLI-Image - DANT-D SIP : TG782T: ZY6XAA8.265.bli
GoLinux RBI-Image - DANT-D SIP : TG782T: ZY6WAA8.265.rbi
New Features:
- Improved GUI interoperability with Internet Explorer 8 and Google Chrome:
Several interoperability issues of the GUI when browsing the pages with Internet Explorer 8 or with Google Chrome have been solved.
- GUI text improvements:
The GUI tasks to setup the Gateway (previously “Set Up”), to restart the Gateway (previously “Restart”) and to reset the Gateway (previously “Return to Factory Default Settings”),
have been renamed to better reflect their actual behaviour. They have been respectively renamed to:- Setup my Thomson Gateway
- Restart my Thomson Gateway
- Reset my Thomson Gateway
- New Firmware Embedded Help integrated:
From this Release onwards an improved FEH is included in the platform software. It:- Introduces single-sourced, conditionalized XML sources for FEH content, facilitating customization and localization.
- Introduces single-sourced, conditionalized XML sources for FEH content, facilitating customization and localization.
New language pack iterations are made available that include a localized version of this improved FEH. However existing language packs can still be re-used and do not conflict with the new FEH framework.
- ECAN has been changed from 48ms to 64ms for G.168 compliancy:
To solve comfortable noise issues seen and to comply with G.168 (for the benefit of inferior phone equipment that produce an echo of up to 64ms), echo cancellation has been changed from the 48ms industry-standard to 64ms.
- tFTP client-based platform software upgrade mechanism:
For customers that do not deploy a CWMP/TR-069 remote device management environment, a tFTP client in running software has been implemented, supporting tFTP-DHCP mode and tFTP-PPP mode (the already featured tFTP-Manual for dual-bank Business products is not impacted).
- Support for device-specific SSID through new environment variable:
A new device-specific environment variable _SSID_WL_ACCCODE_POSTFIX has been added (equal to the last six characters of the Gateway modem access code) to allow customisation of the wireless network name (SSID) to a device-specific value based on this access code.
- Separated authentication trigger point in AAA framework:
The issue where local telnet or serial access is impossible when AAA is enabled and the remote server does not support authentication for telnet and serial access, has been solved by descoping the telnet and serial trigger authentication from the AAA module.
- Changed default CAC value to allow a maximum of two simultaneous external calls:
The default value for the CAC feature has been changed to 2 to allow a maximum of two external (incoming/outgoing) calls per Gateway. In this behaviour, a third caller (incoming/outgoing) will receive busy tone (486 BUSY message) instead of a temporarily unavailable tone (480 TEMPORARILY UNAVAILABLE message).
- SIP Server extensions for advanced CAC configuration:
The SIP server configuration has been extended to allow configuration of the maximum number of external session configuration, and configuration of response codes with customized values. This allows to - for example - support only maximum two external calls and a customized code in the response if more call sessions are requested.
- SIP Server GUI page improvements:
The SIP Server GUI page has been restructured to improve the user-experience: On the SIP Server > Configure GUI page the individual configuration for each UA has been moved to a dedicated configuration page (via an Edit link).
BugFixes:
- TG782: Corrected Broadband LED behaviour:
The issue where, when used in an Ethernet WAN scenario (i.e. one of its Ethernet ports is assigned WAN port), LED behaviour is not correctly representing the operational Internet state, has been solved.
- Improved GUI page loading:
The issue where loading the GUI home page was slowed down due to extensive and redundant Device Discovery actions, has been solved.
- Solved Thomson Gateway GUI HTTP(S) server security vulnerability:
A potential vulnerability issue where the GUI HTTP(S) server replies contain device information, i.e. “SpeedTouch WebServer 1.0” in the Server field, has been solved. The Server field in replies now contains an empty string.
- IPoE WAN connections are not shown on the Thomson Gateway Broadband Connections GUI page:
The issue where IPoE WAN connections were not shown on the BroadBand Connections GUI page, has been solved.
- Legacy front-panel button functionality is unable to disable the wireless interface after restarting:
The issue where, once the legacy front-panel button functionality is enabled, the button cannot be used for disabling the integrated wireless interface after a restart, has been solved.
- The SIP ALG does not add the NAT-ted port to the contact header when the received contact header didn’t contain a port number:
The issue where the SIP ALG does not add the translated proxy port in the contact header of SIP messages when the proxy port was not present in the original contact header of the SIP message, has been solved.
- IGMP proxy’s membership database gets corrupted with multiple Set-Top Boxes:
The issue where the IGMP proxy’s membership database (the group list that keeps track of what STB clients are using what stream) may become corrupted after some time when multiple STB clients are connected, has been solved.
- Two simultaneous incoming calls not handled correctly:
The issue where, during an incoming call that is not answered yet (phone is ringing), and a second incoming call to this phone is received, will not result in busy signal to the calling party and will ultimately fail due to no phone alerting, has been solved.
- Voice parameter lengths compliancy to TR-104:
The maximum supported lengths of the user name, password, proxy addresses, user agent domain, registrar address,... for a SIP UA configuration are now compliant to TR-104.
- It is not possible to reset VoIP profiles via the TR-104 IGD management:
The issue where triggering InternetGatewayDevice.Services.VoiceService.{i}.VoiceProfile.{i}.Reset to reset a VoIP profile does not work, has been solved.
- Adding a second SIP account via TR-069 causes the Thomson Gateway to restart:
The issue where adding a second SIP account via TR-069 caused a restart, has been solved.
- Extension for SIP response code 3xx:
The issue where the Gateway, upon receiving a SIP message 301 Moved Permanent, always resends the REGISTER message to the same, original address, instead of sending a REGISTER request to the new server address (as identified by the maddr address field in the received 301 message, has been solved.
- Customizable call waiting tone support:
The issue where the SIP UA did not support to play a specific customized call waiting tone (as received in a SIP INFO message sent by the remote SIP gateway), has been solved.
- Voice LED behaviour extensions take SIP account status into account:
When independent profiles are created for individual VoIP connections, the Voice LEDs for the particular VoIP connection now take the individual status of the profile into account instead only basing the LED status on the COMMON profile.
- Resume of call on hold fails:
The issue where, when an active call is resumed from being put On Hold, this caused the call to be dropped due to the Gateway not increasing the localSDP version when rehandling the re-invite success, has been solved.
- Fixed SIP Server problem where outgoing calls with authentication are not possible anymore after some time:
The issue where, after a single night of endurance, outgoing calls are not possible anymore (i.e. the re-invite message with proxy-authorization can not be sent by the B2BUA) while incoming calls are still OK, has been solved.
- Solved interoperability issues with Huawei SIP Server:
The issue of restarts due to the following VoIP call actions against a Huawei SIP Server server have been solved:- Picking up the phone a second time after an unsuccessful outgoing call to an unknown phone number
- Calling a busy phone number
- Waiting until ringing time-out during outgoing call that is not answered
- Solved internal SIP Server registration failure:
The issue where it has been observed that after some time the internal SIP Server registration of the voice profile list is not registered anymore, has been solved.
General Fixes:
- TG712(i), TG782(i), TG784(i): Platform-specific fixes:
On various Gateway products it has been observed that, after running the embedded Easy Setup wizard, the Gateway-specific header value “Thomson” disappeared from the configured wireless
network name (SSID). The effect was that the SSID, that should be, for example “Thomson123456”, became “123456” instead. This issue has been solved by adding the required variables in the Easy Setup service templates embedded in the Gateway.
- TG787: Physical Layer - ADSL/ADSL2+:
A new Broadcom-specific Physical Layer Retransmission modem label that can be used in a customized platform software, is available solving crashes observed when a DSL resynchronization is forced while traffic is flowing (e.g. video stream).
- GUI / Firmware Embedded Help / Embedded Easy Setup / Lua:
The issue where the GUI framework does not support auto-adjustment of column widths according to screen-resolution, web browser application, has been solved.
- NAT ALG:
The issue where the SIP ALG can not setup an RTP port map (i.e. doesn’t create the child connection) when PRACK is used by an ATA client connected to the Gateway network, has been solved.
- Services - UPnP AV / Content Sharing:
The issue where if the Content Sharing FTP Server service is enabled to allow FTP connections from the WAN to the shared media, authentication of initiated FTP sessions from the LAN will fail, has not been observed anymore.
- SNTP - Real Time Clock:
The issue where the daylight saving configuration could only be set once SNTP was synchronized at least one time with the Internet SNTP server, has been solved.
- CWMP / Datamodel:
- The issue where extensions to the IGD datamodel do not fully support adding new IP STBs (using DHCP vendor class, or possibly MAC address) to the flexiport functionality, has been solved.
- The issue where configuring IGD voice line object parameters fail if
PhyReferenceList isn’t set as the first parameter, has been solved.
- VoIP - General / DECT / SIP:
- The issue of restarts when configuring a VoIP profile with long VoIP user names and/or long SIP URIs (IMPI-compliant) via the GUI, has been solved.
- The issue where even when a VoIP profile is disabled and unregistered, (V)MWI may still be active, causing the VoIP profile to try to subscribe, has been solved.
- The issue where, if call waiting service is enabled, when during an incoming call a second incoming call is received and the first call is put on hold to answer the second call, after terminating this second call, the phone is alerted for the fist call on hold, but with the CLIP number of the second call instead of the one of the call on hold, has been solved.
- The issue where DTMF/RFC2833 packets are only sent to the first party that joined a 3-way conference call, and not to the third party of the call, has been solved.
- VoIP - SIP Server:
- The issue where deleting an Internal UA via the GUI, causes all mappings between any intUA to any extUA to be deleted instead of only the mappings for the deleted intUA, has been solved.
- The issue where the SIP Reregistration mechanism has not been corrected to avoid an immediate and incorrect SIP reregistration attempt after receiving error messages from the external SIP server (for example due to invalid IP credentials in the SIP registration message), has been solved.
- The issue where when deleting and then adding an another extUA via the GUI, or when changing the extUA interface, the SIP Server cannot trigger the registration of any extUA longer, has been solved.
- The issue where when deleting all intUAs and extUAs via the GUI, the mappings between intUAs and extUAs actually are still present, has been solved.
- The issue where in certain call transfer scenarios, the
REFER message may not properly be translated by the SIP Server, has been solved.
Open Issues:
- Physical Layer - ADSL/ADSL2+:
- TG782i against a Huawei 5100 DSLAM: DSL synchronisation losses have been observed in ADSL2 or ADSL2+ in Interleave 16/2 mode.
- GoLinux-based platform software: It is not possible to enable or disable Dying Gasp.
- High frame loss rate (high BER) in the downstream direction and many CV packets have been observed if the Gateway operates in ADSL1 annex B fast mode against an Alcatel-Lucent NALT-D line card. This problem does not appear if interleave mode is used.
- A large value of data rate spread that can exceed 5Mbps has been observed in ADSL2+ Interleave mode against an Alcatel-Lucent NVLT-C line card.
- Bridge / VLAN / Bridge Filter / Ethernet:
- VLANs are not properly configured on an Ethernet port that has been configured as non-bridge Ethernet WAN interface. This causes tagged packets to be dropped by the Thomson Gateway Ethernet switch. As a workaround, enable
unknownVLAN on the other (LAN-assigned) Ethernet ports of the switch so that the Ethernet switch is forced to flood the packets received on the WAN Ethernet port.
- When sending a unicast packet from an
unknownVlan LAN port, the learned MAC address is lost on the unknownVlan WAN port.
- CWMP / Datamodel:
- When the ACSs server’s DNS name is resolved by the DNS server to multiple IP addresses, the Gateway will only use the first resolved IP address to connect to the ACSs. As a consequence, CWMP actions may fail.
- Changing NAPT port mappings via the IGD data model is not possible; it is only possible to set the port mapping via TR-069 using the same internal and external port on the first attempt.
- CWMP packets may not be forwarded according to QoS label rules.
- Some datamodel parameters of type ‘boolean’, ‘int’ and ‘unsignedint’ are empty in the IGD datamodel, which is not in line with TR-098 specification. This may cause problems with ACSs test scenarios.
- DHCP / IPCP:
- The Gateway crashes when the assigned IP address of the PPP interface is part of the DHCP server’s DHCP pool range.
- The Gateway has been observed to crash when, with Device Discovery enabled (default setting), the DHCP leases are flushed whilst a high number of DHCP hosts are connected.
- GUI / Embedded Help / Embedded Easy Setup / Lua:
- Internet Explorer 8: It is not possible to switch to another user directly via clicking the user name. As a workaround, switch to another user via the User Management page (Toolbox > User Management).
- On the Web Cameras GUI page (if supported and enabled) the MAC address is displayed and used instead of the camera’s IP address. As a consequence the web camera cannot be controlled via the Gateway GUI.
- Housing / LEDs:
TG784: Due to the WAN auto-sensing feature added, after upgrading from r8.2.2 to this release, LED behaviour may be incorrect in Ethernet WAN scenarios.
- IP Acceleration / IP Forwarding / IP Routing:
TG784: TCP traffic configured in IPoA Routed mode, without NAT and IP Acceleration enabled, is dropped on Alcatel-Lucent DSLAM (with ISAM version 3.6.02 or higher) because data packet length=0 is considered as bogus packets. As a workaround, disabling IP acceleration solves the issue.
- IGMP / Video:
- The IGMP proxy’s membership database (the group list that keeps track of what Set Top Box (STB) clients are using what stream) may become corrupted after some time when multiple STB clients are connected. As a consequence, for example, STBs requesting the same channel will freeze whenever one of the STBs leaves the stream. A second problem is that the IGMP proxy does not send a “group specific query” when the last client leaves.
- IPSec / VPN:
- The Gateway cannot relay IPSec packets when IKE and ESP connections are bound to a specific port in the connection bind list. As a workaround unbind IKE and ESP via the CLI.
- The IPSec VPN client cannot be configured via CLI, while it can be configured correctly via GUI pages.
- When multiple IPSec tunnels are configured, only one tunnel can be displayed as “running” in the GUI, though more may actually be started.
- Business Gateways: In IPSec scenarios with NAT-T the products have a segmentation problem, i.e. in case firewall UDP checks are enabled (default setting), the second segment is always dropped. As a workaround, disable UDP checks in the Thomson Gateway firewall.
- NAT ALG:
- The PPTP ALG erroneously deletes the NAT mapping after time-out expiry and no traffic passes, though the PPTP control connection exists. As a consequence, GRE data traffic from WAN cannot pass and the local PPTP client can not communicate with the WAN.
- In PPP-subnet-passthrough scenarios, no transparent NAT map is added for the public DHCP subnet. As a consequence address translation is applied on the public subnet lease addresses of local hosts instead of being transparently passed through.
- The Gateway product’s SIP ALG does not correctly handle the address translation of call forward RTP coming from a local SIP PBX on the local network.
- QoS:
- Queue based rate limiting has no impact.
- PPPoE Active Discovery (PAD) messages (
PADI, PADO, PADR) do not respect the internal class setting assigned by PPP; as a consequence the derived P-bits are wrong.
- SNMP:
ifInOctets and ifOutOctets values of some interfaces (such as eth0, ethport2, ethport3, ethport4) will reset to 0 (zero) if the effective number exceeds 65535.
- UPnP / TR-064:
- It is not possible to browse the UPnP AV Server.
- VoIP - General / DECT / SIP:
- It has been observed that after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI.
- When forcedFXO is provisioned, no corresponding dial plan entry added for forcedFXO calls. As a consequence a forcedFXO call may be done over VoIP.
- During a 3-Party call, if two of the three callers go on hook, the remaining caller does not hear a release tone (no remaining call) as expected.
- When a a terminated active call exists on FXS1 and a second external party calls FXS1, this external party gets the busy tone. When now the existing active call is disconnected from the originating side, the FXS1 port should normally is supplied with release tone accompanied by polarity reversal back to “I” state. However instead no tone is produced at all.
- If all phones (FXS phones and DECT handsets) are common and call waiting service is disabled, if a DECT handset is in a call when another incoming call is received, only the FXS phone(s) will start ringing (normal behaviour). If the DECT handset now terminates its call, it will start ringing as well for the remaining incoming call (if still not picked up). However, when answering this call with the DECT handset, only the dial tone is heard and the FXS phone(s) will continue to ring, i.e. the call is actually not picked up at all.
- Call logs on the voice page of the GUI may not register calls correctly when an interrupted intended call (phone is picked up, no number is dialled and the phone is hung up again) from an FXS phone has been made.
- An Air-upgrade of a DECT handset is not possible when IPQoS is enabled.
- The voice of the ongoing call is interrupted (and not restored) on a phone (DECT or FXS) after a first voice Call Waiting tone alert is received on this phone.
- When the proxy port and/or the registration port of a voice profile are changed, after reconfiguration, RTP streams are dropped.
- If during a 3-party call HF+0 is pressed, the 3-party call is terminated.
- When during a phone call a second call attempt is done to the phone, generating the call waiting tone, after subsequently both the waiting call and the active calls are terminated, no release tone is generated.
- A phone call over the regular phone line via an FXO port (Reduced FXO call), set up while the Gateway is turned of (for example due to power failure), will be broken off when registering its VoIP service during restart (eg in the example given, when power is restored).
- Caller Identification (CLIP) on receiving VoIP calls may not work after reducedFXO calls.
- When the Gateway restarts during reducedFXO calls, the reregistration of VoIP after restart cancels the ongoing calls.
- VoIP - SIP Server:
- In some cases address translation is wrongly applied causing SIP packets to be dropped.
- A SIP Server transfer operation fails if an authentication invite is needed as the
RE-INVITE does not contain the Referred-By and Replaces fields anymore.
- After adding or deleting an External UA, the Gateway must be restarted before the external UA is able to send its Register message.
- Wireless:
- TG784: Packet loss from LAN to WAN may cause a restart.
- 11n: When using WEP encryption or WPA-TKIP wireless security the throughput performance is lower than when using no wireless security or WPA2.
- When configured with multiple SSID and the virtual access point is assigned to a VLAN with separate DHCP pools, wireless clients can only associate on the virtual access points without encryption; i.e. WEP, nor WPA(2) is supported in this case.
- If the wireless hardware button is used for legacy MAC address based registration, if during the registration phase the wireless interface is disabled (e.g. via CLI), the button LED is not turning off.
- When the wireless network name (SSID) contains one or more spaces, after a restart the SSID returns to its factory default value.
- Miscellaneous:
- ST620s: has been observed to occasionally restart when using the ISDN fall-back WAN connection intensively for extended periods of time.
- TG784: Attaching then detaching WAN interfaces used in an Ethernet WAN scenario, may cause the Gateway to stop responding on any management channel (telnet, FTP, GUI, UPnP).
- In normal operating conditions (i.e. in cases where the Gateway is not overloaded with Ethernet WAN traffic processing), VoIP, Video, TR-069 gets prioritized over normal traffic.
- Physical layer version information cannot be read from the archive of some products.
|
|
06 Nov 2009
|
8.2.5
|
BCM6358: Platform CANT-5, CANT-G, CANT-J, CANT-O, CANT-W, CANT-Y, DANT-D
GoLinux BLI-Image - CANT-5 : TG712(i): ZYMHAA8.250.bli
GoLinux RBI-Image - CANT-5 : TG712(i): ZYMGAA8.250.rbi
GoLinux BLI-Image - CANT-G : TG787(i): ZZ73AA8.250.bli
GoLinux RBI-Image - CANT-G : TG787(i): ZZ72AA8.250.rbi
GoLinux BLI-Image - CANT-J : TG585(i)n: ZZBTAA8.250.bli
GoLinux RBI-Image - CANT-J : TG585(i)n: ZZBSAA8.250.rbi
GoLinux BLI-Image - CANT-O : TG587(i)n: ZZ1NAA8.250.bli
GoLinux RBI-Image - CANT-O : TG587(i)n: ZZ1MAA8.250.rbi
GoLinux BLI-Image - CANT-W : TG782(i): ZYUOAA8.250.bli
GoLinux RBI-Image - CANT-W : TG782(i): ZYUNAA8.250.rbi
GoLinux BLI-Image - CANT-Y : TG784: ZYU4AA8.250.bli
GoLinux RBI-Image - CANT-Y : TG784: ZYU3AA8.250.rbi
GoLinux BLI-Image - CANT-D : TG782T: ZY6XAA8.250.bli
GoLinux RBI-Image - CANT-D : TG782T: ZY6WAA8.250.rbi
BugFixes:
- GUI Vulnerability issue:
A vulnerability issue of the Thomson Gateway GUI where a malicious user can access the Thomson Gateway, has been solved (no other information supplied).
- Cannot serve DHCP clients requesting a DHCP lease with DHCP Option 61 and hardware type 0:
The issue where the Thomson Gateway DHCP server is not able to lease IP addresses to clients (for example Set Top Box (STB)) requesting a DHCP IP address with DHCP Option 61 and hardware type 0, has been solved.
General Fixes:
- QoS:
The issue where ATM traffic shaping UBR with PCR shaping category is not enforced, has been solved.
- VoIP - General / DECT / SIP:
The issue where the voice country file setting in the default Thomson Gateway configuration is set to Australia instead of ETSI, has been solved, i.e. country file setting is ETSI.
Open Issues:
- Physical Layer - ADSL/ADSL2+:
- High frame loss rate (high Bit Error Ratio (BER)) in the downstream direction and many Code Violation (CV) packets have been observed if the Thomson Gateway operates in ADSL1 annex B fast mode against an Alcatel-Lucent NALT-D line card. This problem does not appear if interleave mode is used.
- Bridge / VLAN / Bridge Filter / Ethernet:
- VLANs are not properly configured on an Ethernet port that has been configured as non-bridge Ethernet WAN interface. This causes tagged packets to be dropped by the Thomson Gateway Ethernet switch. As a workaround, enable
unknownVLAN on the other (LAN-assigned) Ethernet ports of the switch so that the Ethernet switch is forced to flood the packets received on the WAN Ethernet port.
- When sending a unicast packet from an
unknownVlan LAN port, the learned MAC address is lost on the unknownVlan WAN port.
- CWMP / Datamodel:
- Some encrypted credentials may be readable via getting the values via the Mbus datamodel.
- Changing NAPT port mappings via the IGD data model is not possible; it is only possible to set the port mapping via TR-069 using the same internal and external port on the first attempt.
- CWMP packets may not be forwarded according to QoS label rules.
- Some datamodel parameters of type ‘boolean’, ‘int’ and ‘unsignedint’ are empty in the IGD datamodel, which is not in line with TR-098 specification. This may cause problems with ACSs test scenarios.
- The extensions to the IGD datamodel done do not fully support to add new IP Set-Top Boxes (STBs) (using DHCP vendor class, or possibly MAC address) to the flexiport functionality of the Thomson Gateway.
- Configuring IGD voice line object parameters fail if
PhyReferenceList isn’t set as the first parameter.
- DHCP / IPCP:
- The Gateway crashes when the assigned IP address of the PPP interface is part of the DHCP server’s DHCP pool range.
- GUI / Embedded Help / Embedded Easy Setup / Lua:
- Internet Explorer 8: It is not possible to switch to another user directly via clicking the user name. As a workaround, switch to another user via the User Management page (Toolbox > User Management).
- The GUI framework does not support auto-adjustment of column widths according to screen-resolution, web browser application, ... As a consequence on the GUI - for example browsing the SIP Server page using Internet Explorer - data presented in columns may be wrapped to two lines.
- On the Web Cameras GUI page (if supported and enabled) the MAC address is displayed and used instead of the camera’s IP address. As a consequence the web camera cannot be controlled via the GUI.
- Housing / LEDs:
- TG782: When used in an Ethernet WAN scenario (i.e. one of its Ethernet ports is assigned WAN port), LED behaviour is not correctly representing the operational Internet state.
- TG784: Due to it‘s WAN auto-sensing feature, after upgrading from R8.2.2 to this release, LED behaviour may be incorrect in case of Ethernet WAN scenarios.
- IGMP / Video:
- The IGMP proxy’s membership database (the group list that keeps track of what Set Top Box (STB) clients are using what stream) may become corrupted after some time when multiple STB clients are connected. As a consequence, for example, STBs requesting the same channel will freeze whenever one of the STBs leaves the stream. A second problem is that the IGMP proxy does not send a “group specific query” when the last client leaves.
- IP Acceleration / IP Forwarding / IP Routing:
- TG784: TCP traffic configured in IPoA Routed mode, without NAT and with IP Acceleration enabled is dropped on Alcatel-Lucent DSLAM (with ISAM version 3.6.02 or higher) because data packets with length=0 are considered as bogus packets. As a workaround, disabling IP acceleration solves the issue.
- IPSec / VPN:
- The Gateway cannot relay IPSec packets when IKE and ESP connections are bound to a specific port in the connection bind list. As a workaround unbind IKE and ESP via the CLI.
- The IPSec VPN client cannot be configured via CLI, while it can be configured correctly via GUI pages.
- When multiple IPSec tunnels are configured, only one tunnel can be displayed as ‘running’ in the GUI, though more may actually be started.
- NAT ALG:
- The Gateway PPTP ALG erroneously deletes the NAT mapping after time-out expiry and no traffic passes, though the PPTP control connection exists. As a consequence, GRE data traffic from WAN cannot pass and the local PPTP client can not communicate with the WAN.
- The SIP ALG can not setup an RTP port map (i.e. doesn’t create the child connection) when
PRACK is used by an ATA client connected to the Gateway network. If PRACK is disabled on the ATA client, the SIP ALG behaves normally and RTP is setup correctly.
- The Gateway product’s SIP ALG does not correctly handle the address translation of call forward RTP coming from a local SIP PBX on the local network.
- QoS:
- TG787: Discard-Early doesn’t work properly.
- Queue based rate limiting has no impact.
- PPPoE Active Discovery (PAD) messages (
PADI, PADO, PADR) do not respect the internal class setting assigned by PPP; as a consequence the derived P-bits are wrong.
- Services - UPnP AV / Content Sharing:
- When the Content Sharing FTP Server service is enabled to allow FTP connections from WAN to the shared media, authentication of initiated FTP sessions from the LAN will fail.
- UPnP / TR-064:
- It is not possible to browse the UPnP AV Server.
- VoIP - General / DECT / SIP:
- It has been observed that after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI.
- The Gateway restarts when configuring a VoIP profile with long VoIP user names and/or long SIP URIs (for both, IMPI-compliancy expects to support a maximum of up to 255 characters) via the GUI. As a workaround, configure the VoIP profile via the CLI.
- Even if a VoIP profile is disabled and unregistered, (Visual) Message Waiting Indication ((V)MWI) may still be active, causing the VoIP profile to try to subscribe.
- When forcedFXO is provisioned, no corresponding dial plan entry added for forcedFXO calls. As a consequence a forcedFXO call may be done over VoIP.
- When during a phone call a second call attempt is done to the phone, generating the call waiting tone, after subsequently both the waiting call and the active calls are terminated, no release tone is generated by the Gateway.
- During a 3-Party call, if two of the three callers go on hook, the remaining caller does not hear a release tone (no remaining call) as expected.
- When a a terminated active call exists on FXS1 and a second external party calls FXS1, this external party gets the busy tone. When now the existing active call is disconnected from the originating side, the FXS1 port should normally is supplied with release tone accompanied by polarity reversal back to “I” state. However instead no tone is produced at all.
- If all phones (FXS phones and DECT handsets) are common and call waiting service is disabled, if a DECT handset is in a call when another incoming call is received, only the FXS phone(s) will start ringing (normal behaviour). If the DECT handset now terminates its call, it will start ringing as well for the remaining incoming call (if still not picked up). However, when answering this call with the DECT handset, only the dial tone is heard and the FXS phone(s) will continue to ring, i.e. the call is actually not picked up at all.
- If call waiting service is enabled, when during an incoming call a second incoming call is received and the first call is put on hold to answer the second call, after terminating this second call, the phone is alerted for the fist call on hold, but with the CLIP number of the second call instead of the one of the call on hold.
- Call logs on the voice page of the GUI may not register calls correctly when an interrupted intended call (phone is picked up, no number is dialled and the phone is hung up again) from an FXS phone has been made.
- An Air-upgrade of a DECT handset is not possible when IPQoS is enabled.
- A phone call over the regular phone line via an FXO port (Reduced FXO call), set up while the Gateway is turned of (for example due to power failure), will be broken off when registering its VoIP service during restart (eg in the example given, when power is restored).
- Caller Identification (CLIP) on receiving VoIP calls may not work after reducedFXO calls.
- The Gateway is not able to update the nonce after a failed Unregister of a phone connected to FXS (remote SIP Server sends “401 Unauthorized”) in cases where the SIP account information is used on different locations (account forking). As a consequence the unregistration of the FXS phone fails.
- DTMF/RFC2833 packets are only sent to the first party that joined a 3-way conference call, and not to the third party of the call.
- VoIP - SIP Server:
- In some cases address translation is wrongly applied causing SIP packets to be dropped.
- Deleting an Internal UA via the GUI, causes all mappings between any intUA to any extUA to be deleted instead of only the mappings for the deleted intUA.
- The SIP Reregistration mechanism has not been corrected to avoid an immediate and incorrect SIP reregistration attempt after receiving error messages from the external SIP server (for example due to invalid IP credentials in the SIP registration message).
- A SIP Server transfer operation fails if an authentication invite is needed as the
RE-INVITE does not contain the Referred-By and Replaces fields anymore.
- After adding or deleting an External UA, the Gateway must be restarted before the external UA is able to send its Register message.
- Miscellaneous:
- TG784: Attaching then detaching WAN interfaces used in an Ethernet WAN scenario, may cause the Thomson Gateway to stop responding on any management channel (telnet, FTP, GUI, UPnP).
- In normal operating conditions (i.e. in cases where the Gateway is not overloaded with Ethernet WAN traffic processing), VoIP, Video, TR-069 gets prioritized over normal traffic.
- Physical layer version information cannot be read from the archive of some products.
|
|
21 Sep 2009
|
8.2.4
|
Platform CANT-G, CANT-J, CANT-O, CANT-W, CANT-Y, CANT-5, DANT-D:
GoLinux BLI-image - CANT-G SIP : TG787: ZZ73AA8.24B.bli
GoLinux RBI-image - CANT-G SIP : TG787: ZZ72AA8.24B.rbi
GoLinux BLI-image - CANT-J : TG585n: ZZBTAA8.24B.bli
GoLinux RBI-image - CANT-J : TG585n: ZZBSAA8.24B.rbi
GoLinux BLI-image - CANT-O : TG587n: ZZ1NAA8.24B.bli
GoLinux RBI-image - CANT-O : TG587n: ZZ1MAA8.24B.rbi
GoLinux BLI-image - CANT-W MGCP : TG782: ZYUHAA88.24B.bli
GoLinux RBI-image - CANT-W MGCP : TG782: ZYUGAA8.24B.rbi
GoLinux BLI-image - CANT-W SIP : TG782: ZYUOAA8.24B.bli
GoLinux RBI-image - CANT-W SIP : TG782: ZYUNAA8.24B.rbi
GoLinux BLI-image - CANT-Y SIP : TG784: ZYU4AA8.24B.bli
GoLinux RBI-image - CANT-Y SIP : TG784: ZYU3AA8.24B.rbi
GoLinux BLI-image - CANT-5 SIP : TG712: ZYMHAA8.24B.bli
GoLinux RBI-image - CANT-5 SIP : TG712: ZYMGAA8.24B.rbi
GoLinux BLI-image - DANT-D SIP : TG782T: ZY6XAA8.24B.bli
GoLinux RBI-image - DANT-D SIP : TG782T: ZY6WAA8.24B.rbi
New Features:
- Enabling of legacy WLAN front-panel button functionality:
The WPS button on the front-panel can now be configured via CLI to possess the legacy functionality of this button:- Short press of the WLAN button:
To activate wireless client registration window (when Wireless MAC address-based access control is used for the wireless clients connecting to the Gateway).
- Long push of the WLAN button:
To enable/disable the Gateway wireless access point.
- Improved status messaging on GUI during WAN port sensing mode:
During WAN port sensing mode, instead of allowing access to the GUI (showing pending, hence possibly confusing, WAN connection information) a dedicated intercept page is shown when browsing to the GUI as long as WAN sensing is ongoing.
PPP user name length maximum extension:The maximum length of the PPP user name has been extended to be at least 128 characters.
Improved interoperability with softswitches that use non-compliant CID order:The option CIDIgnoreIncomingDDNParm is now available within the country files. It is designed to distinguish between softswitches typically specific to FCC telcos which take the DDN parameter (0x03) into account to determine the calling number that is displayed, and softswitches that use the ID parameter (0x02)
Note that depending on the option:- if
CIDIgnoreIncomingDDNParm=1 and a DDN parameter is received it will be ignored. If no normal ID parameter is received (or a NOID parameter), the calling number is undefined (“Unavailable”).
- if
CIDIgnoreIncomingDDNParm=0 and both ID and DDN parameter are received, the DDN has priority.
Maximum 10K connection number applied on Business Routers:The maximum number of simultaneous connections has been increased to 10k.
SIP user name and URI extended for IMPI support:The maximum length of the SIP user name and URI has been extended to 255 characters. Note: Configuring long user name and URI via the GUI may cause the Gateway to restart. Use the CLI to configure a voice profile instead.
Introduction of Graceful PPP termination:An option gracefulrestart in the PPP configuration has been added to trigger the Gateway to send PADT to terminate a pending half-open PPPoE session before sending PADI to re-establish the session in case it was restarted while having a PPPoE connection active.
Improved interoperability with Central Office SIP Servers for T38 faxing:The standardised behaviour according to RFC2327 and RFC4566 is that upon an SDP session modification, the versioncheck, the Gateway will decide whether it will check on the
By default the Gateway will check on the
UDP connection timers, defaults altered:The UDP idle and kill timers have been changed from 65s and 60s to 1s and 124s respectively. This allows the Gateway to recycle short-time UDP connection faster, yet by increasing the kill timer not to impact performance and total lookup time (as 65s + 60s equals 1s + 124s).
New Firmware Embedded Help integrated:An improved FEH is included in
the platform software. This FEH:- Introduces single-sourced, conditionalized XML sources for FEH content, facilitating customization and localization.
- Fixes various issues found in earlier versions (such as missing coverage for example).
Swedish VoIP country profile added:A VoIP country profile has been added to the VoIP country file to add support for voice service in Sweden.
Swedish VoIP country profile added:Via the debugger :debug exec cmd="ethd stats" CLI command, internal Ethernet traffic statistics can be read.
Increased IPQoS MaxBuffers size:The maximum buffer size (i.e. the maximum number of packets per IPQoS queue) has been increased from 128 to 256.
VPN clients supported via a Radius server:VPN clients can now connect via a preshared key while authenticating via a Radius server.
TG712:Maximum number of connections increased from 1024 to 2048: the max number of simultaneous connections has been increased from 1024 to 2048 (similar to the maximum number available on the 784) for the purpose of Routed IPTV scenarios.
TG782, TG782T:Introduction of Parental Control: only URL-based web site filtering is supported on the 782, whilst the 782T adds content-based web site filtering in addition to URL-based.
TG784:Syslog dial event manager: full Syslog functionality can be enabled and disabled via the CLI on top of the
‘residential’ Systemlog functionality.
BugFixes:
- Mapping internal to external User Agents via the GUI not OK:
The issue where modifying the mapping of internal UAs to the external UAs through the GUI is not working (and even may restart the Gateway) has been solved.
- SNMP walk via CLI causes restart:
The issue where execution of the :snmp walk CLI command may cause the Gateway to restart has been solved.
- Improved ARP mechanism to resist DOS attacks:
The ARP implementation has been improved so that DOS attacks can not flood the ARP table. Instead of not accepting new entries (hence no new connection possible) when the ARP table is full, entries with a lifetime that exceeds 75% of the time-out value are deleted at once, or--when none are found--the oldest entries first.
- P-asserted-ID if present not used as caller ID:
The issue where the caller ID was not correctly shown on a phone when receiving an INVITE with P-asserted-ID (due to the issue that the P-asserted-ID does not overrule the ID from the message header), has been solved.
- Adding a user via TR-069 causes restart:
The issue where the Gateway restarts when adding a Gateway user account via TR-096, has been solved.
- No event created when DHCP option 125 for TR-111 is not in first discover:
The issue where the manageableDevice host object corresponding to a local TR-111 client connected to the Gateway is not created in the IGD tree when the client sends a DHCP Discover message with option 125, has been solved.
- Ongoing call interruption when second incoming call received:
The issue where during an ongoing call using a DECT phone it receives an incoming call, and during the call waiting tone audio contact from the ongoing call is interrupted at the DECT phone, has been solved.
- DECT pairing via the GUI does not work:
The issue where DECT handset pairing via the GUI does not work, has been solved.
- Internet interfaces set hidden for the GUI are still available on the Dynamic DNS page:
The issue where hiding interfaces on the GUI is not effective in hiding the interface(s) in the interface list on the dynamic DNS page of the GUI, has been solved.
- Embedded Easy Setup wizard behaviour aligned across all Gateway products:
The issue where on some platforms the order in which the service templates are shown is random instead of consistently in inversed alphabetical order, has been solved.
- Voice dial plan configuration not restored when restoring configuration:
The issue where a voice dial plan config is not restored and/or applied when restoring from a previously backed up configuration, unless the Gateway is restarted after the restore, has been solved.
- Corrupted multicast address when zapping:
The issue where the multicast address may get corrupted when zapping from one channel to another several times with a Set Top Box (STB), has been solved.
- FXS phone keeps ringing if incoming FXO to FXS call hung up before FXS answered:
The issues where the FXS phone(s) keep ringing for ever, if an incoming call on the FXO port is hung up before it is answered, has been solved.
- Malformed TR-069 Inform RPC:
The issue where in the Inform RPC the ProductClass is missing in the XML sent to the ACSs, has been solved.
- RTSP NAT ALG doesn’t handle RTSP from ADB Set Top Box and Alcatel-Lucent video server:
The issue where the Gateway RTSP NAT ALG does update the payload of RTSP packets to pass NAPT, but does not open a connection and pinhole for the UDP stream to be received from the video server, has been solved.
- T.38 faxing support improved:
Various T.38 faxing issues have been solved:- The issue where a Gateway restarts when it receives a T.38 fax-over-IP call from another Thomson Gateway in the operator’s network, has been solved
- The issue where the Gateway switches to VBD instead of T.38 after a re-invite to switch to T.38, has been solved
- The issue where the Gateway is replying with malformed response tones during the T.38 fax handshake, has been solved. Instead of sending three cut tones, it sends one consistent tone at 2100Hz, at 2.6 seconds until 4 seconds within 1.8 to 2.5 seconds after receiving the first
tone.
- Bootstrap inform events sent twice to ACSs when using DHCP option 43:
The issue where the Gateway - configured for using DHCP option 43 to receive the ACSs’s URL dynamically - sends a bootstrap inform twice when the ACSs URL changes to NULL, an empty string or any other non-URL value, has been solved.
- If phone picked up during incoming CLIP phase, FXS calling stops working:
The issue where FXS calls stop working when the FXS phone is picked up (to start a call) during the CLIP phase of an incoming call to this phone, has been solved.
- Invites with long a-rtpmap header cause restart:
The issue where the Gateway is not able to properly handle SDP attributes bigger than 2048 bytes (for example, invites are received with long a=rtpmap header), causing it to restart, has been solved.
- RTSP ALG improvement:
The issue where a connection was created, even when a video server refuses an RTSP setup request, and
replies with a “500 Internet Server Error” or “404 Not Found” message, has been solved.
- TG782:
Power LED doesn’t always turn on after restart: the issue where the power LED doesn’t always turn on after restart, has been solved.
- TG712, TG784:
Improved robustness within customer-specific network/service scenarios: the issue of restarts occurring due to the internal scheduling of Gateway processes has been solved by changing some internal guarding parameters.
General Fixes:
- ADSL/ADSL2+: Physical Layer:
- The issue where a Gateway synchronized at ADSL reports the wrong Downstream Max Margin values (often referred to as SNR) via EOC when the actual margin value is higher than the defined maximum value, has been solved.
- Interoperability issues against Alcatel-Lucent’s EBLT-C and some Infineon-based DSLAM using ADSL2 Annex M, causing the Gateway not being able to synchronize, have been solved.
- “ADSL MIPS inactive. Sending Ping” in xdsl logging: the issue where it has been observed that the Gateway often refuses to start DSL synchronization due to internal timing mismatches, has been solved.
- Interoperability issues against some Infineon-based DSLAM (e.g. Lucent72) using ADSL2 Annex M, where the Gateway doesn’t apply powercut back hence causing DSL line instabilities such as multiple re-initialization of the line, line drops, and failures to synchronize on all loop lengths up to 1.5 km, have been solved.
- The issue where Annex L mask 2 is out of the ITU-T specification, has been solved.
- Interoperability issues against Huawei 5300 Connexant EADB and Fujitsu DSLAM using ADSL2 Annex M with ANFP mask set, causing low upstream performance of the Gateway, have been solved.
- The issue where certain DSL multimode configuration changes (for example disabling Annex M on a single ADSL2 flavour instead of both ADSL2 and ADSL2+) are not taken into account after restarting the Gateway, has been solved.
- The issue where the Gateway may synchronize twice (first as defined in the factory default mode, and possibly a second time if the DSL mode is configured non-default in the configuration) due to internal timing mismatches, has been solved.
- Some interoperability issues that have been observed in case the Gateway operates in G.Lite mode, have been solved by an updated G.lite-robust modem label.
- ATM:
The issue where heavy up- and download ATM traffic may cause the Gateway to not respond on the GUI, has been solved.
- CWMP:
- The issue where the secure storage
VARIANT_ID and/or PRODUCT_ID info is not taken into account during remote platform software upgrades, has been solved.
- The issue where remote platform software upgrades are blocked due to erroneous state checks (i.e. activation of the upgrade delay) when receiving non-platform software upgrade files (e.g. STS-files), has been solved.
- The issue where the value range of the CWMP QoS label is limited to [1, 15] in the CLI and where, as a consequence, since the QoS implementation in the Gateway in fact uses 16 internal classes it is not possible to set the CWMP QoS label to zero (0), has been solved.
- Daylight Saving Time:
The issue where the daylight saving implementation only takes into account the earth’s Northern hemisphere, and cannot be used for southern hemisphere daylight saving schemes (where daylight Saving is active between September and April), has been solved.
- DHCP:
The issue where local DHCP clients are unable to access the Internet due to invalid ARP entries in the Gateway ARP table if it is configured for PPP-to-DHCP subnet mode with IPCP subnet spoofing (PPP numbered and DHCP unnumbered), has been solved.
- Dynamic DNS:
The issue where using mulitple Dynamic DNS host names on the same WAN connection was not possible, has been solved.
- Device Discovery / TR-111:
- The issue where the DHCP atomic plugin does not event
Lease RxOptions, where as a consequence if static DHCP leases RxOptions are made available via DHCP discover/request messages, they are never made visible afterwards in the atomic datamodel (hence breaking TR-111 in case of static DHCP leases--where lease object exists on startup but options are only retrieved later--from a use-case perspective), has been solved.
- The issue where, after sending many (different) DHCP discover (and request) packets from different hosts, the Gateway mat restart due to a memory pool depletion, has been solved.
- The issue where Ethernet WAN hosts may be shown by the host manager in both CLI and GUI, has been solved (sic).
- The issue where the host manager starts mixing up the device names of connected hosts as soon as the host name of one of the connected hosts changes, has been solved.
- The issue where the host manager sporadically reports connection status and connection interface of local hosts incorrectly, has been solved.
- Easy Setup:
The issue where, if using a $ in an Embedded Easy Setup service template to use the
value of an existing variable, the string itself, i.e. “$variable_name”, is being used instead of the value of that variable, has been solved.
- GUI:
- The issue where during a GUI-initiated restart (Home > Thomson Gateway > Restart my Thomson Gateway), the GUI may be displayed improperly for some time, has been solved.
- The issue where when two WAN connections are active (with Hyper-NAPT enabled), assignments of the public IP address to local hosts are not or are incorrectly shown on the GUI, has been solved.
- The issue where it is not possible to assign a public IP address to a local host when two (or more) IPoE interfaces are configured as WAN connection, has been solved.
- The issue where it is not possible to backup configurations via the GUI, has been solved.
- The issue where configuring an additional virtual wireless access point (M-SSID) allows to enable/disable multicast from WAN filtering (“Allow multicast from Broadband Network”) and actually enables/disables filtering on all (default and virtual) wireless access points, has been solved. Now the user can enable/disable multicast filtering only for the default wireless access point.
- The issue where the default English Firmware Embedded Help and its localized versions, provided via the language packs contains redundant references to (unavailable) images, has been solved.
- IGMP / Video:
The issue where duplicate TCP ACKs during an RTSP over TCP video stream cause the Gateway to respond with an RTSP message (“400 - Bad Request”) to the local host’s RTSP GET_Parameter to the RTSP server (causing the video on the local host to eventually stall) (continuous buffering or stop), has been solved.
- NAT ALG:
- The issue where the RTSP NAT ALG is not able to correctly translate 10.0.0.0/24 destination addresses in SETUP messages to the appropriate WAN address, has been solved.
- The issue where the Gateway NAT ALG still creates the connection, though the video server refuses an RTSP setup request, and replies with a “500 Internet Server Error” or “404 Not Found” message (meaning that a next RTSP setup request will be refused by the ALG as the internal port is the same and in use), has been solved.
- The issue where in a scenario with more than one PVC, in which one is dedicated for voice traffic, even with the use of routing labels, child connections are not being triggered by the SIP ALG, cannot be reproduced.
- QoS:
The issue where TOS marking works incorrectly when IP Acceleration is enabled, has been solved.
- SNMP:
The issue where an SNMP walk that includes ATM-related nodes (OID=OID=1.3.6.1.2.1.37) or an SNMP get of ATM-related nodes (OID=OID=1.3.6.1.2.1.37) causes the Gateway to restart, has been solved.
- TR-064:
The issue where the wireless interface cannot be controlled via TR-064, and where getting and setting wireless interface parameters via TR-064 may return wrong values and cause wrong wireless interface configurations, has been solved.
- UPnP:
- The issue where the Gateway UPnP framework did not report connectivity to the WAN over ETHoA (Ethernet over ATM), causing the UPnP Internet Connection state shown on a connected PC to be wrong, has been solved.
- The issue where the UPnP framework does not support multiple WAN IP connection devices when multiple WAN IP connection objects are present in the IGD tree, UPnP will not be able to show them (sic).
- Wireless:
The issue where if the Gateway is configured with multiple SSID, the default WPA key configuration per virtual SSID all use the same _WL0_WPAKEY_SERIAL instead of the default built-in indexed MSSID _WLx_WPAKEY_SERIAL environment variables, has been solved.
- VLAN:
The issue where in some circumstances the VLAN configuration may be corrupted or incomplete after restarting the Gateway, has been solved.
- VoIP:
- The issue where the Gateway may restart when VoIP calls are established during heavy FTP traffic, has been solved.
- The issue where when a lot of TCP traffic up or down and a video stream is running at the same time, after a while (5 to 10 minutes) the VoIP RTP signalling still works, but no audio communication is possible anymore in either direction, has been solved.
- The issue where the Gateway does not start the warning tone when receiving a SIP 603 message (and only produces a short bleep) has been solved.
- The issue where the Gateway restarts as soon as it receives a SIP 606 message, has been solved.
- The issue where creating a voice profile via CLI causes the Gateway to restart, has been solved.
- The issue where the Gateway sends a specific ‘disconnect’ / ‘remote party onhook’ kind of signal for handling line reversal when starting the busy tone, causing a line reversal change to reverse polarity to be triggered, has been solved.
- The issue where the Gateway generates a warning tone instead of the release tone when during a phone call the remote end goes on hook (event 25), has been solved.
- The issue where after negotiating the codecs for RTP (
INVITE and 200OK messages), if the Gateway receives the first RTP packet in a codec different than the one originally offered on 200OK message, no voice communication is possible, has been solved.
- The issue where DTMF tones are clipped and not recognized in a 3-way conference call using G.711, has been solved.
- TG784:
- The issue where TR-069 SLA IP ping diagnostics fail on the Ethernet WAN interface, has been solved.
- The issue where a VoIP configuration, if configured via the GUI, is not saved (and hence lost after restart), has been solved.
- TG784:
The issue where when the SIP server configuration is changed due to the WAN auto-sensing Lua scripts, the SIP Server doesn’t add the necessary transparent NAT entries for its ExtUAs, with as a consequence that the SIP Server cannot register its UAs, has been solved.
Open Issues:
- ADSL/ADSL2+ - Physical layer:
High frame loss rate (high BER) in the downstream direction and many CV packets have been observed if a Gateway operates in ADSL1 annex B fast mode against an Alcatel-Lucent NALT-D line card. This problem does not appear if interleave mode is used.
- Content Sharing FTP Server service fails:
When the Content Sharing FTP Server service is enabled to allow FTP connections from the WAN to the shared media, authentication of initiated FTP sessions from the LAN will fail.
- CWMP / Remote Management:
- CWMP packets may not be forwarded according to QoS label rules.
- Some encrypted credentials may be readable by getting the values via MBUS.
- DHCP:
- When the assigned IP address of the PPP interface is part of the DHCP server’s DHCP pool range, the gateway will crash.
- GUI:
- The GUI framework does not support auto-adjustment of column widths according to screen-resolution, web browser application, ... As a consequence, (for example browsing the SIP Server page using Internet Explorer) data presented in columns may be wrapped to two lines.
- (MSIE8): It is not possible to switch to another user directly via clicking the user name. As a workaround, switch to another user via the User Management page (Toolbox > User Management).
- On the Web Cameras GUI page (if supported and enabled) the MAC address is displayed and used instead of the camera’s IP address. As a consequence the web camera cannot be controlled via the GUI.
- IGD:
- Configuring IGD voice line object parameters fail if
PhyReferenceList isn’t set as the first parameter.
- Changing NAPT port mappings via the IGD data model is not possible. It is only possible to set the port mapping via TR-069 using the same internal and external port on the first attempt.
- Some datamodel parameters of type ‘boolean’, ‘int’ and ‘unsignedint’ are empty in the IGD datamodel, which is not in line with TR-098 specification. This may cause problems with ACSs test scenarios.
- IGMP:
The Gateway IGMP proxy’s membership database (the group list that keeps track of what STB clients are using what stream) may become corrupted after some time when multiple STB clients are connected. As a consequence, for example, STBs requesting the same channel will freeze whenever one of the STBs leaves the stream. A second problem is that the Gateway IGMP proxy does not send a ‘group specific query’ when the last client leaves.
- IPQoS:
If IPQoS is enabled, then an Air-upgrade of a DECT handset is not possible.
- IPSec:
- The Gateway cannot relay IPSec packets when the IKE and ESP connections are bound to a specific port in the connection bind list. As a workaround unbind IKE and ESP via CLI.
- The IPSec VPN client cannot be configured via CLI, while it can be configured correctly via GUI.
- On the GUI, when multiple IPSec tunnels are configured, only one tunnel can be displayed as ‘running’, though more may actually be started.
- NAT ALG:
- The SIP ALG cannot setup an RTP port map (i.e. doesn’t create the child connection) when
PRACK is used by an ATA client connected to the Gateway network. If PRACK is disabled on the ATA client, the SIP ALG behaves normally and RTP is setup correctly.
- The SIP ALG does not correctly handle the address translation of call forward RTP coming from a local SIP PBX on the local network.
- The PPTP ALG erroneously deletes the NAT mapping after time-out expiry and no traffic, though the PPTP control connection exists. As a consequence, GRE data traffic from WAN cannot pass and the local PPTP client can not communicate with the WAN.
- QoS:
- Queue based rate limiting has no impact.
- PPPoE Active Discovery (PAD) messages (
PADI, PADO, PADR) do not respect the internal class setting assigned by PPP; as a consequence the derived P-bits are wrong.
- ATM traffic shaping UBR with PCR shaping category is not enforced.
- Traffic priority:
In normal operating conditions (i.e. not overloaded with Ethernet WAN traffic processing), VoIP, Video, TR-069 gets prioritised over normal traffic.
- SHDSL - Physical layer:
Throughput performance is negatively influenced by enabled UPnP and host manager functionality. Therefore, UPnP and host manager functionality have been disabled on SHDSL routers.
- SIP Server:
- Deleting an Internal UA via the GUI, causes all mappings between any intUA to any extUA to be deleted instead of only the mappings for the deleted intUA.
- The SIP Reregistration mechanism has not been corrected to avoid an immediate and incorrect SIP reregistration attempt after receiving error messages from the external SIP server (for example due to invalid IP credentials in the SIP registration message).
- After adding or deleting an External UA, the Gateway must be restarted before the external UA is able to send its Register message.
- In some cases address translation is wrongly applied causing SIP packets to be dropped.
- SNMP:
ifInOctets and ifOutOctets values of some interfaces (such as eth0, ethport2, ethport3, ethport4) will reset to 0 (zero) if their effective number exceeds 65535.
- UPnP:
- It is not possible to browse the Gateway UPnP AV Server.
- The Internet connection state of VDSL products configured with IPoE, is unreliable and cannot be controlled via MS Windows’ Network Connection page.
- Version info unreadable:
Physical layer version information cannot be read from the archive of some products.
- VLAN:
- VLANs are not properly configured on an Ethernet port that has been configured as non-bridge Ethernet WAN interface. This causes tagged packets to be dropped by the Gateway Ethernet switch. As a workaround, enable
unknownVLAN on the other (LAN-assigned) Ethernet ports of the switch so that the Ethernet switch is forced to flood the packets received on the WAN Ethernet port.
- When sending a unicast packet from an
unknownVlan LAN port, the learned MAC address is lost on the unknownVlan WAN port.
- VoIP:
- It has been observed that after some time, depending on the reregistration period (typically 15 to 20 days with default reregistration timer), SIP reregistration fails, hence no VoIP connection exists anymore, though the SIP account may still appear as being registered if checked via CLI and/or GUI.
- The Gateway restarts when configuring a VoIP profile with long VoIP user names and/or long SIP URIs (for both IMPI-compliancy expects to support a maximum of up to 255 characters) via the GUI. As a workaround, configure the VoIP profile via the CLI.
- The voice country file setting in the default configuration is set to Australia instead of ETSI.
- When a VoIP profile is disabled and unregistered, (V)MWI may still be active, causing the VoIP profile to try to subscribe.
- When forcedFXO is provisioned, no corresponding dial plan entry added for forcedFXO calls. As a consequence a forcedFXO call may be done over VoIP.
- When during a phone call a second call attempt is done to the phone, generating the call waiting tone, after subsequently both the waiting call and the active calls are terminated, no release tone is generated.
- During a 3-Party call, if two of the three callers go on hook, the remaining caller does not hear a release tone (‘no remaining call’) as expected.
- When a a terminated active call exists on FXS1 and a second external party calls FXS1, this external party gets the busy tone. When now the existing active call is disconnected from the originating side, the FXS1 port should normally be supplied with release tone accompanied by polarity reversal back to “I” state. Instead, no tone is produced at all.
- In case all phones (FXS phones and DECT handsets) are common and call waiting service is disabled, if a DECT handset is in a call when another incoming call is received, only the FXS phone(s) will start ringing (normal behaviour). If the DECT handset now terminates its call, it will start ringing as well for the remaining incoming call (if still not picked up). However, when answering this call with the DECT handset, only the dial tone is heard and the FXS phone(s) will continue to ring, i.e. the call is actually not picked up.
- If call waiting service is enabled, when during an incoming call a second incoming call is received and the first call is put on hold to answer the second call, after terminating this second call, the phone is alerted for the fist call on hold, but with the CLIP number of the second call instead of the one of the call on hold.
- Call logs on the voice page of the GUI may not register calls correctly when an interrupted intended call (phone is picked up, no number is dialled and the phone is hung up again) from an FXS phone has been made.
- A phone call over the regular phone line via an FXO port (Reduced FXO call), set up while the Gateway is turned off (for example due to power failure), will be broken off on restart (when registering its VoIP service).
- CLID on receiving VoIP calls may not work after reducedFXO calls.
- The Gateway is unable to update the nonce after a failed Unregister of a phone connected to FXS (remote SIP Server sends “401 Unauthorized”) in cases where the SIP account information is used on different locations (account forking). As a consequence the unregistration of the FXS phone fails.
- DTMF/RFC2833 packets are only sent to the first party that joined a 3-way conference call, and not to the third party of the call.
- VPN:
The IPSec VPN client cannot be configured via CLI, though it can be configured correctly via the GUI.
- Wireless:
- Long-time heavy wireless traffic to WAN may cause the Gateway to crash.
- If the Gateway is configured with multiple SSID and the virtual access point is assigned to a VLAN with separate DHCP pools, wireless clients can only associate on the virtual access points without encryption; i.e. neither WEP, nor WPA(2) is supported in this case.
- When using WEP encryption or WPA-TKIP wireless security, the throughput performance of the 802.11n wireless interface is lower than when using no wireless security or WPA2.
- TG605s:
When using QoS labels to rewrite the tos/dscp/precedence fields, the corresponding field is set to 0x00 instead of the configured value in case the incoming packet has already tos/dscp/precedence values equal to the value to be set. In all other cases the value is rewritten with the configured value.
- TG628s:
- On the WAN statistics GUI page (Expert > Thomson Gateway > Diagnostics > WAN > Statistics) wrong CRC values are shown.
- Reports wrong or incomplete SHDSL MIB SNMP info.
- Tip/Ring Reversal does not follow ISAM5 link configuration.
- While EFM 4-pair performance is good, ATM 4-pair performance for small frames is lower than expected.
- Sporadically it may have problems to synchronize its SHDSL lines. To solve, detach and re-attach the DSL interface.
- The DSL-1 port connector layout is wrong. Currently, the following connector pinning is applied:
- Link0: DSL-0 3&4 (inner pair)
- Link3: DSL-0 2&5 (outer pair)
- Link1: DSL-1 2&5 (outer pair)
- Link2: DSL-1 3&4 (inner pair)
i.e. Link1 and Link2 are inverted, as for these the connector pinning should be as follows:- Link1: DSL-1 3&4 (inner pair)
- Link2: DSL-1 2&5 (outer pair)
Possible consequences are:- In EFM mode, the sequence of the links doesn’t matter at all, and in ATM mode, Auto-Master enabled, the sequence of the links are automatically arranged, so once again the inversion doesn’t matter.
- If the CO side is also using Infineon’s chips, based on Infineon’s internal mechanism, the link sequence will not affect connections. Any other chip used at CO side (eg Conexant) can cause an issue. Fixes are to either use Auto-Master, or to cross-connect the cables of link1 and link2 at the DSLAM side.
- TG782:
If is used in an Ethernet WAN scenario (i.e. one of its Ethernet ports is assigned WAN port), LED behaviour is not correctly representing the operational Internet state.
- TG784:
- Packet losses in wireless traffic from LAN through to the WAN may cause a restart.
- Subsequently attaching and detaching WAN interfaces used in an Ethernet WAN scenario, may cause the Gateway to stop responding on any management channel (telnet, FTP, GUI, UPnP).
- TCP traffic configured in IPoA Routed mode, without NAT and IP Acceleration enabled is dropped on Alcatel-Lucent DSLAM (with ISAM version 3.6.02 or higher) because data packed length=0 is considered as bogus packets. As a workaround, disabling IP acceleration solved the issue.
- Due to the WAN auto-sensing feature added, after upgrading from r8.2.2 to this release, LED behaviour may be incorrect in Ethernet WAN scenarios.
- TG787:
Discard-Early doesn’t work properly.
|
Copyright Statement
Compilation, original writings & design Copyright ©2002 - 2013 Modem-Help, Ltd.
All trademarks respected as the property of their respective owners.
Full Copyright + Disclaimer statement
|
