How to use Voice callback for receiving login authentication codes

Background: 

 If you have SMS enabled as two-factor authentication method, you may use Voice callback to receive your login authentication codes. This article will provide you steps on how to select voice callback when logging in to our platforms.

 

How to use Voice callback
 
You may select Voice if you do not receive your login authentication code. You will then receive your login authentication code via an automated callback. Follow the instructions below, depending on which platform you are trying to login to.
 

 

Client Portal

1. Click on "Didn't receive a security code?"

2. From the two options, select "Voice" and wait for the callback.

3. After selecting Voice, you should receive the callback within a minute. Please wait for the callback and be ready to write down the code that will be provided over the callback.

 

TWS

1. Click on "Request new Security Code"

2. From the two options, select "Voice" and click on OK. Then wait for the callback.

 3. After selecting Voice, you should receive the callback within a minute. Please wait for the callback and be ready to write down the code that will be provided over the callback.

Note: Voice callback for the TWS is only available in the LATEST and BETA version.

 

IBKR Mobile - iOS

1. Click on "Request New Code"

2. From the two options, select "Voice" and wait for the callback.

 3. After selecting Voice, you should receive the callback within a minute. Please wait for the callback and be ready to write down the code that will be provided over the callback.

 

IBKR Mobile - Android

1. Click on "Request New Security Code"

2. From the two options, select "Voice" and wait for the callback.

 3. After selecting Voice, you should receive the callback within a minute. Please wait for the callback and be ready to write down the code that will be provided over the callback.

 

References:

 

IB Key Challenge / Response method and missing notifications

In case your smartphone is unable to receive IB Key notifications, you can still complete the login process using the IB Key Challenge/Response method, described on the following pages (according to your device operating system):

The same information applies to you if your phone has no Internet connectivity (you are in roaming, out of coverage, without an active mobile data plan, etc.)

If your smartphone is unable to receive IB Key notifications despite having Internet connectivity, we recommend you to perform the steps outlined in IBKB3234.

 

How to fix the "Cannot create ... file" error during TWS installation on MacOS

Background: 

The filesystem permissions are controlled by your machines operating system. One of their functions is to secure your files, preventing unauthorized access or undesired modifications to the system and to your personal data.   

Some software on your computer may modify or override the permissions assigned by the operating system. Under certain circumstances, this prevents the TWS installer from accessing the folder where the application core files have to be created (/users/youruser/home/Applications). In such cases, the TWS installation usually displays the error "Cannot create ... file. Shall I try again?"

In this article we explain how to reset the filesystem permission of the "Applications" folder located under your user home folder in order to allow a smooth run of the TWS installation.
 

Procedure:

 
1. On your keyboard, press ⌘CMD + ⇧Shift +H to open your home folder
 Figure 1
 
2. Select the folder "Applications" within your home folder and press ⌘CMD + I to open the Info panel
 Figure 2
 
2. At the bottom right of the panel, click on the padlock
 Figure 3
 
3. To unlock the permissions panel, enter your MacOS credentials and click OK
 Figure 4
 
4. In the line correspondent to "everyone", click on "No Access" (Figure 5) and then select "Read & Write" (Figure 6)
 Figure 5                                                                            Figure 6
 
 
5. Click on the icon bellow the permissions panel and select “Apply to enclosed items..."
 Figure 7
 
6. Now run the TWS installer and click on Next> until you complete the installation
 Figure 8

7. Once the installation has completed successfully, repeat the previous steps from 1. to 5. setting back the permissions of “everyone” to “Read Only” to revert your changes to the initial status

 

 

I am not receiving text messages (SMS) from IBKR on my mobile phone

Background: 

Once your mobile phone number has been verified in the Client Portal, you should immediately be able to receive text messages (SMS) from IBKR directly to your mobile phone. This article will provide you with basic troubleshooting steps in case you are unable to receive such messages.

 

1. Activate the IBKR Mobile Authentication (IB Key) as 2-Factor security device

In order to be independent of wireless/phone carrier-related issues and have a steady delivery of all IBKR messages we recommend to activate the IBKR Mobile Authentication (IB Key) on your smartphone.

The smartphone authentication with IB Key provided by our IBKR Mobile app serves as a 2-Factor security device, thereby eliminating the need to receive authentication codes via SMS when logging in to your IBKR account. 

Our IBKR Mobile app is currently supported on smartphones running either Android or iOS operating system. The installation, activation, and operating instructions can be found here:

Android: KB2277
iOS: KB2278

 

2. Restart your phone:

Power your device down completely and turn it back on. Usually this should be sufficient for text messages to start coming through. 

Please note that in some cases, such as roaming outside of your carrier's coverage (when abroad) you might not receive all messages.

 

3. Use Voice callback

If you do not receive your login authentication code after restarting your phone, you may select 'Voice' instead. You will then receive your login authentication code via an automated callback. Further instructions on how to use Voice callback can be found in IBKB 3396.

 

4. Check whether your phone carrier is blocking the SMS from IBKR

Some phone carriers automatically block IBKR text messages, as they are wrongly recognized as spam or undesirable content. According to your region, those are the services you can contact to check if a SMS filter is in place for your phone number:

In the US:

In India:

In China:

  • Call your phone carrier directly to check whether they are blocking IBKR messages

 

References:

 

Documentación de puertos y hosts de IB

Background: 

TWS se conecta a los servidores de IBKR a través de los puertos 4000 y 4001, en caso de utilizar SSL, y no se ejecutará en otros puertos. En caso de utilizar servidores proxy, estos han de ser transparentes y disponer de los puertos de entrada y salida abiertos con el fin de que TWS pueda funcionar correctamente.

A continuación figura una lista con todas las puertas de enlace junto con los host de destino correspondientes que TWS podría utilizar al utilizar nuestros servicios. Debe garantizar el acceso de dichos host.

La manera más fácil de comprobar si su conexión necesita una configuración especial o si se ha configurado correctamente es a través de la página de prueba dedicada de IB, en la que se ofrece una test dinámico de sus conexiones de red a nuestros servidores de negociación y datos de mercado. En caso de mostrarse un mensaje de conexión con éxito ('Success'), no es necesario tomar ninguna medida. En caso de mostrarse un mensaje de error ('Failure'), le recomendamos añadir una excepción para el servidor secundario en su configuración de red o revisar sus cambios.

Nota: En caso de que su red utilice un navegador proxy, la página puede mostrar falsos positivos. En este caso, o si no sabe cuál es la configuración de su red, contacte con sus administradores de red, quienes pueden realizar pruebas ping o telnet para los host indicados a continuación con el fin de confirmar el cumplimiento de los requisitos de conexión.

Especificaciones:

CLIENT PORTAL Y PÁGINA WEB

REGIÓN/PRODUCTO

SERVIDOR (HOST)

PUERTOS1

PÁGINA WEB IBKR – AMÉRICA

www.interactivebrokers.com

443

PÁGINA WEB IBKR – Canadá

www.interactivebrokers.ca

443

PÁGINA WEB IBKR – RU

www.interactivebrokers.co.uk

443

PÁGINA WEB IBKR – INDIA2

www.interactivebrokers.co.in

443

PÁGINA WEB IBKR – JAPÓN2

www.interactivebrokers.co.jp

443

PÁGINA WEB IBKR – HONG KONG2

www.interactivebrokers.com.hk 443

PÁGINA WEB IBKR – CHINA2

www.ibkr.com.cn 443

PÁGINA WEB IBKR - AUSTRALIA

www.interactivebrokers.com.au 443

GESTIÓN DE CUENTA – ESTE

gdcdyn.interactivebrokers.com

443

GESTIÓN DE CUENTA – CENTRAL

cdcdyn.interactivebrokers.com

443

SITIO DE RECUPERACIÓN ANTE DESASTRES

www.ibgdr.com 80

1: Comunicación estándar: TCP Port 80 | Comunicación SSL: TCP Port 443.

2: Este host de servidor de IB no admite solicitudes de ping.

Nota importante: El hecho de acceder a Client Portal a través de una red corporativa cuya conexión a Internet se facilita a través de un equipo de equilibro de carga puede dar lugar a mensajes de error sobre sesiones inválidas o caducadas, o puede que el contenido web no se muestre en su totalidad durante o después del inicio de sesión.   El equilibrador de carga cicla sus conexiones salientes en dos o más interfaces de red para equilibrar el flujo de trabajo de la red. En consecuencia, sus solicitudes HTTP llegan a nuestros sistemas a través de diferentes direcciones de IP, lo que provoca la invalidación de su sesión de Client Portal. En este caso, solicite a su administrador de web o departamento informático que configuren su ordenador/dispositivo con el fin de omitir el equilibrador de carga. De este modo su sesión permanecerá activa y continuará siendo válida.
 

 

TWS ESCRITORIO

REGIÓN/HERRAMIENTA

PRIMARIA/RESERVA

SERVIDOR (HOST)

PORTS


TWS AMÉRICA – ESTE

PRIMARIA

gdc1.ibllc.com / ndc1.ibllc.com


4000 / 4001

RESERVA

gdc1_hb1.ibllc.com / ndc1_hb1.ibllc.com


TWS AMÉRICA – CENTRAL

PRIMARIA

cdc1.ibllc.com


4000 / 4001

RESERVA

cdc1_hb1.ibllc.com


TWS EUROPA

PRIMARIA

zdc1.ibllc.com


4000 / 4001

RESERVA

zdc1_hb1.ibllc.com

TWS ASIA

PRIMARIA

hdc1.ibllc.com

4000 / 4001

RESERVA

hdc1_hb1.ibllc.com

TWS ASIA - CHINA3

PRIMARIA

mcgw1.ibllc.com.cn

4000 / 4001

RESERVA

mcgw1_hb1.ibllc.com.cn
TWS AUTOACTUALIZACIÓN PRIMARIA

download.interactivebrokers.com

443

download2.interactivebrokers.com

RISK NAVIGATOR

PRIMARIA

risk.interactivebrokers.com

443

AJUSTES DE TWS EN LA NUBE

PRIMARIA

s3.amazonaws.com

443

IB CAM

PRIMARIA

gdc1.ibllc.com

4000 / 4001

INFORMES DE DIAGNÓSTICOS

PRIMARIA

https://wit1.interactivebrokers.com

443

3: Portal dedicado a los clientes con cuentas asignadas al servidor de Hong Kong, pero que se conectan físicamente en China continental.

 

 

 

IBKR Host and Ports Documentation

Background: 

TWS connects to IBKR servers via port 4000 and 4001, if using SSL, and will not operate on any other port. If you are using a proxy server, it needs to be a transparent with both inbound and outbound ports open so that the TWS can function properly.

Below are listed all the gateways, along with the corresponding destination host that might be used by the TWS when you use our services, please allow access to those hosts.

The easiest way to test whether your connection needs any special setup or has been configured properly is to use IBKR's Dedicated Test page, which will provide a dynamic test of your network’s connection against our main trading and market data servers. If a “Success” response is returned, there is nothing more for you to do. If the response is “Failure”, we recommend adding an exception for the new hosts to your network’s configuration or review your changes.

Note: If your network uses a browser proxy, the test page can produce false positives. In this case, or if you are not sure what your network setup is, turn to your network administrators, who can perform ping and telnet tests to the hosts listed below to confirm compliance with the connectivity requirements.

Specs:

CLIENT PORTAL AND WEBSITE

REGION/PRODUCT

SERVER (HOST)

PORTS1

IBKR WEBSITE – AMERICA

www.interactivebrokers.com

443

IBKR WEBSITE – Canada

www.interactivebrokers.ca

443

IBKR WEBSITE – UK

www.interactivebrokers.co.uk

443

IBKR WEBSITE – INDIA2

www.interactivebrokers.co.in

443

IBKR WEBSITE – JAPAN2

www.interactivebrokers.co.jp

443

IBKR WEBSITE – HONG KONG2

www.interactivebrokers.com.hk 443

IBKR WEBSITE – CHINA2

www.ibkr.com.cn 443

IBKR WEBSITE - AUSTRALIA

www.interactivebrokers.com.au 443

ACCOUNT MGMT – EAST

gdcdyn.interactivebrokers.com

443

ACCOUNT MGMT – CENTRAL

cdcdyn.interactivebrokers.com

443

DISASTER RECOVERY SITE

www.ibgdr.com 80

1: Standard Communication: TCP Port 80 | SSL Communication: TCP Port 443.

2: This IB Server host does not support ping request.

Important Note: If you are accessing Client Portal from a corporate network where the Internet access is provided through a load balancing equipment, you may receive error messages about expired/invalid session and/or missing web content upon or after the login phase.  The load balancer cycles your outbound connections over two or more network interfaces to equalize the network workload. As a consequence of this mechanism, your HTTP requests reach our systems from different IP addresses, invalidating your Client Portal session.
In this scenario, as a solution, please ask your network administrator or IT group to configure your machine/device for bypassing the load balancer. This will allow your session to remain valid and alive.
 

 

DESKTOP TWS

REGION/TOOL

PRIMARY/BACKUP

SERVER (HOST)

PORTS


TWS AMERICA – EAST

PRIMARY

ndc1.ibllc.com


4000 / 4001

BACKUP

ndc1_hb1.ibllc.com


TWS AMERICA – CENTRAL

PRIMARY

cdc1.ibllc.com


4000 / 4001

BACKUP

cdc1_hb1.ibllc.com


TWS EUROPE

PRIMARY

zdc1.ibllc.com


4000 / 4001

BACKUP

zdc1_hb1.ibllc.com

TWS ASIA

PRIMARY

hdc1.ibllc.com

4000 / 4001

BACKUP

hdc1_hb1.ibllc.com

TWS ASIA - CHINA3

PRIMARY

mcgw1.ibllc.com.cn

4000 / 4001

BACKUP

mcgw1_hb1.ibllc.com.cn
TWS AUTO-UPDATE PRIMARY

download.interactivebrokers.com

443

download2.interactivebrokers.com

RISK NAVIGATOR

PRIMARY

risk.interactivebrokers.com

443

TWS CLOUD SETTINGS

PRIMARY

s3.amazonaws.com

443

IB CAM

PRIMARY

gdc1.ibllc.com

4000 / 4001

DIAGNOSTICS REPORTS

PRIMARY

https://wit1.interactivebrokers.com

443

3: Gateway dedicated to clients with accounts assigned to the Hong Kong server, but are physically connecting from Mainland China.

 

 

 

Funcionamiento de su tarjeta de seguridad digital+

La tarjeta de seguridad digital (DSC) es un dispositivo de seguridad operado por pilas que genera una serie de códigos aleatorios que deben introducirse junto con su nombre de usuario y contraseña cada vez que se conecte. Como la posesión física de la DSC es necesaria para obtener los códigos y conectarse, el dispositivo evita el acceso a su cuenta de piratas informáticos que pudieran haber obtenido su información o su computadora. A continuación se indican las instrucciones para operar la DSC. 

Paso 1:  Cuando se conecte a su cuenta, introduzca su nombre de usuario y contraseña como de costumbre. Aparecerá un código Desafío de 6 dígitos. 

Paso 2: Active su dispositivo pulsando el botón "pulsar" (“press”) hasta que aparezca la pantalla 'PIN>'; introduzca el código PIN de cuatro dígitos que usted especificó cuando solicitó el dispositivo y pulse el botón “OK”. 

Paso 3: Introduzca el código Desafío de 6 dígitos de la pantalla de conexión (paso 1) en el dispositivo cuando aparezca el mensaje 'CHALLNG>'; pulse el botón “OK” y verá un código de respuesta. 

Paso 4: Introduzca los 8 dígitos del código de respuesta (paso 3) en la pantalla de conexión. Seleccione el botón Conexión (Login) para continuar. 

Tenga en cuenta que los botones en la tarjeta de seguridad no son táctiles y deben pulsarse para operar.

  

Artículos relacionados

KB1042 - Instrucciones en vídeo para conectarse con la tarjeta de seguridad digital

KB1942 - Reactivar el dispositivo de acceso seguro permanente

KB1943 - Solicitar un recambio del dispositivo de acceso seguro

KB1131 - Resumen del sistema de acceso seguro

Operating your Digital Security Card+

The Digital Security Card (DSC) is a battery operated security device which generates a series of random codes to be entered along with your user name and password upon each log in attempt.  As physical possession of the DSC is required to obtain the codes and log in, the device effectively prevents hackers who may have compromised your computer or information from accessing your account.  Instructions for operating the DSC are outlined below. 

 

 

Step 1 -  When logging into your account, enter your user name and password as usual. If successful, a 6-digit Challenge Code will appear. 

Step 2 - Turn on your device by pressing the “press” button until the 'PIN>' display appears, enter the 4-digit PIN code you specified at the time you requested the device and press the “OK” button. 

Step 3 - Enter the 6-digit Challenge Code from the login screen (step A) into the device when the 'CHALLNG>' display appears, press the “OK” button and a response code will appear. 

Step 4 - Enter the 8 digits of the response code (Step C) into the login Screen. Select the Login button to proceed. 

Note that the buttons on your security cards are not touch sensitive and must to be pressed to operate.

  

Related Articles

KB1042 - Video instructions for logging in with the Secure Code Card

KB1942 - Reactivating the permanent Secure Login Device

KB1943 - Requesting a replacement Secure Login Device

KB1131  - Overview of the Secure Login System

 

How to fix the error: "Library dbcapi.dll cannot be loaded"

Background: 
 
TWS users may receive the following error message upon configuring TWS to use the eSignal data feed:
 
 
This error may appear for the following reasons:
 
Issue A - You are not using the 32 bit version of TWS and/or eSignal:
The 32-bit versions of both TWS and eSignal have to be installed for the integration to work. In the section below you will find the instructions for installing the 32-bit TWS. Should you need assistance with the installation of the 32-bit eSignal, we suggest you to contact the eSignal customer support.
 
Issue B - There is an incompatibility with the file C:\Jts\dbcapi.dll:
To use 32-bit eSignal version 12, an incompatibility with the C:\Jts\dbcapi.dll file must be fixed. This involves copying a file from the eSignal installation and renaming it to dbcapi.dll. 
 
Note: On certain systems you will need to apply the fixes for both issue A and B. If you applied the fix for issue A (or if you are already sure you are using the 32 bit version of both platforms) and you are still receiving the error message, then please apply as well the fix for issue B.
 
 
 
Instructions to resolve issue A
Installing 32-bit TWS
 
Please open the page http://www.ibkr.com in your browser and perform the steps below:

1) Click on the LOG IN button at the top right corner of the page.

2) Under the section TRADER WORKSTATION, click on TWS Latest.

3) On the next page, click on the link Download for Other Operating Systems.
 

4) Click on the item Windows 32-bit.

5) Make sure that the description under the DOWNLOAD button has changed to "Windows: 32 bit". Click now on DOWNLOAD.

6) Launch the downloaded file. The Trader Workstation installation will start. At this point you may see the warning message "Trader Workstation latest is already installed...". Ignore this warning and click on the button Next > to continue the installation.

 

7) Your "Trader Workstation" Desktop icon will be automatically updated. You can now launch the 32-bit Trader Workstation by a double click on that icon.

If you have launched the 32-bit TWS and the 32 bit version of eSignal but you still receive the same error message, please follow as well the instructions below

 
 
Instructions to resolve issue B
Replacing dbcapi.dll for compatibility between 32-bit TWS and 32-bit eSignal 12

To correct an incompatibility with the dbcapi.dll file, we will replace that file with another version of it taken from the eSignal installation folder. Please follow the steps below to perform the substitution:  

1) Navigate to C:\Jts and rename the file dbcapi.dll to dbcapi_old.dll

2) Navigate to the directory where 32-bit eSignal 12 is installed (most commonly C:\Program Files (x86)\Common Files\Interactive Data\DM)

3) Copy dbcapi_vc8.dll from that directory into the C:\Jts directory.

4) Move to the C:\Jts directory

5) Right click on the dbcapi_vc8.dll file (now in the C:\Jts directory) and select rename. Type dbcapi.dll as the new filename.

6) TWS is now ready to accept the eSignal data feed.

 

Syndicate content