Transcript Where We`re Going, Where We`ve Been

Interoperability Update:
Where We’re Going, Where We’ve Been
Jeanne Bayerl
Director of Product Marketing
Alcatel e-Business Networking Division
The Many Dimensions of Interoperability
• Enterprise voice communications systems must interact with:
–
–
–
–
–
–
–
–
End-user devices
Other voice systems
Public networks
Network infrastructure
Server hardware
Applications
Management systems
Directories
Communication
System
PSTN
• Open standards enable interactions between these components from
multiple vendors
Progress on Interoperability
Where We’ve Been
PSTN
PBX
PSTN
PBX
1995
PSTN
CTI
1950
“One” company,
one choice
1980
Q.SIG
More vendors =
more choices and
options, but little
interoperability
IP Network
2000
H.323
VLANs
Voice systems move into
“open” IP environment,
but remain relatively selfcontained
802.3 af
Progress on Interoperability
Where We Are Going
Com
Server
Application
server farm
Enterprise
IP network
- Voice services becoming intuitively
integrated into desktop tools and ebusiness applications
- Voice services becoming integrated in
web applications
Media
Gateway
PSTN
Carrier
IP Network
- Communications becoming user-centric
- Any device to any media over any network
- Various communications tools become unified
Linux XML
VxML
SIP
- Decoupling of hardware and software
- “PBX” becoming a software application
Interoperability with End-user Devices
• Where we’ve been:
– Very limited interoperability between phones and PBXs from
different vendors
• PBX vendors developed proprietary digital signaling protocols to
deliver enhanced features - analog was only level of interoperability
• With IP telephony, H.323 not feature-rich enough, so vendors put their
proprietary protocols on top
• Where we’re going: SIP
•
•
•
•
•
Concept of “presence”
Web technology: HTTP-like, URL-addressing, DNS, MIME
Media blending, multi-session (conferencing)
Carrier adoption driving “IP-POTS”
Voice services being integrated into PC desktop
SIP and H.323
• SIP and H.323:
– Are protocols that enable communications between two devices to
be set-up, modified and terminated
– Define mechanisms for call routing, call signaling, capabilities
exchange, media control, and supplementary services
• H.323 is a protocol that has been widely adopted for
integrating telephony onto IP networks
• SIP is a lightweight Internet-based protocol that offers ease
of implementation, especially in web environments, and is
being adopted by a growing number of carriers
Interoperability with Other Voice Systems
• Where we’ve been:
– Legacy TDM systems:
• E&M – basic connectivity
• Q.SIG – basic and supplementary services
Vendor
A
PSTN
Vendor
B
– Limited deployment by vendors, but remains
important for migration from legacy
– IP-based systems:
• H.323 – basic features
• Where we’re going:
– Stop-gap approaches:
• H.323 Supplementary Services (H.450)
• Q.SIG over H.323
– SIP – single, consistent approach for endpoints, networks and other systems
Vendor A
Vendor B
IP Network
Interoperability with Public Networks
• Where we’ve been:
– Well established standard interfaces to connect to the PSTN and
other enterprise locations:
• POTS, Digital / T1, ISDN
• Leased lines, VPNs
• ATM, frame relay
• Where we’re going:
– Carriers are deploying SIP-based network services, bundling
Internet and voice services over IP
– Extends “presence” to the WAN
Intranet
SIP
Carrier
WAN
IP-PBX
SIP
Intranet
IP-PBX
PSTN
Interoperability with Network Infrastructure
• Where we’ve been:
– Voice systems running on dedicated infrastructure
• Where we’re going:
– IP communication applications deployed just as any other
application on the corporate IP network
• Requires:
– Adherence to open standards:
• QoS: 802.1 p/Q, ToS / DiffServ
• Power: 802.3 af
– Independence of IPT and IP network
• Voice elements not intertwined with routers, switches
• Consistent management of IPT elements
Application &
e-business layer
Open
APIs
IP telephony
application
infrastructure
Open
Standards
Network
Infrastructure
Interoperability with Server Hardware
• Where we’ve been:
– Voice systems running on proprietary hardware
• Where we’re going:
– PBX becomes an IP communications application:
• Running on standard “communications grade”
operating systems, e.g., Linux
• Running on standard IP appliance servers
• Connecting directly to the LAN
• Communicating directly with endpoints and gateways
Interoperability with Applications
>
IP communication applications must be integrated with other
applications
>
Voice services in e-business applications
>
>
CRM, ERP, WFM, SFA, etc.
Unification of personal communication tools
>
Multiple devices
>
Messaging systems
>
Calendars, PIMs, portals, etc
Application &
e-business layer
Open
APIs
IP telephony
application
infrastructure
Open
Standards
Network
Infrastructure
Interoperability of Applications
• Standards enable the flexibility
– Simplified integration reduces capital expenditures
– User-centric communication makes people more productive and
lowers operating expenses
Contact
Center
Communication
Server
Unified
Communications
Voice
Portal
Application /
Portal
Servers
CRM
ERP
Mail &
Collaboration
Media gateways
LAN
WAN
PLM
Directory
Application
& e-business
Layer
Application
Infrastructure
Layer
Network
Infrastructure
Layer
Interoperability with Applications
Voice Services in e-Business Applications
• Where we’ve been:
– CTI in contact centers where ROI is obvious
• TAPI, TSAPI, CSTA, Cobra, etc.
• Successful in CRM, limited elsewhere
• Where we’re going:
– Enterprise-wide web-based integration of voice services into business
applications
• Unifying the e-business and communications silos
– Web programming model: a new reference
• XML: integration with web services
• VxML: Mobile access to all corporate resources through a voice enabled web
• SIP: New services using presence and media blending
– Enormous developer / integrator base
Interoperability with Applications
Unification of Personal Communication Tools
• Where we’ve been: total communication chaos
At HQ
Office
Branch
Office
Tele
Working
On The
Road
Customers
Multiple
Devices
$$$
Multiple
Networks
$$$
Multiple
mailboxes
directories
$$$
Agents
Colleagues
Fragmented
Experience
$$$
Partners
Interoperability with Applications
Unification of Personal Communication Tools
• Where we’re going:
– Intuitive integration of voice services into existing tools (e.g.,
Outlook, Notes), web applications and employee portals
– Access to corporate resources from any device, over any network
• Relevant standards:
– XML, SIP, VxML, IMAP4
Voice &
Business
Data
applications
Networks
Web Sites
Collaboration
E-mail Directories
Unified
Communications
Platform
IP, PSTN,
Cellular, GPRS,
UMTS, WLAN,
Bluetooth,
etc…
Interoperability with Management Systems
• Where we’ve been:
– Separate, self-contained management systems for voice
• Where we’re going:
– Incorporate various IP telephony system management tasks into enterprise
network management systems, e.g., troubleshooting, alarms, etc.
– While still maintaining consistent IPT system management
• Relevant standards:
– SNMP, CMIP
Interoperability with Directories
• Where we’ve been:
– Many different databases storing employee information
– Often duplicate information, e.g., phone number in multiple places
• Where we’re going:
– Directories synchronizing and sharing information, reducing
repetitious data entry tasks
• Relevant standards:
– LDAP
– XML / web services
Multi-Vendor Solution Example
OmniPCX Enterprise
xpressa™
SNMP
SIP
Unicenter
Q.SIG
DEFINITY ® PBX
LDAP
XML
VxML
802.3af
802.1p/Q
Catalyst switches
VxML
IMAP4
Thank you for your attention