Log into your shiny sipgate account and go to the Feature Store. You can find a button on the right side of the top bar
Within the Feature Store, scroll down and click on the sipgate.io feature.
Click on the orange button to book the free feature and follow the confirmation process.
Select sipgate.io in the sidebar to navigate to your settings section
Select „Webhooks“ in the sidebar and navigate to „URLs“.
Click on „Incoming calls“ or „Outgoing calls“, enter your URL and hit „Save“.
Example URL: https://www.example.com:3000
We strongly encourage you to use a HTTPS server. Although we support plain HTTP connections we do not recommend pushing sensitive call details over unencrypted connections. Be aware that sipgate.io does not accept self-signed certificates. If you need a certificate for your server, you can easily get one at Let´s Encrypt.
The transferred call is a new call. Scenario: Jennifer calls Doc Brown and Doc Brown transfers the call to Marty and Marty picks up. Here’s what sipgate.io sends to your server:
As you can see, the callId changes with the transfer.
This is what sipgate.io sends, in case Marty does not pick up:
The forwarded call is handled as a new call. Let’s assume the previous scenario: Jennifer calls Doc Brown but his line is busy so the call is forwarded to Marty who in turn picks up the call.
Here are the pushes sipgate.io will send to your server:
The answer is: It depends.
If you transfer or forward a call within the same sipgate account then the answer is no. But if you forward or transfer a call to a different sipgate account or an external number then those pushes are being billed to your account.
In every push request the callId parameter is included to identify the current call. Use the callId to manipulate the call at any time with our RTCM-API.
sipgate.io does not process emergency calls. Emergency calls are immediately put through to emergency services.