A Use Case for SIP Client Configuration and Management

A Use Case for SIP Client Configuration and Management

Sumanth Channabasappa (sumanth@cablelabs.com)

Jean-François Mulé (jfm@cablelabs.com)

IETF 65, SIPPING WG(March 22, 2006)

Introduction

• UA Configuration and Management are different– SIPPING-CONFIG and XCAP address SIP UA

configuration– SIP UA Management is typically done via CLI, HTTP,

SNMP, etc.

• Focus of this presentation:– How do we perform management of SIP UAs behind

NATs and Firewalls?– Use Case #3 in

draft-channabasappa-sipua-config-mgmt-00.txt

Typical Configuration & Management Scenario

Management Station

MANAGEMENT

Client or SIP UA

ManagementData Store

NetworkElements

Configuration Changes

Client Configuration

Configuration of Management

Data

ConfigurationData Store

Configuration Server(TFTP, FTP, HTTP)

Configuration file

DHCP

Evolution of Configuration & Management for SIP UAs

CONFIGURATION SERVER(SIPPING-CONFIG, XCAP)

Management Station

MANAGEMENT

SIP UA

ManagementData

Configuration Data

NetworkElements

Configuration Changes

Configuration of SIP UA

Management Data

SIP UA Configuration

NAT & Firewall

c

Requirements

• Define SIP-based mechanisms to enable establishment of management sessions with SIP UAs– Specify methods to initiate management sessions– Specify semantics to indicate session parameters,

e.g.• Management protocol type (e.g. HTTP; CLI or SNMP over

suitable transport like ssh)• Other parameters (initiation time, duration, periodicity)

• Ensure mechanisms operate in the presence of NATs & Firewalls

• Thoughts?