How to make sure that Office Communicator uses the right Location Profile rules?

In case you need to confirm that Office Communicator uses the correct Location Profile for a particular user, you can open the user’s Office Communicator trace (//%userprofile%/tracing) and search for “LocationProfileDescription”. All regular expression rules and patterns will be shown, similar to:   <LocationProfileDescription xmlns=””><Name>RC</Name><Rule><Pattern>…


OCS 2007 German dialplan example

This blog article presents and explains an OCS 2007 Dialplan that has been created for the location Germany (Country code +49) Cologne (Area code 221). In this example the company has a local subscriber number 000 and a 4 digit extension range. We assume that there is only one OCS 2007 Mediation Server with the…


OCS 2007 dialplan using non-DID numbers

In a previous blog article OCS 2007 dialplan fundamentals I have excluded the complexity around non-DID (Direct Inward Dialing) numbers for syntactic reasons. In this blog article I will describe how to handle non-DID numbers in an OCS 2007 dialplan. A non-DID number is a phone number, that cannot be reached directly from the PSTN….


Why Location Profile on OCS 2007 Mediation Server?

In my last blog article OCS 2007 Dialplan fundamentals I have explained that we need Location Profiles in order to maintain the users dialing behavior before the OCS installation. A Location Profile is a set of regular expressions that will be applied on a called party number that is not in +<E.164> format. In General…


OCS 2007 Dialplan fundamentals

I have noticed that many people, in particular those who have a telephony background or were working with common IP PBX solutions, try to match their gained dialplan know how, that they acquired over the last couple of years with many, many PBX/IP PBX projects, on OCS 2007. While there are few similarities with other…