Microsip Api Documentation May 2026

microsip.exe answer
microsip.exe hangup

| Command | Description | Usage Example | | :--- | :--- | :--- | | (none) | Launches the GUI normally. | MicroSIP.exe | | sip:user@domain | Initiates a call to the specified SIP URI immediately upon launch. | MicroSIP.exe sip:123456789@sip.provider.com | | call | Opens the "Call" dialog window. | MicroSIP.exe call | | exit | Gracefully closes the running instance of MicroSIP. | MicroSIP.exe exit | | hide | Hides the main window (minimizes to system tray if configured). | MicroSIP.exe hide | | show | Restores the main window from the system tray. | MicroSIP.exe show |

Use the command_line integration to control MicroSIP via batch scripts, enabling voice calls from automations.

# configuration.yaml
switch:
  - platform: command_line
    switches:
      microsip_call:
        command_on: 'C:\scripts\microsip_dial.bat  phone_number '

MicroSIP does not push events to an API. To get call status programmatically, you have two options: microsip api documentation

Use the SendMessage action in MicroSIP.ini to broadcast to another window:

OnIncomingCall=SendMessage,MyAppWindow,WM_USER+100,%number%

Your target app simply listens for that message ID. microsip

import win32gui
import win32con
def hangup_call():
    # 1. Find the Main MicroSIP Window
    # The window class usually varies, so we search by title or iterate
    hwnd = win32gui.FindWindow(None, "MicroSIP")
if hwnd:
        # 2. Find the child button.
        # Note: You need the specific Control ID (CID) of the button.
        # Tools like "Spy++" (included with Visual Studio) are required 
        # to find the specific Control ID for the Hangup button in your version.
# Example constants (these change between versions):
        HANGUP_BUTTON_ID = 1001
# 3. Send the click command
        win32gui.PostMessage(hwnd, win32con.WM_COMMAND, HANGUP_BUTTON_ID, 0)
    else:
        print("MicroSIP is not running.")

Important Limitation: Because MicroSIP is closed-source, the Control IDs (CIDs) for buttons are not publicly documented. You must use a tool like WinSpy++ or AutoIt Window Info to inspect the buttons and find their IDs every time a new version of MicroSIP is released.

In the world of Voice over IP (VoIP), efficiency and customization are paramount. While many users rely on graphical interfaces for softphones, power users, IT administrators, and developers often need something more: programmatic control. | Command | Description | Usage Example |

MicroSIP is a lightweight, open-source Windows SIP softphone renowned for its minimal resource usage (under 5MB of RAM) and exceptional audio quality. However, its true hidden power lies not in its GUI, but in its Command Line Interface (CLI) and Windows Messaging API.

While MicroSIP does not expose a traditional REST API or JSON web service, its rich API via command-line arguments and window messages allows any application—be it a CRM, a Python script, a batch file, or a web application—to control the phone seamlessly.

This article serves as the definitive resource for MicroSIP API documentation, covering every parameter, message type, and practical integration example.