Tuesday, September 07, 2010

Mengatasi SIP Phone yang berbasis DHCP

Kebetulan sistem IP PBX yang diimplementasikan berbasis IP Static. Sementara SIP Phone sudah terlanjur dikonfigurasi untuk IP Dynamic (mungkin Factory default nya begitu). Untuk mengubah SIP Phone dari IP Dynamic ke IP Static tidak bisa dilakukan secara langsung dari keypad pesawatnya. Pengubahan harus dilakukan melalui bantuan PC. Dan PC tersebut harus menjalankan service dhcpd. Di IGOS Nusantara 2009 atau Fedora 11, instalasi DHCP cukup sederhana. Ikuti langkah-langkah di bawah ini.

Instalasi dhcpd :

[msmunir@svec ~]$ su -
Password:
[root@svec ~]# yum install dhcp


Setelah diinstalasi, jalankan dhcpd dengan cara sbb :

[root@svec ~]# /etc/rc.d/init.d/dhcpd start
Memulai dhcpd: [GAGAL]
[root@svec ~]#


Coba lihat file konfigurasi dhcpd.conf :

[root@svec ~]# more /etc/dhcp/dhcpd.conf
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
[root@svec ~]#


Lihat isi contoh file konfigurasi :

[root@svec ~]# more /usr/share/doc/dhcp-4.1.0p1/dhcpd.conf.sample
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# Use this to enble / disable dynamic dns updates globally.
#ddns-update-style none;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

subnet 10.152.187.0 netmask 255.255.255.0 {
}

# This is a very basic subnet declaration.

subnet 10.254.239.0 netmask 255.255.255.224 {
range 10.254.239.10 10.254.239.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

subnet 10.254.239.32 netmask 255.255.255.224 {
range dynamic-bootp 10.254.239.40 10.254.239.60;
option broadcast-address 10.254.239.31;
option routers rtr-239-32-1.example.org;
}

# A slightly different configuration for an internal subnet.
subnet 10.5.5.0 netmask 255.255.255.224 {
range 10.5.5.26 10.5.5.30;
option domain-name-servers ns1.internal.example.org;
option domain-name "internal.example.org";
option routers 10.5.5.1;
option broadcast-address 10.5.5.31;
default-lease-time 600;
max-lease-time 7200;
}

# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

host passacaglia {
hardware ethernet 0:0:c0:5d:bd:95;
filename "vmunix.passacaglia";
server-name "toccata.fugue.com";
}

# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
host fantasia {
hardware ethernet 08:00:07:26:c0:a5;
fixed-address fantasia.fugue.com;
}

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

class "foo" {
match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
}

shared-network 224-29 {
subnet 10.17.224.0 netmask 255.255.255.0 {
option routers rtr-224.example.org;
}
subnet 10.0.29.0 netmask 255.255.255.0 {
option routers rtr-29.example.org;
}
pool {
allow members of "foo";
range 10.17.224.10 10.17.224.250;
}
pool {
deny members of "foo";
range 10.0.29.10 10.0.29.230;
}
}
[root@svec ~]#


Salin file /usr/share/doc/dhcp-4.1.0p1/dhcpd.conf.sample ke /etc/dhcp/dhcpd.conf. Sebelumnya backup file /etc/dhcp/dhcpd.conf menjadi /etc/dhcp/dhcpd.conf.asli.

Setelah itu file dhcpd.conf di-edit secukupnya, sehingga menjadi sbb :

[root@svec dhcp]# more /etc/dhcp/dhcpd.conf
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name "serpong.batan.go.id";
option domain-name-servers 192.168.2.81;

default-lease-time 600;
max-lease-time 7200;

# Use this to enble / disable dynamic dns updates globally.
ddns-update-style none;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

subnet 10.152.187.0 netmask 255.255.255.0 {
}

# This is a very basic subnet declaration.

subnet 10.254.239.0 netmask 255.255.255.224 {
range 10.254.239.10 10.254.239.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

subnet 192.168.2.0 netmask 255.255.255.0 {
option routers 192.168.2.1;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.2.100 192.168.2.110;
}


# A slightly different configuration for an internal subnet.
subnet 10.5.5.0 netmask 255.255.255.224 {
range 10.5.5.26 10.5.5.30;
option domain-name-servers ns1.internal.example.org;
option domain-name "internal.example.org";
option routers 10.5.5.1;
option broadcast-address 10.5.5.31;
default-lease-time 600;
max-lease-time 7200;
}

# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

host passacaglia {
hardware ethernet 0:0:c0:5d:bd:95;
filename "vmunix.passacaglia";
server-name "toccata.fugue.com";
}

# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
host fantasia {
hardware ethernet 08:00:07:26:c0:a5;
fixed-address fantasia.fugue.com;
}

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

class "foo" {
match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
}

shared-network 224-29 {
subnet 10.17.224.0 netmask 255.255.255.0 {
option routers rtr-224.example.org;
}
subnet 10.0.29.0 netmask 255.255.255.0 {
option routers rtr-29.example.org;
}
pool {
allow members of "foo";
range 10.17.224.10 10.17.224.250;
}
pool {
deny members of "foo";
range 10.0.29.10 10.0.29.230;
}
}
[root@svec dhcp]#


Sekarang coba di-restart DHCP :

[root@svec ~]# /etc/rc.d/init.d/dhcpd restart
Mematikan dhcpd: [ OK ]
Memulai dhcpd: [ OK ]
[root@svec ~]#


Cek IP yang didapat oleh SIP Phone :

[root@svec ~]# nmap -sP 192.168.2.0/24

Starting Nmap 5.00 ( http://nmap.org ) at 2010-09-07 11:23 WIT
Host 192.168.2.1 is up (0.00056s latency).
MAC Address: 00:0C:42:52:A2:99 (Routerboard.com)
Host 192.168.2.31 is up (0.00056s latency).
MAC Address: 00:14:D1:F0:6B:99 (Trendware International)
Host 192.168.2.81 is up.
Host 192.168.2.86 is up (0.0025s latency).
MAC Address: 00:0D:19:03:41:D0 (Robe Show Lighting)
Host 192.168.2.100 is up (0.017s latency).
MAC Address: 00:0D:19:03:40:30 (Robe Show Lighting)
Host 192.168.2.101 is up (0.031s latency).
MAC Address: 00:02:FD:D5:58:C0 (Cisco Systems)
Nmap done: 256 IP addresses (6 hosts up) scanned in 5.68 seconds
[root@svec ~]#


Perhatikan baris :
Host 192.168.2.100 is up (0.017s latency).
MAC Address: 00:0D:19:03:40:30 (Robe Show Lighting)

Tampaknya SIP Phone mendapat IP 192.168.2.100

Sekarang SIP Phone bisa dipanggil menggunakan web browser deh.

No comments:

Post a Comment