Ok Daniel, thanks again. We'll update our server as soon and as safely as possible.

The output you wanted is here (version 3.1.4). The AOR is "phoenixMaster@sip.aeq.es". The commnad has been executed with a 1 second period. The CSeq of the retransmitted REGISTER is 4627 occurring at 12:36:55.

Cheers.

Alejandro.





El 22/09/2011 10:04, Daniel-Constantin Mierla escribió:
Hello,

On 9/21/11 2:14 PM, Alejandro Mingo wrote:
Thanks. I installed version 3.1.4 with a CentOS 5.5 package, but i cannot find the 3.1.5. one.
3.1.5 rpms should be available now.


I've inserted the code you gave me in the config file and version 3.1.4 returns value 1 (instead of 2).

Interesting, can you do kamctl ul show __userid__ before and after the the registration update with retransmission happens and send the output here?

Cheers,
Daniel


Cheers,
Alejandro.



El 21/09/2011 12:38, Daniel-Constantin Mierla escribió:
Hello,

I tried to reproduce with a very simple config to handle register requests. So I sent a REGISTER with expires 60 (very much the same as the one in the trace you sent), waited a while, then sent two REGISTERs having the CSeq incremented. All went fine.

I tested with master and 3.1 branches (so the last is actually 3.1.5). Can you upgrade to 3.1.5 first and try again? If still fails, then update config to print the return code for save() function, something like:

$var(r) = save("location");
xlog("code returned by save is $var(r)\n");
if($var(r) < 0)
      send_reply("500", "Failure");

Let me know the value of the returned code for the register that does not have a contact in reply.

Cheers,
Daniel

On 9/20/11 2:10 PM, Alejandro Mingo wrote:

Hi Daniel-Constantin,

 I send you the PCAP and LOG files corresponding to one of these situations. As you can see in the LOG file, one thread (5444) handles the first REGISTER, other thread (5447) handles the second REGISTER (retransmission) and a third thread (5451) indicates that the binding has expired, six seconds after the arrival of both REGISTERs.
 
 Thanks again.
 
  Alejandro.



El 20/09/2011 10:54, Daniel-Constantin Mierla escribió:
Hello,

On 9/20/11 10:13 AM, Alejandro Mingo wrote:
Hi,

 Since we installed last version of Kamailio (3.1.4)

the last version is now 3.1.5, but this is not really the most important aspect. However, it is recommended to upgrade, there were some fixed to registration handling when register requests have multiple contacts.
we have been experiencing a big problem with REGISTER retransmissions. When the server receives a retransmitted REGISTER it removes the binding and the UAC remains unregistered until next refreshing period. I include a PCAP capture that shows this behaviour.

I am not 100% sure that this problem never happened with older versions.

Has anybody experienced the same problem?
I will try to reproduce and investigate myself. Anyhow, meanwhile maybe you can provide more hints faster. Do you have error messages in the syslog? Can you run with debug=4 in config file and send the output in syslog for such a case?

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda

Se certificó que el correo no contiene virus.
Comprobada por AVG - www.avg.es
Versión: 10.0.1410 / Base de datos de virus: 1520/3909 - Fecha de la versión: 20/09/2011



--




_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda


--