[SR-Users] I found bug in sipdump module.

2021-07-05 Thread woenho
 Line 578    at    Sipdump_mod.c- Error source ->case 8:  if(strncmp(in->s, "src_port", 8)==0)sp->pvp.pvn.u.isname.name.n = 8;  if(strncmp(in->s, "dst_port", 8)==0)sp->pvp.pvn.u.isname.name.n = 9;  else goto error; correct

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread Dmitry Sinina
https://github.com/yeti-switch/sems - yes https://github.com/sems-server/sems - no On 05.07.21 16:11, E. Schmidbauer wrote: Does SEMS support ICE for media negotiation? On Mon, Jul 5, 2021, 8:45 AM Dmitry Sinina > wrote: There is also SEMS forked by yeti

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread E. Schmidbauer
Does SEMS support ICE for media negotiation? On Mon, Jul 5, 2021, 8:45 AM Dmitry Sinina wrote: > There is also SEMS forked by yeti-switch project > https://github.com/yeti-switch/sems It has a lot new features but it is > not fully compatible with old modules. > On 05.07.21 11:42, Daniel-Constan

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread Dmitry Sinina
There is also SEMS forked by yeti-switch project https://github.com/yeti-switch/sems It has a lot new features but it is not fully compatible with old modules. On 05.07.21 11:42, Daniel-Constantin Mierla wrote: On 05.07.21 10:18, Jon Bonilla (Manwe) wrote: El Mon, 5 Jul 2021 06:26:12 +

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread David Villasmil
I’m using freeswitch in a very simple way, it receives a call, makes an api http request, and based on the response does some prefixing, etc. it also provides simple conferencing (three-way call) and provides a very detailed CDR. I’m wondering if I could replace it with SEMS. On Mon, 5 Jul 2021

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread Daniel-Constantin Mierla
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote: > El Mon, 5 Jul 2021 06:26:12 + > Henning Westerholt escribió: > >> Hello Alex, >> >> yes, sipwise maintain a fork of it. >> One related question, the last “official” release 1.6 of sems was in 2015 (at >> least in public github). Are people just

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread Henning Westerholt
Hello Jon, thank you for the explanation, really helpful. I was suspecting a situation like this but did not follow SEMS that closely (it's not used a lot from our customers). Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com -Origi

Re: [SR-Users] Sipwise SEMS

2021-07-05 Thread Jon Bonilla (Manwe)
El Mon, 5 Jul 2021 06:26:12 + Henning Westerholt escribió: > Hello Alex, > > yes, sipwise maintain a fork of it. > One related question, the last “official” release 1.6 of sems was in 2015 (at > least in public github). Are people just using the development version in > production then, also

Re: [SR-Users] SECSIPID Identity Decode ( crash when sending reply)

2021-07-05 Thread Daniel-Constantin Mierla
I assume this was mistakenly replied in the wrong thread, instead of the message with subject: [SR-Users] crash when sending reply. With the async insert for acc module, the reply should have been released quickly, not waiting in the SIP worker process for insert to happen. Could you see the respo

Re: [SR-Users] SECSIPID Identity Decode

2021-07-05 Thread Daniel-Constantin Mierla
Hello, On 02.07.21 22:40, Daniel W. Graham wrote: > > Found it. record_route bit me. > >   > > ERROR: [core/msg_translator.c:3355]: sip_msg_apply_changes(): > cannot apply msg changes after adding record-route header - it breaks > conditional 2nd header > >   > > Assuming not but thought I’d ask,