Hello Sergey!
I did a yum clean all, the rm -Rf /var/cache/yum/* and still the problem
persist.
Now I noticed the modified date of the packages was updated, but anyway,
there is something wrong with this repo and so yum does not allow me to
install the Kamailio packages
I wonder what
Am Mittwoch, 25. Juli 2018, 20:56:17 CEST schrieb Giovanni Maruzzelli:
> in my judgement this presentation (have a look at the slides) is about
> scaling SIP and is at the very least very related to Kamailio. No products
> or mktg in it, only standard techniques to scale via sip proxy and rtp
>
Very interessing...
Thank you to share.
Regards
---
I'm SoCIaL, MayBe
On 7/25/18 11:29, Giovanni Maruzzelli wrote:
Hello fellow RTCers,
just finished presenting about scaling videoconferencing, chat and
moderation/direction controls in SIP, with web clients, deskphones,
smartphone apps,
Hello Henning,
in my judgement this presentation (have a look at the slides) is about
scaling SIP and is at the very least very related to Kamailio. No products
or mktg in it, only standard techniques to scale via sip proxy and rtp
proxy.
I understand you judged differently.
Sorry for this.
Am Mittwoch, 25. Juli 2018, 18:29:47 CEST schrieb Giovanni Maruzzelli:
> just finished presenting about scaling videoconferencing, chat and
> moderation/direction controls in SIP, with web clients, deskphones,
> smartphone apps, server push (google fcm) via cordova and SIP.js
> [..]
Hello
Hello fellow RTCers,
just finished presenting about scaling videoconferencing, chat and
moderation/direction controls in SIP, with web clients, deskphones,
smartphone apps, server push (google fcm) via cordova and SIP.js at
www.cluecon.com.
Here's the slides of my presentation:
I "trigger rebuild" and get this results
https://build.opensuse.org/package/live_build_log/home:kamailio:v5.0.x-rpms/kamailio50/CentOS_7/x86_64
Rebuild is finished
https://prnt.sc/kauq7y
But time stamp of files inside root repo directory is not updated
And updated inside x86_64
Hi,
I have just pushed some changes to master - one of these allows startup to
continue even if initial node resolution fails.
There are some other improvements, too, which I have been planning to push
for some time and which should also help in your situation.
Can you try again with these
Another bit of data:
KDMQ messages flow in the wrong direction i.e. (Node B to A) only for dialog
state: 5 updates.
And this happens after the actual KDMQ from A to B has already been ack'd with
a 200 OK.
From: sr-users on behalf of Patrick
Murphy
Sent:
