New SNOM DECT (M700) firmware with uaCSTA supported by 3CX ?

[SECOIT GmbH]

Hi everyone,

I saw something today that I have been waiting for for ages now: Snom released firmware 450B07 (RC at least) https://service.snom.com/display/wiki/DECT+M-Series+Firmware.
This is a significant change to the 410 most important for me the implementation of uaCSTA starting with 420.

So a few questions to 3CX (or the brave ones out there who already tested):

• Will firmware 450 on M700 work with 3CX v16? Also in a multi-cell environment?
• According to https://www.3cx.com/sip-phones/firmware-update-snom-dect/ it says "... enter the highest currently available firmware as per snoms support website ...". So again, is 450 safe to use with 3CX v16? I'm simply careful since it's a major step from 410.
• I guess even if all works fine with 450 I don't expect CTI via uaCSTA will be working yet (didn't upgrade yet since I'm not brave enough). Are there any plans to get CTI working with Snom IP DECT? That would make some 3CX users really happy...

Thanks,
Michael

 

[cobaltit]

I guess it depends on your definition of 'work'. Any SIP standard device should work with 3CX, and even more so if that manufacturer is already supported. If you are asking for an official answer from 3CX as to if/when a template and official support might happen I wouldn't hold your breath. 3CX is pretty quiet about confirming anything, and if you do get an answer it's going to be vague. Yealink and Snom are one of the better supported brands though so I'd feel pretty confident any new devices from either of them would be supported at some point.

 

[SECOIT GmbH]

If it was a standalond DECT AP I'd simply try. But I use the M700 only as multi-cell and that's why I haven't tried upgrading w/o some form of confirmation that it will work properly.

 

[cobaltit]

Haven't done a multi-cell deployment but what are you actually worried about? Do the multi-cell setups actually try to register the SIP account on each base station?

 

[SECOIT GmbH]

It depends to which AP the phone is connected to. That's the IP used to communicate. Also there is a proper handover between APs.
That's why I'm careful... It's not as simple under the hood as connecting a standalone SIP client.

 

[OliH]

Hi @ll,
today i stumbled on the snom update for the M700 update.
I am interested in your experience how the update perform on a 3cx v16 installation.
Does uaCSTA works? Or does it even works like the older 410 branch?
It would be great if somebody can share his practical knowledge with us.
We also use the M700 in a Multicell envoirment and therefore we are careful in deploying updates, and the snom wiki tells us that a downgrade isnt possible...

 

[dandersonn]

Good morning,

yesterday I updated a M700 Multicell environment to branch 450 without any problems so far.
Customer is using about 50 Cells and 150 M85 handsets.

I didn´t test if uaCSTA works.

I will give you an update if any errors occure

 

[dandersonn]

Update:
uaCSTA doesn´t work. It´s still the "Make call"
rest works fine.

 

[cobaltit]

Missed your response but that is what I would expect. The roaming between cells shouldn't be an issue as I imagine (wireshark would confirm) that 3CX would just request authorization when it comes from a new IP when roaming and then the credentials would be resubmitted. I wouldn't expect uaCSTA to work as the firmware support is just one piece of the puzzle. The template would have to be updated as well.