Member Avatar for simhanry

Hi,

I am looking to develop a software which can initiate phone call from Computer thru VoIP Gateway. I have found some applications, where I should manually dial the phone number. But I need to trigger call by system itself based on some incidents. Can anyone suggest what technology/languages should I use to develop this kind of application ? I am a beginner for this. I don't have any idea where should I start to develop this kind of applciation.

Thanks
Reddy

  • 2 Contributors
  • 3 Replies
  • 185 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by Rush Lover

Dani AI

Generated

— for an incident-driven, server-side caller that runs on IBM/Linux infrastructure, there are two practical architectures to consider; the desktop automation approach suggested by is useful on workstations but not ideal for a headless, event-driven server.

  • Cloud telephony APIs (easy to prototype): providers expose simple HTTP/REST endpoints and SDKs (Python/Node/Java/etc.) to “originate” a call, play TTS or recorded audio, and bridge calls. Advantages: minimal telephony knowledge, rapid development, built-in scale and retry logic. Good first step for a beginner.

  • Self-hosted PBX/gateway (more control): install a PBX engine (Asterisk or FreeSWITCH) and connect it to a SIP trunk or an on-site PSTN gateway. Your app can then trigger outbound calls via the PBX control interfaces (Asterisk AMI/ARI or by using a SIP library such as PJSIP/JAIN-SIP). This gives full control over call routing, audio files, local network integration and often lower long-term cost, but requires SIP/RTP, NAT and codec handling knowledge.

Practical language/layer choices: start with a high-level language (Python or Node.js). Use a message queue (Redis/RabbitMQ) so incident producers don’t block while calls are placed. For cloud APIs use the provider SDK; for on-prem use AMI/ARI libraries or a SIP client library. Typical flow: incident -> enqueue call request -> worker pulls request -> calls PBX/provider to originate call -> plays TTS/file or bridges to extension.

Quick troubleshooting and cautions: test first to a softphone on your LAN, enable SIP/RTP debugging to inspect INVITE/200/4xx responses, confirm RTP ports and NAT traversal (STUN/TURN where needed), verify codec compatibility (start with uncompressed audio for debugging), secure API/AMI credentials, and verify local telecom compliance and caller-ID rules before scaling.

Member Avatar for Rush Lover

Well, if your company/ network is all macs, then you can develop a program that can make calls through a VOIP server, like a Cisco Call Manager. After you develop that, you can use the Apple utility called Automator to make the program you made call a specific phone number/ extension and play a sound.
Example-
User opens Microsoft Word for Mac.
Automator says, "This file has been opened, tell program example to dial x1234
Program you develop Dials x1234
Automator-Dialing
(Phone is picked up)
Automator- Play file "Rush-Force Ten.mp4"

Something like that.

Member Avatar for simhanry

We don't use Mac servers. We use IBM servers. This won't fit for us.

Member Avatar for Rush Lover

No, mac workstations, laptops/desktops.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.