LogoLogo
www.mikopbx.comTelegram communityForum
English
English
  • MikoPBX Manual
    • Quick start
    • Getting to know MikoPBX
    • System requirements
  • Installation
    • Standalone Computer
    • Virtual Machine
      • VMware ESXi
      • VMware Fusion
      • VirtualBOX
      • VMware Workstation Pro
      • Hyper-V
      • Proxmox
    • Cloud
      • AWS
        • AWS deployment guide
        • AWS Marketplace
      • Microsoft Azure
      • Google Cloud
        • Google Cloud deployment guide
        • Google Cloud Marketplace
      • Hetzner cloud (In dev)
      • Digital Ocean
      • Alibaba Cloud
      • Vultr
    • Docker container
      • Docker installation and creating a user and directories
      • Running MikoPBX in a container
      • Running MikoPBX using docker compose
  • User manual
    • Telephony
      • Extensions
      • Call queues
      • IVR Menu
      • Conferences
      • Sound files
      • Call detail records (CDR)
    • Call Routing
      • Telephony providers
      • Incoming routing
      • Outbound routing
      • Night and Holiday Switch
    • Modules
      • Registration in the modules marketplace
      • Module management
      • Application dialplans
    • Maintenance
      • PBX update
        • Updating from the web interface
        • Updating from the MikoPBX console
        • Updating the docker
      • System log entries
      • Reboot
    • Network and Firewall
      • Network interface
      • Firewall
      • Anti brute force
    • System
      • General settings
      • Time Settings
      • Mail settings
        • Setting up E-mail notifications for the Gmail mail service
      • Asterisk Manager Interface(AMI)
      • System files customisation
  • FAQ
    • Setup
      • Installation on MDADM RAID1
      • Fine-tuning the firewall
      • Migrating MikoPBX to Another Server
        • Transfer Using Backup
        • Transfer using scheduled backup (SFTP)
        • Transfer using rsync
      • Reset to factory settings
      • Monitoring Providers on MikoPBX
    • Management
      • Change the login name
      • The extra disk space has run out, the disk size has increased
      • Storing Recordings in a Shared Windows Folder
      • Resetting WEB Interface Credentials
      • Backup Internet and Provider Re-Registration
    • Troubleshooting
      • Connecting to the PBX using SSH
        • Connecting to PBX using SSH client (Putty)
        • Connecting via SSH (Windows)
        • Connecting via SSH (Linux/MacOS)
      • Connecting to a PBX using WinSCP
      • Getting logs using the tcpdump application
      • Capturing Logs from PBX using Wireshark
      • Traffic Analysis Using Sngrep
      • Adjusting the volume
      • Troubleshooting sound problems
      • Jitter Configuration
    • Incoming Routing
      • Choosing a provider when redirecting to a mobile
      • Notification of Employment, Call Waiting
      • Black and white lists
      • Allow additional dialing of the internal number in the queue
      • Output of information about the did number
      • Setting individual non-working hours for a provider account
      • An example of the implementation of a typical route of incoming calls
      • Routing by DID Number
      • Normalization of incoming phone number
      • Basic IVR example
    • Outbound routing
      • Add P-Preferred-Identity and Remote-Party-ID header
      • Conference with a regular external subscriber
      • Outgoing with internal number dialing
      • Remove all special characters from the dialed number
      • Prohibiting calls via a backup route
      • Calls to emergency numbers
      • Number Templates
        • Uniform distribution of outgoing
        • Sample template: calls to another country
        • How to prohibit the replacement of "+" with 00
        • Changing the number prefix from "+345" to "347"
        • Changing the number prefix from "345, 347" to "+345"
        • Removing the area code from the number
        • Adding the prefix "1" to the number
      • Making Calls Through a Specific Provider
    • Scenarios and cases
      • Generate extensions by REST API
      • Missed Call Telegram Notifications
      • Call the company from your mobile and dial an extension to call a third-party company
      • Sending an incoming fax to email
      • Customer's assessment of the quality of service
      • Simulation of external calls
      • Disabling "off-hours" for VIP numbers
      • Registering multiple accounts from one provider
      • Setting up individual non-working hours for several providers on one host
      • Disable forwarding to mobile for internal calls
      • Unique background music for the queue
      • Pause for Queue agent
      • Dynamic Queue Agents
      • Setting up the "Paging" function
      • Limit the number of authorizations per SIP account
      • Call Monitoring (ChanSpy)
      • Conversion of Call History FreePBX -> MikoPBX
      • SSL Certificate for MikoPBX Web Interface from OPNSense
      • Hiding the Caller’s Number from Employees
    • Interconnections
      • Merging two MikoPBX
      • Integration of MikoPBX and Grandstream UCM6202
      • MikoPBX and FreePBX (PJSIP)
      • MikoPBX and FreePBX (IAX)
    • VoIP providers
      • Mango
      • Zadarma
    • Softphones
      • Bria Solo
      • Sessiontalk
      • MicroSIP
      • Groundwire
      • Zoiper
      • Jitsi
      • PhonerLite
      • Linphone (MacOS)
      • Telephone(MacOS)
      • Configuring webRTC client SIMPL5
      • Softphone.pro
      • 3CX Softphone
      • PortSIP
    • IP telefones
      • Snom D120
      • Yealink T19
    • VoIP gateways
      • GoIP4
      • Grandstream HT503
      • Using a Huawei E173 USB Modem for Calls (chan_dongle)
  • Modules
    • MIKO modules
      • for 1C:Enterprise
        • Панель телефонии 4.0 для 1С
        • Панель телефонии 1.0 для 1С
        • Модуль умной маршрутизации
      • Users groups
      • CRM Bitrix24 integration
      • Autoprovision
      • Let's Encrypt
      • Access control management
      • Module auto dialer
      • Backup
      • Synchronization with LDAP/AD
      • Callback module
  • other
    • Changelog
      • MikoPBX 2024.1
      • MikoPBX 2023.2
      • MikoPBX 2023.1.223
Powered by GitBook
On this page
  • Softphone Setup
  • Configuring Employee Status Monitoring
  • Configuring GroundWire with Encryption

Was this helpful?

Edit on GitHub
Export as PDF
  1. FAQ
  2. Softphones

Groundwire

Instructions for configuring and connecting the Groundwire softphone to MikoPBX

Last updated 2 months ago

Was this helpful?

Groundwire is a softphone that offers low power consumption by avoiding constant SIP session maintenance with the server. When an incoming call arrives, a PUSH notification is first sent to the smartphone, which then launches the SIP client and establishes a connection to the server.

Softphone Setup

  1. Download and open the Groundwire app on your smartphone.

  1. Go to Groundwire settings by tapping the corresponding icon at the top of the screen.

  1. Go to the "Accounts" section:

  1. Add a new account by tapping the "+" icon at the top of the screen.

  2. Select "Generic SIP Account."

  3. Fill in the required data:

    • Title – An arbitrary account name.

    • Username – The employee’s extension number (e.g., 201).

    • Password – The SIP password from the employee’s configuration.

    • Domain – The IP address of your MikoPBX server.

  1. Go to "Advanced Settings."

  2. In "Audio Codecs" → "Codecs for Wi-Fi," choose the desired codecs for use.

  1. Navigate to "Caller Id Method." Select "P-Asserted-Identity."

Save the settings. A connection attempt will occur. In the MikoPBX "Employees" section, you can see a status indicator confirming a successful connection:

Configuring Employee Status Monitoring

Groundwire can display the current status of employees (see example below):

To enable this feature, populate the "Quick Dial" section with employees. Tap "EDIT" at the top of the screen. Then tap the "+" at the bottom of the screen to add entries:

  • Title – The employee’s name to display in "Quick Dial."

  • Number or SIP Address – The employee’s extension number.

Tap "Save."

Configuring GroundWire with Encryption

  1. In the MikoPBX web interface, open the employee’s SIP account settings. Change the "Transport Protocol" to "tls."

  1. In Groundwire → Employee’s SIP Account Settings, change the "Domain" field to "MikoPBXAdress:NumOfTLSPort".

You can find or change the TLS port in MikoPBX’s "General Settings" → "SIP."

  1. Go to "Advanced Settings" → "Transport Protocol" and change "udp" to "tls (sip)."

  1. In the "Advanced Settings" of your SIP account, go to "Secure Calls" and, under the "SDES" section, set "Incoming Calls" and "Outgoing Calls" to "Required":

Main menu
Settings button
"Account" section
Data for SIP connection
Audio codecs
Section "Caller Id Method"
Successful SIP-connection
Employee statuses
New employee in the "Quick Dial" section
Changing the transport protocol
Domain for the TLS connection
Changing the transport protoco
SDES Parameters