locked
OCS 2007 with Cisco RCC RRS feed

  • Question

  • We have been using OCS 2007 with Cisco RCC in our site.
    In our client PC's tasktray, Communicator's icon is displayed as
    "Can not connect phone system" with warning mark.
    But Communicator is working correctly with RCC.
    The message is displayed on only task tray.
    After I call through Communicator with RCC once, the message is cleard.
    Why is the message displayed on the task tray icon despite RCC works correctly ?

    Our OCS enviroment is the following system.

    OCS : OCS 2007 R1 Enterprise Edition.
    Cisco : CUCM 6.1 and CUPS 6.1

    minoo
    Tuesday, June 16, 2009 6:05 AM

All replies

  • Is your user a CUPS enabled? If yes, put your presence address on Server URI, and you need to create a Host Authorization and Route to CUPS

    Regards,

    Emerson
    Emerson Moraes
    Tuesday, June 16, 2009 12:46 PM
  • Emerson,

    All users are enabled on CUPS. The settings for OCS and CUPS is no problem.
    And we can use Communicator with Cisco RCC correctly.
    Nevertheless, the warning message is displayed on "only" task tray icon
    when we signed in to Office Communicator every time.
    The warning message is disapeared after we tried to click to call at once.
    Is the message displayed temporary ? I think it is not too a problem..
    Normally, the SIP/CSTA message send to CUPS when we signed in to Communicator
    in the RCC, but it seems the information is not reflect to task tray icon in our case.
    So I am wondering why this is happened.

    Regards,

    minoo
    Thursday, June 18, 2009 4:48 AM
  • Hi,
    This happens usually when you have your extension assigned to multiple cisco phones. OCS isn't sure which one to control, so it waits until you've placed a call and used a phone one time. Whichever phone you use, OCS will control for that session.

    That's been my experience anyway. If you define the device in the line uri, like this - tel:1234;device=SEP112233445566 it seems to clear this up as well - explicitly defining which phone MOC is going to control.

    Regards,
    Matt

    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    Friday, June 26, 2009 3:25 PM
  • Matt,

    Thank you for the reply.
    We are using the extension mobility for cisco phones.
    Is this same thing you pointed ?
    Perhaps, this may affect to our MOC behavior..
    Our line uri is set like tel:1234;phone-context=dialstring,
    not defined the device.

    Regards,
    minoo
    Thursday, July 9, 2009 1:46 AM