Gateway sizing in OCS R2. When estimating the amount of ports on campus, use these guidelines:
· Light telephony users (one PSTN call per hour) should allocate one port for every 15 users. For example, if you have 20 users, you will require a gateway with two ports.
· Moderate telephony users (two PSTN calls per hour) should allocate one port for every 10 users. For example, if you have 100 users, you will require a total of 10 ports allocated among one or more gateways.
· Heavy telephony users (three or more PSTN calls per hour) should allocate one port for every five users. For example, if you have 47,000 users, you will require a total of 9,400 ports allocated among at least 10 large gateways.
· Additional ports can be acquired as the number of users or amount of traffic in your organization increases.
For any given number of users you must support, you have the choice of deploying fewer, larger gateways, or smaller ones. As a rule, a minimum of two gateways for an organization is recommended in the event one goes down. Beyond that, the number and size of gateways that an organization deploys are going to vary widely, based on a careful analysis of each organization’s volume of telephone traffic.
It’s best to work with your partner to define how many gateways need to be deployed for your OCS installation given size and future utilization. Each basic gateway does need to have a corresponding Mediation server so keep that in mind. We will be working on other OCS R2 guidance over the next few weeks.
It still works. I had a question today about custom states. We are still using four custom states and they are configured with the combination of registry settings and the presence XML file.
2 registry keys are needed.
1. CustomStateURL (Reg_SZ) file:///c:/windows/presence.xml
2. EnableSIPHighSecurityMode (Reg_DWORD) 0
Then you create the XML File such as this one:
<customStates> <customState ID="1" availability="online"> <activity LCID="1033">Out and about - use mobile</activity> </customState> <customState ID="2" availability="Busy"> <activity LCID="1033">at Starbucks</activity> </customState> <customState ID="3" availability="busy"> <activity LCID="1033">at lunch</activity> </customState> <customState ID="4" availability="do-not-disturb"> <activity LCID="1033">Executive Briefing with Customer</activity> </customState> </customStates>
Logout and exit the Lync client and restart. You should see the custom states.
I got a chance to do a Tuesday Tech talk on Unified Communications for Education and they recorded it for your viewing pleasure. I turned on my RoundTable for the session and demoed several pieces of UC including web conferencing, ActiveSync, OWA, CWA, software powered VOIP.
We had around 60 schools participate so I was happy with the turnout.
To watch me give an overview of Exchange Server 2007 and Office Communications Server 2007 and some demos visit here. Drop me a blog comment if you have any questions or feedback good or bad. :)
To see other upcoming or recorded Tuesday Tech talks for Education go here.
One of our partners Enabling Technologies was interviewed at VoiceCon by Blair Pleasant of CommFusion and UCStragegies.com. Bill Vollerthum and Christian Stegh of Enabling Technologies discuss unified communications, unified messaging and industry innovations on this podcast.
The OIP has been updated to include Lync 2010. If you are looking for what PBXs provide Direct SIP, Gateways, SBA information, etc. Then I suggest reviewing the updated site here.
One of the many interesting things we’ve added to OCS R2 is the idea of resiliency. In OCS RTM version when you were in an active call if your client lost connectivity to the Front-end server your call was terminated. In OCS R2 we don’t tear down the call if active. Some call-control is obviously not available until connectivity re-established but the call goes on.
Some other great aspects were adding typing suppression so that typing during a call would not sound loud and improvement of “comfort noise”which reduces hisses and smoothes over discontinuous flow of packets in the call, as well as echo suppression to reduce echoes on call setup.