Getting endpoint policy info programmatically

I wanted to share an approach you can use to find out your endpoint’s capabilities and policy settings through UCMA code. To give you an example of where this can be useful, imagine you have an application that creates conferences or provides services to conferences, and in order to work it needs to be able to invite anonymous participants. If the endpoint has this capability turned off in meeting policy, the application will fail or exhibit strange behaviour. You might already have exception handling to deal with the situations where the application tries to do something that’s prohibited by policy, but by that time your application is already running. By querying policy information, you can confirm that the necessary settings are there when your application starts and avoid unpleasant surprises later. Continue reading “Getting endpoint policy info programmatically” »

Trusted applications and policy settings

Unless your Lync environment has a single global policy for each type of policy setting (voice policy, conferencing policy, dial plan, etc.) you may run into problems where your UCMA trusted application endpoints don’t work properly with the default policy. A couple of common examples:

• Voice policy – the default collection of PSTN usages may not be appropriate for the PSTN calls initiated by your application
• External access policy – if your application needs to contact public IM or federated users and the default policy doesn’t allow this Continue reading “Trusted applications and policy settings” »