Cannot provision SNOM M700 DECT Base

Discussion in '3CX Phone System - General' started by kabooz, Feb 1, 2017.

Thread Status:
Not open for further replies.
  1. kabooz

    Joined:
    Feb 1, 2017
    Messages:
    1
    Likes Received:
    0
    Hi,

    I'm trying to provision a SNOM M700 base following this guide: https://www.3cx.com/sip-phones/snom-m300-m700-dect/ however following the provisioning link generated on the FXS/DECT Details page the web server is giving me an http 500 error.

    The M700 syslog shows
    loc3 .Info 1970-01-01T00:00:18Z 173-[ RemCfg: Attempting fetch of file: http://192.168.1.240:5000/provisioning/d3llt9qfrg/cfg000413XXXXXX]

    and in the 3cxManagementConsole.log file i get
    2017/02/01 14:29:45.516|2616|0008|Err|Connection id "0HL2AKIVTTE6H": An unhandled exception was thrown by the application.

    Any ideas what I can do to fix it? The server is recently upgraded from v11 if that can affect anything, also there are no system updates showing in the update page of the management console.
     
  2. Mat Tru

    Joined:
    Feb 1, 2017
    Messages:
    5
    Likes Received:
    1
    ...Exactly the same issue here!

    Brand new installation of 3cx (v15 pro license), brand new M700, inserted the autoprovisioning link into the M700 base, save and reboot, no config applied and the above error in 3cxManagementConsole.log

    We can't provision the base!

    BTW: should I see something if I type the provisioning url in a browser? I see just a blank page, I thought I saw an xml config file or something like that.

    Thanks in advance.
     
  3. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    6,016
    Likes Received:
    420
    Hello @Mat Tru

    Are you on windows or linux?
     
  4. Mat Tru

    Joined:
    Feb 1, 2017
    Messages:
    5
    Likes Received:
    1
    Hello! I'm on windows.
    (Windows server 2012 R2, domain joined machine).

    Thanks.
    Mattia
     
Thread Status:
Not open for further replies.