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

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.

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

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

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

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

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

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,

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

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 > >

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

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():

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

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

[SR-Users] kamailio RTP Engine in kubernetes pods

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

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

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

Re: [SR-Users] No retry on INVITE

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

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

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

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

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

Re: [SR-Users] SRTP

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

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

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

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

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

Re: [SR-Users] dialog_active_dialogs erroneous value

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

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

> 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.

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

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

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

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