Common Support Hints
Common Support Hints

Common Support Hints




General Support News

  • Setting up a VRRP group [16/03/2010]
    This document describes how to set up a VRRP scenario (Virtual Router Redundancy Protocol).

 

 

 



Known Issues with LCOS/LCMS

  • 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 software/options

    • Current: LANCAPI 7.90 RC and ISDN point-to-point [04/19/2010]
      LANCAPI notifies an incoming call to applications which do not have registrered for LANCAPI messages with 'LISTEN' at call setup time (SETUP).

    • Current: LANCAPI 7.90 RC and ISDN point-to-point [04/19/2010]
      At DSS1 ISDN point-to-point landlines direct dialing in digits (OverlapReceive) are not passed to the listening application.

     

    • Current: 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. Thw new RC2 (1.24) firmware for the LANCOM GS-1224 solves this issue and can be downloaded here.

    • Current: Activation problems with the LANCOM Advanced VPN Client [12/29/2008]
      A mistake in the production process has caused a number of VPN Clients to be shipped with an incorrect combination of serial number and license key. If you are having problems with the activation of your VPN Client, you can generate the correct combination of your serial and licence number here.






LOGIN »