Hi List,
some sip clients like Bria and some sip phones like Astra
expect a <dialog-info><dialog></dialog></dialog-info>
on the NOTIFY message sent.
presence sends a NOTIFY after the SUBSCRIBE with NULL body if it doesn't find the presentity.
the patch already in master allows to configure the creation of a dummy dialog to be sent when presence doesn't find the presentity.
this behavior was only observed in dialog subscriptions so the patch was made against presence_dialoginfo.
the new param force_dummy_dialog defaults to 0 to preserve existing behavior.
using this patch Bria, Astra started working with BLF and others (Cisco, Polycom, Jitsi) kept running.
does anyone have anything against backporting this to 4.2 ?
Best
If I load the sca module in a minimal configuration without any sca modparams, it core dumps.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 sca.so 0x000000010de29823 sca_db_get_connection + 35 (sca_db.c:158)
1 sca.so 0x000000010de411e7 sca_subscription_db_update + 55 (sca_subscribe.c:493)
2 sca.so 0x000000010ddd44e3 sca_mod_destroy + 19 (sca.c:367)
3 kamailio 0x000000010d1ab089 destroy_modules + 73 (sr_module.c:790)
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/35
Hi,
may there is a routing-issue in rr-module, that causes some problems
with sip-spirals:
If is_myself("$ru") is true (in-dialog), kamailio rewrites the $ru to
the $route_uri (strict routing). That is usually correct.
loose.c
944 if (is_myself(&_m->parsed_uri)) {
945 return after_strict(_m);
This includes the case if is_myself("$route_uri") is also true - but(!)
$route_uri and $ru can still be different, and this can be very
relevant. rfc3261 says:
16.4 Route Information Preprocessing
The proxy MUST inspect the Request-URI of the request. If the
Request-URI of the request contains a value this proxy previously
placed into a Record-Route header field (see Section 16.6 item 4),
the proxy MUST replace the Request-URI in the request with the last
value from the Route header field, and remove that value from the
Route header field. The proxy MUST then proceed as if it received
this modified request.
It says " If the Request-URI of the request contains a value this proxy
previously placed into a Record-Route header field ". This means
$route_uri == $ru
Then - indeed - it does not matter to replace the $ru (even: does it
really change something?)
I do not see a sign to decide for strict routing instead of loose
routing, if (in-dialog) is_myself("$ru") AND is_myself("$route_uri") in
general, and especially not if $ru == $route_uri
Or is there any reason to process the request like it is now?
Cheers
Jasmin