Sangoma Mirror Shenanigans again?

I may be reading this wrong but is this blog saying that if you use any repo mirrors except sangoma’s official ones your commercial modules will cease to work properly???

https://www.freepbx.org/avoid-walking-the-plank-with-expired-modules/

and if that’s the case what’s the best way to handle this if you use CIP modules like clearly devices, trunking and clearly anywhere

I am using the Clearly Anywhere module and CIP mirror is not required. Its module.xml has this line which allows it to get updates even if you’re using the Sangoma mirror.

       <updateurl>https://mirror.clearlyip.com/modulehosting/clearlysp.json</updateurl>

btw I use this same method in my smsconnector module, which is not hosted on any mirror (but once you install it, you will keep getting updates on it).

Ok, then clearly I’m not understanding something. Why does CIP have their own mirrors then if they are not needed?

The Clearly Mirrors do a couple of things from what I remember, stops sharing all your PBX data with Sangoma and in theory stops poorly QA’d module updates getting on to your system.

I am really curious at to what Sangoma is playing at here. My districts pay for commercial modules and buy platinum support…. Are we in fact being told this is the case? Anyone from Clearly have any weigh in?…. It sure feels like Sangoma is taking some desperate measures.

I’d take whatever that person says with 1/8th of a grain of salt, sounds like propoganda,but, so long as the mirrors you use are current, and licences are valid, to me, it says “ nothing to see hear, move along”

but like lawyers, ask 6 of them the same question, get 6 different answers :slight_smile:

Real quick, you need to fix the json on your module.json for smsconnector, it’s not working the way you think.

You’re redeclaring the key “module” three times so it will only accept sipsettings as the module to depend on.

"depends": {
        "version": "16",
        "module": "sms",
        "module": "userman",
        "module": "sipsettings"
},

Should be more like

 "depends": {
    "depends": {
     "version": "16",
      "module": [
        "sms",
        "userman",
        "sipsettings"
      ]
    }
},

Nice catch, thank you.

It’s been eerily quiet from Clearly/14IP lately. Has the acquisition from 14IP killed this project now?

Not for me but I’m also a sales partner. I’m getting constant updates and webinar sessions to attend from 14IP/ClearlyIP. So on the commercial products/services side, which is the main focus of IP14/ClearlyIP’s portfolio, it’s rather active.

In what context are you referring to? ClearlyIP’s ComXchange PBX was built with FreePBX underneath it but as of 2026 ComXChange v17 is built on top of TangoPBX. So I can’t see it going away or being killed.

If you’re referring to the lack of development and updates, I don’t think ClearlyIP was ever getting into the game of OSS development. I’m not sure how many modules we’ll see from ClearlyIP for TangoPBX. As far as I see it, the community asked ClearlyIP for a version of FreePBX that was not commercial driven so it could be built upon freely and we got it.

Early 2025 there was a lot of “Screw Sangoma and FreePBX” and “Clearly launches a PBX, that’s what I’m using” vibes and talk. Even when the ISO was launched last May there was a lot of “LFG” style posts and attitude then…crickets.

I mean if TangoPBX was for the community and it feels dead…well take a look at the forum itself. The actual TangoPBX based discussions are at the bottom of topics discussed. I’m not seeing any real amount of topics about migrating to TangoPBX, development on TangoPBX, installations of TangoPBX. Those were topics discussed when all this started but as the year progressed they fell to the wayside pretty quickly. You have noticed that a lot of the very, very, very vocal and loud people from last year that were all “Yeah LFG TangoPBX 4 LIFE MOFOS!” have gone completely radio silent?

We are also a partner, so I’m aware that there is a lot going on. Whilst ComX is based on the TangoPBX base, the point was more that they’ve not really been hanging out here so wondering where the long term aim is with TangoPBX for the rest of us.

That’s not really new. ClearlyIP staff hasn’t been overly active on here since the launch.

Let me ask you this, what were your expectations with TangoPBX? Did you (and others) believe that Clearly was just going to start banging out more modules or go full tilt on an OSS PBX? An entire subset of the FreePBX community spent years chasing after a ClearlyIP OSS option going on about how once that happen they’d be “outta here” with FreePBX. Well they got it. They caught the car they’ve been chasing and it seems they don’t know what to do with it.

I get it, I wrote an entire module for the community last year because a bunch of people were bitching about the fact Sangoma was never going to put resources in improving the ChanSpy feature in FreePBX. So I wrote an entire module that allowed not just pretty much complete control over ChanSpy options but added ExtenSpy as an option. Gave them everything they wanted; restricted spying, targeted spying, restrictions on who could spy on who, multiple ChanSpy features codes for different spying needs. Not single person that bitched and whined about wanting this has f’ing used it or engaged in any testing or feedback

Perhaps if there was actual involvement, feedback, etc from the community more then Clearly might be encouraged to be more active. I get why Lorne stopped posting his weekly stuff, no one was really engaging in it (and just lurking and reading isn’t engagement).

Basically the car has been caught, figure it out. Been lead to water, so drink.

I suspect most people venting had already applied the 1 liner to extensions_override_freepbx.conf thats mentioned in a bunch of blogs (including mine since 2022) that secured it.

I remember expressing interest in it (and even made a suggestion), and still am but I don’t think I ever got the repo to test it

There have been release posts both here and on the FreePBX forums. I’m actually going to push another update this weekend. I’ll tag you this time around.