Requirements and Framework for SIP User Agent Auto-Configuration
draft-brunner-sipping-sipautoconf-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marcus Brunner | ||
| Last updated | 2005-10-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The problem of today's VoIP user agents (hardware terminals, SIP soft phones) is the need for quite a bit of manual configuration at the initialization time as well as when moving from one environment to another. The information to be configured is typically not known by the end-user. Automatic configuration of SIP user agents would release the user of these configuration tasks. This memo describes the challenges of auto-configuration of SIP user agents and gives some requirements for further discussions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)