TIPS Clearly Devices module wrong extension

[Steve Dale]

Good afternoon,

I'm currently running incrediblepbx2020 on a fresh install on CentOS 7. Just installed this morning to replace my RPi. I was never able to get the Clearly Devices module working on the Pi, but I thought I would check it out here on CentOS and see if I had any better luck.

I am able to set up a template, and a model, and I can go through the configuration, I can add multiple extensions to one device, and when I edit each extension in the Clearly Devices module, it all looks right. However, when I first load the module, when I see the overview of all of the extensions, they all show as extension 2147483647, and that's how they try to register on my 270.

If I edit either one of the extensions, the edit screen shows the right extensions, but they're not right here, and they don't register correctly.

I'm using 14.0.10 of the module.

It would be very handy if I could get this working.

Thanks,
Steve

 

[krzykat]

CIP staff I'm sure can help you out, but out of curiosity, how long are your extension numbers? that number is a special number: Hex 7FFFFFFF

 

[Steve Dale]

I use 10 digit extensions, because each of the users of my system has a completely distinct DID, and it's easier for them to work with seeing the full number on the screen rather than an abbreviated or dissociated extension number. Having said that, I just created a couple extensions of four digits and they work as expected in the Clearly Devices module. So I'd say this is a bug, but I have a workaround if I need one.

Thanks for the suggestion.

 

[wardmundy]

@Tonyclewis may have some ideas.

 

[Tonyclewis]

That sounds like a bug but I have not realtmhearf if anyone using those kind of long extensions and they create lots of weird issues in FreePBX In the past. Can you open a support ticket with us and we can get it resolved. Https://support.clearlyip.com

 

[krzykat]

I use 10 digit extensions

Yep - that is what I was expecting. I too use 10 digit extensions on occasion and yes, if you do channel-spy - you'll get Asterisk announcing that it is listening to channel 2147483647 instead of the actual extension, real pain in the butt and was hoping that would have been cleaned up by the most recent asterisk, but apparently not.