Cancelling other invites based on ACK

[nathanl@ascci.ab.ca]

1. Brekeke Product Name and Version:SIP Server 3.10.6.5

2. Java version:8

3. OS type and the version:Windows Server 2016

4. UA (phone), gateway or other hardware/software involved:Grandstream PBX

5. Your problem:

Hi All,

I am wondering if it would be possible to set up a rule where I could cancel all other SIP invites based on the Acknowledgement of 1 of them.

So...From our "Sending Device" we are sending out to 4-5 different SIP extensions on our PBX, through Brekeke. Which has a rule that just strips *s out of a FROM=URI using the patterns below.

Matching Patterns
$request=^Invite
$Registered=^False
To=sip:(.+)@
From=Sip:(.+)\*(.+)\*(.+)@IPADDRESS

Deploy Patterns
To=%1@IPADDRESS
From=%3@IPADDRESS

So from our Sending address we will INVITE 4-5 extensions. However with the current setup from our sending hardware, it will only ACK the INVITE based on what SIP extension answers the call. Therefore the other INVITES continue to stay active and those extensions will ring until answered. (Or internally cancelled through the sending hardware)

Would it be possible to create a rule where if 1 SIP extension Acknowledges the call (Or accepts the INVITE) cancel the remaining invites for that specific call?

We would also need this rule to match based on the SIP header AND FROM=URI not just the From=URI itself. As multiple calls can come from the same address (It just uses different information)

[Harold]

There are two options.

Option-1: Use Brekeke PBX instead of Brekeke SIP Server. Brekeke PBX's group dialing feature can cancel other INVITEs without any settings.

Option-2: Ask Brekeke to develop a custom plugin which monitors ACK and sends CANCEL to other INVITEs.

[nathanl@ascci.ab.ca]

We can't really use Brekeke PBX, because of the way that the facility needs to work through it's own PBX.

I am more than happy to go through Brekeke's technical support, and pay them to develop a plugin or rule that would do this for us. However I'm hoping that we can determine if this is even possible before paying them (By the hour) to try and do something that may not even be possible.

This has happened to us once already where we paid for a service that ultimately didn't do us any good...

[Harold]

Have you contacted Grandstream to get some advice?

[nathanl@ascci.ab.ca]

I have not contacted Grandstream, as it is not really a Grandstream issue

The issue is our sending device, which the manufacturer refuses to change the way they are doing things. It would take a "re-engineering" of their hardware.

We were looking for perhaps a way around this through Brekeke, so that we could get our customers happy without waiting on them.

[Harold]

Using Brekeke PBX will be a cost efficient way to avoid the issue.

But you can ask sales@brekeke.com to estimate the plugin development cost if you use Brekeke SIP Server.

[Harold]

> The issue is our sending device, which the manufacturer refuses to change the way they are doing things.

What kind of device is it? Does it have a feature to send multiple calls concurrently from the same caller ID?