Unified Messaging Protocols
by Tom Pacyk, Andrew Abbate, Alex Lewis
Microsoft® Lync Server 2010 Unleashed
- Title Page
- Copyright Page
- Dedication
- Contents at a Glance
- Table of Contents
- About the Authors
- Acknowledgments
- We Want to Hear from You!
- Reader Services
- Introduction
- Part I. Overview
- Chapter 1. What Is Microsoft Lync Server?
- Chapter 2. What Is New in Microsoft Lync Server?
- Introducing New Management Tools
- Topology Changes
- New Enterprise Voice Features
- New Call Management Features
- Integrated Mediation Server
- New Presence Features
- New Conferencing Features
- DNS Load Balancing
- Survivable Branch Appliances
- Operating System Support
- New Lync Client Features
- Client Appearance
- The “Me” Area
- Enhanced Contacts
- Privacy Relationships
- Integration with Office and Windows 7
- Whiteboarding and Application Sharing
- Improved Meeting Join Experience
- Conferencing Attendant and Scheduling
- PSTN Dial-In Conferencing Improvements
- Video Improvements
- Manager/Admin Improvements
- Improved Phone Experience
- Summary
- Chapter 3. Feature Overview of Microsoft Lync Server
- Chapter 4. Benefits of Microsoft Lync Server 2010
- Part II. Microsoft Lync Server 2010 Server Roles
- Chapter 5. Microsoft Lync Server 2010 Front End
- Chapter 6. Microsoft Lync Server 2010 Edge
- Chapter 7. Microsoft Lync Server 2010 Monitoring
- Overview
- Installation
- Configuration
- Administration
- Troubleshooting
- Best Practices
- Summary
- Chapter 9. Director
- Part III. External Dependencies
- Chapter 10. Dependent Services
- Chapter 11. SQL
- Chapter 12. Firewall and Security Requirements
- Part IV. Administration and Management
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Overview
- OpsMgr Lync Server 2010 Monitoring
- What Is New in OpsMgr R2?
- How OpsMgr Works
- OpsMgr Architecture
- How to Use OpsMgr
- OpsMgr Component Requirements
- Advanced OpsMgr Concepts
- Understanding OpsMgr Deployment Scenarios
- Multiple Configuration Groups
- Deploying Geographic-Based Configuration Groups
- Deploying Political or Security-Based Configuration Groups
- Sizing the OpsMgr Database
- Defining Capacity Limits
- Defining System Redundancy
- Monitoring Nondomain Member Considerations
- Securing OpsMgr
- Installing Operations Manager 2007 R2
- Installing Edge Component Monitoring Certificates
- Installing the Lync Server 2010 Management Pack
- Best Practices
- Summary
- Chapter 14. Backup and Restore of Microsoft Lync Server 2010
- Chapter 15. Administration of Microsoft Lync Server 2010
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Part V. Migrating from Older Versions
- Part VI. Voice
- Chapter 17. PBX Integration
- Chapter 18. Enterprise Voice
- Chapter 19. Audio Conferencing
- Part VII. Integration with Other Applications
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Overview
- Exchange 2010 Unified Messaging
- Call Answering Rules
- Exchange 2010 Unified Messaging Architecture
- Unified Messaging Users
- UM Web Services
- Supported IP/VoIP Hardware
- Unified Messaging Protocols
- Unified Messaging Installation
- Postinstall Configuration
- Data Storage in Unified Messaging
- Exchange 2010 Outlook Web Application
- SharePoint 2010 Integration
- Best Practices
- Chapter 21. UCMA
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Part VIII. Clients
- Chapter 22. Microsoft Communicator Client for Macintosh
- Chapter 23. Windows, Browser, and Silverlight Clients
- Chapter 24. UC Endpoints
- Part IX. Planning for Deployment
- Chapter 25. Virtualization
- Chapter 26. Planning for Internal Non-Voice Deployment
- Chapter 27. Planning for Deploying External Services
- Chapter 28. Planning for Voice Deployment
- Index
Unified Messaging Protocols
The Exchange 2010 Unified Messaging servers use several telephony-related protocols to integrate and communicate with telephony devices. These protocols are listed and discussed in the following list:
• Session Initiation Protocol (SIP)—This is the signaling protocol that is used to set up and tear down VoIP calls. These calls include voice, video, instant messaging, and a variety of other services. The SIP protocol is specified in RFC 3261 produced by the Internet Engineering Task Force (IETF) SIP Working Group. SIP is only a signaling protocol and does not transmit data. After the call is set up, the actual communications take place using the RTP for voice and video or T.38 for faxes.
Note
Exchange 2010 only supports SIP over TCP. SIP, in general, can be configured to run over User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). UDP is connectionless and does not provide reliability guarantees over the network. TCP is connection-oriented and provides reliability guarantees for its packets. Exchange 2010 UM supports either SIP over TCP, SIP over TLS, or Dual where both are supported simultaneously.
• Real-Time Transport Protocol (RTP)—This protocol sends the voice and video data over the TCP/IP network. The protocol relies on other protocols, such as SIP or H.323, to perform call setup and teardown. It was developed by the IETF Audio-Video Transport Working Group and is specified in RFC 3550. There is not a defined port for the RTP protocol, but it is normally configured to use ports 16384–32767. The protocol uses a dynamic port range, so it is not ideally suited to traversing firewalls.
• Real-Time Facsimile Transport (T.38)—This protocol is an International Telecommunication Union (ITU) standard for transmitting faxes over TCP/IP. The protocol is described in RFC 3362. Although it can support call setup and teardown, it is normally used in conjunction with a signaling protocol such as SIP.
It is important to note that the Exchange 2010 Unified Messaging server is also a Windows server, a web server, and a member of the Active Directory domain. There are a myriad of protocols, including domain name system (DNS), Hypertext Transfer Protocol (HTTP), Lightweight Directory Access Protocol (LDAP), remote procedure calls (RPCs), and Simple Mail Transfer Protocol (SMTP), among others, that the server uses to communicate with other servers in addition to the telephony communications.
-
No Comment