[SR-Users] Kamailio 4.4.1 REGISTER Parse Error in PCSCF
Mihail Dakov
mihail.dakov at ng4t.com
Mon May 30 15:53:43 CEST 2016
Hi,
DNS error? This is interesting. Well I got a local bind running with a
dnszone provided from ims aio from kamailio.org site. You can have a
look at the bind config which copied adjusting port numbers.
I would say that it does work:
user at host:etc/kamailio$ host hss
hss.open-ims.test has address 192.168.177.100
user at host:/etc/kamailio$ host icscf
icscf.open-ims.test has address 192.168.177.100
user at host:/etc/kamailio$ host pcscf
pcscf.open-ims.test has address 192.168.177.100
user at host:/etc/kamailio$ host scscf
scscf.open-ims.test has address 192.168.177.100
On 05/30/2016 03:40 PM, Carsten Bock wrote:
> Hi,
>
> looks to me, like a typical DNS error. How did you configure DNS?
> You have BIND up and running and a proper Zone-File? Do the CSCF's
> properly query the DNS?
>
> Thanks,
> Carsten
>
> 2016-05-30 16:35 GMT+03:00 Mihail Dakov <mihail.dakov at ng4t.com>:
>> Hi Folks,
>>
>> I have the strangest problem just after installing latest stable
>> version. I had tried both ways using the repo
>> (http://deb.kamailio.org/kamailio44) and downloading code with local
>> compile (https://www.kamailio.org/w/2016/05/kamailio-v4-4-1-released/)
>>
>> The initial scenario is to get M2M with commercial IP and subsequently
>> use the Rx interface to do the same. We are blocked because we cannot
>> even achieve clean register for the UEs.
>>
>> UE1(galaxy s4 zoiper) -------- Kamailio IMS aio
>> |
>> UE2(galaxy s4 zoiper) -------- |
>>
>>
>> What happens is that the first register message triggers some
>> quasi-endless loop in the PCSCF. Hence it cannot be forwarded to SCSCF,
>> ICSCF and HSS. But this doesn't always happen and between all the parse
>> problems there are some register messages which get passed to the scscf
>> icscf and hss. Somehow the parser feeds itself from the previous parse
>> run and thus loops quite intensively. The message I get is SIP/2.0 400
>> CSeq method does not match request method.
>> I must say that reiterating the registration process sometimes i get the
>> register and sometimes i don't.
>>
>> Has anyone encounter similar issue for similar use case and can share
>> some thoughs about a fix?
>>
>> I attached relevant log file, pcaps and configuration files. Let me know
>> if more config files are needed.
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
>
-------------- next part --------------
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
//
// 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 "open-ims.test" IN {
type master;
file "/etc/bind/open-ims.dnszone";
allow-update { none; };
};
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 {
// 0.0.0.0;
192.168.xxx.xxx;
};
//========================================================================
// 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 no;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};
$ORIGIN open-ims.test.
$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 192.168.177.100
ns 1D IN AAAA 2815::192:168:177:100
pcscf 1D IN A 192.168.177.100
pcscf 1D IN AAAA 2815::192:168:177:100
_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 192.168.177.100
icscf 1D IN AAAA 2815::192:168:177:100
_sip 1D SRV 0 0 7060 icscf
_sip._udp 1D SRV 0 0 7060 icscf
_sip._tcp 1D SRV 0 0 7060 icscf
open-ims.test. 1D IN A 192.168.177.100
open-ims.test. 1D IN AAAA 2815::192:168:177:100
open-ims.test. 1D IN NAPTR 10 50 "s" "SIP+D2U" "" _sip._udp
open-ims.test. 1D IN NAPTR 20 50 "s" "SIP+D2T" "" _sip._tcp
scscf 1D IN A 192.168.177.100
scscf 1D IN AAAA 2815::192:168:177:100
_sip.scscf 1D SRV 0 0 6060 scscf
_sip._udp.scscf 1D SRV 0 0 6060 scscf
_sip._tcp.scscf 1D SRV 0 0 6060 scscf
trcf 1D IN A 192.168.177.100
trcf 1D IN AAAA 2815::192:168:177:100
_sip.trcf 1D SRV 0 0 3060 trcf
_sip._udp.trcf 1D SRV 0 0 3060 trcf
_sip._tcp.trcf 1D SRV 0 0 3060 trcf
bgcf 1D IN A 192.168.177.100
bgcf 1D IN AAAA 2815::192:168:177:100
_sip.bgcf 1D SRV 0 0 4060 bgcf
_sip._udp.bgcf 1D SRV 0 0 4060 bgcf
_sip._tcp.bgcf 1D SRV 0 0 4060 bgcf
mgcf 1D IN A 192.168.177.100
mgcf 1D IN AAAA 2815::192:168:177:100
_sip.mgcf 1D SRV 0 0 8060 mgcf
_sip._udp.mgcf 1D SRV 0 0 8060 mgcf
_sip._tcp.mgcf 1D SRV 0 0 8060 mgcf
hss 1D IN A 192.168.177.100
ue 1D IN A 192.168.177.100
ue 1D IN AAAA 2815::192:168:177:100
presence 1D IN A 192.168.177.100
presence 1D IN AAAA 2815::192:168:177:100
pcrf 1D IN A 10.199.0.45
pcrf 1D IN AAAA 2515::10:199:1:45
clf 1D IN A 192.168.177.100
clf 1D IN AAAA 2815::192:168:177:100
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160530/058e10bd/attachment.sig>
More information about the sr-users
mailing list