Download Avaya External Template 31607

Understanding SIP’s Role
in
Intelligent Communications
Tom Doria
Director – Avaya P2P Technical Business Development
Chair – Avaya SIP Virtual Team
© 2007 Avaya Inc. All rights reserved.
1
Agenda
Intelligent Communications & SIP
– The Changing World & Evolving Business Needs
– Understanding Avaya’s Vision for Intelligent Communications
– The Building Blocks to Intelligent Communication
Defining SIP
– IETF’s Vision for SIP
– Key Concepts (SIP, SIPing, SIMPLE)
Why SIP
–
–
–
–
–
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
Why SIP Trunking
Building a SIP Enabled Enterprise
– SIP Communication Components Defined
– Mapping Industry Names to Avaya Solutions
– Peer-to-Peer (P2P) SIP
Vision Executed - SIP Service Examples
– Example #1 - Avaya Quick Edition with SIP Trunking
– Example #2 – Avaya Integration with Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
2
The World Is Changing
from
Separate services:
Local, long distance,
mobile, video, Internet
from
Separate platforms:
Phone for voice,
computer for Internet
from
Separate providers:
Cable companies for
video, phone
companies for voice
© 2007 Avaya Inc. All rights reserved.
to
Bundled services:
All distance voice,
voice/data/video packages
to
Multi-use devices:
Blackberries; mobile phones
with messaging, e-mail,
video; computer for Internet
phone and IM
to
Multi-product providers:
Cable, mobile, and wireline
companies offering
voice/video/data
3
State of Convergence Today!
End user view
We Need Converged
Communication
Applications that
Improve Productivity
and Allow Service
Integration
© 2007 Avaya Inc. All rights reserved.
4
Avaya’s Vision for a
New Era of Intelligent Communications
Intelligent Communication Solutions should:
Seamlessly and openly integrate communication
applications and business applications
Intelligently connects Employees, Customers and
Processes to the right people at the right time
through the right medium
Deliver business agility with speed, responsiveness
and control, increasing global competitiveness
© 2007 Avaya Inc. All rights reserved.
5
What does Intelligent Communications Look Like?
Contact Centers
Collaboration
Unified Communication
Conferencing
Telephony
Email
Mobility & Softphone
Voice Messaging
Instant Messaging
© 2007 Avaya Inc. All rights reserved.
6
Avaya Intelligent Communications
The Building Blocks to Next Generation Intelligent Communication Solutions
Session Initiation Protocol (SIP)
Next Generation Carrier Services
Service Oriented Architecture (SOA)
© 2007 Avaya Inc. All rights reserved.
7
Intelligent Communications
Redefining the way People, Processes, and Information Connect
Application Protocol Fabric
 Intelligent
Routing of Communication & Services
 Supports Open Integration of Devices and Application Services
 Native Support for Multimedia & Multimodal Communications
NEXT GEN Carrier Services
 Mobile and Fixed Services Integrated
 Supports Rich Presence
 SIP Enriched Multimedia Hosted Apps.
• IP & SIP Trunk
• IMS
• 3G & 4G Wireless
INTELLIGENCE Between Applications & User
 Middleware Connects Silos of Application & Communication Services
 Event Driven Services Initiate Communication with Users or Other Applications
© 2007 Avaya Inc. All rights reserved.
8
Agenda
Intelligent Communications & SIP
– The Changing World & Evolving Business Needs
– Understanding Avaya’s Vision for Intelligent Communications
– The Building Blocks to Intelligent Communication
Defining SIP
– IETF’s Vision for SIP
– Key Concepts (SIP, SIPing, SIMPLE)
Why SIP
–
–
–
–
–
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
Why SIP Trunking
Building a SIP Enabled Enterprise
– SIP Communication Components Defined
– Mapping Industry Names to Avaya Solutions
– Peer-to-Peer (P2P) SIP
Vision Executed - SIP Service Examples
– Example #1 - Avaya Quick Edition with SIP Trunking
– Example #2 – Avaya Integration with Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
9
Defining Key Concepts
SIP, SIPPING, SIMPLE
and other words that begin with
“S”
© 2007 Avaya Inc. All rights reserved.
10
What is SIP?
Shorthand Definition
Session Initiation Protocol
– SIP was designed to embrace the IETF concepts of KISS
– IETF standard for communications convergence (RFC 3261)
– Media agnostic – voice, video, text, etc.
– Enables applications to be integrated into communication
sessions
Communication sessions based on “presence”
– I.e. the publication of your willingness and ability to be
communicated with
– Note that Presence publication is selective by user
“preference”
IETF Site: http://www.ietf.org/html.charters/sip-charter.html
© 2007 Avaya Inc. All rights reserved.
11
What is SIPPING-16, SIPPING-19, etc?
Session Initiation Protocol Project INvestiGation
– IETF working group
• Chartered to document the use of SIP for several
applications related to telephony and multimedia
SIPPING-19 refers to SIP Services Examples draft
– draft-ietf-sipping-service-examples-07
– 19 example telephony features implemented in SIP
– Purpose is to ensure that basic features interoperate
Other SIPPING items
– SIP Basic Call Flow Examples (RFC 3665)
– Message Waiting Indication (RFC 3842)
IETF Site: http://www.ietf.org/html.charters/sipping-charter.html
© 2007 Avaya Inc. All rights reserved.
12
SIP Services Examples
a.k.a. SIPPING-19










Call Hold
Consultation Hold
Music on Hold
Transfer – Unattended
Transfer – Attended
Transfer – Instant Messaging
Call Forwarding –
Unconditional
Call Forwarding – Busy
Call Forwarding – No Answer
3-way Conference – 3rd Party
Added
© 2007 Avaya Inc. All rights reserved.










3-way Conference – 3rd Party Joins
Single Line Extension
Find-Me
Incoming Call Screening
Outgoing Call Screening
Call Park
Call Pickup
Automatic Redial
Click to Dial
Message Waiting Indication
13
What is SIMPLE?
SIP for Instant Messaging and Presence Leveraging Extensions
– IETF working group
Introduces “Presence” into communications state
– Builds on RFC 3265
– Now a standard: RFC 3856
Terminology
– Presentity - The entity whose presence information is tracked (also called “buddy”)
– Presence Agent – a program that servers presence subscription for a resource
(also called “Notifier”)
– Watcher - An endpoint (UA) that subscribes to presence changes (also called
“subscriber”)
IETF Site:
© 2007 Avaya Inc. All rights reserved.
http://www.ietf.org/html.charters/simple-charter.html
14
What is a SIP Trunk?
Shorthand Definition
A SIP Trunk is a single conduit pipeline for multimedia elements
(voice, video and data)
A SIP Trunk is primarily a concurrent call that is routed over the IP
backbone of a carrier using VoIP technology
SIP Trunks are commonly used in conjunction with an IP-PBX and are
thought of as replacements for traditional circuits such PRI, T1, or
analog circuits
© 2007 Avaya Inc. All rights reserved.
15
Agenda
Intelligent Communications & SIP
– The Changing World & Evolving Business Needs
– Understanding Avaya’s Vision for Intelligent Communications
– The Building Blocks to Intelligent Communication
Defining SIP
– IETF’s Vision for SIP
– Key Concepts (SIP, SIPing, SIMPLE)
Why SIP
–
–
–
–
–
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
Why SIP Trunking
Building a SIP Enabled Enterprise
– SIP Communication Components Defined
– Mapping Industry Names to Avaya Solutions
– Peer-to-Peer (P2P) SIP
Vision Executed - SIP Service Examples
– Example #1 - Avaya Quick Edition with SIP Trunking
– Example #2 – Avaya Integration with Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
16
Why SIP?
© 2007 Avaya Inc. All rights reserved.
17
SIP Is a Key Enabler of Intelligent Communications
The Right Person, in the Right Place, at the Right Time, the Right Way
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
© 2007 Avaya Inc. All rights reserved.
18
Multi-Vendor Interoperability
SIP Promotes Interoperability
– IETF SIP,SIPPING, and SIMPLE specifications provide the
foundation for interoperability
– Compliant Devices can easily operate in the same enterprise
– Options expand to a wide range of “best-of-breed” devices
– SIP/Telephony Feature servers extend capabilities
RIM Blackberry 7270
(example Avaya Communication Manager)
Example: RIM Blackberry 7270
– All-in-one mobile device combining SIP phone, intranet, email,
corporate data & application access
Nokia Dual-Mode
– Works over any 802.11b/g WLAN
Example: Nokia Dual-Mode Phones
– Support for cellular and 802.11 wireless VoIP
– Embedded SIP client
– Graphical user controls of desktop on cellular phone
© 2007 Avaya Inc. All rights reserved.
19
Presence and Preference
SIP Supports Intelligent Communication Choices
– Use Presence to determine availability
(Avoid mail jail )
– Use Presence to determine correct Modality
(Voice, IM, Video)
– Use Presence enabled applications to trigger event based
communications (SOA)
SIP lets Users Control their World
– Selectively advertise your Presence (buddy lists)
– Monitor key individuals availability
– Select your preferred mode of communication
© 2006 Avaya Inc. All rights reserved.
© 2007 Avaya Inc. All rights reserved.
20
Avaya – Proprietary & Confidential. For Limited Internal Distribution. The information
20
contained in this document may not be distributed or reproduced, in whole or in part.
IP Agent with SIP/SIMPLE IM Services
Intelligent Communications & Customer Service Scenario
1. Customer calls Customer Service
2. Rep needs technical answer from expert
3.
Rep uses presence to “peek over the
cubicle” to see if expert available
4. Expert available online but busy on phone
And has expert join conference with customer
IM
IM
IM
5. Rep IM’s the expert - begins to get answers
© 2007 Avaya Inc. All rights reserved.
6. Rep notices expert has ended conversation
IM
7. Expert answers questions and continues IM
chats with the Rep in the background
21
Native Support for Multimedia
SIP Natively Supports Multimedia Sessions
– Single network for voice & video
– Unified global dial plan for voice & video
Phone features extended to video
– Hold, mute, transfer, forward…
Voice and video meetings
– Presence-based soft phone
– Or MSFT client that is as easy to use as a phone
SIP Gateways support multi-point video integration
– ISDN, H.320, H.323, and SIP video conferences
SIP Promotes Interoperability between multimedia
Solutions from Different Vendors
© 2007 Avaya Inc. All rights reserved.
22
Single User Identity
Connect people with people, not with devices
Single user identity: SIP Address Of Record (AOR) is mapped across
multiple devices (e.g. sip:[email protected] or sip:[email protected])
SIP Presence and Preference controls can be used to automatically route
communications to the preferred device that is being “used”
Softphone
SIP Phone
PDA
Instant Messaging
SIP WiFi
Phone
Traditional phone
© 2007 Avaya Inc. All rights reserved.
23
Why SIP Trunking?
Limitation & Challenges of Private IP (H.323) Trunking
• Private IP (H.323) trunks are limited to VoIP communications between internal systems/sites
• Separate TDM interfaces are required for external communication (partners/suppliers/customers)
• Extra cost, extra hardware, extra complexity
PSTN
Local &
Long Distance
Customers/ Partners/ Suppliers
IP WAN
IP Data &Telephony
LAN
LAN
IP Phone
© 2007 Avaya Inc. All rights reserved.
Internal Communications
IP Phone
IP Phone
IP Phone
24
SIP Trunking
A Single Pipe to the Cloud
• Single IP link for voice/Multimedia/Data
• Optimize use of WAN access by consolidating voice and data services
• Eliminate PSTN interfaces for long-distance and local access (carrier provides the gateways)
• Assign local telephone numbers to any ‘virtual location,’ independent of physical location
• Save on toll charges
• Prepares for future SIP solutions
PSTN
Local &
Long Distance
Customers/ Partners/ Suppliers
Service
Provider’s
WAN
H.323
LAN
LAN
IP Phone
© 2007 Avaya Inc. All rights reserved.
IP Phone
IP Phone
IP Phone
25
Agenda
Intelligent Communications & SIP
– The Changing World & Evolving Business Needs
– Understanding Avaya’s Vision for Intelligent Communications
– The Building Blocks to Intelligent Communication
Defining SIP
– IETF’s Vision for SIP
– Key Concepts (SIP, SIPing, SIMPLE)
Why SIP
–
–
–
–
–
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
Why SIP Trunking
Building a SIP Enabled Enterprise
– SIP Communication Components Defined
– Mapping Industry Names to Avaya Solutions
– Peer-to-Peer (P2P) SIP
Vision Executed - SIP Service Examples
– Example #1 - Avaya Quick Edition with SIP Trunking
– Example #2 – Avaya Integration with Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
26
SIP Infrastructure Components
The building blocks of an Intelligent SIP Network:
• SIP User Agent - Any network endpoint that can originate or terminate a SIP
session; this might include a SIP-enabled telephone, a SIP PC client (known as a
"softphone"), or a SIP-enabled gateway
•Presence Server -
Accepts, stores, and distributes presence information. The
presence server has two distinct sets of clients:
- Presentities (producers of information) provide presence information to the server to
be stored and distributed
- Watchers (consumers of information) receive presence information from the server
•SIP proxy server - A call-control device that provides many services such as
routing of SIP messages between SIP user agents
• SIP redirect server - A call-control device that provides routing information to user
agents when requested, giving the user agent an alternate uniform resource identifier
(URI) or destination user-agent server (UAS)
• SIP registrar server - A device that stores the logical location of user agents within
that domain or subdomain; a SIP registrar server stores the location of user agents and
dynamically updates its data via REGISTER messages
© 2007 Avaya Inc. All rights reserved.
27
SIP Components (Continued)
• SIP location services - Additional functionality that can be used by proxy,
redirect, and registrar servers to find the identity (with a unique URI) and "logical"
location of user agents within the network (e.g. LDAP Directory Structures)
• Back-to-back user agent (B2BUA) - A call-control device that provides routing
similar to a proxy server, but allows centralized control of the network call flows; this
device allows SIP networks to replicate certain traditional telephony services that require
centralized knowledge of device state, such as call park and pickup; this component is
always dialog "stateful” (e.g. Avaya Communication Manager)
• Feature Server - A application server that extends additional capabilities to a SIP
UA in compliment to IETF defined services (e.g. Avaya Communication Manager)
• SIP-aware network devices - Devices that have knowledge of the SIP protocol
and allow the network to function more efficiently; this type of device might be a firewall
or Network Address Translation (NAT) device that can allow SIP traffic to traverse
network borders, or a load-balancing switch that allows requests to SIP servers to be
more efficiently handled
• ENUM services – Electronic Number Mapping, or ENUM, provides a method to
encode telephone numbers (formally known as E.164 numbers) into the Domain Name
System (DNS). ENUM is also used to map phone numbers to URI’s.
© 2007 Avaya Inc. All rights reserved.
28
How Avaya Products Map to Industry SIP Components
SES = Proxy, Presence, Registrar, and Location server
In addition provides SIP/SIMPLE IM Services & LDAP Directory Plug-Ins for extend
location/address translation services
CM = B2BUA (back-to-back User Agent) & Telephony Feature Server
Avaya 4600 SIP Phones = Wire Connected User Agents (UA)
BlackBerry/RIM 7270 = Wireless User Agent (UA)
Example of SIP Stack on Handheld Devices with 802.11 connection
Avaya IP Softphone & Avaya IP Agent = Hybrid soft client UA
Uses H.323/H.248 for call signaling and SIP/SIMPLE for IM Services
Avaya SIP Softphone = Pure SIP Soft Client UA
Uses SIP for call signaling, SIP/SIMPLE for IM, can operate in Peer-to-Peer mode
Quick Edition = Peer-to-Peer (P2P) SIP serverless UAC/UAS with
On-board feature/application services and SIP Trunking
SBC’s & Firewalls = SIP Aware Network Devices
Provides –SIP/NAT, SIP QoS, Security, and ENUM Services (not avail. in all devices)
Session
Border
© 2007 Avaya
Inc. Controllers
All rights reserved.
29
Overview - Avaya’s Current SIP Proxy Based Architecture
User Control
User Access
Third-Party
9600
Series
4600
Series
Mobile
Devices
SES 4.0
SIP
Trunking
Service Provider
SIP Network
SIP
Softphone
IP
Agent
SIP/SIMPLE
H.323
SIP
SIP Personal
Information Mgr
Personal Profile
Manager
SIP
Services
Handle-Based
Dialing
Session Border
Controller
IP
Softphone
Web Browser
SIP/SIMPLE
H.323
HTTPS
LDAP
SIP
SIP-Enabled
Applications
SIP
SIP
Expanded Meet Me
Conferencing
Meeting Exchange
Enterprise
© 2007 Avaya Inc. All rights reserved.
Third-Party SIP
Application
Communication
Manager
30
Peer-to-Peer (P2P) SIP
© 2007 Avaya Inc. All rights reserved.
31
Peer-to-Peer (P2P) SIP: The Future of
“Collective” Communications Intelligence?
“Resistance is Futile …
Prepare to be Assimilated”
(Star Trek Next Generation “Borg” Collective Intelligence)
© 2007 Avaya Inc. All rights reserved.
32
What is Peer-to-Peer (P2P) SIP Telephony?
Peer-to-Peer (P2P) technology overview:
Dramatically different approach to communications
from traditional client/server-based architectures
A “collective” (group) of intelligent nodes (peers),
collaborate with one another to provide the services
traditionally provided by a central server (or group of servers)
Hive Mentality - Processing of services is dynamically
allocated across all the intelligent nodes (Peers)
Information about Peering Group automatically distributed as
new nodes are “assimilated” (added) or dropped from the
collective
Dependency on central servers is greatly reduced
Typical platforms:
– “Smart IP hard phones” (e.g., Avaya Quick Edition)
– P2P soft clients (e.g., Skype)
SIP P2P
Work group
B2BUA
PSTN
© 2007 Avaya Inc. All rights reserved.
33
Example: Traditional SIP/IP PBX Architecture
Attributes
Examples:
Centralized SIP Proxy /
Registrar / Location Services
Central SIP Proxy
&
Applications Services
Centralized Call / Application
Services
“Unintelligent” SIP endpoints
(UACs) register with central
SIP Proxy and derive
application services
IP/SIP Trunk
from servers
“Unintelligent”
SIP Endpoints
© 2007 Avaya Inc. All rights reserved.
CM & SES
Border Controller
IP or SIP Trunks
WAN or LAN
Network Connects
IP/SIP Trunk
“Unintelligent”
SIP Endpoints
IP/SIP Trunk
IP/SIP Trunk
“Unintelligent”
SIP Endpoints
“Unintelligent”
SIP Endpoints
34
P2P SIP Distributed IP Telephony Architecture
(example)
© 2007 Avaya Inc. All rights reserved.
35
P2P SIP Distributed IP Telephony Architecture
(example)
Attributes
Intelligent SIP endpoints (peer nodes)
Call services & applications distributed
between peer nodes
Central SIP Proxy/Registrar replaced with
distributed Proxy/Registrar services
P2P SIP is used to discover peer nodes
within SIP domain and configure services
SIP trunks connect sites
SIP identities for all peer nodes are distributed to all peers
within the SIP domain
“Super Nodes” may be used to support application load for
“lesser” peers/nodes
Peer nodes join via ad hoc connectivity (no predefined
client/server connections)
© 2007 Avaya Inc. All rights reserved.
36
Why Peer-to-Peer (P2P) SIP Telephony?
Advantages:
B2BUA
Distributed architecture minimizes traditional
client/server central points of failure
SIP P2P
Work group
PSTN
Auto-discovery/auto-configuration capabilities simplify
deployment & moves-adds-changes (MACs)
Serverless architecture reduces maintenance and operation costs
Considerations:
Hard-phone processor and memory limitations can limit both
application capabilities and the size of the peering group
Bandwidth and processing resources to support traffic to/from
“Super Nodes” must be carefully planned for
Proper certificate-based security measures needed to prevent
“rogue peers” from illegitimately joining peering groups
© 2007 Avaya Inc. All rights reserved.
37
Combining Traditional SIP/IP PBX Architecture
with P2P-SIP
Hybrid Solutions
– Hybrid solutions combine P2P to address small/medium-size
sites networked with enterprise or hosted SIP
Proxy/Registrars and application services
Advantages
– Leverages Central Application Services where needed
– Improves Scalability
– Distributes Risk - Improves Survivability
– Supports Trunk Aggregation Strategies
SIP P2P
Work group
B2BUA
PSTN
© 2007 Avaya Inc. All rights reserved.
38
P2P SIP Hybrid Hosted Services Architecture
(example)
Hosted or Central Site
PSTN
Local & Long Distance
Access
SIP Trunk(s)
SIP Proxy/Registrar
&
Application Servers
or
Other SIP
Domains
Border Controller
IP or SIP Trunks
IP/SIP Trunk
IP/SIP Trunk
IP/SIP Trunk
“Intelligent Edge”
P2P
Branch
Locations
B2BUA
SIP P2P
Work group
PSTN
© 2007 Avaya Inc. All rights reserved.
B2BUA
IP/SIP Trunk
SIP P2P
Work group
PSTN
B2BUA
SIP P2P
Work group
PSTN
B2BUA
SIP P2P
Work group
PSTN
39
Agenda
Intelligent Communications & SIP
– The Changing World & Evolving Business Needs
– Understanding Avaya’s Vision for Intelligent Communications
– The Building Blocks to Intelligent Communication
Defining SIP
– IETF’s Vision for SIP
– Key Concepts (SIP, SIPing, SIMPLE)
Why SIP
–
–
–
–
–
Multi-Vendor Interoperability
Presence and Preference
Native Support for Multimedia
Single User Identity
Why SIP Trunking
Building a SIP Enabled Enterprise
– SIP Communication Components Defined
– Mapping Industry Names to Avaya Solutions
– Peer-to-Peer (P2P) SIP
Vision Executed - SIP Service Examples
– Example #1 - Avaya Quick Edition with SIP Trunking
– Example #2 – Avaya Integration with Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
40
Vision Executed
SIP Service Examples
(Live Demonstrations)
© 2007 Avaya Inc. All rights reserved.
41
Example #1 - Avaya Quick Edition with SIP Trunking
Avaya Hub Environment
Coppell, TX
Communication
Manager
Service
Provider
SIP Network
B2BUA
Acme Packet
Session Border Controller
SIP,IP, Wireless, Digital & Analog
Endpoints
B2BUA
SIP Trunks
T.38
FAX
SES
SIP Trunk
SIP Routing
between
Sites
Juniper
J2300-2
Series Router
PSTN
Local & Long Distance
Cell Network Access
Gateway
PSTN
Local & Long Distance
Cell Network Access
ISP
Internet (VPN)
IP/VPN
SIP Trunk
B2BUA
IP/VPN
SIP Trunk
B2BUA
IP/VPN
SIP Trunk
B2BUA
IP/VPN
SIP Trunk
Juniper Netscreen – 5GT
SSG appliance
B2BUA
Laptop with QE Multisite
Provisioning Tool &
Avaya SIP Softphone
Branch Locations
PSTN
© 2007 Avaya Inc. All rights reserved.
PSTN
PSTN
PSTN
42
Quick Edition
Laptop PC Demo Platform
SIP Trunk Branch Environment
• one-X Desktop Edition (SIP Softphone client) serves
as a CM extension on Demo Avaya CM Switch
• Multisite Provisioning Tool with local & DemoAvaya QE Branch registration
• QE Web Admin for Site Administration
Avaya Quick Edition
on 4610SW and/or 4621SW IP telephones
• SIP Trunk Created to DemoAvaya.com (10.147.12.7)
• SIP Identity register at DemoAvaya.com (2475)
• “Customer Service” Workgroup linked to SIP Identity (ext. 204)
• “Global” outbound dialing over SIP trunk enabled
PSTN
G10 or G11
Ext. 200
Ext. 201
Ext. 202
Four port PSTN Gateway
(Analog Loop Start Lines)
LAN
IP/SIP Trunk
VPN WAN Connection
to DemoAvaya
Cat5 or better cabling
“Trusted” Network
Connection
Powered Ports
Non-powered Ports
NetGear FS108P PoE Switch
• LAN Backbone for Demo Environment
• (4) IEEE 802.3af Power over Ethernet Ports
• (4) Non-Powered 10/100 Ethernet Ports
© 2007 Avaya Inc. All rights reserved.
“Untrusted” Network
Connection
Juniper NetScreen 5GT
ROUTER, Cable Modem,
ADSL Modem, or
Integrated Access Device (IAD)
IPSec VPN and Firewall
• Provides DHCP Service to Trusted Network Devices (10.10.200.x range)
• Creates Secure VPN tunnel to DemoAvaya.com Site
• Takes IP Address on Untrusted Port from DHCP service on Network Router
43
Quick Edition
Laptop PC Demo Platform
SIP Trunk Branch Environment
• one-X Desktop Edition (SIP Softphone client) serves
as a CM extension on Demo Avaya CM Switch
• Multisite Provisioning Tool with local & DemoAvaya QE Branch registration
• QE Web Admin for Site Administration
(Mobile Broadband Router Option)
Avaya Quick Edition
on 4610SW and/or 4621SW IP telephones
• SIP Trunk Created to DemoAvaya.com (10.147.12.7)
• SIP Identity register at DemoAvaya.com (2475)
• “Customer Service” Workgroup linked to SIP Identity (ext. 204)
• “Global” outbound dialing over SIP trunk enabled
PSTN
IP/SIP Trunk
VPN WAN Connection
to DemoAvaya
Ext. 200
Ext. 201
EVDO
G10 or G11
Four port PSTN Gateway
Ext. 202
(Analog Loop Start Lines)
LAN
Verizon Wireless
Broadband
Service
Cat5 or better cabling
“Trusted” Network
Connection
Powered Ports
Non-powered Ports
NetGear FS108P PoE Switch
• LAN Backbone for Demo Environment
• (4) IEEE 802.3af Power over Ethernet Ports
• (4) Non-Powered 10/100 Ethernet Ports
© 2007 Avaya Inc. All rights reserved.
“Untrusted” Network
Connection
Juniper NetScreen 5GT
IPSec VPN and Firewall
• Provides DHCP Service to Trusted Network Devices (10.10.210.x range)
• Creates Secure VPN tunnel to DemoAvaya.com Site
• Takes IP Address on Untrusted Port from DHCP service on Router
Top Global MB6800
Mobile Broadband Router
• Provides EVDO Broadband Service
• Provides IPSEC/VPN pass-through
• Provides DHCP to Untrusted Port
44
With SIP trunks in place and SIP Identities defined,
calls can be placed from CM to Quick Edition Auto
Attendant, Station Groups, or individual QE extensions
using abbreviated dialing schemes EXAMPLE:
Call Path Examples
PSTN
Demo Avaya
Communication Manager
CM Extension 2311 calls the “Customer Service” QE
Cell Phone
station group (extensions 200, 201, and 202) using the
(972)457-2011
SIP Identity linked with that group to make the call by
in Coppell, Texas Dialing “2475”
Coppell, Texas
CM ext. 2311
IP Trunk
SIP Trunk connections to SES from Quick Edition
branch sites can be used to create communication
session between Quick Edition Branch locations using
the registered SIP Identities to make calls - EXAMPLE:
SIP Enablement Services (SES)
SIP Proxy/Registrar
demoavaya.com SIP Domain
Quick Edition Branch in California calls Demo Avaya
Quick Edition branch’s Auto Attendant (ext. 500) linked to
SIP Identity 2474 by Dialing “82474”
2475
2474
SIP Trunks
Registered SIP
Identities
Demo Kit Site
QE Branch, CA
Demo Avaya
QE Branch, Texas
200
201
SIP Trunk connections to SES from Quick Edition branch
sites can also be used to create communication session
between Quick Edition Branch extensions and CM extensions EXAMPLE:
Quick Edition ext. 201 in California calls Demo Avaya
Communication Manager extension 2311 over the SIP Trunk
by Dialing “82311”
QE Auto Attendant
Local Ext. 500
Linked to SIP Identity = 2474
© 2007 Avaya Inc. All rights reserved.
PSTN
CM Ext. 1022
On Demo Avaya
CM Switch
Quick Edition branch sites can also use PSTN trunks
connected to Communication Manager to make calls to PSTN
stations using the SIP Trunk for long distance toll-bypass Group “Customer Service”
EXAMPLE:
Local Ext. 475 (stations 200,201,202)
Quick Edition ext. 201 in California calls Cell Phone in
Linked to SIP Identity = 2475
Texas over the SIP Trunk by Dialing “894572011”
202
500 AA
45
Example #2 – Avaya Integration with
Microsoft Office Communicator
© 2007 Avaya Inc. All rights reserved.
46
Voice Telephony Integration
Communication Manager
Decades of experience delivering
enterprise class telephony
LCS 2005 and OCS 2007
Simple peer-to-peer conversations
Not enterprise voice
No coverage for voice mail
No PBX rules (class of service)
LCS (OCS) /MOC integration with Avaya CM –
Click to call / call control of Avaya end points from MOC and
SmartTags in Office apps
Network SIP/CSTA gateway
Additional Avaya functions on MOC tabs some months later
LCS (OCS) /MOC integration with Avaya CM –
Application
Enablement
Services 4.0
nothing
required on PC
Click to call / call control of Avaya end points from MOC and
SmartTags in Office apps.
IP
Softphone
6.0
Adds Avaya functions to MOC tabs.
on local PC
MOC as SIP Softphone
SES
Feb
2007
Feb
2007
2007
Avaya provides Enterprise Gateway for MOC
© 2007 Avaya Inc. All rights reserved.
47
Avaya Brings Enterprise Telephony to Communicator
Communicator will be on PC
– Corporate IM is driving
Avaya Provides Telephony
Connection
Click to Call in MOC, SmartTags
Escalate IM to call, Conference
Phone & MOC stay in synch
– Presence is shared
Call Control - Hold,Transfer,etc.
– 17 functions (CSTA)
Additional Avaya Functions
provided as extensions to Office
Communicator on tabbed UI
© 2006 Avaya Inc. All rights reserved.
© 2007 Avaya Inc. All rights reserved.
48
Avaya – Proprietary & Confidential. For Limited Internal Distribution. The information
48
contained in this document may not be distributed or reproduced, in whole or in part.
Application Enablement Services
Microsoft Reference Model
Implements SIP/CSTA
(TR/87) gateway on AE
Services 4.0 Server
Microsoft LCS 2005 - or
Microsoft OCS 2007
Desktop Call Control
AE Services 4.0
– MOC can control phone
– Use phone and MOC is
updated
Avaya CTI
Avaya CM
Server Solution = no local
software required. Can use
MOC alone
Optionally, can add IP
Softphone on PC
– Shared Control
– Telecommuter
H.323
© 2007 Avaya Inc. All rights reserved.
TDM /
Analog
Cell
Phones
(EC500)
– RoadWarrior
49
IP Softphone - LCS integration
Client side solution
Part of upcoming release of
IP Softphone 6.0
Microsoft LCS 2005 - or
Microsoft OCS 2007
– SIP/CSTA gateway on
local Windows client
– Softphone UI hidden if
using MOC
– Requires small server
applet (can be on LCS
server)
Desktop Call Control
Avaya CM
– MOC can control phone
– Use phone and MOC is
updated
H.323
© 2007 Avaya Inc. All rights reserved.
TDM /
Analog
Cell
Phones
(EC500)
Added Avaya features on
MOC tabs – beyond TR/87
– EC500, History, Video
50
Greater than the sum of the parts
Enterprise Telephony
– Mature, five 9’s reliable
Video & Conferencing
– Richer, more mature
Mobility
– Follow Me / EC500
Enterprise IM
– Active Directory
Identities
– Multi-party IMs
– Archived, searchable
Microsoft desktop
–User interface
– SmartTags
Telephony & desktop presence synch
Emails for missed calls
MOC interface controlling your home / mobile phone
© 2007 Avaya Inc. All rights reserved.
51
Q&A
© 2007 Avaya Inc. All rights reserved.
52
© 2007 Avaya Inc. All rights reserved.
Avaya – Proprietary & Confidential. Under NDA
53
Backup Slides
© 2007 Avaya Inc. All rights reserved.
54
Why SIP – Top 10 Reasons:
Presence Based Communications:
– SIP adds intelligence to communications by allowing users, as well as applications, to intelligently connect
parties based on their Presence (registered availability) in the enterprise. This concept is best exemplified
through SIP's ability to support "intelligent forking which is the ability to route communications to the right
persons, in the right medium (voice, video, IM), on the right device, and at the right time.
Preference Based Communications:
– Like SIP Presence, SIP adds intelligence to communications through allowing users to control the parameters
by which they can be communicated with (e.g. time-of-day, preferred medium, preferred users, etc). This
concept is best exemplified through SIP's ability to support "buddy list" based communications.
SIP is an open standard:
– The SIP standard is defined in RFC 3261 by the Internet Engineering Task Force (IETF). The IETF is a large
open international community of network designers, operators, vendors, and researchers concerned with the
evolution of the Internet architecture and the smooth operation of the Internet.
Interoperability:
– Several working groups, including SIPIT, SIP Foundry, and SIP Connect, arrange events where companies with
SIP-based hardware and software products can best interoperability with other SIP-based products. This
helps to promote smoother integration of SIP-based products in enterprise networks.
Uniform Addressing:
– SIP URI (Uniform Resource Identifier) addressing provides a unifying identifier that can be used for routing all
communication to a user. This eliminates the need for tracking users’ multiple phone numbers, email
addresses, and IM contact names. Simply put, SIP URI allows for a single user identity to be mapped across
multiple devices which facilitates the ability for people to connect with people, without needing to know which
devices they have and are presently using.
© 2007 Avaya Inc. All rights reserved.
55
Why SIP – Top 10 Reasons (continued):
Operation Cost Savings / SIP Trunking
– SIP provides a low cost trunking alternative to standard PSTN transport. SIP trunks can be used to facilitate
communication models that leverage the possibilities expressed in the previous points. SIP trunks support
the concepts of converged communications thus allowing for true mutli-media communication streams to exist
on a common carrier circuit. Finally, SIP trunks reduce operational costs by allowing the user to eliminate
hardware, software, and recurrent network charges associated with using traditional PSTN trunks for voice
communications.
Simplified Communication Architecture:
– At the foundation of SIP's philosophy is the concept that intelligence in the communication enterprise should
reside in the endpoint. This concept is manifested in SIP's ability to support peer-to-peer communication
architectures. Peer-to-Peer communications environments do not rely on communications servers, switches,
or other intermediate devices to support communications between users. Because peer-to-peer is, in
essence, "switchless" by its nature, simple easy-to-configure communication environments can be created
which use only intelligence endpoints as the mechanism for establishing a communications enterprise. This
architecture is best exemplified by the technology represented by Avaya's NIMCAT based solutions .
Creation of New Services:
– SIP is a structured, text-based protocol that is modeled after HTTP, or HyperText Transport Protocol, the
language that powers the World Wide Web. Because SIP is text-based and similar to HTTP, application
developers and system engineers will have an easier time developing applications and integrating applications
into complex communications environments.
Ease of Support and Implementation:
– Since SIP is text-based and modeled after HTTP and XML it is much easier to learn and troubleshoot/support.
From analyzing network packets to application code, SIP’s structured language will stand out and be easily
understood and interpreted.
Native Mobility:
– SIP’s awareness of a user’s communication capabilities will aid international travelers who must use different
(or multi-modal) cell phones and other messaging devices and protocols in different countries. A caller who is
trying to locate such a traveler need not know the traveler’s availability or location: SIP by nature will know
how a person can be reached, and facilitate the connection without the calling party’s need to know where the
traveler is or how he (or she) can be contacted.
© 2007 Avaya Inc. All rights reserved.
56
What is SIP? (Longhand explanation)
http://www.ietf.org/html.charters/sip-charter.html
“SIP is an IETF application layer-protocol that can establish, modify, and terminate
multimedia sessions” (summary definition - RFC 3261)
Media agnostic
– Voice, video, instant messaging, etc.
Media negotiation
– Offer-Answer model (Invite & Acknowledge)
Similar to HTTP
– Request-Response model
– Text message-based protocol
• Easy to debug
Reuses other IETF protocols
– UDP, TCP, TLS, DHCP, DNS, SDP, RTP, MIME, etc.
Communication sessions based on “presence”
– I.e. the publication of your willingness and ability to be communicated with
– Note that Presence publication is selective by user “preference”
SIP is a very simple protocol with very few client/server style messages
© 2007 Avaya Inc. All rights reserved.
57
What is SOAP?
SOAP (Simple Object Access Protocol) is a way for a program running in one kind
of operating system (such as Windows 2000) to communicate with a program in
the same or another kind of an operating system (such as Linux) by using the
World Wide Web's Hypertext Transfer Protocol (HTTP) and its Extensible Markup
Language (XML) as the mechanisms for information exchange.
SIP Personal Information Manager
allows the user to access and modify
their profiles, access control lists,
contact lists and device parameters
through a secure web browser
When the user logs into the phone,
the latest parameters are loaded in
automatically
HTTPS
SOAP/HTTPS
SES 3.0
PPM receives/stores/distributes:
SIP Personal
Information Mgr
Personal Profile
Manager (PPM)
SIP
Services
© 2007 Avaya Inc. All rights reserved.
•
•
•
Contact and group list management
Access Control Lists for user
presence
Device Parameters (i.e. dial plan,
speed dial list, feature button
mappings, etc)
58