Re: [OpenSIPS-Users] Transactional REGISTER processing with 2.1

Hi Razvan, this is the code from SER 2.0. There is no equivalent for "s:digest_challenge" or "s:contact" AVPs as far as I can tell looking to the code in question in OpenSIPS. -Max On Mon, Feb 20, 2017 at 12:25 AM Răzvan Crainea wrote: > Hi, Maxim! > > The code you are

[OpenSIPS-Users] Transactional REGISTER processing with 2.1

Hi guys, We are underway to migrate from ancient SER-2.0.0 to more modern OpenSIPS and one of the question that is still in my TODO list is implementing transactional processing of the REGISTER requests. In the old SER we had something along those lines: route[3] { # Ensure that all

Re: [OpenSIPS-Users] Transactional REGISTER processing with 2.1

P.S. python_exec("www_authenticate") does not do any magic here, it's just figures out the right domain to use based on some business rules and then calls www_authenticate() with that parameter. On Fri, Feb 17, 2017 at 11:12 AM, Maxim Sobolev wrote: > Hi guys, > > We are

Re: [OpenSIPS-Users] Transactional REGISTER processing with 2.1

Hi, Maxim! The code you are using now should do what you request. t_newtran() returns 0 for retransmissions, therefore for the second message (retransmission) that will run the script, t_newtran() will immediately absorb the message and return without executing any further instructions.