Common Support Hints

• General Support News
• Known Issues with LCOS/LCMS
• Known problems with Advanced VPN Client
• Known problems with options/LANCAPI/fax modem/dial-in connections

General Support News

• Setting up an Internet connection using a UMTS/3G USB modem [10.01.2012]
  This document describes how to set up a connection to the Internet on a LANCOM router using a UMTS/3G USB modem.

• Configuring the Seamless Roaming function in the LANCOM Advanced VPN Client [07.12.2011]
  This document describes the configuration steps required to use the Seamless Roaming function in the LANCOM Advanced VPN Client.

  Seamless Roaming automatically switches the VPN tunnel to another Internet transmission medium when required. If, for example, a notebook using a wireless LAN or UMTS/3G connection is inserted into a docking station, the connection automatically switches to LAN. The IP address is retained so that an application communicating over the VPN tunnel can remain operational without interruption.

• Centralized firmware management with LANCOM WLAN controllers [09.11.2011]
  LANCOM WLAN controllers provide various options for updating the centrally managed firmware in managed LANCOM access points. The following approaches are possible.

• Setting up load balancing for multiple Internet connections on a LANCOM router with an integrated DSL modem [07.10.2011]
  This document describes how to set up load balancing on LANCOM routers that have an integrated DSL modem.

• Certificate-based wireless LAN connection with 802.1x (EAP-TLS) authentication and LANCOM RADIUS server [02.09.2011]
  This document describes how to set up a certificate-based wireless LAN connection (802.1x) where authentication between wireless LAN client and LANCOM access point is performed using the Extensible Authentication Protocol (EAP) and the Transport Layer Security (TLS) method of authentication. TLS is an established method (supported since the introduction of Windows XP) for server and client to exchange certificates.

Known Issues with LCOS/LCMS

• Prevent the termination of WLAN connections by configuring an alive test

  [11.07.2011]

  Some of the current LANCOM WLAN routers and access points with LCOS 8.5 or earlier, which are to receive new firmware or extensive new configurations over the wireless LAN interface, may under certain circumstances suffer from a loss of connection to the WLAN. The result of this error is that the wireless link is interrupted and, in the worst case—such as with an outdoor point-to-point link—the device may lose contact completely. In this case, reestablishing the radio link would require a manual restart of the remote device by pressing the reset button. To prevent this we recommend to configure an alive test before uploading a new firmware.

• LANCOM WLC-4006: WPA version WPA2 cannot be operated with LCOS 8.50 [19.05.2011]

  When equipped with firmware LCOS 8.50, the WLAN controller model LANCOM WLC-4006 does not operate with the WPA version WPA2.

   

  Even though WPA2 can be selected in the configuration dialog WLAN controller -> Profiles -> Logical WLAN networks (SSIDs), this entry is lost when the firmware is written back to the router's configuration.

   

  We recommend the alternative of selecting the WPA version WPA 1/2. Working with WPA 1/2 does not represent a security risk as this mode also allows you to operate with highly secure AES encryption.

   

  Information:

  If you select the WPA2 in the WPA-version field and write this configuration back to the LANCOM router, an error message is issued because the firmware does not recognize the value WPA2. In this case, set the WPA version to WPA 1/2.

   

  This limitation will be resolved in a coming LCOS release update.

• Update: DynDNS services working properly again [30.08.2010]

  Last week occured problems when using LANCOM routers with firmware LCOS 7.x in conjunction with DynDNS. These problems were caused by a change in the DynDNS server settings. Friday evening, DynDNS changed the settings of their servers back to the previous configuration. Since then, all DynDNS Hosts have been updated properly again.

  In the medium run, though, DynDNS plans to switch their dynamic DNS services back to these settings. In the meantime, we are working closely together with DynDNS to find a solution for the problems that had occurred.

  We will inform you prior to the next switch in settings of DynDNS, and provide the necessary firmware updated for your devices.

   

  No update of Dynamic DNS accounts with DynDNS as provider [27.08.2010]

  Since August, 25, 2010, we have noticed increasing problems with customers using LANCOM routers with firmware versions LCOS 7.x in conjunction with DynDNS. These problems may result in DynDNS Hosts not being updated anymore. As a consequence, some LANCOM devices may not be accessed under their names anymore, and VPN connections using DynDNS domain names as IKE identities (FQDN) risk to fail.

  These problems only occur when using the services of DynDNS in conjunction with LANCOM devices running on firmware versions LCOS 7.x.
  
  

  Solution:

  Updating your LANCOM device to LCOS 8.0 will solve the problem. Should your device support LCOS 8.0 we, therefore, recommend you to update your LANCOM router to the latest version of our operating system.

  For devices that don’t support LCOS 8.0 we will shortly present a solution.

  Please note: When using dynamic DNS services, we generally recommend you to use a second provider as a backup. This will considerably improve the availability of the services.
  
  

  Should the error still occur despite the update to LCOS 8.0, please verify that your DynDNS account has not been blocked. Since August, 25, 2010, a maximum of two hosts and 18 domains have been allowed on the free accounts.

• Limited support of unattended call transfer

  With the LANCOM VP-100, a call on hold can be transferred unattended by entering the target telephone number and immediately pressing the "Transfer" key. Analog or ISDN telephones generally do not have a special key or menu option for direct unattended call transfer.

   

  Solution:

  A full implementation requires a control mechanism, such as hanging-up while dialing or ringing from analog or ISDN telephones. This will be implemented in a future version of LCOS.

• Call forwarding (i.e. automatic call transfer) from various SIP devices functions with restrictions only, or not at all

  For some SIP phones, pressing the hash key ("#") while dialing with an off-hook handset or with an activated speakerphone function triggers immediate dialing. This means that controlling PBXs with the hash key is either not possible, or it can be used for the first character only.

   

  The LANCOM Advanced VoIP Client does not signal an asterisk (*) in the SIP-URI when establishing a call if the sequence ends in a hash.

   

  Solution:

  Generally speaking, telephone numbers that include control codes (keypad facilities) can be entered into SIP telephones even when the handset is on-hook or when the speakerphone is not active. Picking up the handset or activating the speakerphone then initiates dialing. This method is suitable for controlling PBX functions.

   

  The VoIP Call Manager now also supports control by this method if the keypad-facility control code does not end with the hash "#" sign. In this way, keypad facilities can be used with the LANCOM Advanced VoIP Client as well.

   

  Examples

   

  Set up immediate call forwarding to the telephone number 504:

  *21*504# can alternatively be actvated with *21*504

   

  Temporarily disable immediate call forwarding:

  #22# can alternatively be set with #22

• ISDN facilities for automatic call forwarding not supported

  Automatic call forwarding with ISDN telephones cannot be operated via the ISDN facilities (functional protocol) but by entering keypad facility code sequences instead, e.g. "#21#".

   

  Solution:

  An upgrade to include the ISDN functional protocol is planned for a future version of LCOS. Please use the code sequences (keypad facilities) that are described in the documentation.

• Reboot when a configuration is changed during a telephone call

  If the configuration is changed during a telephone call, the router reboots under certain conditions.

   

  Solution:

  The problem will be fixed in a following release update of LCOS.

 

• Changes in the COM Port server due to compliance with RCF 2217 may lead to communication failure in some cases

  As from LCOS 7.70 a change in handling was introduced to comply with RFC 2217. This may lead to communication problems with some client software emulating a virtual COM port.

   

  Solution:

  The following KnowledgeBase document describes a workaround, how to read out e.g. phone system information using an LCOS 7.70, though.





Known problems with Advanced VPN Client

• LANCOM Advanced VPN Client Mac OS X 2.01 [08/24/2011]
  With Mac OS X Lion (10.7) errors in displaying the client may occur up to version 2.01 of LANCOM Advanced VPN Client for Mac OS X. Esp. the client monitor (window) might disappear.

  Solution:

  Please use the software version 2.02. Download






Known problems with
options/LANCAPI/fax modem/dial-in connections

• LANCAPI 8.00 and ISDN point-to-point [11/22/2010]
  LANCAPI notifies an incoming call to applications which do not have registrered for LANCAPI messages with 'LISTEN' at call setup time (SETUP).


• LANCAPI 8.00 and ISDN point-to-point [11/22/2010]
  At DSS1 ISDN point-to-point landlines direct dialing in digits (OverlapReceive) are not passed to the listening application.


• Problems using LANconfig and LANCAPI with LANCOM GS-1224 [03/17/2010]
  LANCOM devices connected to the GS-1224 cannot be correctly detected by LANconfig and used with LANCAPI.  A new firmware 1.24 or higher for the LANCOM GS-1224 solves this issue and can be downloaded here.