Hello,
I noticed that , with kamailio ver. 5.2.1 starting with empty rtpengine
table causes strange messages in kamailio and it doesn't start
modparam("rtpengine", "db_url", "text:///tmp/kamailio/dbtext")
cat /tmp/kamailio/dbtext/rtpengine id(int,auto) setid(int) url(string)
weight(int) disabled
Hello, going back to 5.2.0 is actually not possible anymore if you didn't
save locally the distro packages because right now on the repos only
Kamailio 5.2.1 is available
Il giorno gio 31 gen 2019 alle ore 13:13 * Paolo Visintin - evosip.cloud
ha scritto:
> Hello,
>
> I noticed that , with kamai
On Fri, Feb 01, 2019 at 05:44:45PM +0100, Enrico Bandiera wrote:
> Hello, going back to 5.2.0 is actually not possible anymore if you didn't
> save locally the distro packages because right now on the repos only
> Kamailio 5.2.1 is available
I made the same conclusion with an upgrade to 5.1.6 from
Hi there,
Is in my TODO list to integrate aptly into our deb build environment.
https://github.com/sipwise/kamailio-deb-jenkins/issues/9
On Mon, 4 Feb 2019 at 11:09, Daniel Tryba wrote:
> But maybe the maintainer can keep older versions?
>
If you really need them, jenkins keeps the artifacts,
On Mon, Feb 04, 2019 at 01:33:32PM +0100, Victor Seva wrote:
> Hi there,
>
> Is in my TODO list to integrate aptly into our deb build environment.
> https://github.com/sipwise/kamailio-deb-jenkins/issues/9
Okay, good to know that others see this as a "problem". I'll wait
patiently for this enhanc
good to know for the future implementation and super for the artifacts!
Anyone else experienced the bug regarding a empty rtpengine table causing
non kamailio starting ?
Many thanks
Il giorno lun 4 feb 2019 alle ore 17:22 Daniel Tryba ha
scritto:
> On Mon, Feb 04, 2019 at 01:33:32PM +0100,
I noticed it as well when switching from 5.2.0 to 5.2.1 using the docker
images, but got around it by adding a row with localhost as the
destination. Kamailio did start but wasnt able to connect, which was fine.
On Mon, 4 Feb 2019 at 18:22, * Paolo Visintin - evosip.cloud
wrote:
> good to know f
Hello Grant,
Can you elaborate more on your solution?
Thanks!
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Tue, Feb 5, 2019 at 7:05 AM Grant Bagdasarian
wrote:
> I noticed it as well when switching from 5.2.0 to 5.2.1 using the docker
> images, but go
