Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Can I populate msRTCSIP-Line using the system.directoryservices.accountmanagement .NET namespace from a c# program? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I like to do my AD maintenance with custom c# programs using the system.directoryservices.accountmanagement .NET namespace.  I've seen OcsAssignTelUri.wsf, but I really don't like WMI and VB.  I can modify any AD attribute with .NET -- is there any reason why populating the msRTCSIP-Line attribute won't work or would be a bad idea?  Would I need to set any additional msRTCSIP attributes, e.g. OptionsFlags? 
    Thanks!

    Friday, October 16, 2009 9:15 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you want to configure user accounts for Enterprise Voice in OCS R2 (and not just populate the Line URI for Dial-In Conferencing authentication usage) then you'll also need to configure additional attributes which control the Telephony Mode of the user.

    Take a look at these two related articles for more specific details:
    http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=20
    http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=29
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by a1.618 Monday, October 19, 2009 2:31 PM
    Saturday, October 17, 2009 12:07 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    There's definitely nothing to worry about here.. we're doing just that for a customer and it works like a charm.
    We've had some weird behavior only on site (but it has since gone away.. no idea if it was a hotfix or a machine boot) - if I populated the tel uri for an entvoice user, then you tried to configure another via the mmc snapin, you could suddenly assign the same extension twice and it wouldn't block (like it normally does).. but as I said that has since gone away and was not reproducible in our inhouse deployment.
    • Marked as answer by a1.618 Monday, October 19, 2009 2:31 PM
    Monday, October 19, 2009 11:51 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you want to configure user accounts for Enterprise Voice in OCS R2 (and not just populate the Line URI for Dial-In Conferencing authentication usage) then you'll also need to configure additional attributes which control the Telephony Mode of the user.

    Take a look at these two related articles for more specific details:
    http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=20
    http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=29
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by a1.618 Monday, October 19, 2009 2:31 PM
    Saturday, October 17, 2009 12:07 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    There's definitely nothing to worry about here.. we're doing just that for a customer and it works like a charm.
    We've had some weird behavior only on site (but it has since gone away.. no idea if it was a hotfix or a machine boot) - if I populated the tel uri for an entvoice user, then you tried to configure another via the mmc snapin, you could suddenly assign the same extension twice and it wouldn't block (like it normally does).. but as I said that has since gone away and was not reproducible in our inhouse deployment.
    • Marked as answer by a1.618 Monday, October 19, 2009 2:31 PM
    Monday, October 19, 2009 11:51 AM