hello
im coming back to ask on this forum, sorry if im at the wrong place, but i guess there are some sip experts around here (if it's not the right place, tell me where...)
i was wondering, what about the public enum usage for sip networks?
i mean, is there any type of public networks, known for having an opened/accessible users scheme?
eg : here in france there are linphone and ippi, and others (providing software+service)
both, offers both software+service, but can be dissociated
…
[View More]means its possible (normally) to use another sip software with a provider, etc
the idea is, there is what i think called a DID/URI, whom looks like email principle :
user(a)domain.com ; but in a way, it's a bit similar for xmpp and sip : alice(a)first.com could email, call or message bob(a)second.net ; and normally, it's minded to be interoperable (or federated) on an opened-network circuit.
what i try to understand is :
URI or DID might be i guess, the user(a)domain.net.
however, if sip is really used today, it's on closed networks. I mean, using data, only whatsapp and others, I guess uses xmpp or sip, but not in an opened-way, means not +123475(a)whatsapp.org, what would be great to be communicate with, without having to install their app.
on ""real"" opened-community, such as callcentrix or voip.ms, it's the case : a user of a domain could reach another domain, using it's DID/URI email.
well, I found then that there is a kind of ENUM thing I discovered few days ago. instead of defunct iNum, where it was supposed to be as an online voip accessible and free from internet (like skype) new kind of voip network, ENUM looks like to be enclosed one. As operators mainly looks for ""security"" (or security of closed-business), i found those things :
https://wiki.freepbx.org/display/DIMG/SIP+Enum+Supporthttps://en.wikibooks.org/wiki/Voice_over_IP/ENUM_and_E146_Technologyhttps://www.lightreading.com/cable-technology/the-impact-of-enum-on-voiphttps://lafibre.info/images/peering/201506_efort_carrier_enum.pdf
so if i understand well, mainly operators took SIP protocol to create their own voIP network, to their susbcribers ; not bad if it wasnt totally-closed?
imho, i then discovered that all operators around the world have (for a part of them) a voip/sip account for all volte or even for business lines. My mind was, sip looks like to be great working. But what surprised me in the bad way : why isnt it possible, because it's 100% data usage, to call them directly from a common "voip/callcentric/linphone/other" sip account?
i guess it's a question of money, but i dont understand then why people dont go directly on a sip account if their computer is internet connected h24 or even LTE/5G running permanently on their phone : it would be double unlimited plus free of charge international calls. Know people will tell me "just it's whatsapp", but no : whatsapp brings just simplicity + zero rating in some countries, not privacy-compliant and opened and federated usage. am I wrong?
on my own, I would have a little question for the nerds or passionate, like me, to SIP protocol for opened-networks, to ensure it's possible to simple voip communicate with relatives, on the same scheme as email : just call a contact by it's user(a)domain.net, and it might work. How could you convince your relatives to go on a such scheme?
I mean, in EU we have several voip initiative, whom are fully accessible from worldwide callers, where in N/america there are voip.ms and callcentric, maybe others.. are those users only using it for pstn-paid calls? why not skype then?
in addition : is there a directory of opened-sip URI/DID/ENUM to be in touch with, to see what operators/voip service providers permits their users to be called from anywhere around the world?
the main advantage of this is like email (or xmpp) : just with a voip/sip software, + a sip account, calls to any other sip user around the world, is generally totally free and unlimited. Why dont people adopt it, instead of whatsapp&etc?
are they some opened-voip providers directory, where some individuals or organisations could be called from over the world, through sip?
do you know some organisation, NGO or companies whom can be called from just a opened-sip network provider?
thank you for reading, and much more if you share your thoughts
(and sorry for bad eng..)
[View Less]
hello,
i have tried with a friend recently, im unsure if it's the proper place to talk about it, but it's one of the rare forums with a category focused about SIP/VoIP.
here it is :
gigaset c530ip, i guess it's among the most solt model from the last decade, from that manufacturer.
on frenchy telcos forums, several nerds also have it, so i guess that device is pretty well know. What is highly less known, is the gigaset.net voip network offered by the manufacturer. I was thinking it was …
[View More]running about xmpp protocol. Looks like it's sip only. Well, it started like :
1. i tried to see if it was usable, alive, for a several yrs old device. So i looked into the phone's system, and saw a kind of directory, really difficult to use nowadays, regarding our smartphone's new features : it's both slow and limited in entry's public directory. well, half-public : browse it requires to get a gigaset voip professional phone.
2. when i discovered that "worldwide" directory, i tried to "call" like that, registred accounts. Uh: all were busy/unactive, no one seems available. From family-like accounts, to SMB or others usages, hundred of "sip account" are still registred, and listed.
3. well, after few months of little investigation, with a friend whom gets a such similar phone, we tried to see if it was a out of order network, or just a dormant one with thousand of forgotten accounts. we were then surprised to see that the network was working well, able to get a (unsecured) sip/voip communication.
4. thus, device looks like to get released in retail too early to support s/zrtp. however, even if between both same models, from two different cities, with two different internet access, the communication was working, but from another type of phone/service, it's not at all : i tried from both linphone/ippi software/services. Each time, the gigaset rings, shows the incoming call alert, but even when pushing the green button to hang up, isnt able to start a new communication : it's blocked on the gigast device, while the other (not gigaset, linphone) phone says its entered in communication, with no sound at all, for a while (about a minute) before the communication gets stopped.
qusetion is : how could it be fixed? anyone get success to call a sip gigaset device on gigaset.net network, with a working communication?
here are various logs we went about to retrieve from a friends (from linphone app or device's base with tcpdump) are here :
https://e.pcloud.link/publink/show?code=kZaqksZwM00MtijVWhqlGajWiyL7RWmDwg7
i thank you vm for your help !
[View Less]
"200,405,486" ??
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf7f963466a/130981248(a)github.com>
which responses are ??
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf7f963466a/130981246(a)github.com>
Module: kamailio
Branch: master
Commit: c1bc5f7095659182401e6dd2b25bfaf7f963466a
URL: https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-10-26T13:41:12+02:00
usrloc: docs for ka_reply_codes parameter
---
Modified: src/modules/usrloc/doc/usrloc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]c1bc5f7095659182401e6dd2b25bfaf…
Patch: https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
---
diff --git a/src/modules/usrloc/doc/usrloc_admin.xml b/src/modules/usrloc/doc/usrloc_admin.xml
index 61491648a0c..5f244bc80e5 100644
--- a/src/modules/usrloc/doc/usrloc_admin.xml
+++ b/src/modules/usrloc/doc/usrloc_admin.xml
@@ -1504,6 +1504,29 @@ modparam("usrloc", "ka_logmsg", " to-uri: [$tu] remote-addr: [$sas]")
</example>
</section>
+ <section id="usrloc.p.ka_reply_codes">
+ <title><varname>ka_reply_codes</varname> (str)</title>
+ <para>
+ Comma separated list of reply code values or reply code classes to be
+ considered valid for keepalive processing. If the reply code does not
+ match any of them, then the reply is ignored, not considered a valid
+ response to keepalive request. It could be useful to skip replies
+ from intermediary proxies that could not forward the request.
+ </para>
+ <para>
+ Default value is <quote>0</quote> (checking of reply code is not done,
+ are responses are considered valid).
+ </para>
+ <example>
+ <title><varname>ka_reply_codes</varname> parameter usage</title>
+ <programlisting format="linespecific">
+...
+modparam("usrloc", "ka_reply_codes", "2,405,486")
+...
+ </programlisting>
+ </example>
+ </section>
+
<section id="usrloc.p.load_rank">
<title><varname>load_rank</varname> (int)</title>
<para>
[View Less]
>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000134:
```
Source: kamailio
Severity: important
User: matthew-pcredep(a)debian.org
Usertags: obsolete-pcre3
Dear maintainer,
Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.
The …
[View More]newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/
Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html
Regards,
Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2946
[View Less]
Module: kamailio
Branch: master
Commit: b882db36bbb7f7f13366bcc8f1db9f50910d2c0c
URL: https://github.com/kamailio/kamailio/commit/b882db36bbb7f7f13366bcc8f1db9f5…
Author: Nicolas C <nchaigne(a)capgemini.fr>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-10-24T20:36:39+02:00
http_client: Add parameter timeout_mode (timeout in seconds or milliseconds)
A new parameter timeout_mode is added.
This parameter defines if timeouts are enabled, and in which unit …
[View More]timeout values are expressed.
- 0 - Timeouts are disabled.
- 1 - Timeout values are in seconds (default).
- 2 - Timeout values are in milliseconds.
Implementation detail:
default global timeout = 0 (unconfigured).
Parse connections as usual. If they have a timeout configured, use it.
In mod_init:
if global timeout == 0 (unconfigured), and timeout_mode is 1 or 2:
if timeout_mode == 1 -> global timeout = 4 (seconds)
if timeout_mode == 2 -> global timeout = 4000 (milliseconds)
for each connection "conn" (fixup):
if timeout_mode is not 1 or 2 -> conn.timeout = 0 (to reflect the fact that no timeout will be handled)
else if conn.timeout is not configured -> conn.timeout = global timeout (in seconds or milliseconds, depending on timeout_mode).
When doing Curl requests (curL_request_url):
if timeout_mode == 1: set CURLOPT_TIMEOUT
if timeout_mode == 2: set CURLOPT_TIMEOUT_MS
---
Modified: src/modules/http_client/curlcon.c
Modified: src/modules/http_client/curlcon.h
Modified: src/modules/http_client/doc/http_client_admin.xml
Modified: src/modules/http_client/functions.c
Modified: src/modules/http_client/http_client.c
Modified: src/modules/http_client/http_client.h
---
Diff: https://github.com/kamailio/kamailio/commit/b882db36bbb7f7f13366bcc8f1db9f5…
Patch: https://github.com/kamailio/kamailio/commit/b882db36bbb7f7f13366bcc8f1db9f5…
[View Less]
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature …
[View More](non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
A new parameter timeout_mode is added.
This parameter defines if timeouts are enabled, and in which unit timeout values are expressed.
- 0 - Timeouts are disabled.
- 1 - Timeout values are in seconds (default).
- 2 - Timeout values are in milliseconds.
For reference, see discussion in: https://github.com/kamailio/kamailio/pull/3611
Implementation detail:
```
default global timeout = 0 (unconfigured).
Parse connections as usual. If they have a timeout configured, use it.
In mod_init:
if global timeout == 0 (unconfigured), and timeout_mode is 1 or 2:
if timeout_mode == 1 -> global timeout = 4 (seconds)
if timeout_mode == 2 -> global timeout = 4000 (milliseconds)
for each connection "conn" (fixup):
if timeout_mode is not 1 or 2 -> conn.timeout = 0 (to reflect the fact that no timeout will be handled)
else if conn.timeout is not configured -> conn.timeout = global timeout (in seconds or milliseconds, depending on timeout_mode).
When doing Curl requests (curL_request_url):
if timeout_mode == 1: set CURLOPT_TIMEOUT
if timeout_mode == 2: set CURLOPT_TIMEOUT_MS
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3615
-- Commit Summary --
* http_client: Add parameter timeout_mode (timeout in seconds or milliseconds)
-- File Changes --
M src/modules/http_client/curlcon.c (27)
M src/modules/http_client/curlcon.h (14)
M src/modules/http_client/doc/http_client_admin.xml (35)
M src/modules/http_client/functions.c (21)
M src/modules/http_client/http_client.c (32)
M src/modules/http_client/http_client.h (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3615.patchhttps://github.com/kamailio/kamailio/pull/3615.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3615
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3615(a)github.com>
[View Less]