8 Jan
2019
8 Jan
'19
8:03 a.m.
Hello, I am trying to implement Kamailio as IMS system. I have followed
tutorial linked below:
https://www.kamailio.org/wiki/tutorials/ims/installation-howto
When I try to configure my DNS, I cannot ping cscf modules on my local
network, however when I'm on wireless, I can ping them.
Config:
kamailio-ims.org.dnszone
$ORIGIN kamailio-ims.org.
$TTL 1W
@ 1D IN SOA localhost. root.localhost. (
2006101001 ; serial
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
1D IN NS ns
ns 1D IN A 127.0.0.1
pcscf 1D IN A 127.0.0.1
_sip.pcscf 1D SRV 0 0 5060 pcscf
_sip._udp.pcscf 1D SRV 0 0 5060 pcscf
_sip._tcp.pcscf 1D SRV 0 0 5060 pcscf
icscf 1D IN A 127.0.0.1
_sip 1D SRV 0 0 5060 icscf
_sip._udp 1D SRV 0 0 5060 icscf
_sip._tcp 1D SRV 0 0 5060 icscf
kamailio-ims.org. 1D IN A 127.0.0.1
kamailio-ims.org. 1D IN NAPTR 10 50 "s" "SIP+D2U"
"" _sip._udp
kamailio-ims.org. 1D IN NAPTR 20 50 "s" "SIP+D2T"
"" _sip._tcp
scscf 1D IN A 127.0.0.1
_sip.scscf 1D SRV 0 0 5060 scscf
_sip._udp.scscf 1D SRV 0 0 5060 scscf
_sip._tcp.scscf 1D SRV 0 0 5060 scscf
hss 1D IN A 127.0.0.1
named.conf.options
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 127.0.0.1;
// };
//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https://www.isc.org/bind-keys
//========================================================================
dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};
named.conf.local
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "kamailio-ims.org" {
type master;
file "/etc/bind/kamailio-ims.org.dnszone";
};
dhclient.conf
# Configuration file for /sbin/dhclient.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
# man page for more information about the syntax of this file
# and a more comprehensive list of the parameters understood by
# dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
# not leave anything out (like the domain name, for example), then
# few changes must be made to this file, if any.
#
option rfc3442-classless-static-routes code 121 = array of unsigned integer
8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
prepend domain-name-servers 127.0.0.1;
#require subnet-mask, domain-name-servers;
timeout 300;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/sbin/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;
#alias {
# interface "eth0";
# fixed-address 192.5.5.213;
# option subnet-mask 255.255.255.255;
#}
#lease {
# interface "eth0";
# fixed-address 192.33.137.200;
# medium "link0 link1";
# option host-name "andare.swiftmedia.com";
# option subnet-mask 255.255.255.0;
# option broadcast-address 192.33.137.255;
# option routers 192.33.137.250;
# option domain-name-servers 127.0.0.1;
# renew 2 2000/1/12 00:00:01;
# rebind 2 2000/1/12 00:00:01;
# expire 2 2000/1/12 00:00:01;
#}
Thanks for helps,
Yağız
--