> > I tested it for REGISTER, and it seems to break if the registrar sends e.g.
> > a 4xx with no contact back, causing the log line
> > ```
> > ERROR: topos [tps_storage.c:1407]: tps_db_load_dialog(): invalid dlg uuid
> > provided
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Is this something you've experienced, @toharish ?
>
> Thinking of it: if the Contact is not handled by topos, where is the lookup
> key `cparam_name` stored? Could it be that this only works with
> `contact_mode=2`? If so, could you please provide a full example to
> reprooduce it?
ERROR: topos [tps_storage.c:1407]: tps_db_load_dialog(): invalid dlg uuid
provided ,This error was noticed before the last commit [9769806]. After this
update it was fine. I have tested with more than 135000 active registrations
and many failures.
I have used contact_mode=1. In this case contact is stored but not replaced.
This can be further worked out to replace the contact, however I felt it may
vary based on the user requirement, hence it was left to the users to modify it
in the kamailio script as required.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3766#issuecomment-1992152386
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3766/c1992152...@github.com>
_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
