date:20220510

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

2022-05-10 Thread Henning Westerholt

Hello,

Yes, its aparently missing in the output. I checked in my local checkout, its 
there.

But the version rc0 was set later as the commits in question, so they should be 
included.

If the error is still there, re-open the ticket 3090 and add more information 
there.

Cheers,

Henning



From: George Diamantopoulos 
Sent: Tuesday, May 10, 2022 8:06 PM
To: Henning Westerholt 
Cc: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Hello Henning,

Thanks for the reply. Here's the output, but I don't see anything relevant to 
git commits:

version: kamailio 5.6.0-rc0 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, 
USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, 
DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, 
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, 
TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, 
BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 10.2.1

BR,
George

On Tue, 10 May 2022 at 18:55, Henning Westerholt 
mailto:h...@gilawa.com>> wrote:
Hello,

it seems to be included, at least in the git branch.

~/repositories/5.6$ git log | egrep "c309122|ceb688b" -A 5
commit c309122864eaa2bfa58253290bed49084ccc9302
Author: Daniel-Constantin Mierla mico...@gmail.com
Date:   Thu Apr 21 14:28:26 2022 +0200

topos: restore attributes based on direction for early dialog requests

--
commit ceb688b3d364bb7b8d9f52b7238d560cb4e30b3d
Author: Daniel-Constantin Mierla mico...@gmail.com
Date:   Thu Apr 21 09:00:09 2022 +0200

topos: use direction for loading invite record for other early dialog 
requests

It would be good to double-check with the output of “kamailio -v”, please paste 
it here.

Cheers,

Henning

From: George Diamantopoulos mailto:georged...@gmail.com>>
Sent: Tuesday, May 10, 2022 4:43 PM
To: Henning Westerholt mailto:h...@gilawa.com>>
Cc: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Hello again,

I've just tested 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly, but 
loose_route() still returns false for early-dialog UPDATE... Does this build 
include c309122 and ceb688b referenced in 
https://github.com/kamailio/kamailio/issues/3090?

Cheers,
George

On Thu, 7 Apr 2022 at 10:21, George Diamantopoulos 
mailto:georged...@gmail.com>> wrote:
Hello all,

Thanks for the feedback, Henning. There seems to have already been a ticket 
about this but it's closed now: https://github.com/kamailio/kamailio/issues/2659

I'm a little confused here. It seems early-dialog UPDATE should be handled 
similarly to PRACK, so I guess maybe a patch like 
https://github.com/kamailio/kamailio/commit/37830f53b1f21fba5beef5d8e22913c431dcd708
 would be needed.

However, Daniel has commented in this issue about the need to do record_route() 
in config. To quote him: "The module requires record routing, so if the UPDATE 
requires to re-enforce Record-Route, then you have to do it. [...] I was aware 
that only NOTIFY requires to re-enforce Record-Route, but can be also a matter 
of UA implementation to want it for other requests."

However, RR reinforcement for NOTIFY only happens (in the kamailio sample 
configuration file) in route[WITHINDLG] only if loose_route() check is 
successful. In my case, UPDATEs fail this test, so control goes directly to 
"sl_send_reply("404","Not here");", same as the author of the aforementioned 
ticket. Unless Daniel meant one needs to reinforce RR for PRACKs in order for 
subsequent UPDATEs to work?

Any thoughts?

BR,
George

On Wed, 6 Apr 2022 at 22:48, Henning Westerholt 
mailto:h...@gilawa.com>> wrote:
Hello,

Thanks for the update. Opening a github issue about it is probably a good idea.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com

From: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 On Behalf Of George Diamantopoulos
Sent: Wednesday, April 6, 2022 7:29 PM
To: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

This seems to be a topos issue regardless of backend, I tried with mariadb as 
storage and UPDATE routing fails in the same way as it does with redis. I'll 
probably open an issue on Github about this (early dialog UPDATE broken by 
topos). PRACK seems to work fine in my case. Direction of UPDATE vs PRACK 
however is different, not sure if that's important in any way.

BR,
George

On Wed, 6 Apr 2022 at 06:31, George Diamantopoulos 
mailto:georged...@gmail.com>> wrote:
Hello again,

I have confirmed the problem doesn't manifest without loading the topos module. 
I'll see if I can also try a

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

2022-05-10 Thread George Diamantopoulos

Hello Henning,

Thanks for the reply. Here's the output, but I don't see anything relevant
to git commits:

version: kamailio 5.6.0-rc0 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE,
USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC,
TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST,
HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024,
BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 10.2.1

BR,
George

On Tue, 10 May 2022 at 18:55, Henning Westerholt  wrote:

> Hello,
>
>
>
> it seems to be included, at least in the git branch.
>
>
>
> ~/repositories/5.6$ git log | egrep "c309122|ceb688b" -A 5
>
> commit c309122864eaa2bfa58253290bed49084ccc9302
>
> Author: Daniel-Constantin Mierla mico...@gmail.com
>
> Date:   Thu Apr 21 14:28:26 2022 +0200
>
>
>
> topos: restore attributes based on direction for early dialog requests
>
>
>
> --
>
> commit ceb688b3d364bb7b8d9f52b7238d560cb4e30b3d
>
> Author: Daniel-Constantin Mierla mico...@gmail.com
>
> Date:   Thu Apr 21 09:00:09 2022 +0200
>
>
>
> topos: use direction for loading invite record for other early dialog
> requests
>
>
>
> It would be good to double-check with the output of “kamailio -v”, please
> paste it here.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> *From:* George Diamantopoulos 
> *Sent:* Tuesday, May 10, 2022 4:43 PM
> *To:* Henning Westerholt 
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
>
>
>
> Hello again,
>
>
>
> I've just tested 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly, but
> loose_route() still returns false for early-dialog UPDATE... Does this
> build include c309122 and ceb688b referenced in
> https://github.com/kamailio/kamailio/issues/3090?
>
>
>
> Cheers,
>
> George
>
>
>
> On Thu, 7 Apr 2022 at 10:21, George Diamantopoulos 
> wrote:
>
> Hello all,
>
>
>
> Thanks for the feedback, Henning. There seems to have already been a
> ticket about this but it's closed now:
> https://github.com/kamailio/kamailio/issues/2659
>
>
>
> I'm a little confused here. It seems early-dialog UPDATE should be handled
> similarly to PRACK, so I guess maybe a patch like
> https://github.com/kamailio/kamailio/commit/37830f53b1f21fba5beef5d8e22913c431dcd708
> would be needed.
>
>
>
> However, Daniel has commented in this issue about the need to do
> record_route() in config. To quote him: "The module requires record
> routing, so if the UPDATE requires to re-enforce Record-Route, then you
> have to do it. [...] I was aware that only NOTIFY requires to re-enforce
> Record-Route, but can be also a matter of UA implementation to want it for
> other requests."
>
>
>
> However, RR reinforcement for NOTIFY only happens (in the kamailio sample
> configuration file) in route[WITHINDLG] only if loose_route() check is
> successful. In my case, UPDATEs fail this test, so control goes directly to
> "sl_send_reply("404","Not here");", same as the author of the
> aforementioned ticket. Unless Daniel meant one needs to reinforce RR for
> PRACKs in order for subsequent UPDATEs to work?
>
>
>
> Any thoughts?
>
>
>
> BR,
>
> George
>
>
>
> On Wed, 6 Apr 2022 at 22:48, Henning Westerholt  wrote:
>
> Hello,
>
>
>
> Thanks for the update. Opening a github issue about it is probably a good
> idea.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* sr-users  *On Behalf Of *George
> Diamantopoulos
> *Sent:* Wednesday, April 6, 2022 7:29 PM
> *To:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
>
>
>
> This seems to be a topos issue regardless of backend, I tried with mariadb
> as storage and UPDATE routing fails in the same way as it does with redis.
> I'll probably open an issue on Github about this (early dialog UPDATE
> broken by topos). PRACK seems to work fine in my case. Direction of UPDATE
> vs PRACK however is different, not sure if that's important in any way.
>
>
>
> BR,
>
> George
>
>
>
> On Wed, 6 Apr 2022 at 06:31, George Diamantopoulos 
> wrote:
>
> Hello again,
>
>
>
> I have confirmed the problem doesn't manifest without loading the topos
> module. I'll see if I can also try a different topos backend this week to
> confirm if this is a topos_redis issue or topos in general.
>
>
>
> BR,
>
> George
>
>
>
> On Tue, 22 Mar 2022 at 17:11, George Diamantopoulos 
> wrote:
>
> Hello Henning,
>
>
>
> This is on kamailio 5.5.4.
>
>
>
> I'll try with a different backend and without topos and post the result
> here as soon as I find the time, just curious if anyone has stumbled on
> this with topos_redis before. Thanks!
>
>
>
> BR,
>
> George
>
>
>
> On Tue, 22 Mar 2022 at 15:51, Henning

Re: [SR-Users] Accept IP/Domain Register

2022-05-10 Thread Raúl Alexis Betancor Santana

As allways, there are 1 thousand ways of skinning a cat

You have 3 options:

1) Create the 100 user in all the domains with the same password.
2) Disable domain in auth_check
3) On the routing logic, when you detect your 100 user, do an auth without 
domain chekin (kind of option 2 but only for specific users)

- Original Message -
From: "Social Boh" 
To: "Kamailio" , "Alex Balashov" 

Sent: Tuesday, May 10, 2022 6:45:20 PM
Subject: Re: [SR-Users] Accept IP/Domain Register

I think my question not is clear.

I'd like create/configure, for example, user 100 and this user can 
register with kamailio using Kamailio IP or Kamailio associated Domains; 
this using digest authentication.

Regards

---
I'm SoCIaL, MayBe

El 10/05/2022 a las 12:26 p. m., Alex Balashov escribió:
> Yes. There is no rule that you have to issue a digest authentication 
> challenge in response to registrations.
>
> You can handle them like any other request, including validating the source 
> IP against an IP ACL (e.g. allow_trusted(), or hard-coded like if(src_ip == 
> 1.2.3.4)).
>
> — Alex
>
> —
> Sent from mobile, with due apologies for brevity and errors.
>
>> On May 10, 2022, at 12:49 PM, Social Boh  wrote:
>>
>> Hello,
>>
>> maybe is a very basic question; How Kamailio can accept any kind of 
>> register, over IP or domains.
>>
>> Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org or 
>> sip1.domain.org, domains associated with ip 1.2.3.4
>>
>> Thank you in advance.
>>
>> Regards
>>
>> -- 
>> ---
>> I'm SoCIaL, MayBe
>>
>>
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> * sr-users@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the 
>> sender!
>> Edit mailing list options or unsubscribe:
>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
>* sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:
>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Accept IP/Domain Register

2022-05-10 Thread Alex Balashov

Oh, I see. Sure, you can do that.

—
Sent from mobile, with due apologies for brevity and errors.

> On May 10, 2022, at 1:45 PM, Social Boh  wrote:
> 
> I think my question not is clear.
> 
> I'd like create/configure, for example, user 100 and this user can register 
> with kamailio using Kamailio IP or Kamailio associated Domains; this using 
> digest authentication.
> 
> Regards
> 
> ---
> I'm SoCIaL, MayBe
> 
>> El 10/05/2022 a las 12:26 p. m., Alex Balashov escribió:
>> Yes. There is no rule that you have to issue a digest authentication 
>> challenge in response to registrations.
>> 
>> You can handle them like any other request, including validating the source 
>> IP against an IP ACL (e.g. allow_trusted(), or hard-coded like if(src_ip == 
>> 1.2.3.4)).
>> 
>> — Alex
>> 
>> —
>> Sent from mobile, with due apologies for brevity and errors.
>> 
 On May 10, 2022, at 12:49 PM, Social Boh  wrote:
>>> 
>>> Hello,
>>> 
>>> maybe is a very basic question; How Kamailio can accept any kind of 
>>> register, over IP or domains.
>>> 
>>> Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org or 
>>> sip1.domain.org, domains associated with ip 1.2.3.4
>>> 
>>> Thank you in advance.
>>> 
>>> Regards
>>> 
>>> -- 
>>> ---
>>> I'm SoCIaL, MayBe
>>> 
>>> 
>>> __
>>> Kamailio - Users Mailing List - Non Commercial Discussions
>>> * sr-users@lists.kamailio.org
>>> Important: keep the mailing list in the recipients, do not reply only to 
>>> the sender!
>>> Edit mailing list options or unsubscribe:
>>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>>   * sr-users@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the 
>> sender!
>> Edit mailing list options or unsubscribe:
>>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Accept IP/Domain Register

2022-05-10 Thread Social Boh


I think my question not is clear.

I'd like create/configure, for example, user 100 and this user can 
register with kamailio using Kamailio IP or Kamailio associated Domains; 
this using digest authentication.


Regards

---
I'm SoCIaL, MayBe

El 10/05/2022 a las 12:26 p. m., Alex Balashov escribió:

Yes. There is no rule that you have to issue a digest authentication challenge 
in response to registrations.

You can handle them like any other request, including validating the source IP 
against an IP ACL (e.g. allow_trusted(), or hard-coded like if(src_ip == 
1.2.3.4)).

— Alex

—
Sent from mobile, with due apologies for brevity and errors.


On May 10, 2022, at 12:49 PM, Social Boh  wrote:

Hello,

maybe is a very basic question; How Kamailio can accept any kind of register, 
over IP or domains.

Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org or 
sip1.domain.org, domains associated with ip 1.2.3.4

Thank you in advance.

Regards

--
---
I'm SoCIaL, MayBe


__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

__
Kamailio - Users Mailing List - Non Commercial Discussions
   * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


__
Kamailio - Users Mailing List - Non Commercial Discussions
 * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
 * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Accept IP/Domain Register

2022-05-10 Thread Alex Balashov

Yes. There is no rule that you have to issue a digest authentication challenge 
in response to registrations. 

You can handle them like any other request, including validating the source IP 
against an IP ACL (e.g. allow_trusted(), or hard-coded like if(src_ip == 
1.2.3.4)).

— Alex

—
Sent from mobile, with due apologies for brevity and errors.

> On May 10, 2022, at 12:49 PM, Social Boh  wrote:
> 
> Hello,
> 
> maybe is a very basic question; How Kamailio can accept any kind of register, 
> over IP or domains.
> 
> Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org or 
> sip1.domain.org, domains associated with ip 1.2.3.4
> 
> Thank you in advance.
> 
> Regards
> 
> -- 
> ---
> I'm SoCIaL, MayBe
> 
> 
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> * sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:
> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Accept IP/Domain Register

2022-05-10 Thread Social Boh


Hello,

maybe is a very basic question; How Kamailio can accept any kind of 
register, over IP or domains.


Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org 
or sip1.domain.org, domains associated with ip 1.2.3.4


Thank you in advance.

Regards

--
---
I'm SoCIaL, MayBe


__
Kamailio - Users Mailing List - Non Commercial Discussions
 * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
 * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

2022-05-10 Thread Henning Westerholt

Hello,

it seems to be included, at least in the git branch.

~/repositories/5.6$ git log | egrep "c309122|ceb688b" -A 5
commit c309122864eaa2bfa58253290bed49084ccc9302
Author: Daniel-Constantin Mierla mico...@gmail.com
Date:   Thu Apr 21 14:28:26 2022 +0200

topos: restore attributes based on direction for early dialog requests

--
commit ceb688b3d364bb7b8d9f52b7238d560cb4e30b3d
Author: Daniel-Constantin Mierla mico...@gmail.com
Date:   Thu Apr 21 09:00:09 2022 +0200

topos: use direction for loading invite record for other early dialog 
requests

It would be good to double-check with the output of “kamailio -v”, please paste 
it here.

Cheers,

Henning

From: George Diamantopoulos 
Sent: Tuesday, May 10, 2022 4:43 PM
To: Henning Westerholt 
Cc: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Hello again,

I've just tested 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly, but 
loose_route() still returns false for early-dialog UPDATE... Does this build 
include c309122 and ceb688b referenced in 
https://github.com/kamailio/kamailio/issues/3090?

Cheers,
George

On Thu, 7 Apr 2022 at 10:21, George Diamantopoulos 
mailto:georged...@gmail.com>> wrote:
Hello all,

Thanks for the feedback, Henning. There seems to have already been a ticket 
about this but it's closed now: https://github.com/kamailio/kamailio/issues/2659

I'm a little confused here. It seems early-dialog UPDATE should be handled 
similarly to PRACK, so I guess maybe a patch like 
https://github.com/kamailio/kamailio/commit/37830f53b1f21fba5beef5d8e22913c431dcd708
 would be needed.

However, Daniel has commented in this issue about the need to do record_route() 
in config. To quote him: "The module requires record routing, so if the UPDATE 
requires to re-enforce Record-Route, then you have to do it. [...] I was aware 
that only NOTIFY requires to re-enforce Record-Route, but can be also a matter 
of UA implementation to want it for other requests."

However, RR reinforcement for NOTIFY only happens (in the kamailio sample 
configuration file) in route[WITHINDLG] only if loose_route() check is 
successful. In my case, UPDATEs fail this test, so control goes directly to 
"sl_send_reply("404","Not here");", same as the author of the aforementioned 
ticket. Unless Daniel meant one needs to reinforce RR for PRACKs in order for 
subsequent UPDATEs to work?

Any thoughts?

BR,
George

On Wed, 6 Apr 2022 at 22:48, Henning Westerholt 
mailto:h...@gilawa.com>> wrote:
Hello,

Thanks for the update. Opening a github issue about it is probably a good idea.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com

From: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 On Behalf Of George Diamantopoulos
Sent: Wednesday, April 6, 2022 7:29 PM
To: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

This seems to be a topos issue regardless of backend, I tried with mariadb as 
storage and UPDATE routing fails in the same way as it does with redis. I'll 
probably open an issue on Github about this (early dialog UPDATE broken by 
topos). PRACK seems to work fine in my case. Direction of UPDATE vs PRACK 
however is different, not sure if that's important in any way.

BR,
George

On Wed, 6 Apr 2022 at 06:31, George Diamantopoulos 
mailto:georged...@gmail.com>> wrote:
Hello again,

I have confirmed the problem doesn't manifest without loading the topos module. 
I'll see if I can also try a different topos backend this week to confirm if 
this is a topos_redis issue or topos in general.

BR,
George

On Tue, 22 Mar 2022 at 17:11, George Diamantopoulos 
mailto:georged...@gmail.com>> wrote:
Hello Henning,

This is on kamailio 5.5.4.

I'll try with a different backend and without topos and post the result here as 
soon as I find the time, just curious if anyone has stumbled on this with 
topos_redis before. Thanks!

BR,
George

On Tue, 22 Mar 2022 at 15:51, Henning Westerholt 
mailto:h...@gilawa.com>> wrote:
Hello,

please give a recent 5.5.x Kamailio a try. There was a fix regarding 
early-dialog UPDATE handling in topos committed one year ago.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com

From: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 On Behalf Of George Diamantopoulos
Sent: Monday, March 21, 2022 11:53 PM
To: d.tr...@pocos.nl; Kamailio (SER) - Users Mailing 
List mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Hello all,

Any chance this could be affecting early-dialog UPDATE methods as well? I 
haven't tried with a different backend (mysql) yet, but loose_route returns 
false...

BR,
George

On Fri, 25 May 2018 at 18:00, Daniel Tryba

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

2022-05-10 Thread George Diamantopoulos

Hello again,

I've just tested 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly, but
loose_route() still returns false for early-dialog UPDATE... Does this
build include c309122 and ceb688b referenced in
https://github.com/kamailio/kamailio/issues/3090?

Cheers,
George

On Thu, 7 Apr 2022 at 10:21, George Diamantopoulos 
wrote:

> Hello all,
>
> Thanks for the feedback, Henning. There seems to have already been a
> ticket about this but it's closed now:
> https://github.com/kamailio/kamailio/issues/2659
>
> I'm a little confused here. It seems early-dialog UPDATE should be handled
> similarly to PRACK, so I guess maybe a patch like
> https://github.com/kamailio/kamailio/commit/37830f53b1f21fba5beef5d8e22913c431dcd708
> would be needed.
>
> However, Daniel has commented in this issue about the need to do
> record_route() in config. To quote him: "The module requires record
> routing, so if the UPDATE requires to re-enforce Record-Route, then you
> have to do it. [...] I was aware that only NOTIFY requires to re-enforce
> Record-Route, but can be also a matter of UA implementation to want it for
> other requests."
>
> However, RR reinforcement for NOTIFY only happens (in the kamailio sample
> configuration file) in route[WITHINDLG] only if loose_route() check is
> successful. In my case, UPDATEs fail this test, so control goes directly to
> "sl_send_reply("404","Not here");", same as the author of the
> aforementioned ticket. Unless Daniel meant one needs to reinforce RR for
> PRACKs in order for subsequent UPDATEs to work?
>
> Any thoughts?
>
> BR,
> George
>
> On Wed, 6 Apr 2022 at 22:48, Henning Westerholt  wrote:
>
>> Hello,
>>
>>
>>
>> Thanks for the update. Opening a github issue about it is probably a good
>> idea.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Henning
>>
>>
>>
>> --
>>
>> Henning Westerholt – https://skalatan.de/blog/
>>
>> Kamailio services – https://gilawa.com
>>
>>
>>
>> *From:* sr-users  *On Behalf Of *George
>> Diamantopoulos
>> *Sent:* Wednesday, April 6, 2022 7:29 PM
>> *To:* Kamailio (SER) - Users Mailing List 
>> *Subject:* Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
>>
>>
>>
>> This seems to be a topos issue regardless of backend, I tried with
>> mariadb as storage and UPDATE routing fails in the same way as it does with
>> redis. I'll probably open an issue on Github about this (early dialog
>> UPDATE broken by topos). PRACK seems to work fine in my case. Direction of
>> UPDATE vs PRACK however is different, not sure if that's important in any
>> way.
>>
>>
>>
>> BR,
>>
>> George
>>
>>
>>
>> On Wed, 6 Apr 2022 at 06:31, George Diamantopoulos 
>> wrote:
>>
>> Hello again,
>>
>>
>>
>> I have confirmed the problem doesn't manifest without loading the topos
>> module. I'll see if I can also try a different topos backend this week to
>> confirm if this is a topos_redis issue or topos in general.
>>
>>
>>
>> BR,
>>
>> George
>>
>>
>>
>> On Tue, 22 Mar 2022 at 17:11, George Diamantopoulos 
>> wrote:
>>
>> Hello Henning,
>>
>>
>>
>> This is on kamailio 5.5.4.
>>
>>
>>
>> I'll try with a different backend and without topos and post the result
>> here as soon as I find the time, just curious if anyone has stumbled on
>> this with topos_redis before. Thanks!
>>
>>
>>
>> BR,
>>
>> George
>>
>>
>>
>> On Tue, 22 Mar 2022 at 15:51, Henning Westerholt  wrote:
>>
>> Hello,
>>
>>
>>
>> please give a recent 5.5.x Kamailio a try. There was a fix regarding
>> early-dialog UPDATE handling in topos committed one year ago.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Henning
>>
>>
>>
>> --
>>
>> Henning Westerholt – https://skalatan.de/blog/
>>
>> Kamailio services – https://gilawa.com
>>
>>
>>
>> *From:* sr-users  *On Behalf Of *George
>> Diamantopoulos
>> *Sent:* Monday, March 21, 2022 11:53 PM
>> *To:* d.tr...@pocos.nl; Kamailio (SER) - Users Mailing List <
>> sr-users@lists.kamailio.org>
>> *Subject:* Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
>>
>>
>>
>> Hello all,
>>
>>
>>
>> Any chance this could be affecting early-dialog UPDATE methods as well? I
>> haven't tried with a different backend (mysql) yet, but loose_route returns
>> false...
>>
>>
>>
>> BR,
>>
>> George
>>
>>
>>
>> On Fri, 25 May 2018 at 18:00, Daniel Tryba  wrote:
>>
>> On Wed, May 23, 2018 at 10:51:37PM +0200, Daniel-Constantin Mierla wrote:
>> > I got a bit of time to look at this issue, can you try with the patch
>> > from the next commit?
>> >
>> > ?? -
>> >
>> https://github.com/kamailio/kamailio/commit/2a3ca5942291d29de05b14338a36cecbec11f129
>> >
>>
>> This off by 1 fix solved the PRACK issue with redis backend.
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Daniel-Constantin Mierla

Thanks for the useful details about hugo!

For the records, in the past we used the mkdocs for a couple of
tutorials, like the one for KEMI framework or install guidelines, eg:

  * https://www.kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/

Built from:

  *
https://github.com/kamailio/kamailio-docs/tree/master/kamailio-kemi-framework

But I can't say I am that familiar with it to assert if it is the best
one for the wiki, which has lot of content and some pages could end up
with large ToC (e.g., the cookbooks for core, variables, ...).

Anyhow, let's have it in the list and see if we get more feedback or
other suggestions from the community.

Cheers,
Daniel

On 10.05.22 13:01, Greg Troxel wrote:
> Daniel-Constantin Mierla  writes:
>
>> Ideally it is an app that can run on or behind a http server/proxy and
>> serve html pages generated from the .md files directly from the folder
>> with the clone of the github repo. But maybe I ask too much and adapting
>> the wiki structure for a static site generator from .md files is enough
>> or even better.
> I have been slowly converting my own content to hugo.   It's a very
> straightforward static site generator, and it runs very quickly.
>
> It also has a built-in webserver, and by default it watches the content
> files and provides the built website on port 127.0.0.1:1313.  This is
> intended for previewing while editing - once you save a file the browser
> window gets the new content in under a second.
>
> So if you either make hugo use your layout, or adapt to hugo's idea of
> layout (which is quite sane), then not only can bits be pushed to a
> server, but "hugo server" will make them available.
>
> So if I were tackling this, of all the options listed, I would lean
> strongly to hugo.

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online: June 20-23, 2022
  * https://www.asipto.com/sw/kamailio-advanced-training-online/

__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] unable to get local issuer certificate

2022-05-10 Thread Володимир Іванець

Hello Olle!

Thank you for the hint! I checked my test server where the connection was
working before and now I see the same problem. Looks like Microsoft could
update certificate on their side. Will try to find appropriate root and
intermediate certificates.

Thanks a lot!

чт, 5 трав. 2022 р. о 17:52 Olle E. Johansson  пише:

> tls_dump_cert_info(): tls_connect: server certificate
> issuer:/C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>
> THis is not sectigo signed - is my guess. It’s the other sides cert that
> Kamailio can’t verify. You need to add that CA cert to the Kamailio CA
> store.
>
> /O
>
> On 5 May 2022, at 14:09, Володимир Іванець 
> wrote:
>
> tls_dump_cert_info(): tls_connect: server certificate
> issuer:/C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
>   * sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Greg Troxel

Daniel-Constantin Mierla  writes:

> Ideally it is an app that can run on or behind a http server/proxy and
> serve html pages generated from the .md files directly from the folder
> with the clone of the github repo. But maybe I ask too much and adapting
> the wiki structure for a static site generator from .md files is enough
> or even better.

I have been slowly converting my own content to hugo.   It's a very
straightforward static site generator, and it runs very quickly.

It also has a built-in webserver, and by default it watches the content
files and provides the built website on port 127.0.0.1:1313.  This is
intended for previewing while editing - once you save a file the browser
window gets the new content in under a second.

So if you either make hugo use your layout, or adapt to hugo's idea of
layout (which is quite sane), then not only can bits be pushed to a
server, but "hugo server" will make them available.

So if I were tackling this, of all the options listed, I would lean
strongly to hugo.

signature.asc
Description: PGP signature
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Daniel-Constantin Mierla

Thanks for all your PRs this morning! I got the one with pandoc locally
and run it, I noticed some warnings, but didn't get deep into them.
Opened the start page and I could browse locally a few links.

To be able to organize better in the future, I am considering to
relocate the wiki content to a new docs/ subfolder.

Then we can have a main Makefile in the root folder that can be used to
generate various formats, like the one you proposed using pandoc. A new
subfolder (fmt/, misc/, tools, ...) can be created to collect
configs/scripts specific to each formatting variant.

The root folder should be like:

docs/[wiki files]
fmt/pandoc/links.lua
fmt/mkdocs/...
Makefile
README.md
...

I used pandoc and mkdocs as examples just to express what I meant.

Any other opinions/suggestions?

Cheers,
Daniel

On 10.05.22 11:25, Bastian Triller wrote:
> Fiddled around w/ pandoc [1]
>
> [1] https://github.com/kamailio/kamailio-wiki/pull/3
>
> On Tue, May 10, 2022 at 9:08 AM Henning Westerholt  wrote:
>> Hello,
>>
>>
>>
>> thanks Seven for your feedback.
>>
>>
>>
>> I have made good experiences with static site generators that just generate 
>> html that you can serve with standard web servers.
>>
>>
>>
>> I did not personally have used it, but I heard that hugo works well and is 
>> used a lot. I personally have used gravcms, which is based on PHP.
>>
>>
>>
>> You can easily combine this static generators with some cron job and it 
>> should work for our existing setup by just adding another path to the apache.
>>
>> In my experience this is easier as having another app to deploy, monitor and 
>> frequently update.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Henning
>>
>>
>>
>> From: sr-users  On Behalf Of 
>> Daniel-Constantin Mierla
>> Sent: Tuesday, May 10, 2022 8:29 AM
>> To: Seven Du ; Kamailio (SER) - Users Mailing List 
>> 
>> Subject: Re: [SR-Users] Info: converting dokuwiki content to markdown files
>>
>>
>>
>> Thanks, I will check them.
>>
>> Ideally it is an app that can run on or behind a http server/proxy and serve 
>> html pages generated from the .md files directly from the folder with the 
>> clone of the github repo. But maybe I ask too much and adapting the wiki 
>> structure for a static site generator from .md files is enough or even 
>> better.
>>
>> Cheers,
>> Daniel
>>
>> On 10.05.22 00:28, Seven Du wrote:
>>
>> We'd like to help.
>>
>>
>>
>> Select one from Jekyll, Hugo and TailwindBlog
>>
>>
>>
>> Jekyll: Ruby based https://jekyllrb.com/, can directly convert to html by 
>> github
>>
>> Hugo: Go based,  can also auto covert to html 
>> https://gohugo.io/hosting-and-deployment/hosting-on-github/
>>
>> TailwindBlog: Next.js based 
>> https://github.com/timlrx/tailwind-nextjs-starter-blog
>>
>>
>>
>> We built a few websites with the TailwindBlog recently and it looks very 
>> good. But as all JS projects, you have to download a giant deps of 
>> node_modules and build locally manually to generate static html pages, we 
>> haven't found how to do it automatically, since our updates are not 
>> frequent, we are ok to do it by hand.
>>
>>
>>
>> There may be other options. Anyway, look and discuss, as long as it's 
>> determined we can help to build.
>>
>>
>>
>> As a reference, these are sites we just built recently:
>>
>>
>>
>> - https://xswitch.cn/
>>
>> - http://rts.cn/
>>
>>
>>
>>
>>
>>
>>
>> On Mon, May 9, 2022 at 8:11 PM Daniel-Constantin Mierla  
>> wrote:
>>
>> Hello,
>>
>> it was discussed a couple of times during the past Kamailio development
>> meetings and several days ago the works started to convert the Kamailio
>> Wiki content to markdown format and host the files on Kamailio
>> github.com organisation.
>>
>> The Dokuwiki engine has served us very well during more than a decade
>> and a half, but open editing had to be disabled many years ago due to
>> bad actors pushing inappropriate content. The contributors had to make a
>> dedicated account on our portal only for Wiki editing. More recently we
>> had add another layer of protection requiring to grant manually edit
>> permissions to newly created wiki accounts because bots started to work
>> around CAPTCHA and other security extensions, posting again
>> inappropriate content.
>>
>> All these added to operational overhead, but also made it difficult for
>> new people to contribute, specially for small editing to fix typos or
>> add usage examples.
>>
>> Thanks to Kenneth Stowe, who undertook the first big effort of
>> converting the Dowkuwiki files to markdown format, we are now in the
>> position of moving further with the plans of using github for hosting
>> the content of the wiki and enable easier contributions via pull
>> requests. The history of changes done via Dokuwiki show up now as git
>> commits.
>>
>> The github repository for the wiki content is available at:
>>
>>   * https://github.com/kamailio/kamailio-wiki
>>
>> It is still work in progress, therefore we ask for the help of community
>> to speed up the conversion, among the tasks

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Bastian Triller

Fiddled around w/ pandoc [1]

[1] https://github.com/kamailio/kamailio-wiki/pull/3

On Tue, May 10, 2022 at 9:08 AM Henning Westerholt  wrote:
>
> Hello,
>
>
>
> thanks Seven for your feedback.
>
>
>
> I have made good experiences with static site generators that just generate 
> html that you can serve with standard web servers.
>
>
>
> I did not personally have used it, but I heard that hugo works well and is 
> used a lot. I personally have used gravcms, which is based on PHP.
>
>
>
> You can easily combine this static generators with some cron job and it 
> should work for our existing setup by just adding another path to the apache.
>
> In my experience this is easier as having another app to deploy, monitor and 
> frequently update.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> From: sr-users  On Behalf Of 
> Daniel-Constantin Mierla
> Sent: Tuesday, May 10, 2022 8:29 AM
> To: Seven Du ; Kamailio (SER) - Users Mailing List 
> 
> Subject: Re: [SR-Users] Info: converting dokuwiki content to markdown files
>
>
>
> Thanks, I will check them.
>
> Ideally it is an app that can run on or behind a http server/proxy and serve 
> html pages generated from the .md files directly from the folder with the 
> clone of the github repo. But maybe I ask too much and adapting the wiki 
> structure for a static site generator from .md files is enough or even better.
>
> Cheers,
> Daniel
>
> On 10.05.22 00:28, Seven Du wrote:
>
> We'd like to help.
>
>
>
> Select one from Jekyll, Hugo and TailwindBlog
>
>
>
> Jekyll: Ruby based https://jekyllrb.com/, can directly convert to html by 
> github
>
> Hugo: Go based,  can also auto covert to html 
> https://gohugo.io/hosting-and-deployment/hosting-on-github/
>
> TailwindBlog: Next.js based 
> https://github.com/timlrx/tailwind-nextjs-starter-blog
>
>
>
> We built a few websites with the TailwindBlog recently and it looks very 
> good. But as all JS projects, you have to download a giant deps of 
> node_modules and build locally manually to generate static html pages, we 
> haven't found how to do it automatically, since our updates are not frequent, 
> we are ok to do it by hand.
>
>
>
> There may be other options. Anyway, look and discuss, as long as it's 
> determined we can help to build.
>
>
>
> As a reference, these are sites we just built recently:
>
>
>
> - https://xswitch.cn/
>
> - http://rts.cn/
>
>
>
>
>
>
>
> On Mon, May 9, 2022 at 8:11 PM Daniel-Constantin Mierla  
> wrote:
>
> Hello,
>
> it was discussed a couple of times during the past Kamailio development
> meetings and several days ago the works started to convert the Kamailio
> Wiki content to markdown format and host the files on Kamailio
> github.com organisation.
>
> The Dokuwiki engine has served us very well during more than a decade
> and a half, but open editing had to be disabled many years ago due to
> bad actors pushing inappropriate content. The contributors had to make a
> dedicated account on our portal only for Wiki editing. More recently we
> had add another layer of protection requiring to grant manually edit
> permissions to newly created wiki accounts because bots started to work
> around CAPTCHA and other security extensions, posting again
> inappropriate content.
>
> All these added to operational overhead, but also made it difficult for
> new people to contribute, specially for small editing to fix typos or
> add usage examples.
>
> Thanks to Kenneth Stowe, who undertook the first big effort of
> converting the Dowkuwiki files to markdown format, we are now in the
> position of moving further with the plans of using github for hosting
> the content of the wiki and enable easier contributions via pull
> requests. The history of changes done via Dokuwiki show up now as git
> commits.
>
> The github repository for the wiki content is available at:
>
>   * https://github.com/kamailio/kamailio-wiki
>
> It is still work in progress, therefore we ask for the help of community
> to speed up the conversion, among the tasks that need to be done:
>
>   * convert relative links between wiki pages – the conversion tools
> used relative paths without file extensions, like:
>
> [Install Kamailio v4.4.x From GIT](/install/4.4.x/git)
>
> They have to be converted to relative path with .md extension in order
> to be able to browse directly :n the github.com portal — practically the
> leading / has to be removed and .md added at the end, like:
>
> [Install Kamailio v4.4.x From GIT](install/4.4.x/git.md)
>
>   * some section heading markers were not detected/converted, onee may
> notice many equal signs (=) around a section name, it has to be replaced
> with the appropriate markdown format based on hash signs (#). For example:
>
> === Install And Maintain Kamailio v4.4.x From GIT ===
>
> Should be converted to:
>
> # Install And Maintain Kamailio v4.4.x From GIT
>
>   * some Dokuwiki paragraphs used special formatting based on plugins,
> for example the notes, warnings, … had special colors. The common
>

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Henning Westerholt

Hello,

thanks Seven for your feedback.

I have made good experiences with static site generators that just generate 
html that you can serve with standard web servers.

I did not personally have used it, but I heard that hugo works well and is used 
a lot. I personally have used gravcms, which is based on PHP.

You can easily combine this static generators with some cron job and it should 
work for our existing setup by just adding another path to the apache.
In my experience this is easier as having another app to deploy, monitor and 
frequently update.

Cheers,

Henning

From: sr-users  On Behalf Of 
Daniel-Constantin Mierla
Sent: Tuesday, May 10, 2022 8:29 AM
To: Seven Du ; Kamailio (SER) - Users Mailing List 

Subject: Re: [SR-Users] Info: converting dokuwiki content to markdown files


Thanks, I will check them.

Ideally it is an app that can run on or behind a http server/proxy and serve 
html pages generated from the .md files directly from the folder with the clone 
of the github repo. But maybe I ask too much and adapting the wiki structure 
for a static site generator from .md files is enough or even better.

Cheers,
Daniel
On 10.05.22 00:28, Seven Du wrote:
We'd like to help.

Select one from Jekyll, Hugo and TailwindBlog

Jekyll: Ruby based https://jekyllrb.com/, can directly convert to html by github
Hugo: Go based,  can also auto covert to html 
https://gohugo.io/hosting-and-deployment/hosting-on-github/
TailwindBlog: Next.js based 
https://github.com/timlrx/tailwind-nextjs-starter-blog

We built a few websites with the TailwindBlog recently and it looks very good. 
But as all JS projects, you have to download a giant deps of node_modules and 
build locally manually to generate static html pages, we haven't found how to 
do it automatically, since our updates are not frequent, we are ok to do it by 
hand.

There may be other options. Anyway, look and discuss, as long as it's 
determined we can help to build.

As a reference, these are sites we just built recently:

- https://xswitch.cn/
- http://rts.cn/



On Mon, May 9, 2022 at 8:11 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:
Hello,

it was discussed a couple of times during the past Kamailio development
meetings and several days ago the works started to convert the Kamailio
Wiki content to markdown format and host the files on Kamailio
github.com organisation.

The Dokuwiki engine has served us very well during more than a decade
and a half, but open editing had to be disabled many years ago due to
bad actors pushing inappropriate content. The contributors had to make a
dedicated account on our portal only for Wiki editing. More recently we
had add another layer of protection requiring to grant manually edit
permissions to newly created wiki accounts because bots started to work
around CAPTCHA and other security extensions, posting again
inappropriate content.

All these added to operational overhead, but also made it difficult for
new people to contribute, specially for small editing to fix typos or
add usage examples.

Thanks to Kenneth Stowe, who undertook the first big effort of
converting the Dowkuwiki files to markdown format, we are now in the
position of moving further with the plans of using github for hosting
the content of the wiki and enable easier contributions via pull
requests. The history of changes done via Dokuwiki show up now as git
commits.

The github repository for the wiki content is available at:

  * https://github.com/kamailio/kamailio-wiki

It is still work in progress, therefore we ask for the help of community
to speed up the conversion, among the tasks that need to be done:

  * convert relative links between wiki pages – the conversion tools
used relative paths without file extensions, like:

[Install Kamailio v4.4.x From GIT](/install/4.4.x/git)

They have to be converted to relative path with .md extension in order
to be able to browse directly :n the github.com portal — 
practically the
leading / has to be removed and .md added at the end, like:

[Install Kamailio v4.4.x From GIT](install/4.4.x/git.md)

  * some section heading markers were not detected/converted, onee may
notice many equal signs (=) around a section name, it has to be replaced
with the appropriate markdown format based on hash signs (#). For example:

=== Install And Maintain Kamailio v4.4.x From GIT ===

Should be converted to:

# Install And Maintain Kamailio v4.4.x From GIT

  * some Dokuwiki paragraphs used special formatting based on plugins,
for example the notes, warnings, … had special colors. The common
markdown format does not specify a syntax to color the text, the propose
solution is to use emoji at the start of the paragraph to signal its
special purpose. For example, the Dokuwiki content:

//IMPORTANT: Content for older releases than 3.2.0 is
available at the **Old Wiki Site**://

Has to be transformed to:

:fire:*IMPORTANT: Content for older releases than

Re: [SR-Users] Info: converting dokuwiki content to markdown files

2022-05-10 Thread Daniel-Constantin Mierla

Thanks, I will check them.

Ideally it is an app that can run on or behind a http server/proxy and
serve html pages generated from the .md files directly from the folder
with the clone of the github repo. But maybe I ask too much and adapting
the wiki structure for a static site generator from .md files is enough
or even better.

Cheers,
Daniel

On 10.05.22 00:28, Seven Du wrote:
> We'd like to help.
>
> Select one from Jekyll, Hugo and TailwindBlog
>
> Jekyll: Ruby based https://jekyllrb.com/, can directly convert to html
> by github
> Hugo: Go based,  can also auto covert to html
> https://gohugo.io/hosting-and-deployment/hosting-on-github/ 
> TailwindBlog: Next.js
> based https://github.com/timlrx/tailwind-nextjs-starter-blog
>
> We built a few websites with the TailwindBlog recently and it looks
> very good. But as all JS projects, you have to download a giant deps
> of node_modules and build locally manually to generate static html
> pages, we haven't found how to do it automatically, since our updates
> are not frequent, we are ok to do it by hand.
>
> There may be other options. Anyway, look and discuss, as long as it's
> determined we can help to build.
>
> As a reference, these are sites we just built recently:
>
> - https://xswitch.cn/
> - http://rts.cn/
>
>
>
> On Mon, May 9, 2022 at 8:11 PM Daniel-Constantin Mierla
>  wrote:
>
> Hello,
>
> it was discussed a couple of times during the past Kamailio
> development
> meetings and several days ago the works started to convert the
> Kamailio
> Wiki content to markdown format and host the files on Kamailio
> github.com  organisation.
>
> The Dokuwiki engine has served us very well during more than a decade
> and a half, but open editing had to be disabled many years ago due to
> bad actors pushing inappropriate content. The contributors had to
> make a
> dedicated account on our portal only for Wiki editing. More
> recently we
> had add another layer of protection requiring to grant manually edit
> permissions to newly created wiki accounts because bots started to
> work
> around CAPTCHA and other security extensions, posting again
> inappropriate content.
>
> All these added to operational overhead, but also made it
> difficult for
> new people to contribute, specially for small editing to fix typos or
> add usage examples.
>
> Thanks to Kenneth Stowe, who undertook the first big effort of
> converting the Dowkuwiki files to markdown format, we are now in the
> position of moving further with the plans of using github for hosting
> the content of the wiki and enable easier contributions via pull
> requests. The history of changes done via Dokuwiki show up now as git
> commits.
>
> The github repository for the wiki content is available at:
>
>   * https://github.com/kamailio/kamailio-wiki
>
> It is still work in progress, therefore we ask for the help of
> community
> to speed up the conversion, among the tasks that need to be done:
>
>   * convert relative links between wiki pages – the conversion tools
> used relative paths without file extensions, like:
>
> [Install Kamailio v4.4.x From GIT](/install/4.4.x/git)
>
> They have to be converted to relative path with .md extension in order
> to be able to browse directly :n the github.com
>  portal — practically the
> leading / has to be removed and .md added at the end, like:
>
> [Install Kamailio v4.4.x From GIT](install/4.4.x/git.md)
>
>   * some section heading markers were not detected/converted, onee may
> notice many equal signs (=) around a section name, it has to be
> replaced
> with the appropriate markdown format based on hash signs (#). For
> example:
>
> === Install And Maintain Kamailio v4.4.x From GIT ===
>
> Should be converted to:
>
> # Install And Maintain Kamailio v4.4.x From GIT
>
>   * some Dokuwiki paragraphs used special formatting based on plugins,
> for example the notes, warnings, … had special colors. The common
> markdown format does not specify a syntax to color the text, the
> propose
> solution is to use emoji at the start of the paragraph to signal its
> special purpose. For example, the Dokuwiki content:
>
> //IMPORTANT: Content for older releases than 3.2.0 is
> available at the **Old Wiki Site**://
>
> Has to be transformed to:
>
> :fire:*IMPORTANT: Content for older releases than 3.2.0 is
> available at
> the **Old Wiki Site**:*
>
> You are welcome to propose a better syntax for this kind of
> transformation.
>
>   * review config examples and evaluate what improvements can be done
> (e.g., in terms of formatting and syntax highlighting)
>
> Any of these changes do not require any C programming knowledge, nor
> much Kamailio config knowledge. Can be your

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Re: [SR-Users] Accept IP/Domain Register

Re: [SR-Users] Accept IP/Domain Register

Re: [SR-Users] Accept IP/Domain Register

Re: [SR-Users] Accept IP/Domain Register

[SR-Users] Accept IP/Domain Register

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK

Re: [SR-Users] Info: converting dokuwiki content to markdown files

Re: [SR-Users] unable to get local issuer certificate

Re: [SR-Users] Info: converting dokuwiki content to markdown files

Re: [SR-Users] Info: converting dokuwiki content to markdown files

Re: [SR-Users] Info: converting dokuwiki content to markdown files

Re: [SR-Users] Info: converting dokuwiki content to markdown files

Re: [SR-Users] Info: converting dokuwiki content to markdown files

16 matches

Site Navigation

Mail list logo

Footer information