locked
Auto-Attendant and Subscriber Access Presence Offline RRS feed

  • Question

  • Hi,

    I was wondering if anyone else had exprienced this and if there is something i am missing.

    The issue is that the Auto-Attendant, Subscriber Access and Conferencing Attendant all have presence of Offline.

    They all work great, it's just the prensence!

    Any ideas welcome.

    Thanks again,

    Alex.
    Monday, March 15, 2010 12:14 PM

Answers

  • It is by design, they are just contact objects that do not participate in Presence sharing.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by Alex_Harvey Sunday, March 21, 2010 1:06 PM
    Thursday, March 18, 2010 8:08 PM

All replies

  • Hi Alex,

    I can just confirm I have the same situation.
    My Exchange UM integration works fine but both the AD contact objects (Auto-Attendant and Subscriber Access) shows the presence as Offline.

    /mk
    Tuesday, March 16, 2010 11:48 AM
  • I can also confirm this on the conferencing attendant and the UM contact objects. So i guess this is by design.

    // Tommy Clarke - Blog: http://www.cinline.se/ - Twitter: http://twitter.com/itommyclarke
    Thursday, March 18, 2010 7:43 PM
  • It is by design, they are just contact objects that do not participate in Presence sharing.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by Alex_Harvey Sunday, March 21, 2010 1:06 PM
    Thursday, March 18, 2010 8:08 PM
  • Great, thanks for clearing that up Jeff.

     

    Alex.

    Sunday, March 21, 2010 1:07 PM
  • Hi ,

     

    Can you please help as my auto attendant and subscriber access is not working .

    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Date:          1/20/2011 12:45:43 PM
    Event ID:      1004
    Task Category: UMCore
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:     Description:
    A call was received with the following parameters:
    Calling Party: "sip:umtest@test.com",
    Called Party: "sip:+14185490051@test;user=phone",
    Diversion Information: "",


    Thursday, January 20, 2011 5:50 PM