[SR-Users] Kamailio 4.4.1 REGISTER Parse Error in PCSCF

[Carsten Bock]

Hi,

the Zone-File is the interesting part, not the Bind-Config.

Did you configure the outbound Proxy on Zoiper properly?

You can actually see in the trace, that the Proxy-CSCF is forwarding
the packet to itself (looping) and at some point it drops the request.

Thanks,
Carsten

2016-05-30 16:53 GMT+03:00 Mihail Dakov <mihail.dakov at ng4t.com>:
> 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
>>>
>>
>>
>>
>
> _______________________________________________
> 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
>



-- 
Carsten Bock
CEO (Geschäftsführer)

ng-voice GmbH
Millerntorplatz 1
20359 Hamburg / Germany

http://www.ng-voice.com
mailto:carsten at ng-voice.com

Office +49 40 5247593-40
Fax +49 40 5247593-99

Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284

Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/