Hello,
sr-docs mailing list was created with the purpose of discussing about
creating Kamailio documentation, but there was no real activity around
it over the years. Moreover, sometimes spammers subscribed to post
inappropriate messages.
Therefore, give the lack of usefulness so far, the mailing list is going
to be closed. The sr-dev or sr-users mailing lists can be used for
discussing changes to documentation content.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
Hello,
due to some changes from certain cloud infrastructure provider related to spam filtering with DMARC, we need to change the list manager "mailman" configuration for the following lists:
* sr-users
* sr-user-es
* sr-dev
* business
* sr-docs
* kamailio-announce
* the administrative mailing list
The change will impact the "From" that is displayed in your email program. Without that change large e-mail providers (Gmail, Microsoft O365) will reject messages from a sender with certain strict DMARC policy. This is already affecting several people on the lists (for example with GitHub notice mails), but over time the problem will certainly increase.
Regarding the technical change:
We will munge the From: header so it doesn't contain the domain that triggers the DMARC rejection. Essentially, the Mailman list takes ownership of the message and injects its own address into the From: header. This can affect reply-to-sender, although we add the original From: address in the Reply-To: header (or sometimes the Cc: header) to reduce the impact of this. We plan to do this for all emails unconditionally, regardless of their sender DMARC policy, to have an identical behaviour for all users. Please refer to this [1] page for more details. For a general description of DMARC refer to this page [2].
This change should have not a big impact for you, but some users might need to adapt some mail filters. Therefore, we would like to gather feedback on that change from you. We expect that the most visible change is that It will be not possible anymore to just reply by e-mail to mails from GitHub and have them "automatically" added to the discussed issue. This feature was so far used rarely and only from a few people.
We plan to implement this change by the end of this week, when its done it will be also shortly announced.
Best regards,
Henning Westerholt
[1] https://wiki.list.org/DEV/DMARC
[2] https://dmarc.org/overview/
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
This is easy to understand. As its name suggests, it is a male, female, or shemale torso. It doesn’t look like a full human. It only has a torso, but no limbs, no head. Of course, some expensive sex doll torsos may have a lifelike sex doll head.
https://www.uusextoy.com/sex-doll-torso/
This is easy to understand. As its name suggests, it is a male, female, or shemale torso. It doesn’t look like a full human. It only has a torso, but no limbs, no head. Of course, some expensive sex doll torsos may have a lifelike sex doll head.https://www.uusextoy.com/sex-doll-torso/
Hi guys;
Im using "REGISTRAR MODULE" to control the users login by device.
if (af==INET6){
reg_fetch_contacts("location", "$fu", "existingContact");
xlog("L_INFO","****************$si******************************");
xlog("L_INFO","****************$(hdr(Call-ID){s.substr,0,4})******************************");
if ( $(ulc(existingContact=>user_agent)[0]) =~ "SPI/v") &&
($(hdr(Call-ID){s.substr,0,4}) != "TTCN") {
$var(oldDeviceId) =
$(ulc(existingContact=>callid)[0]{s.substr,9,0});
$var(newDeviceId) = $(hdr(Call-ID){s.substr,9,0});
if($var(oldDeviceId) != $var(newDeviceId) ){
xlog("L_INFO","New device id is different:warn
previous user another user overide him");
$var(address) =
$(ulc(existingContact=>received){s.substr,9,0});
$var(ruri) = $(var(address){s.substr,4,0});
#$var(ruri) = "[" + $var(address)+ "]" + ":" + $sp
+ ";" + "transport" + "=" + $proto;
#Send a SIP Request signalling the problem and its
reason on the body
xlog("L_INFO","******************
$var(address)***************************");
$uac_req(method)="MESSAGE";
$uac_req(ruri) = "sip:"+ $au + "@" + $var(ruri);
$uac_req(furi) = "sip:kamailio@sip_domain";
$uac_req(turi) = $fu;
$uac_req(hdrs)="Max-Forwards: 70\r\nEvent:
reg\r\nContent-Type:
text/plain\r\nAccept-Contact:*;+g.ext.app.registration\r\n";
$uac_req(body)="Already registered with another
device id";
uac_req_send();
}
}
So as you can see Im trynig to get the variable $var(address) from
reg_fetch_contacts but is working for ipv4 unfortunatly not for ipv6. For
ipv6 it give me '0'.
Somthing is happening related to "[" "]".
How can I solve this problem?
Thank you.
OS: Centos 7
KAMILIO: version: kamailio 4.4.7 (x86_64/linux) 35d8ab
Hi,
We have followed the steps mentioned in the below link
https://kamailio.org/docs/tutorials/devel/kamailio-install-guide-git/#contr…
But these steps are not enough as P-CSCF, I-CSCF and S-CSCF are not installed so we also followed the steps mentioned in the below link
https://www.kamailio.org/wiki/tutorials/ims/installation-howto<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.kamai…>
But here, we are not able to understand configuration setting for starting P-CSCF, I-CSCF and S-CSCF and it looks like it needs separate server for each node. We need a document in which installation steps and configuration settings are clearly explained and we want to provide single server for each node.
Please provide the document or help so that we install kamailio successfully
Thanks & Regards,
Gaurav Kumar Gupta
Technical Architect
HCL Technologies Ltd.
A-8/9, Scetor-60, Noida-201301
Mob: +91-9873284610
www.hcltech.com<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hcltec…>
www.hcl.com<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hcl.co…>
[Fact_File_d8]
::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------