Tanjay does not update (R2) RRS feed

  • Question

  • I have uploaded and approved all instances of 3.5.6907.0 firmware. CX700 is currently on 1.0.522.101 ENU.

    Logging shows:

    02/06/2009 11:17:50,administrator@r2test.lan,,UCPhone,2/6/2009 11:18:12 AM,"0004F2BAA59F","C183R001160","Polycom","CX700","A","ENU",cpe.nbt;1.0.522.101;2/3/2009 3:55:16 PM,http://r2-ocs.r2test.lan/DeviceUpdateFiles_Int/UCPhone/Polycom/CX700/A/ENU/3.5.6907.0/CPE/CPE.nbt;3.5.6907.0;12/16/2008 4:43:58 AM

    and Wireshark trace shows:

    GET /DeviceUpdateFiles_Int/UCPhone/Polycom/CX700/A/ENU/3.5.6907.0/CPE/CPE.nbt HTTP/1.1
    Accept: */*
    User-Agent: Microsoft UCPhone Device
    Host: r2-ocs.r2test.lan
    Cache-Control: no-cache


    HTTP/1.1 200 OK
    Server: Microsoft-IIS/7.0
    X-Powered-By: ASP.NET
    Date: Fri, 06 Feb 2009 10:17:50 GMT
    Content-Length: 0

    and the same with CPE.cat. Both files exist in specified virtual (and physical) directory. After several hours still no update occurs.

    Any ideas?


    Johann Deutinger | MCTS Exchange 2007 / OCS 2007
    Friday, February 6, 2009 11:34 AM

All replies

  • The mystery deepens.

    My test device (Polycom CX700) took the update via OCS R2 update service 15 min. after the files were uploaded. Another 10 minutes later, while in the middle of a call, Tanjay rebooted!!! and reverted to 1.0.522.101 (1.23). Ever since I'm unable to update it.

    Trace shows the following sequence -

    1. Tanjay sends request to the updates server: 2009-02-08 22:13:27 W3SVC1 POST /requestHandler/ucdevice.upx - 80 - Microsoft+UCPhone+Device 200 0 0

    2. The answer is returned properly: 02/08/2009 17:13:27,,,UCPhone,2/8/2009 2:10:25 PM,"0004F2BA65C6","C181R001867","Polycom","CX700","A","ENU",cpe.nbt;1.0.522.101;7/22/2008 7:08:28 PM,http://ocs_server.contoso.com/DeviceUpdateFiles_Int/UCPhone/Polycom/CX700/A/ENU/3.5.6907.0/CPE/CPE.nbt;3.5.6907.0;12/16/2008 4:43:58 AM

    3. Tanjay NEVER attempts to download the files...

    Any ideas what is going on?

    Sunday, February 8, 2009 11:27 PM
  • Im having exactly the same problem.

    It did once update to 3.5.6907, but I rolled it back as I was having another issue (since fixed). It is now stuck on 1.0.522.101 and just does not update.

    I am seeing the same log entries as dragbot, ie the update server is giving it the correct 3.5.6907 update url in the logs. Unlike jwdberlin it is not attempting to download the new firmware.

    Friday, February 13, 2009 11:38 AM
  • We know the latest R1 update is 1.0.522.101 (1.23)

    Does anyone have a previous R1 firmware version? I want to rollback to lowest version via R1 Update service and then attempt to update to R2 3.5.6907.0

    If you have one and wiling to share - I can be reached here: drago at alltel.net

    Thanks in advance.


    Sunday, February 15, 2009 8:37 PM
  • The ordeal is finally over.

    I've managed to downgrade the device via R1 Update Services to 1.0.522.71 (1.23)

    After hard reset and creating DNS record for UcUpdates-R2.sipdomain.com the device promptly update itself to 3.5.6907.0 (1.23)

    Microsoft really need to look in to this issue...


    P.S. Special thanks to Jan Boguslawski from http://www.itacs.de/ and Johann Deutinger from http://www.ferrari-electronic.de/ for their lightening response to my request.
    • Edited by Drago Totev Monday, February 16, 2009 3:16 PM
    Monday, February 16, 2009 12:56 AM
  • Hi Drago,

    Could you give a little more info on how you actually achieved this? Will I need to redeploy R1 completley, move my user account back to that, and setup R1 update service? Sounds annoying, especially as I have removed all R1 services now.

    Did you get an older R1 firmware and roll back to that? If so, I would really like to know where I can obtain an old version.

    I also never heard of needing a ucupdates-r2 domain record.

    Thanks in advance,
    • Proposed as answer by Drago Totev Monday, February 16, 2009 3:05 PM
    Monday, February 16, 2009 1:19 PM
  • Here is quote from the deployment guide:

    "If for some reason Communicator Phone Edition cannot sign in and has never been able to do so, the device attempts to connect to the Update Server by using the DNS A record, hostname UcUpdates. This DNS A record should resolve to the IP address of the pool or the Standard Edition server that hosts the Update Server."

    Same apply to R2, only the record should be UcUpdates-r2.sipdomain.com

    Again, my problem was that after successful update from 1.0.522.101 (1.23) to 3.5.6907.0 (1.23) and then roll back to 522.101, Tanjay lost its ability to perform update.

    I used OCS R1 Update services to downgrade to 1.0.522.71 (1.23) after which the device took 3.5.6907.0 (1.23) promptly from OCS R2 Update Service.

    • Proposed as answer by Drago Totev Monday, February 16, 2009 5:42 PM
    Monday, February 16, 2009 3:16 PM
  • You should not have to install an OCS R1 environment to get the cx700 to update correctly, that is crazy.
    Friday, March 20, 2009 12:10 AM
  • Hi all,
            i've the same problem , but when i search a firmware 1.0.522.71 (1.23) i fall.... in microsoft site there's only 1.0.522.101 (1.23) ...anyone can help me in this search ? Drago, have you possibilty to send me via mail or other ?

    Thanks in advance


    Thursday, June 11, 2009 9:50 AM
  • Patience...
    Your device has updated the latest firmware, so just wait a little bit longer to update itself
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    • Proposed as answer by Fabio B. _ Thursday, June 11, 2009 9:55 AM
    Thursday, June 11, 2009 9:53 AM
  • I start with the beta version of tanjay, 1.0.0.xxx i don't remeber the exactly rel, but doesn't matter, anyway :

    - start device update with 1.0.522.101 (1.23) firmware approved, my tanjay keep 1.0.522.101 (1.23) correctly.
    - i load the last
    3.5.6907.31 (1.23) , my tanjay keep 3.5.6907.31 correctly .
    - roolback firmware to
    1.0.522.101 , tanjay correctly rollback
    - now i want to re upgrade to
    3.5.6907.31 (1.23) , but it doesn't upgrade ...after an check i've the same log e the same problem meet by Drago....

    i suppose that the only way to upgrade 3.5.6907.31 (1.23) is to first downgrade to
    1.0.522.71 (1.23) with OCS R1, SUS, sharepoint bla bla.. and then reupgrade to 3.5.6907.31 (1.23) with OCS r2 device update.

    this is my problem...

    Thursday, June 11, 2009 10:12 AM