<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style>.EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; }</style>
</head>
<body>
<font face="Calibri, sans-serif" size="2">
<div>Hello Everyone,</div>
<div> </div>
<div>We’ve connected OCS to Asterisk via OpenSips, and the voice functionality is working fine. I was wondering if anyone out there who has implemented a similar system would be willing to share any information on how they have implemented this, specifically
with regards to URI numbering on the OCS side. So far, we’ve done this:</div>
<div> </div>
<ol style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>Extensions in * are 4-digit, and the Caller-ID is configured with this number. We append the area code and prefix for outbound calling. In order for the Communicator to pop-up with the username, we’ve had to put the full number with a + so that the normalized
number will match the AD phone number. I would assume that we could fiddle with the Caller-Id with macros or something to correct this.</li><li>We really aren’t sure how to handle the URI for OCS, since most people will continue to use both systems. Right now, it’s their 10-digit number without the +, but I really don’t know what a good solution is here. We add a SIP channel to their Dial() statement
so that the desk phone and OC ring at the same time; we don’t use Trixbox or anything like that, just a vanilla 1.4 installation</li><li>Calls from OCS use the URI configured for the account, so it’s number only. I would assume there is a way to use LDAP with * to match a number to AD information and populate it that way.</li></ol>
<div> </div>
<div>Overall, I’m fairly pleased with the setup so far. Call quality is good, people like the ability to dial straight from Outlook and OC, and people can use it on the road as a smartphone, without VPN access required. We have a lot of remote users and daily
conference calls, so it’s going to save money for that sort of thing as well.</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>Kevin</div>
<div> </div>
</font>
</body>
</html>