[SR-Users] Re: CentOS 7 and 8 deprecated
Hi Sergey, yes Centos 7 and 8 are still in use. Most users tend to upgrade / switch to an stabilized Centos 8 clone like alma Linux and Rocky Linux and one I forgot. I used centos 7 in the past and switched to Rocky Linux 8 (aka centos 8). "Rocky 8 (Code Name "Green Obsidian") has general support until 1 May 2024 and security support through 01 May 2029. The supported architectures are x86_64 and aarch64." https://docs.rockylinux.org/release_notes/ They support centos 8 then longer as RHEL did. So please leave at least the 8 as lowest number. Kind regards Karsten Horsmann Sergey Safarov via sr-users schrieb am Di., 4. Juni 2024, 19:44: > The CentOS project page shows that the 7 and 8 releases are deprecated. > https://www.centos.org/ > > Does the Kamailio community use these releases for prod? > If yes then I will keep the packaging for this release. > > If not, I will remove the packaging for 7 and 8 releases, and in the > future Kamailio will be packaged for 9 and 10 releases (planned). > > https://www.phoronix.com/news/CentOS-Stream-10-Start > > https://composes.stream.centos.org/stream-10/development/latest-CentOS-Stream/compose/BaseOS/x86_64/iso/ > > https://composes.stream.centos.org/stream-10/development/latest-CentOS-Stream/compose/BaseOS/x86_64/os/Packages/ > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: loose_route false when using topos? At which point in the call flow, does topos restore the Route header?
Hi, did you use some kind of db backend for topos like redis or mysql? Benoit Panizzon via sr-users schrieb am Mo., 26. Feb. 2024, 16:28: > Hi > > https://lists.kamailio.org/pipermail/sr-users/2020-July/109801.html > > I have the exact same issue. > > When the B side is starting a new transaction (UPDATE to refresh the > session in my case) without topos enabled, that transaction contains > one or multiple route header and a to_tag. > > Therefore loose_route() is true and the call is more or less sent to > route(RELAY) immediately without further checks. > > If topos is enabled, all record-route header are removed and only one > Via sent to the CPE. > So when the CPE replies, there is no Route header. > Therefore loose_route returns false. > > This makes me wonder, at which stage is topos restoring the route > headers? Shouldn't that happen before loose_route is evaluated? > > Mit freundlichen Grüssen > > -Benoît Panizzon- > -- > I m p r o W a r e A G-Leiter Commerce Kunden > __ > > Zurlindenstrasse 29 Tel +41 61 826 93 00 > CH-4133 PrattelnFax +41 61 826 93 01 > Schweiz Web http://www.imp.ch > __ > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Reject TCP SYN
Hi David, I have most of my setups with OPTIONS pings (upstream carrier and myself). If I want to fade out a Kamailio I set the option response to an not 200 value (like 603 or whatever) and my internal and the external system didn't bring in new invites but leave the currently running out. You can use cfg values for that or some kind of htable with value or so. Maybe an idea for your setup. David Villasmil via sr-users schrieb am Fr., 9. Feb. 2024, 15:04: > > Hey, Henning, yeah I thought about that, but thought that maybe there was > a better way to do it via Kamailio > > Thanks! > > Regards, > > David Villasmil > email: david.villasmil.w...@gmail.com > phone: +34669448337 > > > On Fri, 9 Feb 2024 at 14:08, Henning Westerholt wrote: > >> Hello, >> >> >> >> what about e.g. just using something like iptables, nftables etc..? >> >> >> >> iptables -A INPUT -p tcp --syn --destination-port -j REJECT >> --reject-with icmp-host-prohibited >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> *From:* David Villasmil via sr-users >> *Sent:* Donnerstag, 8. Februar 2024 14:28 >> *To:* Kamailio (SER) - Users Mailing List >> *Cc:* David Villasmil >> *Subject:* [SR-Users] Reject TCP SYN >> >> >> >> Hello all, >> >> >> >> Is there any way of actually rejecting (RST) NEW tcp connection attempts, >> while allowing the ongoing ones to finish naturally? >> >> >> >> I’m thinking maybe we can add this feature? >> >> >> Regards, >> >> >> >> David Villasmil >> >> email: david.villasmil.w...@gmail.com >> >> phone: +34669448337 >> > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Latest point releases seem to break early dialog UPDATEs from B-side when using topos (again)
Hi George, if you think it's a issue please fill a bug report on Github to let the Devs investigate. Also the questions in the form ask for all what they need. Thank you George Diamantopoulos via sr-users schrieb am Do., 15. Feb. 2024, 16:06: > Update: I have just downgraded to 5.6.4 using > https://deb-archive.kamailio.org/repos/kamailio-5.6.4 > > I have confirmed that topos works correctly with this version, so the > commit that broke things happened between 5.6.4 and 5.6.5 > > It might be related to how multi-homed installations interact with topos > when doing double rr. Tne difference I noticed is that in 5.6.4, the topos > substitution in Via is: > * inbound: Via: SIP/2.0/UDP 195.167.21.66:5060 > ;branch=z9hG4bKq27z808ysq87yrzq6vp8m26yq;Role=3;Hpt=8e88_16 > * outbound: Via: SIP/2.0/UDP > 172.30.154.1;branch=z9hG4bKae0b.fce5449c22b5e79eb01d4f1ab3f7c014.0 > > That is kamailio replaces the hop with its internal interface. With topos > on in 5.6.5, the behaviour is different for the UPDATE: > * inbound: Via: SIP/2.0/UDP 195.167.21.66:5060 > ;branch=z9hG4bK1jo121j8j2h5h3wzh2mzj51q5;Role=3;Hpt=8ea8_16 > * outbound: Via: SIP/2.0/UDP > 185.73.42.241;branch=z9hG4bKc45b.e6226bcf14264ae3b8674dd25a71191c.0 > > 185.73.42.241 is an interface on the same instance, but represents its > "public" interface. Additionally, it happens to reside on a VRF, so the > 200OK never reaches it because the routing table of the UAS directs it to > another host with the same IP. > > Hopefully this is enough to get an idea of what might have gone wrong? > Thanks! > > On Thu, 15 Feb 2024 at 15:55, George Diamantopoulos > wrote: > >> Hello all, >> >> I've noticed that there seems to be a regression with the topos module, >> more specifically the redis flavour, but I'm assuming the storage backend >> shouldn't make a difference. >> I have confirmed this affects both 5.6.5 and 5.7-nightly, so I'm assuming >> some backported commit is to blame. Kamailio 5.6.4 used previously, to the >> best of my memory, was not affected. >> >> Early dialog UPDATEs sent from the callee seem to be somehow malformed, >> since the 200 OK the UAS produces goes directly to the UAC despite having >> executed record_route() for the original INVITE. I can't imagine how this >> is possible, I thought responses always honour the Via header and record >> route shouldn't play a role in this case, right? >> >> Simply turning topos off restores the intended behaviour, however, so I >> can't help but think this is somehow related. Here's two call flows >> demonstrating the behaviour: >> * Topos on, 200 OK to UPDATE missing: https://pastebin.com/raw/J0zQeM5g >> * Topos off, 200 OK to UPDATE routed correctly: >> https://pastebin.com/raw/49yErezb >> >> I was wondering if anyone is aware of any commits that might be >> responsible for this. Additionally, is there an archive of debian packages >> with previous point releases so that I can confirm this regression with the >> latest versions? >> >> Thank you! >> >> Best regards, >> George >> > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: How to know registration status
Hi, I use the rpc stuff for nagios monitoring the uac register status and give some alerts (I watch you DTAG). On the other side the in script states are good to reply for example with 503 or whatever sip rc to get this disabled. Just as Sergiu described build stuff for your needs. Sergiu Pojoga via sr-users schrieb am Di., 9. Jan. 2024, 05:17: > Have you consulted the UAC module documentation? It's all in there. You > won't get faster help than that. > > BTW, it won't tell you the latest reply status code per se, usually that's > not a direct indicator of a registration status. If you are looking for > that specifically - then you'll have to build some kind of [in-memory] > [htable] storage to keep track of the latest reply status codes for each > r_uuid, somewhere in the reply route. > > RPC > https://kamailio.org/docs/modules/devel/modules/uac.html#uac.r.uac.reg_info > > Within script > > https://kamailio.org/docs/modules/devel/modules/uac.html#uac.f.uac_reg_status > > On Mon, Jan 8, 2024 at 10:26 PM mm e via sr-users < > sr-users@lists.kamailio.org> wrote: > >> After using the uac module to initiate registration to the remote end, is >> there a method to call back to notify the registration result? I want to >> get the registration result, such as 200 or 403 >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email to sr-users-le...@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: How to filter out xhttp request in event_route[siptrace:msg]
Hi Benoit,
how are you measure the traffic you don't want to your Homer? Print stuff
in that Kamailio event route or something else?
Kind regards
Karsten Horsmann
Benoit Panizzon via sr-users schrieb am Di.,
17. Okt. 2023, 13:54:
> Hi
>
> Further trying to eliminate every possible cause of UDP drops...
>
> We use Homer as HEP server in conjunction with the siptrace module.
>
> So to prevent DQM traffic to be sent to Homer I added:
>
> event_route[siptrace:msg] {
> if(is_method("KDMQ")) {
> drop();
> }
> }
>
> And had a closer look to the traffic sent to homer.
>
> I noticed, also xhttp:requests, as far as I see the replies, not the
> requests, get mirrored to homer.
>
> xhttp is not a sip method I could match I guess.
>
> The event_route[siptrace:msg] docs state only method can be filtered.
> So I can not filter requests on the separate http port I listen on for
> xhttp json-rpc requests.
>
> How can I prevent xhttp traffic to be mirrored to homer by the siptrace
> module?
>
> Mit freundlichen Grüssen
>
> -Benoît Panizzon-
> --
> I m p r o W a r e A G-Leiter Commerce Kunden
> __
>
> Zurlindenstrasse 29 Tel +41 61 826 93 00
> CH-4133 PrattelnFax +41 61 826 93 01
> Schweiz Web http://www.imp.ch
> __
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: 503(service unavailable)
Hi, I would go with the advise from Daniel to upgrade your Kamailio and if the error stays then come back or fill a issue on Github. And your server is really, really good sized for your use. I use VMs with much less specs and a higher CPS. Kind regards Masud via sr-users schrieb am Fr., 13. Okt. 2023, 09:10: > Hello. > Daniel can you help with these questions?) > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: UDP Fragmentation webRTC/UDP Call
Hi, did you pass over the ice stuff from webrtc to the udp side? You could strip that of with rtpengine options. Social Boh via sr-users schrieb am Sa., 14. Okt. 2023, 01:00: > Hello, > > I'm trying to solve a problem with calls WebRTC/UDP. I think is a > fragmentation problem because udp/webRTC calls works without problem. The > INVITE from Kamailio to the UDP device not receive any type of answer. > > I'm trying to reduce the SDP annex size using: > sdp_remove_line_by_prefix > > for some lines unsuccessfully. Maybe I don't know where put this function > in the script. > > Or, is there another way to solve this issue? > > Thank you in advance > > Regards > > -- > --- > I'm SoCIaL, MayBe > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
