Hello,
Kamailio SIP Server v3.3.1 stable release is out.
This is a maintenance release of the latest stable branch, 3.3, that
includes fixes since release of v3.3.0. There is no change to database
schema or configuration language structure that you have to do on
installations of v3.3.0. Deployments running previous v3.x.x versions
are strongly recommended to be upgraded to v3.3.1.
For more details about version 3.3.1 (including links and hints to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2012/08/kamailio-v3-3-1-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hi, full agree with this bug report. Adding the devel maillist. More
comments at the end of the mail:
2012/7/26 José Luis Millán <jmillan(a)aliax.net>:
> Hi,
>
> I'm using Kamilio 3.3.0 as registrar server. I`m using an outbound proxy so
> 'use_path' parameter or 'registrar' module is enabled.
>
> According to RFC 5626, a re-registration from a specific combination of AoR,
> instance_id and reg_id must update the binding.
>
> ""
> If the registrar receives a re-registration for a specific
> combination of AOR, and instance-id and reg-id values, the registrar
> MUST update any information that uniquely identifies the network flow
> over which the request arrived if that information has changed, and
> SHOULD update the time the binding was last updated.
> ""
>
> In my installation this is not fullfilled as shown:
>
> ""
> AOR:: jmillan
> Contact:: sip:jmillan@MY_IP;transport=ws;ov-ob=a570655c14 Q=
> Expires:: 181
> Callid:: 1hgq3khalq2rzfr
> Cseq:: 108
> User-agent:: JsSIP 0.1.0
> Path::
> <sip:OUTBOUND_IP:9090;transport=tcp;lr;ovid=de0c0b9f>,<sip:a570655c14@OUTBOUND_IP:10080;transport=ws;lr;ovid=de0c0b9f;ob>
> State:: CS_SYNC
> Flags:: 0
> Cflag:: 0
> Socket:: tcp:KAM_IP:5060
> Methods:: 783
> Ruid:: uloc-50119d99-328e-1
> Instance::
> <urn:uuid:38dce009-ae1f-4fd1-91dc-99ed9affddc1>
> Reg-Id:: 1
> Contact:: sip:jmillan@MY_IP;transport=ws;ov-ob=1dd97b4d51 Q=
> Expires:: 193
> Callid:: 1hgq3khalq2rzfr
> Cseq:: 110
> User-agent:: JsSIP 0.1.0
> Path::
> <sip:OUTBOUND_IP:9090;transport=tcp;lr;ovid=de0c0b9f>,<sip:1dd97b4d51@OUTBOUND_IP:10080;transport=ws;lr;ovid=de0c0b9f;ob>
> State:: CS_SYNC
> Flags:: 0
> Cflag:: 0
> Socket:: tcp:KAM_IP:5060
> Methods:: 783
> Ruid:: uloc-50119d99-3290-2
> Instance::
> <urn:uuid:38dce009-ae1f-4fd1-91dc-99ed9affddc1>
> Reg-Id:: 1
> ""
>
> The scenario is such that when the client looses the connection with the
> Outbound Server, it reconnects and re-registers to Kamailio in order to
> replace registration and be able to receive in-dialog messages.
Receiving in-dialog requests should work since GRUU is also being
used. The problem is that the new REGISTER (after UA disconnection)
does not update the previous one (as this thread reports) so Kamailio
still chooses the previous binding which does not work anymore.
Regards.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>