Hello,
hopefully the devel version is now more stabilized after the freezing,
the new components being adjusted enough not to need many more changes.
Therefore I consider to branch 5.8 out of devel version next week on
Friday, February 23, 2024, sometime around noon UTC.
After that the master
We have recently upgraded from 5.6.4 to 5.7.4.
No change in the KAMAILIO configuration.
On all upgraded servers we are now getting this message in the logs for
every destination when the dispatcher sends out OPTIONS to destinations
listed in the dispatcher list:
WARNING:
Thanks Karsten,
That won’t work for me with TLS clients, which is what I’m trying to do.
I’m making a PR with a new tcp param.
Thanks!
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Thu, 15 Feb 2024 at 17:42, Karsten Horsmann wrote:
> Hi David,
>
> I
I don't think you can send a REGISTER immediately, like literally the same
moment, with any of the RPC commands.
There's a Kamailio UAC REG timer that processes records at certain
intervals like reg_timer_interval() modparam. It also depends on
reg_random_delay() and/or per uuid reg_delay values.
Once Again, Thank you very much.
I'll try to dig a little more before making more "stupid" questions! :)
Cheers,
David
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to
Hi David,
I have most of my setups with OPTIONS pings (upstream carrier and myself).
If I want to fade out a Kamailio I set the option response to an not 200
value (like 603 or whatever) and my internal and the external system didn't
bring in new invites but leave the currently running out.
You
Hi George,
if you think it's a issue please fill a bug report on Github to let the
Devs investigate. Also the questions in the form ask for all what they
need.
Thank you
George Diamantopoulos via sr-users schrieb am
Do., 15. Feb. 2024, 16:06:
> Update: I have just downgraded to 5.6.4 using
>
Hi List,
I would like to know if it's possible in my kamailio script
to force an immediate REGISTER for an existing entry using l_uuid
If I'm correct, uac_reg_refresh(luuid)is an API to reload into the database
but doesn't send a REGISTER immediately.
Is there an existing API available from
Hello,
you can find the tables and their mapping to the modules e.g. here:
https://kamailio.org/docs/db-tables/kamailio-db-5.6.x.html
The subscriber table is usually used for authentication purposes in kamailio.
Cheers,
Henning
> -Original Message-
> From: djcsalvador--- via sr-users
Hi Henning,
Thanks a lot for your reply, and for the time spent.
I'm currently following the tutorial and trying to install Kamailio on our
local environment, and I've faced with another question.
For what i can see, there is a subscriber table, which stores user information.
If we want
Update: I have just downgraded to 5.6.4 using
https://deb-archive.kamailio.org/repos/kamailio-5.6.4
I have confirmed that topos works correctly with this version, so the
commit that broke things happened between 5.6.4 and 5.6.5
It might be related to how multi-homed installations interact with
Hi,
check out open5gs as MME or PGW. Regarding ePDG, there is activity in the
osmocom Project, maybe you can put these
two projects together: https://osmocom.org/projects/osmo-epdg, Otherwise
there are references in strongswan for ePDG,
but i did not hat the time to play around.,
Markus
On Thu,
Hello all,
I've noticed that there seems to be a regression with the topos module,
more specifically the redis flavour, but I'm assuming the storage backend
shouldn't make a difference.
I have confirmed this affects both 5.6.5 and 5.7-nightly, so I'm assuming
some backported commit is to blame.
Hi Carsten,
thank you very much for your fast reply!
Good to know that from IMS point of view it is fairly simple, but as far as
I know it is more complex for MME, PGW and ePDG.
May you know any Open Source Mobile Core which is supporting VoLTE <->
VoWiFi HO with Kamailio?
Unfortunately, I am
Hello,
regarding your questions:
1. Besides from the Kamailio core, you only need to use the modules that are
actually necessary for your configuration. There are over 220 modules, so they
are of course not always used.
2. Can't comment with too much detail here, but generally speaking,
Hi,
The handover between VoWifi and VoLTE is fairly simple, as it has little to
do with IMS.
Technically speaking, the data session is migrated from the PGW (LTE) to
the ePDG (Wifi), using GTP on the S2b interface. The device keeps it's IP
address and the the handover is fully transparent to the
Hi all,
While researching for Open Source IMS Services I’v found the presentation
“What’s up with IMS & VoLTE?” at KamailioWorld 2018.
There is a quote that raises a question:
“Things, you shouldn’t expect (at least initially):
● Seamless handover between LTE and Wifi, as this requires some
17 matches
Mail list logo
