Register SIP account and receive calls with Twilio
How to register your SIP softphone and receive inbound calls using TwilioProperly terminate crystal-lang service in docker
How to handle signals and properly terminate docker service written with the Crystal-lang.Create the smallest Crystal-lang docker image based on scratch
How to use docker multi-stage builds to create a smallest by size Crystal-lang docker image.All-in-one (Crystal-lang library that handle all the Asterisk PBX interfaces)
I've created and open-sourced a Crystal-lang shard (library) that handles all Asterisk PBX interfaces (ARI, AMI, and all types of AGI).How to install software on firewalled server
How to use a reverse SSH proxy to install software on a server with outbound firewalls (gray zone ;) )DigitalOcean, Floating IP and VoIP
How to configure DigitalOcean's floating IP with VoIP, specifically with Asterisk, using Docker.Tiny docker image with ngrok
I've found an excellent tiny Docker image for ngrok (wernight/ngrok). From now just using it to handle this blog.Updated OPUS codec patch that supports Asterisk 11.11.0 and 12.2.5
I have updated the OPUS codec patch, which now supports Asterisk 11.11.0 and 12.2.5. I have tested it with VP8 in pass-through mode, and it functions correctly. You can download the patch here.
WebRTC with Asterisk 11?
Tonight, I tried two WebRTC clients (JsSIP and sipML5) with Asterisk 11. I was able to get both of them working for echo test calls with the ulaw (g711u) codec. However, when I called from WebRTC to the SIP softphone, there was only one-way audio.Roaming PBX update
What's new: Asterisk 11.4, SILK codec, watchdog to improve Raspberry Pi board performance and prevent deadlocks.First release of Roaming PBX
Announcing the first alpha release of the Roaming PBX image, featuring Ruby, pcapsipdump, Asterisk PBX, and the SILK codec.Creating your own custom image for Raspberry Pi
How to cross-compile a custom Raspberry Pi image and to build custom Asterisk PBX installation.SIP TCP vs UDP with mobile client: awesome results
While it is generally known that TCP can be more battery-efficient for mobile VoIP compared to UDP, the extent of this improvement can be surprising. After switching my Android softphone (Bria) from UDP to TCP yesterday, I observed a significant difference. Typically, by 2:20 PM, my mobile phone battery would be around 50%; however, with TCP, it is now at 88%.