SIP and Unified Messaging in a Mixed Environment

1
SIP and Unified Messaging in a Mixed Environment

• October 2006

2

• Trish Weiser Harris
• Business Development Manager
• TeleData Technology
• 32 Broadway, Suite 1214
• New York, NY

3

• TeleData Technology Inc.
• Technological leader in voice messaging, and
  connectivity applications since 1991
• Headquartered in New York City
• Research and Development
• United States
• Costa Rica
• Greece
• Telephony application known as T3

4
My Goal

• New way of thinking about how applications such
  as Unified Messaging can not only fit into your
  technology roadmap, but reach out and embrace
  your legacy voice investments

5
Agenda

• What is SIP, UM and a Mixed environment
• Real Life example of T3 in a Mixed environment
• T3 Evolution in a Mixed environment
• QA

6
SIP

• SIP and Unified Messaging in a Mixed Environment
• SIP is a protocol
• Unified Messaging is an application
• Mixed Environment

7
SIP

• SIP in Messaging applications
• Session Initiation Protocol (SIP)
• De facto VoIP standard
• Beyond infancy and toddler stage
• Cost benefits
• Elimination of voice boards
• Simplifies redundancy and resiliency
• Application advantages
• Can be embedded in SIP based PBX
• Ease of implementation of new applications such
  as Instant Messaging and Enhanced Presence

8
Unified Messaging

• SIP and Unified Messaging in a Mixed Environment
• SIP is a protocol
• Unified Messaging is an application
• Mixed Environment

9
Unified Messaging

• Unified Messaging
• More than voicemail messages in your email inbox
• Voicemail in email inbox
• Voicemail from a telephony device
• Email from desktop
• Email from telephony device
• Fax from email inbox
• Fax from telephony device
• Fax from desktop

10
New voicemail message
11
Internal voicemail message (listened to and saved)
12
Unified Messaging

• Benefits of Unified Messaging
• All message types in one location
• Ease of message retrieval
• Reduction in port usage
• Archive
• Forward

13
Mixed Environment

• SIP and Unified Messaging in a Mixed Environment
• SIP is a protocol
• Unified Messaging is an application
• What is a Mixed Environment ? ? ?

14

Mixed Environment

• Mix of Hardware and Applications
• PBX from multiple manufacturers
• Key Systems
• Centrex
• ACD
• Voicemail
• Fax
• Email

15
Mixed Environment

• Mix of Vertical Markets
• Service provider
• Business Units
• Small to Enterprise
• Call Centers
• Formal and informal
• Residential
• Emergency services

16
Mixed Environment

• Mix of protocols
• TDM
• TDM contemplating IP
• TDM migrating to IP
• TDM integrating IP
• IP
• IP integrating TDM

17

Mixed Environment

• Mixed signals
• Best technology
• No funding

18
Challenge
Stretch the life of your TDM
investments. Philip Beidelman, WTC

• How do you cost effectively integrate new
  technology, such as Unified Messaging into your
  domain without stranding or obsolescing legacy
  voice equipment?

19
Challenge

• Different PBX integrations and protocols
• In-band
• SMDI
• QSIG
• Digital Station Emulation
• Proprietary integrations
• SIP

20
Example of a Mixed Environment

• Example Major Western University
• Issued RFP for an IP enabled PBX platform
  incorporating the requirement for Unified
  Messaging
• 5 to 7 year project to replace legacy equipment
• 20,000 plus users at project completion
• Legacy equipment included various PBX, Key
  systems, lots of Centrex and several voicemail
  systems

21
Example of a Mixed Environment

• Selection criteria
• Technology that would simultaneously accommodate
  both TDM and IP
• Technology that would integrate with legacy
  systems, including Centrex
• A high degree of reliability and redundancy
• Flexibility to adapt to each departments specific
  needs
• No or little loss of investment as legacy systems
  are replaced with new technology
• Price

22
Example of a Mixed Environment

• Unified Messaging was a major consideration in
  vendor selection
• GroupWise user with plans to migrate to Exchange
• Secure IMAP clients
• Unix, Mac, etc.
• UM must be easy and economical to implement and
  maintain

23
Roadmap
Voice Network
Hub Switch
Hub Switch
Remote Switch
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Remote Switch
Hub Switch
Remote Switch
Remote Switch
IP phones
24
Roadmap
Voice Network
Hub Switch
Hub Switch
Remote Switch
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Remote Switch
X
Hub Switch
Should a hub switch fail, its remote switches
will automatically fail over to another hub
switch
Remote Switch
Remote Switch
25
Roadmap
Voice Network
Hub Switch
Hub Switch
Remote Switch
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Remote Switch
X
Hub Switch
Should a hub switch fail, its remote switches
will automatically fail over to another hub
switch
Remote Switch
Remote Switch
26
Roadmap

• Design allows for
• TDM between Hub switches
• Reliability
• Traffic management
• Look ahead routing for automatically rerouting
  calls should a network link fail
• TDM at the desktop
• Less administration
• Already owned inside cable plant
• IP connectivity of remote TDM switches to Hub
  switches
• Allows for fail over to secondary Hubs for
  resiliency
• IP stations at very small locations

27
Roadmap

• Design also allows for centralization of
  applications
• Auto Attendant
• Voice mail
• Unified Messaging
• Administration

28
Roadmap
Voice Network
Hub Switch
Hub Switch
Remote Switch
Voicemail Unified Messaging
TDM
T3 Voicemail/Unified Messaging can be installed
at one site providing service to all Hub
switches, Remote switches and IP phones with TDM
or SIP connectivity
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Remote Switch
Email Server
Hub Switch
Remote Switch
Remote Switch
IP phones
29
Roadmap
Voice Network
Hub Switch
Hub Switch
Remote Switch
Voicemail Unified Messaging
SIP
T3 Voice mail/Unified Messaging can be installed
at one site providing service to all Hub
switches, Remote switches and IP phones with TDM
or SIP connectivity
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Remote Switch
Email Server
Hub Switch
Remote Switch
Remote Switch
IP phones
30
Roadmap

• Critical applications should have the same
  resiliency and redundancy as the communications
  core

31
Roadmap
T3 Gateway
T3 Gateway
Hub Switch
Hub Switch
Remote Switch
Voice Network
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Net APP storage device
Remote Switch
T3 Gateways provide for the physical interface to
the PBX (TDM or SIP) along with local timers and
promts
Hub Switch
Remote Switch
Remote Switch
T3 Gateway
IP phones
32
Roadmap
T3 TDM Gateway
T3 TDM Gateway
Hub Switch
Hub Switch
Remote Switch
Voice Network
IP Data Network
Remote Switch
T3 database is stored in the Database Cluster.
This cluster is composed of a minimum of 3
servers which are normally dispersed for
redundancy
Remote Switch
Remote Switch
Net APP storage device
Remote Switch
Hub Switch
Remote Switch
Remote Switch
T3 TDM Gateway
IP phones
33
Roadmap
T3 TDM Gateway
T3 TDM Gateway
Hub Switch
Hub Switch
Remote Switch
Voice Network
IP Data Network
Remote Switch
Remote Switch
Remote Switch
Net APP storage device
Remote Switch
Actual voicemail files are stored in a fully
redundant storage device
Hub Switch
Remote Switch
Remote Switch
T3 TDM Gateway
IP phones
34
Maintaining Legacy Investments

• What about the Legacy PBXs and Key systems?
• How do you give Unified Messaging to Centrex
  users?

35
Roadmap
T3 Gateway
T3 Gateway
Hub Switch
Hub Switch
Remote Switch
Voice Network
T3 Gateway
IP Data Network
SMDI/PRI
Centrex
Remote Switch
Net APP storage device
T3 Gateway
Hub Switch
Remote Switch
Avaya Switch
T3 Gateway
IP phones
36

• Drivers for replacement of Octel with T3 for
  Avaya PBX
• Reduction of maintenance agreement costs
• Elimination of management of multiple systems
• Standardization for all users
• Clientless Unified Messaging
• Migration of PBX platform without change in Voice
  Mail and UM applications
• Octel prompts

37
Evolution of a Mixed Environment

• Single stand alone T3 can become a T3 Gateway
• Allows for slow controlled migration into Cluster
  Network
• TDM Gateways can be reconfigured for SIP
• Integrate legacy TDM PBX
• Maintain investment as legacy systems replaced
• TDM and SIP Gateways will operate on the same T3
  system
• Use protocol that makes sense for your campus
• Allows for a migration at the pace your funding
  and personal can accommodate

38
My goal

• New way of thinking about how applications such
  as Unified Messaging can not only fit into your
  technology roadmap, but reach out and embrace
  your legacy voice investments

39

• QA

www.myt3.com