Hello,
I confirm that this issue has been:
- patchedto master (4efb386) branch
- backported to 4.2(2a5d17b) branch
- backported to to 4.3 (f5d11d1) branch
Thanks to Daniel for providing the patch
Luca
Il 13/07/2015 11:32, Daniel-Constantin Mierla ha scritto:
Hello,
it is better to ope
Hello,
it is better to open an issue, making sure it doesn't get lost, although
it is in my short list to investigate, priorities can change unexpectedly.
Cheers,
Daniel
On 13/07/15 10:59, Luca Mularoni wrote:
> Hi Daniel,
> I didn't get if I have to open an issue to GitHub for usrloc problem.
>
Hi Daniel,
I didn't get if I have to open an issue to GitHub for usrloc problem.
Regards
Luca
Il 07/07/2015 11:55, Luca Mularoni ha scritto:
Il 07/07/2015 11:23, Daniel-Constantin Mierla ha scritto:
On 07/07/15 11:19, Luca Mularoni wrote:
Found! Thanks for the advice, pv_xavp_print() is a
Il 07/07/2015 11:23, Daniel-Constantin Mierla ha scritto:
On 07/07/15 11:19, Luca Mularoni wrote:
Found! Thanks for the advice, pv_xavp_print() is a not documented
function of pv module.
Oh, interesting. A bug should be filled on github not to forget about
it and document in near future.
On 07/07/15 11:19, Luca Mularoni wrote:
> Found! Thanks for the advice, pv_xavp_print() is a not documented
> function of pv module.
Oh, interesting. A bug should be filled on github not to forget about it
and document in near future.
>
> Below a printout of 'ulvals' struct before invoking save(
Found! Thanks for the advice, pv_xavp_print() is a not documented
function of pv module.
Below a printout of 'ulvals' struct before invoking save():
all stuff seems to be correclty filled...
Do You need any other test/data?
INFO: [xavp.c:496]: xavp_print_list_content(): + start XAVP
list
On 03/07/15 16:47, Luca Mularoni wrote:
> Hi Daniel,
> I would propend for a usrloc issue, because if I print just created
> xavp (below chunk of real code I'm using for debugging) before invoke
> save() func:
>
> xlog("REGDATAGET - FromUser [$xavp(ulvals[0]=>FromUser)]\n");
> xlog("REG
Hi Daniel,
I would propend for a usrloc issue, because if I print just created xavp
(below chunk of real code I'm using for debugging) before invoke save()
func:
xlog("REGDATAGET - FromUser [$xavp(ulvals[0]=>FromUser)]\n");
xlog("REGDATAGET - FromDomain [$xavp(ulvals[0]=>FromDomain)]\n
Hello,
hmm, can you print the xavps just after you added them before
save(location)? Trying to spot where the issue is, in storing inside
usrloc or outside in the xavp framework. There should be some function
to dump all xavps, iirc.
Cheers,
Daniel
On 02/07/15 23:09, Luca Mularoni wrote:
> Hi Da
Hi Daniel,
yes, when I use db_mode 2 [1 not tested], after 'timer_interval' seconds
(30s in my case),
data are passed to location_attrs table (through insert query for first
registration and then delete/insert for refresh)
but just first and last attribute are passed (i.e. in db table I can
fin
Hello,
when you use db_mode 1 or 2, do you see the values in location_attrs
database table?
Cheers,
Daniel
On 02/07/15 12:45, Luca Mularoni wrote:
> Hi All,
> I'm using kamailio 4.2.5 (compiled from source and aligned up to
> commit [00a36ae07c587992d6486277ce2e9ae6c009685f]).
> In order to enri
11 matches
Mail list logo
