SIP Plug & Play
Dr. Christian Stredicke, snom technology AG
Cebit 2002
Hannover, March 13th, 2002
2
Contents
V1.0
Plug and Play Benefits
3
Requirements
4
Proposed Standards and Solutions
5
Conclusion
6
3
The Session Initiation Protocol (SIP) will play a major
role in future telephony
• Wide acceptance in industry
– Microsoft Messenger
– Cisco gateways and phones
– All major players are offering SIP equipment or are planning to do
so
• Solves all important problems
– Code size in embedded devices
– SIP aware firewalls
– NAT (however requires special software or hardware)
– Feature list
V1.0
4
Today, installation and maintenance of a VoIP telephone
can only be done by experts
• Every vendor has different setup procedure
• Details, details, details
– Multiple lines, outbound proxy
– LDAP server connectivity
– Daylight saving, different time server
• VoIP operators offer only devices they are able to manage
– Customers choose operator and equipment at the same time
– Limited competition
• Network administrators stay with one manufacturer
– Lock in effect as with POTS PBX
– Economically, nothing new
V1.0
5
Simple installation and maintenance is key for VoIP
going to the mass market
• Most customers don’t know how to install VoIP
– Even simple network equipment is often a problem
– Many customers don’t want to know
• Customers who know spend too much time for setting up a
phone
– Multiply hourly rates for manual provisioning by time spent
– Operators and manufacturers spend too much time on support
V1.0
6
Contents
V1.0
Plug and Play Benefits
3
Requirements
4
Proposed Standards and Solutions
5
Conclusion
6
7
Requirements on SIP devices must be objective,
complete and measurable
• Counting the number of features is not enough
• Decision makers need a guideline to this new topic
– draft-sinnreich-sipping-device-requirements-00.txt
• Contains “checklist” on all relevant topics
– Configuration Process
– Emergency Calling
– Codec and media capabilities
– User interface requirements
– Security profile
– Physical layer requirements
– Supported protocols other than SIP
– etc.
V1.0
8
Configuration Requirement 1: Interoperability
Operators
• Operator can
offer any device
• Customer can
choose operator
Network
elements
Phones
Interoperability is the ketchup between the
business areas of the VoIP industry
V1.0
9
Req. 2: Retrieve all necessary data for making and
receiving a call without user interaction
• “Plug and play”
• User may interact
– But only if explicitly requested
– Operator may make some settings read only
• User may choose several operators
– Line identity can be selected
– Call by call gets a new meaning
• Data storage in the network
– Address book, last calls, preferences
– Different paradigm than SIM card in GSM networks
– Customer is not bound to operator because location may be
independently
– Roaming between different outlets
V1.0
10
Req. 3: Remote management of a large number of
phones
• Don’t walk to a phone
– “Operator” may be network administrator, telecom, [internet
[telephony]] service provider, manufacturer
– Push-technology: Don’t wait until a phone reboots, no polling
• Administration tool for managing thousands of phones
– Generic settings
– Specific settings
– Firmware realms
V1.0
11
Contents
V1.0
Plug and Play Benefits
3
Requirements
4
Proposed Standards and Solutions
5
Conclusion
6
12
snom’s current solution reads the configuration from a
predefined location and redirects according to MAC addr
0. Sales department notes which
device has been sold to which
operator and sets up web server
accordingly
www.snom.de
1. Device looks at
predefined web
page for redirect
setting and other
settings
V1.0
www.operator.com
2. Get the latest
firmware, if
necessary
3.+4. Get the
generic and
specific settings
13
The framework for exchanging SIP configuration
messages is based on subscription/notification
Configuration Server
Configuration Resource
2. Device
receives URL for
configuration
information
1. Device
subscribes to
configuration
notifications
3. Device reads
configuration
http://conf.abc.com
www.softarmor.com/sipwg/drafts/draft-petrie-sip-config-framework-00.txt
V1.0
14
The message format itself is open to vendor specific
extensions
• Message format:
– Definitions on how to exchange line identities, proxies addresses,
address books, call lists, ringer behavior, redirections, ...
– XML with reduced featureset (easy to parse)
– http://www.pingtel.com/docs/draft-stredicke-sipping-ep-config00.txt
• Example:
<lineDefaults>
<outboundProxy>10.1.1.1</outboundProxy>
<callHandling>
<busy behavior=”busy”/>
<callWaiting behavior=”busy”/>
</callHandling>
</lineDefaults>
V1.0
15
Contents
V1.0
Plug and Play Benefits
3
Requirements
4
Proposed Standards and Solutions
5
Conclusion
6
16
Conclusion
• SIP plug and play is an economical must
• Support non SIP-aware users as well as savvy users
• Customers may easily choose their operators
• Plug and play is available today
• Interoperable standard is on the way
V1.0
sip:[email protected]
© 2002 snom technology Aktiengesellschaft
Written by:
Dr. Christian Stredicke
sip:[email protected], mailto:[email protected]
Version: 1.1
The author has made his best effort to prepare this document. The content is
based upon latest information whenever possible. The author makes no
representation or warranties of any kind with regard to the completeness or
accuracy of the contents herein and accept no liability of any kind including but
not limited to performance, merchantability, fitness for any particular purpose,
or any losses or damages of any kind caused or alleged to be caused directly or
indirectly from this document.
For more information, mail [email protected], Pascalstr. 10E, 10587 Berlin,
Germany.