1 denotes a protocol.
???ApplicationInstallPath???=???C:\\fdm.exe??? Path where the application is
installed
???Path???=???C:\\fdm.exe %user-id% Path information along with user
%contact-id%??? information to be passed as
parameters while launching the
application
???SessionType???=???REG_DWORD: 0 denotes that it??™s a local session.
00000001??? The application will be launched on
the local computer. 1 denotes that
it??™s a two-party and 2 denotes
that it??™s a multiparty application.
???ExtensibleMenu???=???Conversation Menus on which this application
WindowActions;MainWindowRightClick??? should appear. If you have not
specifi ed the ExtensibleMenu option,
the default values MainWindow-
RightClick and ConversationWindow-
Contextual are taken. In this case,
we have defi ned the Conversation
window??™s Action menu and the main
window when the user performs
the right-click.
418 Appendix A ??? Customizing the MOC Client
Summary
The MOC client is the corporate version of Windows Messenger (now Windows Live
Messenger). MOC works on the OCS 2007 platform to provide instant messaging (IM),
audio and video conversations.
MOC allows you to confi gure contacts from your corporate network, public IM network,
and federation network.
Administrators can customize the MOC client to display custom presence states, Web content
through custom tabs, and additional menu items that are not available in the default installation.
Solutions Fast Track
Adding Custom Presence States
?› You can customize MOC client features through XML fi les and Registry
modifi cations.
Pages:
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421