Understand the Role of the Default Package
[This is preliminary documentation and is subject to change.]
Use the default package in Microsoft Lync 2013 Preview SDK contextual conversation applications to specify an application that starts on the receiver side of a conversation.
If an incoming conversation has no context then you can specify a default package that starts when the conversation is accepted. For example, you may want to start a customer relationship management application together with every incoming call, as in the following scenario.
John receives a telephone call on Microsoft Lync 2013 Preview from an important customer. When he answers, the most important data about the customer appears in his conversation window, including that they just opened a high-priority support case. He answers the customer by name and immediately acknowledges the issue.
You must use Install Registration to register context packages on a computer. To use a context package, register it with Lync 2013 Preview. For more information about installing and registering packages, see Register Contextual Conversation Packages and the walkthroughs listed at the bottom of this topic. Although multiple context packages can be installed on a computer, there is only one default package. To specify that a context package is the default, set the DefaultContextPackage registry key to 1.
On the sender side, the default package should start to run after an outgoing conversation is initiated. On the computer receiving an audio or instant message call, the default package starts to run in either of the following two circumstances.
A default context package is registered on the receiving computer, and the message does not specify an application ID.
A default context package is registered on the receiving computer, and the application ID in the message does not match an installed application.