Re: [SR-Users] Replicate REGISTER and save original received value

This worked out. Thanks again. -dan -Original Message- From: sr-users On Behalf Of Daniel W. Graham Sent: Monday, March 11, 2019 4:53 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Replicate REGISTER and save original received value Ok, that’s why I was asking

Re: [SR-Users] Replicate REGISTER and save original received value

Ok, that’s why I was asking wasn't finding a way to do so. Thanks for the input and I'll see where I can get with the second option. -dan -Original Message- From: sr-users On Behalf Of Alex Balashov Sent: Monday, March 11, 2019 4:48 PM To: Kamailio (SER) - Users Mailing List Subjec

Re: [SR-Users] Replicate REGISTER and save original received value

On Mon, Mar 11, 2019 at 08:46:01PM +, Daniel W. Graham wrote: > No problem. I didn’t consider either option but like the first idea, > how do you recommend overriding the received parameter value? Well, now that I look at the docs, there isn't really a straightforward way short of manipulatin

Re: [SR-Users] Replicate REGISTER and save original received value

No problem. I didn’t consider either option but like the first idea, how do you recommend overriding the received parameter value? -dan -Original Message- From: sr-users On Behalf Of Alex Balashov Sent: Monday, March 11, 2019 4:28 PM To: Kamailio (SER) - Users Mailing List Subject: Re:

Re: [SR-Users] Replicate REGISTER and save original received value

Oh, I’m sorry! I misread your message and was sure you meant “with DMQ”. In that case, if you have complete control over the relay process, why not just append the proximate source IP and port as a custom SIP header before forwarding the registration, then extract it on the other side and store

Re: [SR-Users] Replicate REGISTER and save original received value

Hi, I can confirm dmq_usrloc does replicate received, however I need to do this outside of DMQ. I have a host I need to send specific REGISTERs to so I can't include that host in the DMQ group, as it would receive all usr_loc records. -dan -Original Message- From: sr-users On Behalf Of

Re: [SR-Users] Replicate REGISTER and save original received value

Now that I think about it, I wonder if the issue is that add_rcv_param() won't add the 'received' parameter to the necessary usrloc structures to be passed over DMQ. We don't use add_rcv_param(). We have these options set: modparam("registrar", "received_avp", "$avp(contact_recv)") modparam("reg

Re: [SR-Users] Replicate REGISTER and save original received value

On Mon, Mar 11, 2019 at 04:15:21PM -0400, Alex Balashov wrote: > There's a 50% chance I could be mistaken, but I vaguely remember that > replication of 'received' was an issue in some earlier version of > Kamailio than that. And by "that" I mean 5.1.1. -- Alex Balashov | Principal | Evariste Sy

Re: [SR-Users] Replicate REGISTER and save original received value

Hi Daniel, The 'received' parameter should be replicated. It is in one of our dmq_usrloc rigs, which has four nodes, and registrations can come into any of them. By way of example: [root@gw kamailio]# kamcmd -s /tmp/kamailio_ctl ul.lookup location abalashov@sip.$DOMAIN { AoR: abalashov@

Re: [SR-Users] [sr-dev] Planning next IRC devel meeting

I'm sorry I missed the meeting due to an unexpected event. Cheers, Federico On Mon, Mar 11, 2019 at 5:07 PM Daniel-Constantin Mierla wrote: > Hello, > > meeting still going on. Maybe you can succeed to join, I guess the > freenode has stricter policies for new accounts due to the DDoS they had

[SR-Users] Replicate REGISTER and save original received value

When forwarding / replicating a REGISTER, is it possible (without using DMQ) for the receiving host to save the contact with the original received parameter? REGISTER > server 1 (received set) > forward > server 2 (received not set) add_rcv_param will set received to server 1 IP, but I'm looking

Re: [SR-Users] [sr-dev] Planning next IRC devel meeting

Hello, meeting still going on. Maybe you can succeed to join, I guess the freenode has stricter policies for new accounts due to the DDoS they had a while ago. Cheers, Daniel On 11.03.19 16:50, Julien Chavanton wrote: > Hi, I missed the meeting, it seems like I needed to register my > nickname t

Re: [SR-Users] [sr-dev] Planning next IRC devel meeting

Hi, I missed the meeting, it seems like I needed to register my nickname to connect but I never received the email from NickServ, was not able to identify " NickServ 08:40:53 You are already logged in as jchavanton. Please check your email for instructions to complete your registration. " On Mon

Re: [SR-Users] Planning next IRC devel meeting

Hello, this is a 20min notification before the start of the IRC devel meeting. Cheers, Daniel On 11.03.19 08:25, Daniel-Constantin Mierla wrote: > Hello, > > quick reminder for those that plan to participate: the IRC devel meeting > will be later today, at 15:00UTC, on #kamailio channel from > f

Re: [SR-Users] MSRP module. How to generate a REPORT message

Hello, is the MSRP relay supposed to generate a REPORT request? Or it just forwarding them? At a very quick look, the examples with REPORT show them being generated by endpoints. Cheers, Daniel On 11.03.19 12:16, Nacho Garcia wrote: > Hi all, > > I'm just trying to use Kamailio as an MSRP relay

[SR-Users] Kamailio v5.2.2 Released

Hello, Kamailio SIP Server v5.2.2 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2

[SR-Users] MSRP module. How to generate a REPORT message

Hi all, I'm just trying to use Kamailio as an MSRP relay with MSRP module https://www.kamailio.org/docs/modules/5.1.x/modules/msrp.html. I'm trying to set up https://tools.ietf.org/html/rfc4976#section-6.4.1 and https://tools.ietf.org/html/rfc4976#section-6.4.3 behavior. I was able to read the "F

Re: [SR-Users] ICSCF and SCSCF Problem

Hello, According to the logs, It seems some modules does not load, For I-CSCF and S-CSCF thoes cdp and cdp_avp would be loaded. those modules will be needed in P-CSCF if RX interface is enabled, too With Regards.Mojtaba On Mon, Mar 11, 2019 at 10:32 AM Rust Cohle wrote: > Hello, > > I am trying

Re: [SR-Users] Releasing Kamailio v5.2.2

Thank you for the reply, Daniel. I'll check the IRC logs after work today and cherry-pick in the meantime. -A On Monday, March 11, 2019 2:21:24 AM CDT Daniel-Constantin Mierla wrote: > Hello, > > they look like new features, which we do not backport to stable branches. > Only fixes, improvement

Re: [SR-Users] Releasing Kamailio v5.2.2

I guess you replied to a different email than wanted. Cheers, Daniel On 11.03.19 09:50, Sergey Safarov wrote: > Please create ticket for this issue. > And point to me or Victor Seva. > > Yes, it must be handled via systems tmpfiles. > > пн, 11 мар. 2019 г., 10:24 Daniel-Constantin Mierla

Re: [SR-Users] Releasing Kamailio v5.2.2

Please create ticket for this issue. And point to me or Victor Seva. Yes, it must be handled via systems tmpfiles. пн, 11 мар. 2019 г., 10:24 Daniel-Constantin Mierla : > Hello, > > short notification to remember everyone that today I will package the > version 5.2.2 out of the git branch 5.2, t

Re: [SR-Users] Planning next IRC devel meeting

Hello, quick reminder for those that plan to participate: the IRC devel meeting will be later today, at 15:00UTC, on #kamailio channel from freenode.net. More details at:   * https://www.kamailio.org/wiki/devel/irc-meetings/2019a Cheers, Daniel On 26.02.19 13:28, Daniel-Constantin Mierla wrote:

Re: [SR-Users] Releasing Kamailio v5.2.2

Hello, short notification to remember everyone that today I will package the version 5.2.2 out of the git branch 5.2, therefore any backports to that branch must be announced on sr-dev or irc kamailio channel and wait for ack before pushing to the branch to avoid conflicts with the release build p

Re: [SR-Users] Releasing Kamailio v5.2.2

Hello, they look like new features, which we do not backport to stable branches. Only fixes, improvements to docs and tools (e.g., kamctl) or missing compatibility to kemi scripting (when no major impact) are eligible for backporting. Later today we will have the IRC devel meeting and decide when

Re: [SR-Users] Releasing Kamailio v5.2.2

Hello, check if you have the file: /etc/tmpfiles.d/kamailio.conf There you can update the access rights value to suit better your environment. Cheers, Daniel On 07.03.19 16:40, PICCORO McKAY Lenz wrote: > El jue., 7 de mar. de 2019 a la(s) 09:12, Daniel-Constantin Mierla > (mico...@gmail.com <

[SR-Users] ICSCF and SCSCF Problem

Hello, I am trying to run all CSCF nodes and I managed to run the PCSCF without any issues with the following: kamailio -f /etc/kamailio/pcscf/kamailio.cfg -Ee When I try to do the same with I-CSCF and S-CSCF, I get lots of errors and could not figure out the reason. I included the terminal logs