Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Provisioning issues after Version 12 Upgrade

Discussion in '3CX Phone System - General' started by afinite, Oct 28, 2013.

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

    Joined:
    Mar 11, 2012
    Messages:
    18
    Likes Received:
    0
    We have "successfully" updated our Version 11 to Version 12, but seem to be getting 404s from the provisioning URL, even when we craft the URLs from our own browser.

    This is using Cisco 504G and 508G - we have two handsets which aren't playing ball, but 3 others work fine.

    HELP! Is there somewhere we can look in 3CX to find rejected handsets / MAC addresses?
     
  2. afinite

    Joined:
    Mar 11, 2012
    Messages:
    18
    Likes Received:
    0
    The handsets are all running 7.5.4 firmware
    Should we try older firmware?
     
  3. afinite

    Joined:
    Mar 11, 2012
    Messages:
    18
    Likes Received:
    0
    It would appear this is no longer possible in 3CX version 12 - phones must be manually provisioned, with option 66 as a helper, rather than as per the instructions on the 3CX site which say to use option 66 and the assign phone to extension / create function.

    You should instead create an extension manually and enter the provision information in the phone provisioning tab, complete with model and firmware.

    :(
     
  4. accelerated

    Joined:
    Jul 26, 2013
    Messages:
    10
    Likes Received:
    0
    We had that issue when we upgraded from V11 to V12. Somehow the provisioning on the phones was not updated. We have Cisco Spa509G and Cisco Spa525G phones.

    After some digging I found this :

    Cisco SPA5XXG Phones:

    3CX Phone System 11: http://10.172.0.2:5000/provisioning/$MA.xml
    3CX Phone system 12: http://10.172.0.2:5000/provisioning/%%ProvSubDir%%/$MA.xml

    The sub directory will look something like "asdfghert/$MA.xml"

    The new V12 includes a new sub-directory as underlined above. You can verify if you have the old V11 provisioning on your current phones by logging into the web page of the phone .

    We updated our DHCP server option 66 to reflect the new V12 provisioning address and factory re-set and re-boot all the phones and everything worked like it should.
     
  5. uknod

    Joined:
    Oct 30, 2013
    Messages:
    3
    Likes Received:
    0
    Yes I have the exact same problem. But looking at the last post, what is the directory, how do I find out what it is.
     
  6. einherjar

    Joined:
    Nov 19, 2012
    Messages:
    4
    Likes Received:
    0
    In version 12 the provisioning URL is listed in Settings --> Phone Provisioning --> General

    You can also find it manually in C:\ProgramData\3CX\Data\Http\Interface\provisioning\xxxxxxxx
     
  7. afinite

    Joined:
    Mar 11, 2012
    Messages:
    18
    Likes Received:
    0
    Hi
    I know what you're saying, but I'm fairly confident in version 11 we didn't have to manually enter a handset's MAC Address when provisioning an extension - instead we could use DHCP option 66 (which know about the new Randomised URL) and then just assign extensions freely from the phones screen.

    This seems to have been lost in Version 12 :cry:
     
  8. ian.watts

    ian.watts Active Member

    Joined:
    Apr 8, 2011
    Messages:
    532
    Likes Received:
    1
    There was that randomly added directory added under Provisioning.. adjust your Option 66 accordingly.
    No need to specify a MAC, no.

    They are pointing you to the place to find that randomly named folder, though.
     
  9. afinite

    Joined:
    Mar 11, 2012
    Messages:
    18
    Likes Received:
    0
    We have added the randomised directory URL, but have been told by support this is the way things should be now, so have bought barcode scanner to scan MAC address barcodes from handset backs / boxes in future.
     
Thread Status:
Not open for further replies.