Re: [SR-Users] kamailio RTP Engine in kubernetes pods

[Pavithra Mohanraja]

Hi,
I am not using free switch.In my case, I am testing with
Ue (vm) -> ims (pods) -> ue (vm)

Here rtp engine is running inside pcscf pod with 2223 as exposed UDP port

When I make a call from ue , rtp packets flow from ue to pcscf pod ip .

Rtp engine is listening to pod ip inside pcscf pod.

How can I resolve this?

Thanks,
Pavithra

On Wed, Oct 21, 2020, 1:19 AM David Villasmil <
david.villasmil.w...@gmail.com> wrote:

> I have it running perfectly in network host mode. Public to private and
> private to public. My freeswitches are in the private and
> kamailio+rtpengine do the translation from public to private (and
> viceversa). All in k8s pods.
>
> When fs or rtpengine a come up in the pods, they register themselves in
> kamailio’s db tables rtpengine and dispatcher with their private IPs.
>
>
> On Tue, 20 Oct 2020 at 15:43, Sergey Safarov  wrote:
>
>> UDP in k8s not stable.
>> So looks as need use host network.
>>
>> Second options troubleshoot nat in k8s.
>>
>> Thirt options, add RTP engine control over TCP in Kamailio.
>>
>> On Tue, Oct 20, 2020, 5:22 PM Pavithra Mohanraja 
>> wrote:
>>
>>> Hi,
>>> I have installed rtp engine inside pcscf pod and tried to make a call.
>>> caller was unable to reach the pod environment with 2223 port exposed for
>>> rtp. Kindly anyone help, if you have already done with pod based deployment
>>> of ims.
>>>
>>>
>>> Thanks,
>>> Pavithra
>>>
>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>> --
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio RTP Engine in kubernetes pods

[David Villasmil]

I have it running perfectly in network host mode. Public to private and
private to public. My freeswitches are in the private and
kamailio+rtpengine do the translation from public to private (and
viceversa). All in k8s pods.

When fs or rtpengine a come up in the pods, they register themselves in
kamailio’s db tables rtpengine and dispatcher with their private IPs.


On Tue, 20 Oct 2020 at 15:43, Sergey Safarov  wrote:

> UDP in k8s not stable.
> So looks as need use host network.
>
> Second options troubleshoot nat in k8s.
>
> Thirt options, add RTP engine control over TCP in Kamailio.
>
> On Tue, Oct 20, 2020, 5:22 PM Pavithra Mohanraja 
> wrote:
>
>> Hi,
>> I have installed rtp engine inside pcscf pod and tried to make a call.
>> caller was unable to reach the pod environment with 2223 port exposed for
>> rtp. Kindly anyone help, if you have already done with pod based deployment
>> of ims.
>>
>>
>> Thanks,
>> Pavithra
>>
> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> --
Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ERROR: [core/socket_info.c:2225]: parse_protohostport():

[Andy Kama]

Thanks!!

On Tue, Oct 20, 2020 at 6:18 PM Ovidiu Sas  wrote:

> It could be! It is for anything that is using proto:ip:port format.
> It is used by "listen" and by "alias".
> Also, there are some module params that require this format.
>
> -ovidiu
>
> On Tue, Oct 20, 2020 at 12:24 PM Andy Kama  wrote:
> >
> > Is this for listen:
> >
> > ?
> >
> > On Tuesday, October 20, 2020, Ovidiu Sas  wrote:
> >>
> >> You should use yourproto:yourip:yourport
> >> yourproto could be udp|tcp|tls
> >>
> >> -ovidiu
> >>
> >> On Tue, Oct 20, 2020 at 12:07 PM Andy Kama 
> wrote:
> >> >
> >> > I am seeing this error in the logs
> >> >
> >> > i am using kamailio 5.4.1
> >> > any idea what the cause is?
> >> >
> >> >
> >> > ERROR:  [core/socket_info.c:2225]: parse_protohostport(): bad
> protocol in sip:myp:5060
> >> > ___
> >> > Kamailio (SER) - Users Mailing List
> >> > sr-users@lists.kamailio.org
> >> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> >>
> >>
> >>
> >> --
> >> VoIP Embedded, Inc.
> >> http://www.voipembedded.com
> >>
> >> ___
> >> Kamailio (SER) - Users Mailing List
> >> sr-users@lists.kamailio.org
> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> >
> > ___
> > Kamailio (SER) - Users Mailing List
> > sr-users@lists.kamailio.org
> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ERROR: [core/socket_info.c:2225]: parse_protohostport():

[Ovidiu Sas]

It could be! It is for anything that is using proto:ip:port format.
It is used by "listen" and by "alias".
Also, there are some module params that require this format.

-ovidiu

On Tue, Oct 20, 2020 at 12:24 PM Andy Kama  wrote:
>
> Is this for listen:
>
> ?
>
> On Tuesday, October 20, 2020, Ovidiu Sas  wrote:
>>
>> You should use yourproto:yourip:yourport
>> yourproto could be udp|tcp|tls
>>
>> -ovidiu
>>
>> On Tue, Oct 20, 2020 at 12:07 PM Andy Kama  wrote:
>> >
>> > I am seeing this error in the logs
>> >
>> > i am using kamailio 5.4.1
>> > any idea what the cause is?
>> >
>> >
>> > ERROR:  [core/socket_info.c:2225]: parse_protohostport(): bad 
>> > protocol in sip:myp:5060
>> > ___
>> > Kamailio (SER) - Users Mailing List
>> > sr-users@lists.kamailio.org
>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>> --
>> VoIP Embedded, Inc.
>> http://www.voipembedded.com
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ERROR: [core/socket_info.c:2225]: parse_protohostport():

[Andy Kama]

Is this for listen:

?

On Tuesday, October 20, 2020, Ovidiu Sas  wrote:

> You should use yourproto:yourip:yourport
> yourproto could be udp|tcp|tls
>
> -ovidiu
>
> On Tue, Oct 20, 2020 at 12:07 PM Andy Kama  wrote:
> >
> > I am seeing this error in the logs
> >
> > i am using kamailio 5.4.1
> > any idea what the cause is?
> >
> >
> > ERROR:  [core/socket_info.c:2225]: parse_protohostport(): bad
> protocol in sip:myp:5060
> > ___
> > Kamailio (SER) - Users Mailing List
> > sr-users@lists.kamailio.org
> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ERROR: [core/socket_info.c:2225]: parse_protohostport():

[Ovidiu Sas]

You should use yourproto:yourip:yourport
yourproto could be udp|tcp|tls

-ovidiu

On Tue, Oct 20, 2020 at 12:07 PM Andy Kama  wrote:
>
> I am seeing this error in the logs
>
> i am using kamailio 5.4.1
> any idea what the cause is?
>
>
> ERROR:  [core/socket_info.c:2225]: parse_protohostport(): bad protocol 
> in sip:myp:5060
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Load balance on HA scenario

[Joel Serrano]

Yes. I do exactly this but with an extra step:

1.  I have the default Kamailio dispatcher pings disabled.

2. I have the Kamailio init route check if we have the floating IP locally,
if we do in startup that route will run the rpc cmd to enable pings.

3. On floating IP switchover, keepalived (or whatever) tells Kamailio also
to enable pings.


This way, you only have pings from the active node, and you don’t have
warnings in the passive node. (and yes, I also set the socket to the
floating IP in the dispatcher records).

Cheers,
Joel.





On Tue, Oct 20, 2020 at 03:40 Yufei Tao  wrote:

> Hi Duarte,
>
> Not sure if I understand it correctly but are you trying to set up an HA
> pair of dispatchers?
>
> If so I am doing it differently in that, I use the Virtual/floating IP
> (VIP) as socket. This way the master node (which has got the VIP) can send
> OPTIONs pings out fine but the backup node won't be able to send.
> Functionally it is fine, but the backup node keeps logging errors because
> it doesn't have the VIP:
>
> ERROR:  [core/udp_server.c:599]: udp_send(): sendto(sock, buf: 
> 0x7f0e6b54e2e0, len: 372, 0, dst: (192.168.213.143:5060), tolen: 16) - err: 
> Network is unreachable (101)
> ERROR: tm [../../core/forward.h:231]: msg_send_buffer(): udp_send failed
>
> When FO happens, the backup node becomes master and takes the VIP, and it
> functions correctly. But I haven't worked out how to avoid the ERROR
> loggings on the backup node. Maybe someone else has any better
> ideas/suggestions?
>
> Cheers,
> Yufei
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] kamailio RTP Engine in kubernetes pods

[Pavithra Mohanraja]

Hi,
I have installed rtp engine inside pcscf pod and tried to make a call.
caller was unable to reach the pod environment with 2223 port exposed for
rtp. Kindly anyone help, if you have already done with pod based deployment
of ims.


Thanks,
Pavithra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] about registrar save()/lookup()

[Juha Heinanen]

Added note about branch flags in registrar readme:

https://github.com/kamailio/kamailio/commit/f2996bf733a0b5e00fe124440353b9a69a3532a2

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] No retry on INVITE

[Allan Kristensen]

Hello,

Okay, so I just found out retransmissions are actually working fine, but
siptrace doesn't send them to the trace server, only initial invite is sent.

My bad, thanks for the help.
/Allan



On Mon, Oct 19, 2020 at 7:19 PM Henning Westerholt  wrote:

> Hello,
>
>
>
> not sure if I understand it correctly, If you are t_relay() the INVITE to
> the new destination Kamailio should take care of the re-transmits of the
> INVITE automatically until it receives a provisional reply or fr_timer.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* sr-users  *On Behalf Of *Allan
> Kristensen
> *Sent:* Monday, October 19, 2020 2:02 PM
> *To:* mico...@gmail.com
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] No retry on INVITE
>
>
>
> Hello Daniel,
>
> Okay, so I had a look at the config and we do use the t_relay() for
> customer facing proxy, so I was mistaken.
>
>
>
> So I guess it's okay to reply 100 and then let kamailio handle the retry.
> Question is, how do I get it to resend INVITE when there is no response to
> the INVITE after a few seconds?
>
> Is it a TM parameter or should I do it in the config script?
>
>
>
> Thank you...
>
> /Allan
>
>
>
> On Mon, Oct 19, 2020 at 1:28 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
> Hello,
>
> if kamailio is stateless (ie., you do not use tm module, but forward() for
> sending out requests), then it will not do any retransmission and it is not
> sending 408 itself (likely received from downstream).
>
> With a stateless Kamailio, you should not send out 100 trying, but let
> upstream do retransmission if it is the case.
>
> Cheers,
> Daniel
>
> On 19.10.20 11:34, Allan Kristensen wrote:
>
> Hello,
>
>
>
> I'm trying to get Kamailio to retry INVITE.
>
>
> We have a Freeswitch which is sending INVITE to a sip user via Kamailio
> proxy using static ip/location.
>
> All is well, calls are flowing, but sometimes INVITE from kamailio to user
> is lost and no attempt to retry is occurring and so after 30 sec kamailio
> just returns 408 Request timeout.
>
>
>
> Call flow is like this:
>
>
>
> FS   Kamailio  User
>
> --- INVITE -->
>
> <-- 100 Trying
>
> --- INVITE --->
>
>   (Waiting 30 secs)
>
> <-- 408 Timeout
>
> --- ACK --->
>
>
>
> So assume we have failed in handling retries somehow. Kamailio is running
> stateless, but other retries are working, so I assume this is not a problem?
>
>
>
> Can someone perhaps point us in the right direction on where to solve this?
>
>
>
> Kamailio is version 5.2.4
>
> Thank you...
>
> /Allan
>
>
>
>
>
> ___
>
> Kamailio (SER) - Users Mailing List
>
> sr-users@lists.kamailio.org
>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
>
> Daniel-Constantin Mierla -- www.asipto.com
>
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>
> Funding: https://www.paypal.me/dcmierla
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Load balance on HA scenario

[Yufei Tao]

Hi Duarte,

Not sure if I understand it correctly but are you trying to set up an HA
pair of dispatchers?

If so I am doing it differently in that, I use the Virtual/floating IP
(VIP) as socket. This way the master node (which has got the VIP) can send
OPTIONs pings out fine but the backup node won't be able to send.
Functionally it is fine, but the backup node keeps logging errors because
it doesn't have the VIP:

ERROR:  [core/udp_server.c:599]: udp_send(): sendto(sock, buf:
0x7f0e6b54e2e0, len: 372, 0, dst: (192.168.213.143:5060), tolen: 16) -
err: Network is unreachable (101)
ERROR: tm [../../core/forward.h:231]: msg_send_buffer(): udp_send failed

When FO happens, the backup node becomes master and takes the VIP, and it
functions correctly. But I haven't worked out how to avoid the ERROR
loggings on the backup node. Maybe someone else has any better
ideas/suggestions?

Cheers,
Yufei
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] about registrar save()/lookup()

[Juha Heinanen]

I didn't find any mention in registrar module README that save()
function saves also branch flags and that lookup() retrieves them.

Is that documented somewhere?

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] SRTP

[Yufei Tao]

Hi,

Like Olle said RTPEngine is perfectly capable of handling one leg in RTP
the other in SRTP. When looking up RTPEngine's documentation, may be worth
checking these out:
SRTP
SDES-unencrypted_srtp
SDES-unencrypted_srtcp
SDES-unauthenticated_srtp
e.g. try apply these flags to rtpengin_offer() on the incoming RTP leg, to
get RTPEngine to add encryption to the outgoing leg etc.

Cheers,
Yufei
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 5.2.5 - Need help with rtpengine error

[Yufei Tao]

Hi Andrew,
Like Alex said, have a look at the commands RTPEngine received and the
responses it sent in the history of the call, and see if RTPEngine has ever
received any commands regarding this call, or, if the call has been deleted
from RTPEngine. You can raise the RTPEngine logging level to 6 for example
so you can see the command/responses of RTPEngine.

Cheers,
Yufei
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] about registrar save()/lookup()

[Daniel-Constantin Mierla]

If one wants to create an issue and assign it to himself/herself to
track it over time, that's fine. But creating an issue and let others
deal with it in this case doesn't seem suitable, because the one that is
supposed to create the issue knows better what was found missing and how
it should be there from his point of view.

Cheers,
Daniel

On 20.10.20 09:14, Olle E. Johansson wrote:
>
>
>> On 20 Oct 2020, at 09:12, Daniel-Constantin Mierla > > wrote:
>>
>> The functions are in corex module:
>>
>>   -
>> https://www.kamailio.org/docs/modules/stable/modules/kex.html#kex.f.setbflag
>>
> Thanks, I missed that.
>>
>> Enhancements to the documentation is welcome always. Given that
>> people here have commit access, is there no reason to open an issue
>> about this one, just add to the docs what is considered to be good to
>> have there.
>>
>>
>
> Well, sometimes having an issue makes it easier to remember to fix it
> when you can’t attack the problem right away. :-)
>
> /O
>
>>
>>
>> Cheers,
>> Daniel
>>
>> On 20.10.20 09:02, Olle E. Johansson wrote:
>>> It is mentioned
>>> here https://kamailio.org/dokuwiki/doku.php/utils:flags
>>> 
>>>
>>> But you are right, it is something that should exist in both
>>> registrar and usrloc
>>> documentation.
>>>
>>> The functions for managing them seems to be missing from the core
>>> cookbook too.
>>>
>>> Please open an issue on this.
>>>
>>> Thanks.
>>>
>>> /O
>>>
 On 20 Oct 2020, at 07:45, Juha Heinanen >>> > wrote:

 I didn't find any mention in registrar module README that save()
 function saves also branch flags and that lookup() retrieves them.

 Is that documented somewhere?

 -- Juha

 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org 
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> -- 
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Funding: https://www.paypal.me/dcmierla
>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dialog_active_dialogs erroneous value

[Daniel-Constantin Mierla]

Unfortunately the design of the dialog statistics, which are basically
just counters, do not allow dealing easy with retransmissions or
duplicate operations that can happen with dmq. That was the reason to
add the rpc command to scan what the dialog module has internally.
Probably the dialog statistics should be diabled when dmq is enabled or
switched to use function callbacks behind and to the scanning mechanism
as well, but some of them won't be possible with callbacks without
refactoring.

Cheers,
Daniel

On 20.10.20 02:28, Sergiu Pojoga wrote:
> Sorry to insist but... looks like it's not just the active_dialogs
> stats that's messed up. Early_dialogs are also often erroneous and the
> dialog counters don't match against different RPCs.
>
> What would the devs like me to do with this: drop it, open another
> GitHub issue? 
>  
> # kamcmd dlg.stats_active && kamcmd stats.get_statistics all | grep dialog
> {
>  starting: 0
>  connecting: 0
>  answering: 0
>  ongoing: 2
>  all: 2
> }
> dialog:active_dialogs = 20
> dialog:early_dialogs = 18446744073709551614
> dialog:expired_dialogs = 0
> dialog:failed_dialogs = 6978
> dialog:processed_dialogs = 11248
>
> # kamcmd dmq.list_nodes
> {
>  host: 65.xx.xx.11
>  port: 5062
>  resolved_ip: 65.xx.xx.11
>  status: active
>  last_notification: 0
>  local: 0
> }
> {
>  host: 65.xx.xx.22
>  port: 5062
>  resolved_ip: 65.xx.xx.22
>  status: active
>  last_notification: 0
>  local: 1
> }
>
> # kamailio -v
> version: kamailio 5.3.4 (x86_64/linux) fc28a1
>
> Thanks.
> --Sergiu
>
> On Fri, Oct 16, 2020 at 5:10 PM Sergiu Pojoga  > wrote:
>
> Hi Joel,
>
> Thanks, that's precisely it! 
>
> Indeed, `dlg.stats_active` works correctly and what's nice about
> it is that it shows stats summary from all DMQ nodes combined.
> However, I use xHTTP_PROM module to export my stats, which seems
> to rely on the 'problematic' counters. Sad... Let's hope this gets
> resolved one day.
>
> Regards,
> --Sergiu 
>
> On Fri, Oct 16, 2020 at 4:17 PM Joel Serrano  > wrote:
>
> Hey Sergiu, 
>
> I think I've been through a similar case... have a look
> at: https://github.com/kamailio/kamailio/issues/1591
>  in case you
> find it helpful.
>
> You might have to rely on the different metric that Daniel added.
>
> Joel.
>
>
>
> On Fri, Oct 16, 2020 at 3:35 AM Sergiu Pojoga
> mailto:pojo...@gmail.com>> wrote:
>
> Hi Daniel,
>
> You guessed right, two dmq nodes with dialog replication. 
>
> Thanks,
>
>
> On Fri., Oct. 16, 2020, 2:15 a.m. Daniel-Constantin
> Mierla, mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> is this happening when using dmq for dialog with
> multiple sip servers? Or is a single instance sip server?
>
> Cheers,
> Daniel
>
> On 16.10.20 04:12, Sergiu Pojoga wrote:
>> Hi there,
>>
>> Every now and then, the value of active dialogs
>> metric spikes to an erroneous huge number, messing up
>> my otherwise beautiful grafana gauges :(
>>
>> Example:
>> kamailio_dialog_active_dialogs 18446744073709551614
>> 1602812239115
>> kamailio_dialog_early_dialogs 0 1602812239115
>> kamailio_dialog_expired_dialogs 2 1602812239115
>> kamailio_dialog_failed_dialogs 7361 1602812239115
>>
>> Anybody faced the same symptoms, any clues what might
>> be causing this?
>>
>> Thanks,
>> --Sergiu
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org 
>> 
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users 
>> 
>
> -- 
> Daniel-Constantin Mierla -- www.asipto.com 
> 
> www.twitter.com/miconda  -- 
> www.linkedin.com/in/miconda 
> Funding: https://www.paypal.me/dcmierla 
> 
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
>
> ___
> Kamailio 

Re: [SR-Users] about registrar save()/lookup()

[Olle E. Johansson]

> On 20 Oct 2020, at 09:12, Daniel-Constantin Mierla  wrote:
> 
> The functions are in corex module:
> 
>   - 
> https://www.kamailio.org/docs/modules/stable/modules/kex.html#kex.f.setbflag 
> Thanks,
>  I missed that.
> Enhancements to the documentation is welcome always. Given that people here 
> have commit access, is there no reason to open an issue about this one, just 
> add to the docs what is considered to be good to have there.
> 
> 

Well, sometimes having an issue makes it easier to remember to fix it when you 
can’t attack the problem right away. :-)

/O

> 
> 
> Cheers,
> Daniel
> 
> On 20.10.20 09:02, Olle E. Johansson wrote:
>> It is mentioned here https://kamailio.org/dokuwiki/doku.php/utils:flags 
>> 
>> 
>> But you are right, it is something that should exist in both registrar and 
>> usrloc
>> documentation.
>> 
>> The functions for managing them seems to be missing from the core cookbook 
>> too.
>> 
>> Please open an issue on this.
>> 
>> Thanks.
>> 
>> /O
>> 
>>> On 20 Oct 2020, at 07:45, Juha Heinanen >> > wrote:
>>> 
>>> I didn't find any mention in registrar module README that save()
>>> function saves also branch flags and that lookup() retrieves them.
>>> 
>>> Is that documented somewhere?
>>> 
>>> -- Juha
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org 
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users 
>>> 
>> 
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org 
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users 
>> 
> -- 
> Daniel-Constantin Mierla -- www.asipto.com 
> www.twitter.com/miconda  -- 
> www.linkedin.com/in/miconda 
> Funding: https://www.paypal.me/dcmierla 
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] about registrar save()/lookup()

[Daniel-Constantin Mierla]

The functions are in corex module:

  -
https://www.kamailio.org/docs/modules/stable/modules/kex.html#kex.f.setbflag

Enhancements to the documentation is welcome always. Given that people
here have commit access, is there no reason to open an issue about this
one, just add to the docs what is considered to be good to have there.

Cheers,
Daniel

On 20.10.20 09:02, Olle E. Johansson wrote:
> It is mentioned
> here https://kamailio.org/dokuwiki/doku.php/utils:flags
> 
>
> But you are right, it is something that should exist in both registrar
> and usrloc
> documentation.
>
> The functions for managing them seems to be missing from the core
> cookbook too.
>
> Please open an issue on this.
>
> Thanks.
>
> /O
>
>> On 20 Oct 2020, at 07:45, Juha Heinanen > > wrote:
>>
>> I didn't find any mention in registrar module README that save()
>> function saves also branch flags and that lookup() retrieves them.
>>
>> Is that documented somewhere?
>>
>> -- Juha
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org 
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] about registrar save()/lookup()

[Olle E. Johansson]

It is mentioned here https://kamailio.org/dokuwiki/doku.php/utils:flags 


But you are right, it is something that should exist in both registrar and 
usrloc
documentation.

The functions for managing them seems to be missing from the core cookbook too.

Please open an issue on this.

Thanks.

/O

> On 20 Oct 2020, at 07:45, Juha Heinanen  wrote:
> 
> I didn't find any mention in registrar module README that save()
> function saves also branch flags and that lookup() retrieves them.
> 
> Is that documented somewhere?
> 
> -- Juha
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users