Hello Calvin,
Looks like your coerecing a float into an integer field. I think it's your
delay field. What do you expect to happen here? I mean that seriously. If
the delay field is an integer, you can't put anything but an integer in it
if you have no access to change the database type.
Alternati
It appears that OpenSIPS is assuming an incorrect integer data type on a
field that is a floating-point value. I have no access to change the field
type in the database. What can be done?
Server version: 10.2.31-MariaDB MariaDB Server
Query and response attached
async(avp_db_query("call lrn.full
i do
if(isflagset(8))
{
setbflag(3);
setbflag(NAT);
setbflag(7);
}
save("location");
exit;
I have modparam("usrloc", "nat_bflag", "NAT") & modparam(
Have you tried setting the bflag right before save()’ing during the
REGISTER?
On Sun, 8 Mar 2020 at 23:34, Jehanzaib Younis
wrote:
> Hi David,
>
> I have one contact in the Usrloc
> Do you think it could be a timeout issue? or i should use
> remove_on_timeout_bflag option?
>
> On Mon, Mar 9, 202
Hi David,
I have one contact in the Usrloc
Do you think it could be a timeout issue? or i should use
remove_on_timeout_bflag option?
On Mon, Mar 9, 2020 at 12:31 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Make sure you don’t have 2 contacts
>
> On Sun, 8 Mar 2020 at 23:22, Jeh
Make sure you don’t have 2 contacts
On Sun, 8 Mar 2020 at 23:22, Jehanzaib Younis
wrote:
> but i have strange issue.
> nathelper keep on sending the OPTION to old IP:PORT. As soon as the new
> REGISTER comes in, it should only send the option to the latest one.
> For example, I see OPTION going
but i have strange issue.
nathelper keep on sending the OPTION to old IP:PORT. As soon as the new
REGISTER comes in, it should only send the option to the latest one.
For example, I see OPTION going to xx.xxx.xx.xx:25001 and opensips keep on
sending to this after every 120 seconds (which is my sett