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
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,
Hello,
On 10/17/11 10:10 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
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
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
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
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
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.
have you tried calling t_newtran() on register request?
-- juha
I didn't get any syslog messages by defining WITH_DEBUG. I've set
log_stderror = NO and now I get DEBUG messages. I'll keep
monitoring...
Thanks.
El 20/09/2011 10:54, Daniel-Constantin Mierla escribi:
Hello,
On 9/20/11 10:13 AM,
