[OpenSIPS-Users] Cannot get registration to work with v3.2.8??

Hi. Have been a long time OpenSER user in a production environment. I managed to convert to OpenSIPS v3.2.8 on a CentOS 7 system and is working based on IP authentication however, I just cannot get sip registrations to work that used to work fine with OpenSER. I'm using a SPA112 running

[OpenSIPS-Users] OpenSIPS 3.2.7 tracer module for sip dialogs leads to an endless loop

Hi there, I try very basic scenario with tracing sip dialogs in OpenSIPS 3.2.7, and this scenario leads in an endless loop inside Opensips for SIP messages. Maybe someone is similarly affected or can point to the error on the route scenario? I use out of box residential configuration. I read the

Re: [OpenSIPS-Users] dialplan out_var

Yes. exactly I apologize for my stupidity вт, 30 авг. 2022 г. в 17:12, Stas Kobzar : > Hi, > $fn is from name and name maybe quoted in the header value. > Try to use $fU to have username part (actual number) > > On Tue, Aug 30, 2022 at 9:00 AM Bogdan-Andrei Iancu > wrote: > >> Again, >> >> your

Re: [OpenSIPS-Users] dialplan out_var

Hi, $fn is from name and name maybe quoted in the header value. Try to use $fU to have username part (actual number) On Tue, Aug 30, 2022 at 9:00 AM Bogdan-Andrei Iancu wrote: > Again, > > your DP rule is performing NO change over the input. The whole input, as > received, it provided as

Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module

Hi Bogdan, Thank you very much for the help, I have located the issue in our script. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 30, 2022 9:20 AM To: Li Cai ; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC

Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module

Hi Li, The INVITE in #77 is an initial INVITE, connecting to a new party (as a result of the bridging), so the TO hdr in that INVITE is dictated by the B2B logic - as you can see the TO URI is the same as RURI, pointing to the new party in the bridging. Regards, Bogdan-Andrei Iancu

Re: [OpenSIPS-Users] dialplan out_var

Again, your DP rule is performing NO change over the input. The whole input, as received, it provided as output. And the quotes you see in the output value are part of the input value. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS

Re: [OpenSIPS-Users] Dispatcher within a K8s environment

Hi Jonathan, You mean something similar to that option in drouting ? If so, yes, it would make sense IMO. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 27-30 Sept 2022, Athens

Re: [OpenSIPS-Users] opensips crash while using siprec module

Hi, Hitesh! You are using both dialog and B2B for the same call - this is not supported in OpenSIPS. Moreover, SIPREC is not working with B2B. So you either have a setup with dialog (where siprec can be enabled) or b2b (siprec is not available). Best regards, Răzvan Crainea OpenSIPS Core

Re: [OpenSIPS-Users] dialplan out_var

that's the point. there are no conversions, but quotes appear вт, 30 авг. 2022 г. в 09:26, Bogdan-Andrei Iancu : > Your DP rule is doing nothing, as transformation - it is matching > everything and returning it as output..so not sure what are your > expectations here. > > Regards, > >

Re: [OpenSIPS-Users] dialplan out_var

Your DP rule is doing nothing, as transformation - it is matching everything and returning it as output..so not sure what are your expectations here. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 27-30 Sept 2022, Athens