Re: [SR-Users] driver error: Can't connect to MySQL server with kamailio 5.3.x and mysql-config-groups
you can try docker image of 5.3 branch docker run -it --network host --privileged kamailio/kamailio-ci:5.3-alpine Sergey On Mon, Nov 4, 2019 at 7:06 PM Henning Westerholt wrote: > Hi Karsten, > > > > there is no date yet. I think it will be done probably during or after the > developer meeting next week. Make sense to integrate eventual fixes that > are done there. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt - https://skalatan.de/blog/ > > Kamailio services - https://skalatan.de/services > > > > *From:* Karsten Horsmann > *Sent:* Monday, November 4, 2019 9:45 AM > *To:* Henning Westerholt > *Cc:* Kamailio (SER) - Users Mailing List > *Subject:* Re: [SR-Users] driver error: Can't connect to MySQL server > with kamailio 5.3.x and mysql-config-groups > > > > Hello Henning, > > > > is there an planed release date for this 5.3.x version? > > Unfortunately without this change i cant deploy it without changing all my > > mysql user credentials to be sure there is no "kamailio DBURL separator" > within the password field. > > > > Cheers > > Karsten > > [...] > > > > -- > > Mit freundlichen Grüßen > *Karsten Horsmann* > ___ > 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] driver error: Can't connect to MySQL server with kamailio 5.3.x and mysql-config-groups
Hi Karsten, there is no date yet. I think it will be done probably during or after the developer meeting next week. Make sense to integrate eventual fixes that are done there. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services From: Karsten Horsmann Sent: Monday, November 4, 2019 9:45 AM To: Henning Westerholt Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] driver error: Can't connect to MySQL server with kamailio 5.3.x and mysql-config-groups Hello Henning, is there an planed release date for this 5.3.x version? Unfortunately without this change i cant deploy it without changing all my mysql user credentials to be sure there is no "kamailio DBURL separator" within the password field. Cheers Karsten [...] -- Mit freundlichen Grüßen *Karsten Horsmann* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio - failover setup
On Tue, Oct 29, 2019 at 11:24:34AM -0400, Sergiu Pojoga wrote: > Hi Daniel, > > In an ideal world, DNS is, as you said, the easiest of approaches one can > think of. However, not all endpoints support [properly] SRV failover. And that is why you do both. Both a hot standby and multiple active frontends. BTW I hate the hot standby keepalive/heartbeat/whatever solutions. They work perfectly during testing, they fail in production. But luckily a static kamailio.cfg itself (just playing a proxy) is very stable. ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] driver error: Can't connect to MySQL server with kamailio 5.3.x and mysql-config-groups
Hello Henning, is there an planed release date for this 5.3.x version? Unfortunately without this change i cant deploy it without changing all my mysql user credentials to be sure there is no "kamailio DBURL separator" within the password field. Cheers Karsten [...] -- Mit freundlichen Grüßen *Karsten Horsmann* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to use sdp_remove_media() ?
Hey Karsten,
I am not sure RTPengine allows us to delete a specific stream from SDP (as
it is the main task I am solving).
Anyway, I put route(SDP_VIDEO_REMOVER) above calling record_route and it
works well.
So that the main question is about the source of an issue: my configuration
or something wrong with sdp_remove_media()?
пт, 1 нояб. 2019 г. в 19:03, Karsten Horsmann :
> Hi Denys,
>
> AFAIK read and writes rtpengine the complete sdp. So manipulating with the
> "classic" textops tools is more for RtpProxy. You can search for things but
> writing will done by rtpengine.
> I remove for example an codec with codec-mask. Or you can manipulate the
> avp you read from rtpengine (via modparam) in the request.
>
> Did you try to *codec-mask= in the rtpengine calls (answer / manage)? *
> *So rtpengine takes care for the removal. *
> *It needs to know what to remove. *
>
> https://www.kamailio.org/docs/modules/5.3.x/modules/rtpengine.html#idm1459
>
>
> Cheers
> Karsten
>
> Denys Pozniak schrieb am Fr., 1. Nov. 2019,
> 15:10:
>
>> If I put route(SDP_VIDEO_REMOVER) into the section route[NATMANAGE] (
>> https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L820
>> ), Kamailio shows the error I posted below.
>>
>> route[SDP_VIDEO_REMOVER] {
>> if ( is_request() && has_body("application/sdp") &&
>> sdp_with_media("video") ) {
>> sdp_remove_media("video");
>> msg_apply_changes();
>> xlog("L_WARN","[$cfg(route)] *m=video detected* |
>> $rm/$rs/$avp(sdp_mvideo_line)/ \n");
>> }
>> }
>>
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:883]: sdp_with_media(): attempting
>> to search for media type: [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 0 of
>> 0 - media [audio]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 1 of
>> 0 - media [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1038]: sdp_remove_media():
>> attempting to search for media type: [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 0
>> of 0 - media [audio]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 1
>> of 0 - media [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1061]: sdp_remove_media(): removing
>> media stream: video16(15993) *ERROR: textopsx [textopsx.c:181]:
>> ki_msg_apply_changes(): invalid usage - not in request route or a reply*
>> 16(15993) WARNING:
