[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Chaigneau, Nicolas via sr-users
--- 2024-01-12 15:11:42.763400 UDP message sent (314 bytes): INVITE sip:+18080678901@10.118.21.108:5061 SIP/2.0 Via: SIP/2.0/UDP 10.118.21.108:5060;branch=z9hG4bK-268285-1-0 From: ;tag=1 To: Call-ID: test_sip.20240112-151142.268284.1///1-268285@10.118.21.108 Cseq: 1

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Alex Balashov via sr-users
Yes, but one wonders why this would be necessary, given that there is no relay operation to consume the R-URI? > On 12 Jan 2024, at 09:43, Ben Kaufman via sr-users > wrote: > > I think you can remove the warning simply by "touching" the ruri: > > $ru = $ru; > > > > -Original Message---

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Chaigneau, Nicolas via sr-users
Hello Ben, Thanks for the idea ! I tried that, the WARNING message is no longer logged. However, the SIP 302 response is changed. Kamailio will build an additional Contact header, using the Request-URI. That's not good :/ -Message d'origine- De : Ben Kaufman Envoyé : vendredi 12 j

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Chaigneau, Nicolas via sr-users
From the code: In function sl_reply_helper (sl_funcs.c): /* if that is a redirection message, dump current message set to it */ if(code >= 300 && code < 400) { dset.s = print_dset(msg, &dset.len, sl_rich_redirect); if(dset.s) {

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Ben Kaufman via sr-users
I think you can remove the warning simply by "touching" the ruri: $ru = $ru; -Original Message- From: Chaigneau, Nicolas via sr-users Sent: Friday, January 12, 2024 8:26 AM To: Kamailio (SER) - Users Mailing List Cc: Chaigneau, Nicolas Subject: [SR-Users] Re: Using http_async_query -

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Alex Balashov via sr-users
That's a little puzzling. Could you post the incoming invite, and perhaps the entire configuration? — Sent from mobile, apologies for brevity and errors. > On Jan 12, 2024, at 9:26 AM, Chaigneau, Nicolas > wrote: > > Thanks for the clarification. So "branches" is not what I need. > > So I s

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Chaigneau, Nicolas via sr-users
Thanks for the clarification. So "branches" is not what I need. So I should do something like that: append_to_reply("Contact: <...>\r\n"); sl_send_reply("302", "Moved Temporarily"); exit; (I do have an "exit" immediately after all calls to "sl_send_reply") I tried with a minimalist request_rou

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Igor Potjevlesch via sr-users
You're right, sorry: kamcmd dns.add_srv _sip._udp.example.com 3600 0 50 5060 srv1.com 2 kamcmd dns.add_srv _sip._udp.example.com 3600 0 50 5060 srv2.com 2 kamcmd dns.add_a srv1.com 3600 192.168.1.1 2 kamcmd dns.add_a srv2.com 3600 192.168.1.2 2 Finally, it looks to work fine by adding: dns_

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Sergiu Pojoga via sr-users
Just so ppl you're asking don't lose their minds either trying to be clairvoyants of your particular setup, can you post what records exactly were added and what makes you think they are not followed by Kam when selecting a destination? So you add records with *dns.add* and then lookup them up wit

[SR-Users] Re: xavp_params_explode broken comma in value?

2024-01-12 Thread Daniel-Constantin Mierla via sr-users
Hello, On 12.01.24 11:56, Benoît Panizzon wrote: > Hi Daniel > >> comma is not allowed in an unquoted value for SIP parameters because >> it is separator for header bodies that are set on the same header >> name. Practically the comma is the end of parameters list. > Thank you for your confirmat

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Igor Potjevlesch via sr-users
Hello, Just to be sure that I'm not losing my time: is there any chance to do a load-balancing using add_srv? I just tried with two equal entries but it's always the same which is returned. Regards, Igor. De : Daniel-Constantin Mierla Envoyé : vendredi 12 janvier 2024 11:17 À : Igor

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Alex Balashov via sr-users
Hi Nicolas, Yes, I think that unfortunately this is the outcome of some confusion. Apart from the word "append", there is nothing in common between the concepts of append_branch() and append_to_reply(). I'm not sure why you are getting the messages you are just sending redirects, but the prime

[SR-Users] Re: xavp_params_explode broken comma in value?

2024-01-12 Thread Alex Balashov via sr-users
I used base64 encoding transformations to deal with these kinds of problems. — Sent from mobile, apologies for brevity and errors. > On Jan 12, 2024, at 6:11 AM, Benoît Panizzon via sr-users > wrote: > > Hi Daniel > >> comma is not allowed in an unquoted value for SIP parameters because >> i

[SR-Users] Re: xavp_params_explode broken comma in value?

2024-01-12 Thread Benoît Panizzon via sr-users
Hi Daniel > comma is not allowed in an unquoted value for SIP parameters because > it is separator for header bodies that are set on the same header > name. Practically the comma is the end of parameters list. Thank you for your confirmation I was on the right track. > It should work with: > >

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Igor Potjevlesch via sr-users
Hello, Wonderful! Thank you Daniel. Regards, Igor. De : Daniel-Constantin Mierla Envoyé : vendredi 12 janvier 2024 11:17 À : Igor Potjevlesch ; 'Kamailio (SER) - Users Mailing List' Objet : Re: [SR-Users] Internal DNS resolver Hello, the core rpc lack proper documentation, not li

[SR-Users] Re: xavp_params_explode broken comma in value?

2024-01-12 Thread Daniel-Constantin Mierla via sr-users
Hello, On 12.01.24 11:01, Benoît Panizzon via sr-users wrote: > Hey! > > I'm hunting down an issue with xavp_params_explode, maybe somebody has > already come adross it and could confirm it exists and maybe know a > solution? > > xavp_params_explode("a=foo;c=hello,world;e=baar", "x"); > > $xavp(x=

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Daniel-Constantin Mierla via sr-users
Hello, the core rpc lack proper documentation, not like the case of modules. In this case, the code should be suggestive of what parameters have to be provided:   - https://github.com/kamailio/kamailio/blob/master/src/core/dns_cache.c#L4744 For each of those values, the corex docs for dns_cache

[SR-Users] Re: Internal DNS resolver

2024-01-12 Thread Igor Potjevlesch via sr-users
Hello Daniel, Thanks! I wll try. I didn't find out how to use dns.add_a. Is someone has the exact params lists? Thank you. Regards, Igor. De : Daniel-Constantin Mierla Envoyé : jeudi 11 janvier 2024 19:36 À : Kamailio (SER) - Users Mailing List Cc : Igor Potjevlesch Objet : Re: [SR-

[SR-Users] xavp_params_explode broken comma in value?

2024-01-12 Thread Benoît Panizzon via sr-users
Hey! I'm hunting down an issue with xavp_params_explode, maybe somebody has already come adross it and could confirm it exists and maybe know a solution? xavp_params_explode("a=foo;c=hello,world;e=baar", "x"); $xavp(x=>a) is 'foo' but x=>c and x=>e are null Am I right to assume the issue being

[SR-Users] Re: registrar questions

2024-01-12 Thread mm e via sr-users
Cheers, it worked __ 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 mailin

[SR-Users] Re: registrar questions

2024-01-12 Thread mm e via sr-users
After using sqlops to modify the "subscriber" table, how to refresh the configuration to take effect? __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: k

[SR-Users] Re: registrar questions

2024-01-12 Thread Daniel-Constantin Mierla via sr-users
On 12.01.24 09:48, mm e via sr-users wrote: > In addition to the RPC command "kamctl add username password", is there a > module with a method to operate the "subscriber" database table? You can "operate" any sql database table with sqlops module. Cheers, Daniel -- Daniel-Constantin Mierla (@

[SR-Users] Re: registrar questions

2024-01-12 Thread mm e via sr-users
Sorry, this is a shell script. Is it possible to add username in the module method? __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing li

[SR-Users] registrar questions

2024-01-12 Thread mm e via sr-users
In addition to the RPC command "kamctl add username password", is there a module with a method to operate the "subscriber" database table? __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-

[SR-Users] Re: Using http_async_query - transaction seems "reused" for subsequent SIP INVITE requests received ? (Kamailio 5.7.3)

2024-01-12 Thread Chaigneau, Nicolas via sr-users
Hello Alex, The confusion is probably on my part. Reading this: https://kamailio.org/docs/modules/devel/modules/sl.html#sl.f.sl_send_reply 3.1. sl_send_reply(code, reason) For the current request, a reply is sent back having the given code and text reason. The reply is sent s