...
| No Format |
|---|
Media: Communicator 2007 <-SRTP-> OCS <-SRTP-> OCS med serv <------------RTP----------> Asterisk <-> PSTN |
This recipe needs one bug to be resolved concerning RTP flowing from Asterisk to the Mediation server. Solution coming soon.
Prerequisites
- Linux machine with Asterisk, a number plan and PSTN connectivity
- Linux machine with OpenSER 1.2.1 or higher http://www.openser.org/mos/view/Download/
- Microsoft Office Communications Server 2007 core installation
- Windows 2003 machine to install OCS Mediation Server
...
Fortunately, the Microsoft Communicator translates numbers automatically to this format, leaving out the +, (), spaces and dashes, even when starting a call from Microsoft Outlook. However, we have to add at least one rule. The normalization rule is written in .net regular expression format. See http://www.regular-expressions.info/tutorial.html for more explanation of regular expressions. In our case, we translate any number starting with a zero to a Dutch number:
| No Format |
|---|
\^0(\d*)$ -> \+31$1 |
It basically means that for any new translation (^) of a number that starts with a 0 and then containing any number of digits \d* it should take the part of the number between brackets () and use it as variable in the translation. The translation adds +31 to it.
THE '+' SIGN IS ABSOLUTELY CRUCIAL!!!!! Don't forget to put it there! Please double check whether it's in the config! Don't say we didn't warn!
...
Finally add a 'route' under the 'routes' tab.
Here is defined that for numbers matching a certain regular expression, the call should be routed to our mediation server. The regular expression states in this case that any number should be forwarded:
| No Format |
|---|
\^(\d*)$
|
Part of the route definition are the phone usages that are allowed for this route.
...