End of Support for the M700 on 3CX V18

Content:

With the version 18, 3CX decided to furthermore improve security and therefore ended the support of specific Cipher Suites that are considered Not Best Practise anymore. Additionally, v18 will simplify the DNS configuration with its DNS Helper feature. These changes prevent the M700 - a product that has been declared end of sales/support (EOS) June 2020, after 6 successful years in the market by us - to be auto-provisioned by the 3CX SIP server when updated to V18.

Local installations

The only way an M700 base station can be provisioned on 3CX V18 is to switch off the DNS Helper feature, and use the provisioning method Local LAN. Any other provisioning method will request an HTTPs connecting to the 3CX server and therefore fail.

• Page:
  Adding an M5 or M6 repeater in a multicell environment
• Page:
  After upgrading my DECT base to 400B02 my M65 cannot register anymore
• Page:
  After upgrading my DECT multicell system, I can't access the WUI anymore
• Page:
  After upgrading the base to version 400B02 the provisioning via HTTPS/TLS isn't working anymore
• Page:
  Assign a handset to a SIP account on a M300
• Page:
  Attended or blind call transfer of the 2nd call results in merging the 1st and 2nd incoming call
• Page:
  Can I daisy-chain M5 DECT repeaters
• Page:
  Can I install a mixed system with M700 and M900 together
• Page:
  Can I register a 3rd party DECT handset or repeater to a Snom M300,M700,M900 base station
• Page:
  Common faults on M-series DECT base stations: causes and solutions
• Page:
  DECT Solution FAQ
• Page:
  Difference between DECT and configuration synchronization
• Page:
  Do the M300,M700,M900 support GAP
• Page:
  Dropped connections and failed handset handovers in a DECT multi-cell
• Page:
  Dropped SIP registrations on DECT multicell
• Page:
  End of Support for the M700 on 3CX V18
• Page:
  How can I trigger a settings sync on a DECT M300,M700,M900
• Page:
  How to disinfect my DECT handset
• Page:
  How to factory reset an M10 KLE handset
• Page:
  How to factory reset an M15 SC handset
• Page:
  How to factory reset an M18 KLE handset
• Page:
  How to factory reset an M55, M56, M58 M500 handset
• Page:
  How to get a Log from the DECT base
• Page:
  How to get a SIP trace from the DECT base
• Page:
  How to use the pound key to debug in-a-call issues
• Page:
  Is it possible to assign more than one DECT handsets to an identity
• Page:
  Is it possible to assign more than one identity to a Snom DECT Handset
• Page:
  Is the differentiated ringtone feature supported on M300, M400, M700, M900
• Page:
  Is the Snom M85 ATEX 2014,34,EU compliant a for use in potentially explosive atmospheres
• Page:
  M900 and LLDP protocol
• Page:
  My DECT M-Series base is resetting the ethernet link periodically
• Page:
  My M700,M900 refuses to join the DECT chain
• Page:
  Snom products lifecycle
• Page:
  Troubleshooting Audio Issues DECT M700,M300,M85,M65,M25
• Page:
  What DECT frequency bands are supported by M-series base stations
• Page:
  What does the cross (X) icon means on a DECT handset?
• Page:
  What does the error - Insufficient capacity or Insufficient resources - mean
• Page:
  What does the error -Multi cell system version conflict , Provider conflict , Primary conflict IP- mean?
• Page:
  What is the meaning of the LED colours on the M300, M700 and M900
• Page:
  What is the syntax of the LDAP filter on the M300,M700,M900
• Page:
  Why am I not able to add a repeater to a M300, M400, M700 or M900
• Page:
  Why did the central address book icon disappear on my handset
• Page:
  Why does my local central directory does not import contacts from the .txt file?
• Page:
  Why does the configured SIP Server change after I reboot a M300, M700, M900
• Page:
  Why my Snom M65 doesn't show the transfer Key