According to the https://travis-ci.org/sippy/voiptests:
LD (gcc) [M ratelimit.so] ratelimit.so
CC (gcc) [M registrar.so] api.o
CC (gcc) [M registrar.so] common.o
CC (gcc) [M registrar.so] config.o
CC (gcc) [M registrar.so] lookup.o
CC (gcc) [M registrar.so] path.o
CC (gcc) [M registrar.so]
That also affects 4.1. JFYI.
On Fri, Aug 7, 2015 at 4:56 PM, Maxim Sobolev sobo...@sippysoft.com wrote:
According to the https://travis-ci.org/sippy/voiptests:
LD (gcc) [M ratelimit.so] ratelimit.so
CC (gcc) [M registrar.so] api.o
CC (gcc) [M registrar.so] common.o
CC (gcc) [M
@fredposner Do you have any more details regarding so be careful how you deal
with REGISTER retransmissions in this case? Also, even considering a UA which
is compliant with RFC3261's recommendation, the `contact only` mode would fail
on UA restart. What am I missing?
---
Reply to this email
Indeed -- the log messages went out of view size, needing scrolling.
However, the issue has been fixed, the code is ok. You probably run an old
version, upgrade to latest version in 4.1.
---
Reply to this email directly or view it on GitHub:
I fixed that!
56b54a5767a3ad0df446fe181aee0ee5fd64276d
e8a795a6a413ae453f619e3deaf36c26b85b0077
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/280#issuecomment-128706816___
sr-dev mailing list
Oh, how embarrassing. I guess this server might not have got updated :/ Sorry
guys, I'll make sure my house is in order again and close this assuming it is
indeed fixed.
---
Reply to this email directly or view it on GitHub:
Well replacing this :
```C++
if (dbmode != RLS_DB_ONLY)
```
By this :
```C++
if(get_to(msg)-tag_value.s==NULL || get_to(msg)-tag_value.len==0)
```
Which is a detection of initial transaction if I'am understanding well (no to
tag). There is such a detection upper in the code (line 610-611) :
What do you refer as current configuration? Default config?
The fact is that many options in various modules are there to cope with real
world, rather than specs. If implementing strictly the specs, it will be very
rare cases when all it works -- eg, nat traversal, by specs sdp should not
A quick check in the code and the UPDATE is using only contact. No call-id
involved.
Have you checked with the source code or grabbed the sql queries that showed
call-id being used?
---
Reply to this email directly or view it on GitHub:
The SQL queries are above in the original bug report.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/280#issuecomment-128702978___
sr-dev mailing list
sr-dev@lists.sip-router.org
i want to replace MySQL with redis database in kamalio,but in kamalio
supports transactions with MySQL ,ie saving data in MySql DB.but while
trying to run kamailio with redis ,transaction are not happening,is there
any module that i have to enable in kamalio for No SQL databases
transaction
Hi All,
i want to replace MySQL with redis database in kamalio,but in kamalio
supports transactions with MySQL ,ie saving data in MySql DB.but while
trying to run kamailio with redis ,transaction are not happening,is there
any module that i have to enable in kamalio for No SQL databases
Great!
Daniel
On 05/08/15 18:31, M S wrote:
yes, using set_contact_alias() fixed the problem.
Many thanks and kind regards.
On Wed, Aug 5, 2015 at 4:18 PM, Daniel-Constantin Mierla
mico...@gmail.com mailto:mico...@gmail.com wrote:
Use set_contact_alias()/handle_uri_alias() instead
Thanks, fix pushed to master branch. Made all message lowercase, as well.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/275#issuecomment-128642028___
sr-dev mailing list
sr-dev@lists.sip-router.org
Closed #275.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/275#event-376120733___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Thanks
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/277#issuecomment-128642137___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
To understand properly, is it like the Expires was not updated?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/278#issuecomment-128643419___
sr-dev mailing list
sr-dev@lists.sip-router.org
Module: kamailio
Branch: 4.2
Commit: 5b62b14c0655bfff77359d1169b31f74a354783f
URL:
https://github.com/kamailio/kamailio/commit/5b62b14c0655bfff77359d1169b31f74a354783f
Author: Victor Seva linuxman...@torreviejawireless.org
Committer: Victor Seva linuxman...@torreviejawireless.org
Date:
Module: kamailio
Branch: 4.1
Commit: f2d23c1a038703e37a32dd5ea75d9b442e2fbc93
URL:
https://github.com/kamailio/kamailio/commit/f2d23c1a038703e37a32dd5ea75d9b442e2fbc93
Author: Victor Seva linuxman...@torreviejawireless.org
Committer: Victor Seva linuxman...@torreviejawireless.org
Date:
Module: kamailio
Branch: master
Commit: 6b15a51b016c232fab6665fc03ed01dad09ac8b5
URL:
https://github.com/kamailio/kamailio/commit/6b15a51b016c232fab6665fc03ed01dad09ac8b5
Author: Daniel-Constantin Mierla mico...@gmail.com
Committer: Daniel-Constantin Mierla mico...@gmail.com
Date:
Module: kamailio
Branch: 4.3
Commit: a2b8efe1c24a213ef6c4221a59af544a3873e9d2
URL:
https://github.com/kamailio/kamailio/commit/a2b8efe1c24a213ef6c4221a59af544a3873e9d2
Author: Victor Seva linuxman...@torreviejawireless.org
Committer: Victor Seva linuxman...@torreviejawireless.org
Date:
Merged #279.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/279#event-376153298___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Module: kamailio
Branch: master
Commit: e5ec5a443aaec732390bae6247fe561ea312b709
URL:
https://github.com/kamailio/kamailio/commit/e5ec5a443aaec732390bae6247fe561ea312b709
Author: Victor Seva linuxman...@torreviejawireless.org
Committer: Victor Seva linuxman...@torreviejawireless.org
Date:
No the problem is:
```
P-Registrar-Error: Too many registered contacts
```
The check:
https://github.com/kamailio/kamailio/blob/master/modules/registrar/save.c#L644-L651
for a REGISTER that is updating gets rejected
---
Reply to this email directly or view it on GitHub:
Can be merged and backported if needed. Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/279#issuecomment-128644582___
sr-dev mailing list
sr-dev@lists.sip-router.org
Module: kamailio
Branch: master
Commit: b48bbd377a9dd9c8d18e4f6642f785659848ff2c
URL:
https://github.com/kamailio/kamailio/commit/b48bbd377a9dd9c8d18e4f6642f785659848ff2c
Author: Daniel-Constantin Mierla mico...@gmail.com
Committer: Daniel-Constantin Mierla mico...@gmail.com
Date:
Oh, ok, missed the response code in the first place, focused on returned
contact -- apparently still jet lagged.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/278#issuecomment-128644543___
sr-dev
The problem seems to be that ci_pack when calling only with msg was not setting
the intance and reg_id into the contact_info, so ul.get_ucontact_by_instance at
https://github.com/kamailio/kamailio/blob/master/modules/registrar/save.c#L582
was at
Module: kamailio
Branch: master
Commit: 99ce64fc555cc0b6b0189d812c6156cb05fb2e1b
URL:
https://github.com/kamailio/kamailio/commit/99ce64fc555cc0b6b0189d812c6156cb05fb2e1b
Author: Victor Seva linuxman...@torreviejawireless.org
Committer: Victor Seva linuxman...@torreviejawireless.org
Date:
Closed #278.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/278#event-376158117___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi Daniel,
We are testing Kamailio 4.1.8 and we are running into a deadlock in the
dialog module. I therefore searched the git commits if something has
been done to the locking in dialog module and I found this commit.
I wanted to ask you if there was a specific motivation for you to change
Closed #280.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/280#event-376412049___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello,
are you using cnxcc or other module on top of dialog?
The reason was cnxcc, as it apparently does some lower level dialog ops
that involve locking in case of a dialog being already locked.
Have you got the backtrace in case of the lock you encountered to see
what situations ended there?
First, this kind of debate is not appropriate for tracker, it is a discussion
for mailing lists. Here we track bugs or request for feature, not using it as a
forum.
Column id is not used internally in most of the modules, but some do and I
guess they need int. usrloc doesn't use it. On the
Closed #274.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/274#event-376282460___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Can you try replacing the IF condition in the snippet you pasted above with:
```
if(get_to(msg)-tag_value.s==NULL || get_to(msg)-tag_value.len==0) {
```
then re-compile, install and test?
I will look deeper when I get a chance, but for the moment it might be an
workaround to get you going.
Have you changed the maching_mode parameter for usrloc module:
*
http://kamailio.org/docs/modules/stable/modules/usrloc.html#usrloc.p.matching_mode
---
Reply to this email directly or view it on GitHub:
I have not, @miconda, because that would be only a workaround for this bug,
rather than a solution. My claim is that the current configuration *should*
work. Am I mistaken?
---
Reply to this email directly or view it on GitHub:
38 matches
Mail list logo
