Hi,
Since we installed last version of Kamailio (3.1.4) 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?
Thanks in advanced.
Alejandro.
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.
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?
Cheers, Daniel
Hi Daniel,
I've just installed version 3.1.5 and the problem still occurs. The output of the command "save (location)" is 1.
I send you PCAP traces, the kamailio log and the "kamctl ul show" log second by second. The AOR is "phoenixMaster@sip.aeq.es". The CSeq of the retransmitted REGISTER is 27871 occurring at 10:09:43
This is an important issue for us. Thanks again.
Alejandro.
El 20/09/2011 10:54, Daniel-Constantin Mierla escribió:
Hi again,
Finally I found that the problem was in my configuration file, not in the server code. There was a "unregister" command before the "save" command, in order to delete all other contacts. In that moment I tried with save ("location", 0x04) but it didn't work for me (I don't remember why) and so I included the "unregister" command.
Thanks.
Alejandro.
El 03/10/2011 10:26, Alejandro Mingo escribió:
Hello,
glad to hear it was discovered. As a matter of fact, over the weekend, due to approach time for next release, I made a testbed and tried to reproduce but all was fine in my side.
My next thing to ask, and can be helpful in the future, was to ask you load the debugger module with cfgtrace parameter set to 1 to see all the config file actions that were executed.
Cheers, Daniel
On 10/17/11 8:40 AM, Alejandro Mingo wrote:
Has the behaviour of "save ("location", 0x04)" changed from version 3.1.0 to version 3.1.5? I hardly remember why it didn't work for me. May be the behaviour was different, keeping the first contact received instead of the last.
Thanks again.
Cheers,
Alejandro.
El 17/10/2011 9:24, Daniel-Constantin Mierla escribió: