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:

 

Dokumentation zu IB Hosts und Ports

Background: 

Die TWS verbindet sich mit IBKR-Servern über die Ports 4000 und 4001 und falls SSL verwendet wird, wird sie über keinen anderen Port aktiv sein. Falls Sie einen Proxy-Server verwenden, muss es sich um einen transparenten mit sowohl eingehenden als auch ausgehenden offenen Ports handeln, damit die TWS ordnungsgemäß funktionieren kann.

Nachstehend finden Sie alle Gateways sowie den zugehörigen Destination-Host, der unter Umständen von der TWS verwendet wird, wenn Sie unsere Dienste nutzen. Bitte gewähren Sie den Zugang zu diesen Hosts.

Ob Ihre Verbindung eine besondere Einrichtung erfordert bzw. korrekt konfiguriert wurde, können Sie am einfachsten herausfinden, indem Sie die Testseite von IBKR verwenden, die einen dynamischen Test Ihrer Netzwerkverbindung zu unseren wichtigsten Trading- und Marktdatenservern ermöglicht. Falls Sie „Erfolg“ (success) als Rückmeldung erhalten, müssen Sie nichts weiter unternehmen. Falls die Rückmeldung „Fehlgeschlagen“ (failure) lautet, empfehlen wir, eine Ausnahme für die neuen Hosts zur Konfiguration Ihres Netzwerks hinzuzufügen oder Ihre Änderungen zu prüfen.

Hinweis: Falls Ihr Netzwerk einen Browser-Proxy verwendet, ist es möglich, dass die Testseite ein fälschlich positives Ergebnis ausgibt. In diesem Fall, oder wenn Sie nicht genau wissen, wie Ihre Netzwerkeinrichtung aussieht, sollten Sie sich an Ihren Netzwerkadministrator wenden. Dieser kann Ping- und Telnet-Tests zu den nachstehend aufgeführten Hosts durchführen, um die Konformität mit den Verbindungsanforderungen zu überprüfen.

Spezifikationen:

CLIENT PORTAL UND WEBSITE

REGION/PRODUKT

SERVER (HOST)

PORTS1

IBKR-WEBSITE - AMERIKA

www.interactivebrokers.com

443

IBKR-WEBSITE - Kanada

www.interactivebrokers.ca

443

IBKR-WEBSITE - UK

www.interactivebrokers.co.uk

443

IBKR-WEBSITE - INDIEN2

www.interactivebrokers.co.in

443

IBKR-WEBSITE - JAPAN2

www.interactivebrokers.co.jp

443

IBKR-WEBSITE - HONGKONG2

www.interactivebrokers.com.hk 443

IBKR-WEBSITE - CHINA2

www.ibkr.com.cn 443

IBKR-WEBSITE - AUSTRALIEN

www.interactivebrokers.com.au 443

KONTOVERWALTUNG - OST

gdcdyn.interactivebrokers.com

443

KONTOVERWALTUNG - ZENTRAL

cdcdyn.interactivebrokers.com

443

NOTFALLWIEDERHERSTELLUNGSSEITE

www.ibgdr.com 80

1: Standardkommunikation: TCP-Port 80 | SSL-Kommunikation: TCP-Port 443.

2: Dieser IB-Serverhost unterstützt keine Ping-Anfragen.

Wichtiger Hinweis: Falls Sie auf das Client Portal von einem Unternehmensnetzwerk aus zugreifen, bei dem der Internetzugang über einen Lastenausgleich bereitgestellt wird, ist es möglich, dass Sie Fehlermeldungen zu abgelaufenen/ungültigen Sitzungen und/oder fehlenden Webinhalten im Zuge oder nach der Login-Phase erhalten. Das Lastenausgleichsmodul leitet Ihre abgehenden Verbindungen über zwei oder mehrere Netzwerkoberflächen weiter, um die Netzwerkauslastung auszugleichen. Aufgrund dieses Mechanismus erreichen Ihre HTTP-Anfragen unsere Systeme aus unterschiedlichen IP-Adressen und machen Ihre Client-Portal-Sitzung somit ungültig.
In diesem Szenario bitten wir Sie, als Lösung Ihren Netzwerkadministrator oder IT-Abteilung Ihre Maschine/Ihr Gerät dahingehend zu konfigurieren, dass das Lastenausgleichsmodul umgangen wird. Dies wird dazu beitragen, dass Ihre Sitzung gültig und aktiv bleibt.
 

 

DESKTOP-TWS

REGION/TOOL

PRIMÄR/BACKUP

SERVER (HOST)

PORTS


TWS AMERIKA - OSTKÜSTE

PRIMÄR

gdc1.ibllc.com / ndc1.ibllc.com


4000 / 4001

BACKUP

gdc1_hb1.ibllc.com / ndc1_hb1.ibllc.com


TWS AMERIKA - ZENTRAL

PRIMÄR

cdc1.ibllc.com


4000 / 4001

BACKUP

cdc1_hb1.ibllc.com


TWS EUROPA

PRIMÄR

zdc1.ibllc.com


4000 / 4001

BACKUP

zdc1_hb1.ibllc.com

TWS ASIEN

PRIMÄR

hdc1.ibllc.com

4000 / 4001

BACKUP

hdc1_hb1.ibllc.com

TWS ASIA - CHINA3

PRIMÄR

mcgw1.ibllc.com.cn

4000 / 4001

BACKUP

mcgw1_hb1.ibllc.com.cn
TWS AUTO-UPDATE PRIMÄR

download.interactivebrokers.com

443

download2.interactivebrokers.com

RISK NAVIGATOR

PRIMÄR

risk.interactivebrokers.com

443

TWS-CLOUD-EINSTELLUNGEN

PRIMÄR

s3.amazonaws.com

443

IB KAM

PRIMÄR

gdc1.ibllc.com

4000 / 4001

PROBLEMDIAGNOSE-BERICHTE

PRIMÄR

https://wit1.interactivebrokers.com

443

3: Gateway für Kunden mit Konten, die dem Hongkonger Server zugeteilt sind, sich jedoch physisch vom chinesischen Festland aus verbinden.

 

 

 

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.

 

 

 

Verwendung Ihrer digitalen Sicherheitskarte

Die digitale Sicherheitskarte (DSC) ist ein batteriebetriebenes Sicherheitsgerät, das zufällige Codes generiert. Bei jedem Loginversuch muss ein solcher Code zusammen mit Ihrem Benutzernamen und Passwort eingegeben werden. Da physischer Zugang zur DSC erforderlich ist, um diese Codes zu generieren und den Login erfolgreich abschließen zu können, stellt dieses Gerät ein effektives Mittel dar, um Hacker, die möglicherweise Ihren Computer oder Ihre Daten manipuliert haben, am Zugriff auf Ihr Konto zu hindern. Nachstehend finden Sie eine Anleitung zur Verwendung Ihrer digitalen Sicherheitscodekarte. 

 

  

Schritt 1 - Geben Sie bei der Anmeldung in Ihrem Konto wie gewohnt Ihren Benutzernamen und Ihr Passwort ein. Bei erfolgreichem Login wird ein 6-stelliger Prüfcode angezeigt. 

Schritt 2 - Schalten Sie Ihr Sicherheitsgerät ein, indem Sie auf den Kopf „Press“ drücken, bis die Anzeige 'PIN>' erscheint. Geben Sie die 4-stellige PIN ein, die Sie bei Beantragung des Geräts festgelegt haben, und drücken Sie anschließend auf den „OK“-Knopf. 

Schritt 3 - Geben Sie den 6-stelligen Prüfcode von der Login-Maske (Schritt 1) in das Gerät ein, wenn die Anzeige 'CHALLNG>' erscheint, und drücken Sie den „OK“-Knopf. Ihnen wird ein Antwortcode angezeigt. 

Schritt 4 - Geben Sie den 8-stelligen Antwortcode (Schritt 3) in die Login-Maske ein. Klicken Sie auf die Schaltfläche „Login“, um fortzufahren. 

Bitte beachten Sie, dass die Knöpfe des Sicherheitsgeräts nicht berührungsempfindlich sind, sondern gedrückt werden müssen.

  

Verwandte Artikel

KB1042 - Videoanleitung zum Login mit der Sicherheitscodekarte

KB1942 - Reaktivierung eines dauerhaften Sicherheitsgeräts

KB1943 - Beantragung eines ersatzweisen Sicherheitsgeräts

KB1131 - Überblick über das Secure-Login-System

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