1 mx-one configuration, Mx-one configuration, Microsoft – AASTRA MX-ONE V4.0 OCS 2007 Quick Setup Guide User Manual
Page 9: Office communications server r2 configuration
Quick Setup Guide
Doc. No.
ASE/MXO/PLM/ 0123 / EN Rev.C Date: 01.12.2011
9/18
3.2.1 MX-ONE Configuration
A SIP trunk has to be configured in MX-ONE Telephony System as well the access code for
this route.
The setup presented below uses TCP as transport protocol, in this case the destination
access is expected to listening on port 5060 as default. This might be changed using SIP
route parameter “–remoteport”
In order to secure a good interoperability between MX-ONE and Microsoft
®
OCS 2007 R2,
we recommend the use of “Forced Gateway” because it will guarantee the same behavior
for all type of calls passing through MX-ONE and going to OCS 2007 R2.
number_initiate -numbertype ED -number 2110
number_data_initiate -externalnumber 2110 -minlength 4 -maxlength 5
sip_route -set -route 51 -uristring sip:[email protected] -fromuri0
sip:[email protected] -protocol tcp -codecs PCMA,PCMU
sip_route -set -route 51 -accept REMOTE_IP -match 192.168.222.46
ROCAI:ROU=51,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515
,TRM=4,SERV=3100000001,BCAP=000100;
#varc d5=1 forced gateway
RODAI:ROU=51,TYPE=TL66,VARI=00000000,VARC=00001000,VARO=0000090
0;
RODDI:ROU=51,DEST=2110,ADC=0005000000000250000001000000,SRT=1;
Server 1 has the IP address 192.168.222.56, so the route needs to be defined in
the Server 1.
ROEQI:ROU=51,TRU=1-1;
3.2.2 Microsoft
®
Office Communications Server R2 configuration
This guide describes the Microsoft
®
OCS R2 Standard Edition configuration with one pool.
Microsoft
®
Deploying Enterprise Voice documentation is used for this setup.
(
Open the Office Communications Server 2007 snap-in.