SIP Proxies in DHCP

RFC3361 specifies DHCP option 120 to specify SIP proxies.

The syntax below is used in ISC dhcpd.

option sip-server code 120 = string;

option sip-server 00:08:6d:6f:74:69:76:69:74:79:02:63:61:00;

^^ ^^ ^^^^^^^^^^^^^^^^^^^^^^^ ^^ ^^^^^ ^^

|| || || || || || || || || || || || || ||

encoding ---------++ || || || || || || || || || || || || ||

0 = domain name || || || || || || || || || || || || ||

|| || || || || || || || || || || || ||

length of part ------++ || || || || || || || || || || || ||

"motivity" = 8 || || || || || || || || || || || ||

m o t i v i t y || || || ||

|| || || ||

length of part ---------------------------------++ || || ||

"ca" = 2 c a ||

null terminator -----------------------------------------++

Each domain name is seperated by a length indicator of zero.

To specify SIP servers at 192.168.1.1 and 192.168.1.2 use:

option sip-server code 120 = string;

option sip-server 01:c0:a8:01:01:c0:a8:01:02;

^^ ^^^^^^^^^^^ ^^^^^^^^^^^

|| || || || || || || || ||

encoding ---------++ || || || || || || || ||

1 = IP address || || || || || || || ||

|| || || || || || || ||

192.168.1.1 ---------++-++-++-++ || || || ||

|| || || ||

192.168.1.2 ---------------------++-++-++-++

RFC3361 specifies DHCP option 120 to specify SIP proxies.

The syntax below is used in ISC dhcpd.

option sip-server code 120 = string;

option sip-server 00:08:6d:6f:74:69:76:69:74:79:02:63:61:00;

00: encoding, 0 = domain name

08: length of part, "motivity" = 8

6d:6f:74:69:76:69:74:79: "motivity"

02: length of part, ca = 2

00: null terminator

Each domain name is seperated by a length indicator of zero.

To specify SIP servers at 192.168.1.1 and 192.168.1.2 use:

option sip-server code 120 = string;

option sip-server 01:c0:a8:01:01:c0:a8:01:02;

01: encoding, 1 = IP address

c0:a8:01:01: 192.168.1.1

c0:a8:01:02: 192.168.1.2

Type: How-To - Archive ID: 2.64 - 469 Views - Last Updated: December 05, 2010 18:34:07
Tags: IETF Software Design