@xkaraman: the PR has conflicts with the master branch, which introduced a
while ago checks for access rights of the rc files.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3594#issuecomment-1813909143
You are receiving this because you are
You match using `uri` (request-uri) which does not match on port, as the
default one for tls is 5061. For further discussions about using kamailio and
its configuration file, use sr-users mailing list.
--
Reply to this email directly or view it on GitHub:
Closed #3638 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3638#event-10976631543
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
If an item on tracker is wanted to stay open, the `Stale` label has to be
removed.
On the other hand, this is a free collaboration project. If nobody has time or
financial resources to support the development of the new features, then it
does not seem worth enough. This particular request is
> Has anyone figured out a clean alternative for this problem?
unfortunately no, only using the different sip proxy server :(
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2137#issuecomment-1813808584
You are receiving this because you are
This problem is almost more of a bug than enhancement and so it shouldn't be
closed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1968#issuecomment-1813796746
You are receiving this because you are subscribed to this thread.
Message ID:
This change is a very nice to have and shouldn't be closed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2011#issuecomment-1813795417
You are receiving this because you are subscribed to this thread.
Message ID:
Has anyone figured out a clean alternative for this problem?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2137#issuecomment-1813794358
You are receiving this because you are subscribed to this thread.
Message ID:
Module: kamailio
Branch: master
Commit: 4e614ba6b7a5663bd88f353a3ce7a0976d8e878f
URL:
https://github.com/kamailio/kamailio/commit/4e614ba6b7a5663bd88f353a3ce7a0976d8e878f
Author: Ovidiu Sas
Committer: Ovidiu Sas
Date: 2023-11-15T22:47:58-05:00
pua_dialoginfo: safety check for request pointer
This issue is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3589#issuecomment-1813701721
You are receiving this because
Closed #3523 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3523#event-10969811645
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
Since we are obviously the only ones having this problem and it's not possible
for us to set up a useful test system and to find anything without it, I'm
going to close it. Seems to be an edge case and we'll write a "restart every 4
weeks" wrapper around.
--
Reply to this email directly or
Would like to, but don’t know how to; first attempt failed with: Pull request
creation failed. Validation failed: must be a collaborator
From: Henning Westerholt ***@***.***>
Sent: Wednesday, November 15, 2023 9:11 AM
To: kamailio/kamailio ***@***.***>
Cc: BISHOP James (JRC-ISPRA) ***@***.***>;
After seeing the crashes on a system serving a lot of user requests, we see it
happening on a system being connected to some carriers dealing with only
outbound TLS connections, too.
Here are four more resolved core dumps.
Updated to close the db connection and added a module parameter for being able
to disable the check.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3639#issuecomment-1812438827
You are receiving this because you are subscribed to this thread.
@xkaraman pushed 2 commits.
bf0ef03ce0b55fb8a7998f06bbac6434e188ca9a topos: Close db connection
0f05b4f143bc3e46e89ed477c35532fb509dbcdb topos: Add version_table parameter
--
View it on GitHub:
@xkaraman pushed 2 commits.
a5773fefa83a8a74399211793a6a4404a9e3d32d topos: Close db connection
02974ce0d805cbb093ddf2c5d4ac39fa8d373ee8 topos: Add version_table parameter
--
View it on GitHub:
Callback function might do an operation which creates a new transaction, which
will result in a deadlock.
!-- Kamailio Pull Request Template --
!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull
@mtryfoss pushed 1 commit.
fe9cdb97c6312c47cbf1688bdb66d33661450238 ims_charging: Various changes to make
module compatible to other charging servers
--
View it on GitHub:
Thanks for the PR. @charlesrchance any feedback from your side regarding it?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3642#issuecomment-1812161330
You are receiving this because you are subscribed to this thread.
Message ID:
!-- Kamailio Pull Request Template --
!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable
I use uri_db module and the does_uri_exist() function to know if a user
exist or not.
I don't know if there is other function I can use with the same task
Regards
---
I'm SoCIaL, MayBe
El 14/11/2023 a las 7:30 a. m., Daniel-Constantin Mierla via sr-users
escribió:
Hello,
during the
@jbipre2 Could you maybe create a pull request with your patch suggestion? Then
it could be reviewed from the developers and possible also integrated in the
code base.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3570#issuecomment-1811984001
23 matches
Mail list logo