27 Jul
2012
27 Jul
'12
2:43 p.m.
Yes,
Verified, 'gruu_enabled' is set to one.
Regards
2012/7/27 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
just to be sure before going to any further investigation (as I remember,
such case I tested a bit with some command line tools due to lack of a sip
phone with good ob/gruu support), do you have in the config:
modparam("registrar", "gruu_enabled", 1)
The default config file in 3.3, has the parameter set to 0.
Cheers,
Daniel
On 7/27/12 10:05 AM, Iñaki Baz Castillo wrote:
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>et>:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/**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
______________________________**_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http:/…
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.