New Year, New Momentum: Here are three Copilot updates to get you started into 2026

on
It's a new year, so I thought I'd start the year by mentioning three features already released, or soon going to be released. One of the features improves the workflow of sharing files with comments, the other improves the application specific Copilot, and the last feature makes it easer to find the nest available timeslot for a 1:1 meeting. As with all of my other posts, timelines can shift, and the timelines in this post is as written in the Message Center at the time of posting. AI-Summary experience when sharing files. With this new feature, copilot intent to help users share files with clearer context in just a few steps. Users will get the capability to generate a concise summary of a file and include it when sharing from the File Explorer share dialog or the OneDrive activity center. This will make it easier to share the context of a file and giving the receiver a faster understanding of what a document or file contains before they open it. General Availability announced...

Pushing the SBC 2000?

on
Recently, I ran into what seems to be an undocumented limitation in the SBC2000's from Sonus.

I have a customer who wanted to do billing based on a subscriber-ID from the telco provider. In order to do so, we created a lot of transformation rules to catch different number ranges based on calling number and then populate a "SG User Field" with a pre defined string.

fig1 - transformation)


On the outgoing trunk, we enabled header manipulation to add a diversion header populated with the subscriber-ID we wanted to bill the call to (a call without the diversion header would be blocked by the telco).

To set the the correct diversion header, we created a series of conditional rules and header manipulation rules.

fig 2 - conditional rules)


At first it all seemed to work fine, but then failed calls were reported, and we could not figure out what was wrong. It seemed like random errors, but it soon turned out to be related to certain calling number ranges.

All failed calls had a conditional rule and a matching header manipulation rule way down in the list of rules. A thought struck me, and I moved the failing rules to the top. This resulted in an instant success, but new users now reported failed calls. Again, these failed attempts came from users related to lists at the bottom.

fig 3 - header rules)


We opened a tac at Sonus, and soon learned there is a limit of 32 rules within the SBC (a close look at the fig above will reveal 64 rules ) . As soon as we trimmed the lists to be less than 33 rules, all calls were successful.

I have not been able to find this limitation in the official documentation from Sonus, but hopefully it will soon be updated. I am also surprised it is possible to create more rules than the Sonus can handle. It would make more sense to me if the creation of the 33 rule failed in the interface, than for me to discover the limitation by "accident".

I'm hoping the interface gets an update to reflect the limitation, or a change to allow for more rules to be created.

So if anyone else out there is trying the same "crazy" thing as me, to have more than 32 rules within a Message Rule, please don't it won't work ;)