Kamailio permission module

The permission module includes features and controls to create ACLs based on source IP, From, Request Uri. This allows to control who can do what, for example whether requests arriving from a certain source IP can be rotated to the destination, or whether a certain SIP Uri can be handled or must be rejected.

Kamailio SecureSIP gateway with rtpengine

In previous posts we have already discussed about rtpengine and how to use it with Kamailio to manage NAT or voice transcoding. In this article we’ll see how to use Kamailio with the TLS module and rtpengine to create a TLS/SRTP proxy, which on the first call leg uses secure SIP with TLS and SRTP and on the second leg uses UDP and RTP. In this way we will have the possibility to add Secure SIP support to existing media servers that only support UDP transport with RTP, adding security. The SRTP (Secure RTP) protocol is used with SIP over TLS and transmits voice in encrypted IP packets, avoiding the interception and decoding of audio packets.

Kamailio with TLS module

The “tls” module is specifically designed to add TLS (Transport Layer Security) support at the TCP transport level, and allows to manage traffic that uses SIPS (SIP Secure) for SIP encryption. All details are available on the official Kamailio documentation for the [tls] module (https://kamailio.org/docs/modules/stable/modules/tls.html). Here we will see how to activate it on our Kamailio installation.

Genesys Cloud Third Party ChatBot integration

With the introduction of the WebChat APIs in Genesys Cloud it is now possible to integrate your external ChatBot with the Genesys platform offering an interesting user experience for users. By taking advantage of the WebChat APIs you can, for example, develop your own ChatBot that welcomes users with the possibility of switching between ChatBot and real Agent on Genesys Cloud, also making the history of the conversation that the user had with the BOT available to the agent.

Genesys Cloud integration with SIP external IVR, transfer back to Genesys

In the previous post we configured a BYOC SIP Trunk on Genesys Cloud and transferred a call from a Genesys flow to an external IVR. Here we will see how to return the call back to the Genesys after connected it with the external IVR.
In summary, we have a user who is connected with an Architect voice flow in Genesys Cloud, the user is transferred via SIP to an external IVR and from there he is transferred back into Genesys Cloud, on the same flow or on any other flow.

Genesys Cloud integration with SIP external IVR

In the last days I have had the opportunity to experiment a bit with the Genesys Cloud platform and I decided to write a couple of articles on integration with external systems, in particular on the possibility of transferring call to an external IVR and then resuming it on the Genesys flow, but also on chat integration capabilities. The purpose of this first article is to describe how to handle the first case, transferring a call from a Genesys flow to an external IVR.

Balancing traffic to Galera Cluster with HAProxy

We described here Galera Cluster with its features, which allows you to create a multi-master active-active database cluster with synchronous data replication, enabling read and write operations on all the cluster nodes.

Configuring SSL encryption on Galera Cluster

To secure at all communications between nodes in a Galera Cluster, as well as client and servers running MySQL inside the cluster, you need to enable three degrees of security:

Setting up rtpengine with Kamailio for transcoding

In my previous posts, you will have discovered the power of rtpengine, from the installation procedure to the configuration for using it with kamailio. Here we will go further into the functionality of rtpengine, using it as an audio transcoder, i.e. to adapt the audio streams generated by two RTP endpoints that use different audio codecs.

Activate a Galera Arbitrator node in a Galera Cluster

In the previous posts Galera Cluster for MySQL and Automating the startup of Galera Cluster we focused on installing the Galera cluster on 2 nodes and starting it automatically using a script job in the crontab. Here I want to talk about the Galera Arbitrator module.