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:

 

IBKR主機與端口文檔

Background: 

如果使用SSL,TWS會通過4000和4001端口連接IBKR的服務器。如果您使用的是代理服務器,則其需同時開放入站端口和出站端口, 使其成為透明代理,這樣TWS才能正常運行。

下方表格列出了在您使用我方服務的過程中TWS可能會用到的所有網關及對應的目的地主機,請允許訪問該等主機。

要測試您的連接是否需要特殊設置或者是否已配置妥當,最簡便的方法便是使用IBKR的專用測試頁面,其可針對您的網絡與我方主交易與數據服務器的連接提供動態測試。如果返回的響應結果為“成功”,則您無需再進行進一步操作。如果響應結果為“失敗”,我們建議您在網絡配置中為新主機添加例外或檢查您的更改。

:如果您的網絡使用的是瀏覽器代理,測試頁面可能會產生錯誤正值。這種情況下,或者如果您不確定自己的網絡設置情況 ,您可求助於您的網絡管理員,網絡管理員可對下表所列主機進行ping和telnet測試以確認符合連接要求。

說明:

客戶端及網站

地區/產品

服務器(主機)

端口1

IBKR網站 – 美國

www.interactivebrokers.com

443

IBKR網站 – 加拿大

www.interactivebrokers.ca

443

IBKR網站– 英國

www.interactivebrokers.co.uk

443

IBKR網站 – 印度2

www.interactivebrokers.co.in

443

IBKR網站 – 日本2

www.interactivebrokers.co.jp

443

IBKR網站– 香港2

www.interactivebrokers.com.hk 443

IBKR網站 – 中國2

www.ibkr.com.cn 443

IBKR網站 - 澳大利亞

www.interactivebrokers.com.au 443

賬戶管理 – 東部

gdcdyn.interactivebrokers.com

443

賬戶管理 – 中部

cdcdyn.interactivebrokers.com

443

災難恢復網站

www.ibgdr.com 80

1: 標准通信: TCP端口80| SSL通信: TCP端口443。

2: 本IB服務器主機不支持ping請求。

重要提示:如您通過企業網絡訪問客戶端,且企業網絡是通過負載平衡設備提供互聯網連接的,則您在登錄時或登錄后可能會收到會話已過期/無效及/或網頁內容丟失等錯誤信息。負載平衡器會將您的連出請求循環連至兩個或以上網絡界面以平衡網絡負載。由於該機制,您的HTTP請求會通過不同的IP地址達到我們的系統,從而使您的客戶端會話無效。
在這種情況下,請聯系您的網絡管理員或IT部門配置您的設備以繞過負載平衡器。這樣您的會話將繼續有效。
 

 

桌面端TWS

地區/工具

主要/備用

服務器(主機)

端口


TWS美國 – 東部

主要

gdc1.ibllc.com / ndc1.ibllc.com


4000 / 4001

備用

gdc1_hb1.ibllc.com / ndc1_hb1.ibllc.com


TWS美國 – 中部

主要

cdc1.ibllc.com


4000 / 4001

備用

cdc1_hb1.ibllc.com


TWS歐洲

主要

zdc1.ibllc.com


4000 / 4001

備用

zdc1_hb1.ibllc.com

TWS亞洲

主要

hdc1.ibllc.com

4000 / 4001

備用

hdc1_hb1.ibllc.com

TWS亞洲 - 中國3

主要

mcgw1.ibllc.com.cn

4000 / 4001

備用

mcgw1_hb1.ibllc.com.cn
TWS自動更新 主要

download.interactivebrokers.com

443

download2.interactivebrokers.com

風險漫游

主要

risk.interactivebrokers.com

443

TWS云設置

主要

s3.amazonaws.com

443

IB CAM

主要

gdc1.ibllc.com

4000 / 4001

診斷報告

主要

https://wit1.interactivebrokers.com

443

3:網關面向賬戶被分配至香港的服務器、但實際從中國大陸訪問的客戶。

 

 

 

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.

 

 

 

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.

 

How to install the TWS API Components on Mac / Unix

NOTE: If you have already agreed to the API License Agreement please start at Step 3 below.

Instructions

  1. Click directly on the button below to access the API software download page. 
  2. This will direct you to Interactive Brokers API License Agreement, please review it.
  3. Once you have clicked "I Agree", refer to the Mac / Unix section to download the API Software for your o.s.
    API Software Download List
  1. This will download twsapi_macunix.n.m.zip to your computer.
    (where n and m are the major and minor version numbers respectively)
  2. Open Terminal (Ctrl+Alt+T on most distributions)
    (On Mac press Command+Space to launch Spotlight, then type terminal and press Return)
  3. Navigate to the directory where the installer has been downloaded (normally it should be the Download folder within your home folder) and confirm the file is present.

     $  cd ~/Downloads
     $  ls

  1. Unzip the contents the installer into your home folder with the following command (if prompted, enter your password):
    $  sudo unzip twsapi_macunix.n.m.zip -d $HOME/
    Installation directions Step 3 and Step 4
  2. To access the sample and source files, navigate to the IBJts directory and confirm the subfolders samples and source are present.
    $  cd ~/IBJts
    $  ls
    Installation directions Step 5
 

 

Legacy Instructions - API Version ≤ 9.71

Note: IB only offers API Version 9.72+. In the event you already have an existing legacy version and need to install it, please refer to the directions below:

  1. locate the file twsapi_macunix.n.m.jar on your computer.
    (where n and m are the major and minor version numbers respectively.)
  2. Open Terminal (Ctrl+Alt+T on most distributions)
    (On Mac press Command+Space to launch Spotlight, then type terminal and press Return)
  3. Navigate to the directory where the .jar file has been located (normally it should be the Download folder within your home folder) and confirm it is present.
    cd ~/Downloads
    $  ls
  4. Extract the contents of the .jar file into your home folder.
    $  jar xf twsapi_macunix.n.m.jar -d $ HOME/
  5. To access the sample and source files, navigate to the IBJts directory and confirm the subfolders samples and source are present.
    $  cd ~/IBJts
    $  ls
 
 

Additional Information 

You can as well refer to KB2222 for video instructions on installing the Legacy API Components on a Mac.

 

Syndicate content