[sr-dev] [kamailio/kamailio] Advertise in listen directive doesn't let to use hostname without port (Issue #3932)

2024-07-26 Thread Evgenii Buchnev via sr-dev
Hey Team, Thank you for the awesome software ### Description Neither option work: `listen=... advertise some.custom.hostname.io` `listen=... advertise some.custom.hostname.io:0` to make Kamailio present only hostname(without port) in Record-Route headers, affects NAPTR/SRV. ### Troublesho

[sr-dev] Re: [kamailio/kamailio] Advertise in listen directive doesn't let to use hostname without port (Issue #3932)

2024-07-26 Thread Henning Westerholt via sr-dev
Closed #3932 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3932#event-13657280834 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Devel

[sr-dev] Re: [kamailio/kamailio] Advertise in listen directive doesn't let to use hostname without port (Issue #3932)

2024-07-26 Thread Henning Westerholt via sr-dev
If you want to control your Record-Route, just use the function for it: record_route_preset(string [,string2]), see rr module README for details. Please adress further questions on how to use Kamailio to our users mailing list, as the tracker is for reporting bugs or other issues in the code. -

[sr-dev] Re: [kamailio/kamailio] Advertise in listen directive doesn't let to use hostname without port (Issue #3932)

2024-07-26 Thread Henning Westerholt via sr-dev
And to add - if there is a bug in the functionality, we can of course re-open the old bug as referenced above. According to the comments from Daniel there, advertise should work without port. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3932#

[sr-dev] Re: [kamailio/kamailio] Advertise in listen directive doesn't let to use hostname without port (Issue #3932)

2024-07-26 Thread Evgenii Buchnev via sr-dev
Re-opened. https://github.com/kamailio/kamailio/issues/3933 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3932#issuecomment-2252176460 You are receiving this because you are subscribed to this thread. Message ID: __

[sr-dev] [kamailio/kamailio] Advertise in listen directive still gives port in headers even though it's not set or set to 0 (Issue #3933)

2024-07-26 Thread Evgenii Buchnev via sr-dev
Reopening. (https://github.com/kamailio/kamailio/issues/3932#issuecomment-2252138364) It's bug. Please see highlighted on screenshot. ![image](https://github.com/user-attachments/assets/88b9671d-d2be-4d49-8596-3e6ab3a2d294) Hey Team, Thank you for the awesome software ### Description Ne

[sr-dev] Re: [kamailio/kamailio] p-charging-vector bug in siputils with force flag (Issue #3929)

2024-07-26 Thread Michael via sr-dev
Hi Daniel, yes, topoh is active. But without topoh the problem is more or less the same. Exept the line "TH: dih" is missing: ``` INVITE sip:+49;npdi;rn=+49x...@bob.com;user=phone SIP/2.0 Record-Route: Record-Route: Via: SIP/2.0/UDP 62.xxx.xxx.xxx:5070;branch=z9hG4bK7b0f.6d6fba11

[sr-dev] Re: [kamailio/kamailio] p-charging-vector bug in siputils with force flag (Issue #3929)

2024-07-26 Thread Daniel-Constantin Mierla via sr-dev
I just wanted to be sure that topos is not creating any issue, because `TH` should never leave Kamailio as a header. As it looks right now, some lenght is not computed right, because it adds more data than needs, which was in the buffer at some point in time. -- Reply to this email directly or

[sr-dev] Re: [kamailio/kamailio] p-charging-vector bug in siputils with force flag (Issue #3929)

2024-07-26 Thread Michael via sr-dev
In this example, the incorrect length also included part of the SDP. This generated an additional error message because there was a duplicate Content-Length header : ``` INVITE sip:+49xxx...@bob.com;transport=udp;user=phone SIP/2.0 Call-ID: 02817-md-4463d585-52e48e...@c4swlmgc2.alice.com Con

[sr-dev] Re: [kamailio/kamailio] p-charging-vector bug in siputils with force flag (Issue #3929)

2024-07-26 Thread Michael via sr-dev
Apart from the incorrect length, it seems strange to me that the PCV is being copied at all. If I understand the F-flag correctly, the old header should be deleted and a new one generated. `Manage the P-Charging-Vector header (RFC7315). The flags can be: 'r' - remove; 'g' - generate; 'f' - forc

[sr-dev] git:master:660a0192: xprint: return on mod init error case

2024-07-26 Thread Daniel-Constantin Mierla via sr-dev
Module: kamailio Branch: master Commit: 660a019263b81d318700c205531bf4e042c912cf URL: https://github.com/kamailio/kamailio/commit/660a019263b81d318700c205531bf4e042c912cf Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date: 2024-07-26T19:50:40+02:00 xprint: return on mod

[sr-dev] git:master:3333611a: core: cfg select - check res when getting the variable

2024-07-26 Thread Daniel-Constantin Mierla via sr-dev
Module: kamailio Branch: master Commit: 611a3ef9078cbcb9867db88921f0c48fce1b URL: https://github.com/kamailio/kamailio/commit/611a3ef9078cbcb9867db88921f0c48fce1b Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date: 2024-07-26T19:50:40+02:00 core: cfg select - che

[sr-dev] Re: [kamailio/kamailio] topos:added get_callid_mask/get_callid_unmask funtion for handeling Refer-To header (PR #3872)

2024-07-26 Thread github-actions[bot] via sr-dev
This PR 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/pull/3872#issuecomment-2253719457 You are receiving this because you are

[sr-dev] Contribute with AUR package

2024-07-26 Thread Nikos Toutountzoglou via sr-dev
Dear Sirs, I have adopted an orphaned AUR package and tried to fine tune it to be used with Your great Kamailio open source project. I can continue to maintain it in the AUR space. If anything needs to be modified in the package please let me know. Link to the package: https://aur.archlinux.org