Paul Duffy Director, Technical Strategy Modality Systems UNC306 Agenda Where does it all fit in? Concept / technology review Deployment considerations Now what? Q&A.

Download Report

Transcript Paul Duffy Director, Technical Strategy Modality Systems UNC306 Agenda Where does it all fit in? Concept / technology review Deployment considerations Now what? Q&A.

Paul Duffy
Director, Technical Strategy
Modality Systems
UNC306
Agenda
Where does it all fit in?
Concept / technology review
Deployment considerations
Now what?
Q&A
Where does it all fit in?
OCS 2007 R2 Roles
Management
Information Worker (UC endpoints)
Remote
Users
Reverse Proxy
Communicator
Phone Edition
Meeting Console
Communicator
Attendant
Console
MOM
MMC
WMI
Access Edge
Front End
Federated
Company
Back End
ABS,DL,Content
Active
Directory
Archiving
Web Edge
Monitoring
A/V Edge
SIP Trunk
PSTN and
Mobile Phones
TDM
PBX
Registrar, Proxy, Presence
Response Group
SQL Database
Group Chat
Mediation
Server
A/V
MCU
Web Conf
MCU
App Share
MCU
Exchange
2007 SP1
CWA
Server
SIP/Media
Translation
Audio, Video
Slide/Meeting
Content
Desktop
Sharing
Email, Unified
Messaging
Communicator
Web Access
PSTN
GW
IP PBX
Archiving, CDR & QoE Architecture
Front End Server
MSMQ
Archiving Server
MSMQ
Archiving
+ CDR
Agent
Archiving
Service
Archiving DB
Monitoring Server
MSMQ
QoE
Agent
MSMQ
MSMQ
MSMQ
CDR
Service
CDR DB
QoE
Service
QoE DB
Concept Review
Archiving
Only Instant Messaging is archived
No file transfer
No media
This can help meet compliance requirements
I am not a lawyer: domain expertise is needed
Exactly What is Archived?
Instant message data in 2 party and multi-party
(group IM)
“From”, “To”, “Time” and message body
There are considerations for where the conversation
is occurring
Archives both internal & federated communications
Variety of configuration options (global, individual, etc)
Database schema is defined in product documentation
IM Archiving Architecture (Logical)
Client 2
Client 1
Front End Server
Archiving
Agent
MSMQ
Client ‘n’
Archiving Server
MSMQ
Archiving
Service
Archiving DB
Configuration Options
Global IM Archiving Settings
Globally set: no users/all users/some users
Internal/federated or all communications
Pool-level IM Archiving Settings
Associate pool/front end with archiving server
Specify Error Handling Behavior (‘critical mode’)
Usually enable all pools or none
Be aware of where messages will be archived
‘Critical’ Mode – Critical to Understand
‘Critical’ mode helps ensure archiving occurs
If archiving failure occurs – OCS shuts down
Two key parameters – configurable with WMI
TimeToBeReceived
TimeToReachQueue
Think carefully about enabling this
Consider exactly what the timers will do
Configuration Steps
Install Message Queuing
Install SQL Server
Install and activate monitoring server
Associate front-end(s) with monitoring server
Configure global setting
Configure user archiving settings if necessary
Start service
Configuring Archiving
CDR – Call Detail Records
Provide details about all ‘calls’ made
Peer to Peer
Conferences
VoIP
This captures usage not data
Useful for billing, utilisation
Can provide useful management ROI data
Not a compliance solution
CDR – What's Recorded
Peer to Peer sessions
Start & End Times
Media Type,
From & To Users
Client Versions
Message Count
Conferencing Sessions
Attendees & Roles
Start & End Times
Conferencing servers
Conferencing server Join & Leave Times
Client Versions
VoIP Sessions (UC to PSTN & PSTN to UC)
P2P + From/To Numbers
Forwarded by Number
Gateway
CDR Architecture (Logical)
Client 2
Client 1
Client ‘n’
SQL Server
Reporting Services
Front End Server
CDR
Agent
MSMQ
Monitoring Server
MSMQ
CDR
Service
CDR DB
Configuration Steps
Install Message Queueing
Install SQL Server
Install SQL Server and reporting services
Install and activate monitoring server
Start service
Deploy reports
Configure logging
Associate pool/servers with monitoring server
Ensure port 5069 is open on load balancer
Start service
Note: Not all steps may be required if IM archiving is configured
Configuring CDR
QoE – Including Primer
Who is This all About?
Not the IT Professional!
Conventional vs. Voice Data
Conventional data (“elastic”):
E-mail, File transfer, and Web applications
Relies on TCP for reliable operation
Tolerant of variations of network
Voice data (“inelastic”):
VoIP traffic
Relies on UDP for better performance
Intolerant of effects of congestion
22
Absolute Categorization Rating (ACR)
Traditional Assessment of Voice Quality
Subjective test of Voice quality based on a scale of 1–5
Scoring is done by group of testers listening to calls
Listeners rate the calls
Mean Opinion Score (MOS) is the average ACR
Rating
Quality
Impairment
5
Excellent
Imperceptible
4
Good
Perceptible but not annoying
3
Fair
Slightly Annoying
2
Poor
Annoying
1
Bad
Very Annoying
Voice Quality Test Options
Subjective:
Uses panel of testers to determine VoIP quality
Results vary from one test to another
Active: Inject reference signal into stream and compare it to
the output at other end
Objective:
QoE Server approach
Similar to ITU ‘PESQ’
Passive: Output signal is compared to a model to predict
perceived quality
Voice Quality
Key to success of IP Telephony + a
UC deployment
Subjective and elusive goal
Good vs. Bad varies
Traditional VoIP very sensitive to network issues
Matching existing TDM performance is difficult
Traditional approach – very tight management
‘NSQ’
NSQ (‘Traditional’) Approach
Uses QoS to manage performance
Applied only to network you control
Can be expensive to implement
Does not handle payload ‘device’ corruption
Quality can still be poor when network is good
Just one component of QoE
QoE – Quality of Experience
A key Microsoft differentiator
A different approach to the traditional one
Both a strategy and a toolset
Never consider QoE monitoring optional
Use the collected data
There is still no Panacea!
Quality of Experience
Considers all factors influencing user perception:
Hardware
Application
Psychological
Physical parameters
Media stack continually monitoring / optimizing
Intelligent end points for authorization and encryption
Bad devices worse impact than bad network
Focuses on both network and payload content issues
e.g. Noise level, echo, gain and double talk
Codec (Coder/Decoder)
Converts analog voice for transmission
Uses compression to reduce packet size
Compression affects VoIP quality
Most traditional VoIP uses narrowband, old
technology codecs such as G.711 and G.729
RTAudio: Microsoft’s wideband codec
OCS 2007 RTAudio Codec
Built-in intelligence
Multi-rate codec
Robust under loss and jitter
Packet Loss Concealment
Time-warping jitter buffer
Highly efficient use of Bandwidth
Codec
Payload Rate
RTAudio
(8kHz)
11.8 Kbps
RTAudio
(16kHz)
29 Kbps
G.711
64 Kbps
Wideband mode transmits 50Hz – 7000Hz voice frequency range
(vs. G.711 @ 300Hz – 3400Hz )
Variable bit-rate encodes voice based on variations in conversation to
save bandwidth
Supports six wideband and three narrowband rates
Higher fidelity at lower bandwidth that traditional VoIP codecs
‘HD experience’ for telephony
QoE Summary
Right-provision network
Use DiffServ when traffic control is required
OCS 2007 does not support IntServ
OCS 2007 does not implement or require CAC
Use OCS 2007 qualified UC devices
QoE focuses on the network and payload
Hear the Difference!
QoE Architecture
Client
(UC endpoint)
Leg A
Front End Server
QoE
Agent
SIP – PSTN Gateway
Mediation Server
MSMQ
Leg B
Leg C
Client
(PSTN endpoint)
Monitoring Server
MSMQ
QoE
Service
QoE DB
In this example, QoE reports
generated for legs ‘A’ and ‘B’
only
Systems Center
Operations Manager
(alerts)
SQL Server
Reporting Services
QoE Monitoring Scenarios
Users – Helpdesk, NOC, Engineering
Near Real-time monitoring
Quality of Experience validation
VoIP planning
Don’t consider this optional!
Key Metrics per Call
Conversational MOS
Listening MOS
Sending MOS
Network MOS / Network MOS Degradation
Packets / Packet loss rate
Jitter / Round Trip Time
Latency
Burst
SIP Session data
Endpoint IP address/mask
Inside/outside user flag
ICE Connectivity Path
Codec(s)
Capture / Render device
Noise Level / Signal Level
QoE Reporting - Mean Opinion Score (MOS)
Wideband vs. Narrowband MOS
Listening, Sending, Network MOS reported on
wideband scale
Conversational MOS on narrowband
Be aware of scale when comparing vendor-vendor scores
For MOS, need to compare similar scenarios
Larger sample sizes deliver more meaningful average scores
Minimum of 30 calls
MOS values between tests cannot be compared unless test
conditions are the same
Average of scores collected during a “subjective” ACR voice
quality test
MOS Detail
Network MOS:
Considers only network factors (i.e. Codec used, Packet
loss/reorder/errors, Jitter)
Useful for identifying network conditions impacting audio quality
Supported by all UC endpoints, except for Exchange 2007 UM
Listening MOS:
Considers codec used, capture device characteristics, transcoding,
mixing, defects from packet loss/packet loss concealment, speech level,
and background noise
Useful for identifying payload effects impacting audio quality
Supported by Communicator 2007
QoE Reporting: Two Classes of MOS Scores
Listening Quality MOS (MOS-LQ):
Commonly used class of MOS scores for VoIP deployments
Does not consider bi-directional effects, such as delay or echo
Microsoft UC provides three wideband MOS-LQ metrics:
Network MOS: Audio played to user
Listening MOS: Audio played to user
Sending MOS: Audio sent from user
Conversational Quality MOS (MOS-CQ):
Considers Listening Quality on both ends, plus bi-directional effects
Microsoft UC provides one narrowband MOS-CQ score
Conversational MOS: Audio played to user
Max MOS Rating by Codec
Network MOS scores vary considerably, based on call
type
Call type determines codec used
Different codecs have different max MOS ratings for
Network
PC to PC appears to have better VoIP quality than PC to
PSTN (RTAudio NB) when it may not
Scenario
PC – PC Call
Codec
Max Network MOS
RTAudio WB
4.10
Conference Call
SIREN
3.72
PC – PSTN Call
RTAudio NB
2.95
PC – PSTN Call
SIREN
3.72
Configuration Steps
Install Message Queueing
Install SQL Server
Install SQL Server and reporting services
Install and activate monitoring server
Start service
Deploy reports
Install management pack (optional)
Configure logging
Associate pool/servers with monitoring server
Ensure port 5069 is open on load balancer
Start service
Note: Not all steps may be required if IM archiving is configured
Configuring QoE
Deployment Considerations
Archiving & Monitoring Roles
OCS 2007
“Archiving & CDR” Server Role
QoE Server available out-of-band
OCS 2007 R2
Archiving server role
Monitoring server role = QoE + CDR
Basic Topology Options
Everything can be collocated with SE server!
Clearly not recommended for large deployments
Requires full version of SQL Server
Monitoring and archiving roles can
be collocated
Databases can be clustered
Each role can be collocated with its database
Databases can be collocated with the BE database
SE: Standard Edition
BE: Back-end
Pool Association Options
Pools associated to one monitoring server
Mediation servers associated to one monitoring
server
Front end servers associated to one archiving
server
Archiving or monitoring servers can support
multiple pools
Sizing & Capacity Planning
Throughput:
200K users per Monitoring Server
300K users per Archiving Server
Storage:
Databases not designed for long-term storage
Query performance will suffer first
Pay attention to disc recommendations in
planning guide to ensure good performance
Calculating Space Required
DB size = (DB growth per user per day) * (# users) *
(# days)
Using numbers from the Office Communications Server
planning model:
CDR database: 8.8KB per user per day
QoE database: 16.8KB per user per day
Archiving database: 75.5 KB per user per day
You may need to vary these numbers if your usage is
different than the model
Clearly, adjusting retention time can greatly impact
DB size
Be Careful!
Multiple Archiving Stores
Clients in an IM conference, hosted on Pool ‘B’
Client 1
Client 2
Pool ‘A’
Client ‘n’
Pool ‘C’
Pool ‘B’
Archiving
Agent
Archiving
Agent
Archiving
Agent
Archiving DB
Archiving DB
Archiving DB
Note: Archiving architecture is simplified on this slide for readability
• Data may be archived into multiple different archiving stores
• User settings may appear inconsistent during conferences
• In the MSFTSIPLogoptions WMI class, configuring the ArchivingBEToken value can
control behavior
Fault Tolerance – Scenario 1
Front End Server
L
o
a
d
b
a
l
a
n
c
e
r
Archiving
Agent
MSMQ
Archiving Server
MSMQ
Front End Server
Archiving
Agent
Archiving
Service
Archiving DB
MSMQ
If ‘critical’ mode is enabled, failure of the
archiving infrastructure will result in OCS
service outage – regardless of whether there
are multiple front-end servers
Fault Tolerance – Scenario 2
Front End Server
L
o
a
d
b
a
l
a
n
c
e
r
Archiving
Agent
MSMQ
Front End Server
Archiving
Agent
MSMQ
Archiving Server
MSMQ
Archiving
Service
Archiving DB
Archiving Server
MSMQ
Archiving
Service
Archiving DB
If ‘critical’ mode is enabled, failure of the archiving
infrastructure will not cause OCS service outage
(assuming archiving redundancy is present)
Now What?
What Might You use CDR Data for?
Billing
Utilisation
ROI
Other, extensible reporting
Probably not compliance
Working with CDR Data
What Might You use QoE Data for ?
Helpdesk troubleshooting
Early warnings
Capacity monitoring
Verifying deployment goals
And many more uses...
Working with QoE Data
Review
Where does it all fit in?
Concept / technology review
Deployment considerations
Now what?
Q&A
Additional Resources on Web
Office Communications Server Tech Center:
http://technet.microsoft.com/enus/library/dd250572(office.13).aspx
Archiving database schema:
http://technet.microsoft.com/enus/library/dd572568(office.13).aspx
CDR database schema:
http://technet.microsoft.com/enus/library/dd572914(office.13).aspx
New CDR Data in OCS 2007 R2
Multipart MIME invites
Boss/Admin
Team Call
Capture both incoming and outgoing gateways
Correlation ID
Access types – internal/external
Auth types: enterprise, federated, PIC,
anonymous
New in OCS 2007 R2 – New QoE Data
Audio Quality
New Echo metrics for the client
New Speech/Signal and Noise metrics for the client
Video Quality Metrics
PSTN
Mediation Server to Gateway leg reporting
Transport
Network Connectivity Information
Wired v.s. WiFi
Link Speed
VPN or not
Sample SQL Queries:
Find top 10 A/V Conferencing Users (CDR)
select top 10
users.UserUri,
count(*)
from
McuJoinsAndLeaves as mjal
join Users as users on (mjal.UserId=users.UserId)
join Mcus as mcus on (mjal.McuId=mcus.McuId)
where
mcus.McuType = 'audio-video'
group by
users.UserUri
order by count(*) desc
Sample SQL Queries:
Find Total Number of PSTN to UC calls (CDR)
Select Count(*) as 'Number Of PSTN to UC
Calls' From VoipDetails as voipd Join
SessionDetails as sd on (voipd.SessionIdTime
= sd.SessionIdTime and voipd.SessionIdSeq =
sd.SessionIdSeq and sd.User1Id is null) and
FromNumberId in (SELECT PhoneId from
Phones) and GatewayId is not null
Sample SQL Queries:
Find IM Messages (Archiving)
SELECT * from LcsLog.dbo.Messages,
LcsLog.dbo.Users where
LcsLog.dbo.Users.UserId =
LcsLog.dbo.Messages.ToId and
LcsLog.dbo.Users.UserUri =
‘[email protected]'
This will show all IM messages sent and received by ‘[email protected]’
You may need to modify the query if you have modified the name of the
database.
Resources
www.microsoft.com/teched
www.microsoft.com/learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
http://microsoft.com/technet
http://microsoft.com/msdn
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
Microsoft Certification and Training Resources
Call to Action
Learn More!
Related Content at TechEd on “Related Content” Slide
Attend in-person or consume post-event at TechEd Online
Check out online learning/training resources
http://technet.microsoft.com/exchange/2010
http://technet.microsoft.com/office/ocs
Try It Out!
Download the Exchange Server 2010 Beta Evaluation
http://www.microsoft.com/exchange/2010/try-it
Get a 5-Day Trial of Office Communications Server 2007 R2
https://r2.uctrial.com/
Related Content
Breakout Sessions
UNC205 – "What's new in Microsoft Office Communications Server 2007 R2"
UNC309 – "Microsoft Office Communications Server 2007 R2 Dial-in audio conferencing
UNC311 – "Planning Voice Deployments for Microsoft Office Communications Server
2007 R2"
Interactive Theater Sessions
UNC304-TLC – "Q&A: Troubleshooting Edge Server Issues in Office Communications
Server 2007 R2"
Hands-on Labs
UNC05-HOL, - "Deploying and Configuring Office Communications Server 2007 R2 Enterprise
Edition"
UNC18-HOL – "Using the Managing and Troubleshooting Tools in Microsoft Office
Communications Server 2007 R2"
Complete an
evaluation on
CommNet and
enter to win!
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.