[sr-dev] git:master:c3acb864: rtpproxy: comment about child init rank filtering

Module: kamailio Branch: master Commit: c3acb864688656ef57d5a0a5263556fcf67d09d4 URL: https://github.com/kamailio/kamailio/commit/c3acb864688656ef57d5a0a5263556fcf67d09d4 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:4.3:68141ae0: tm: check branch uri against current uri when deciding if append a new branch

Module: kamailio Branch: 4.3 Commit: 68141ae0610faefafe3de25d98fcc09f9ffb2524 URL: https://github.com/kamailio/kamailio/commit/68141ae0610faefafe3de25d98fcc09f9ffb2524 Author: grumvalski Committer: Federico Cabiddu Date:

[sr-dev] git:master:335e4463: tm: check branch uri against current uri when deciding if append a new branch

Module: kamailio Branch: master Commit: 335e44635aa69ab73ec76f713a7d5ce7ce06748c URL: https://github.com/kamailio/kamailio/commit/335e44635aa69ab73ec76f713a7d5ce7ce06748c Author: grumvalski Committer: grumvalski Date:

[sr-dev] git:master:76f1f06d: Merge pull request #702 from kamailio/grumvalski/ts_append-instance

Module: kamailio Branch: master Commit: 76f1f06d1edab3f4fd530ec28a6834adaf3d3e1a URL: https://github.com/kamailio/kamailio/commit/76f1f06d1edab3f4fd530ec28a6834adaf3d3e1a Author: Federico Cabiddu Committer: GitHub Date: 2016-07-08T10:54:18+02:00

Re: [sr-dev] [kamailio/kamailio] Conflict between tls module and mongo-c-driver with ssl enabled (#660)

@lglayal -- can you give here the backtrace from gdb when you get the crash with mongo-c-driver-1.3.5 with --enable-ssl=yes ? I was digging a bit in mongodb-c-driver and looks like they don't set the locking functions if they are already set: ``` static void _mongoc_openssl_thread_startup

Re: [sr-dev] [kamailio/kamailio] tm: check branch uri against current uri when deciding if append a ne… (#702)

You're right. Maybe adding also the check on the received address? I didn't want to have a too heavy logic there, but it could make sense. On Fri, Jul 8, 2016 at 10:15 AM, Daniel-Constantin Mierla < notificati...@github.com> wrote: > You can merge it. > > I think it covers the most of the cases,

[sr-dev] git:master:0421bf53: pv: return 5061 for port variables (e.g., $dp) when transport is tls

Module: kamailio Branch: master Commit: 0421bf53c6ec193238b15907cf4a7c83bbae4401 URL: https://github.com/kamailio/kamailio/commit/0421bf53c6ec193238b15907cf4a7c83bbae4401 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] tm: check branch uri against current uri when deciding if append a ne… (#702)

You can merge it. I think it covers the most of the cases, but some corner ones may not be covered. Like one behind a nat router that is changing the public ip -- so the contact is the same, but the received address (computed from source ip) will be different. I guess this can happen only if

[sr-dev] git: new commits in branch master

- URL: https://github.com/kamailio/kamailio/commit/8af239f6483d935c981c5a187ebc3b2e804bd098 Author: Spencer Thomason Date: 2016-07-07T16:40:00-07:00 core: add portable rand() macros - add kam_rand(), kam_srand(), and KAM_RAND_MAX macros - provides

Re: [sr-dev] [kamailio/kamailio] Destination Port Inferred Incorrectly When Assigning $du (#700)

It is only about the returned value of the variable $dp. The port is not set in the outbound proxy uri. The logic is, if the $du has no port value, then return 5060 -- probably some old code relying on default value for port -- relevant piece of code inside the pv module: ``` } else

[sr-dev] [kamailio/kamailio] tm: check branch uri against current uri when deciding if append a ne… (#702)

…w branch This patch allows t_append_branches to cope with sip.instance usage, at least for the case when the contact uri has changed with regards to a previous registration. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/702 --

Re: [sr-dev] [kamailio/kamailio] Destination Port Inferred Incorrectly When Assigning $du (#700)

If the $du is referring to a SRV record, chances are that 5060 is wrong too as the SRV may have any port. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: