> I would also say that at this point, almost all classical uses of MI
> that I know of can be met with RPC.
Alex,
Did you see my message about pua_mi? Is there now rpc version of it that
I have missed to notice?
-- Juha
___
sr-dev mailing list
> More or less what I want to ask here is whether the forking of the other
> children should wait until the event_route[core:worker-one-init] is
> finished (e.g., what is done in this event route is important before any
> sip packet is routed) or just leave it like it is.
I need htable
Olle E. Johansson writes:
In addition: Xavps are not as well documented as avps. We need to add
something. There's a wiki page with a proposal from Daniel, but I
don't know if it documents the way it turned out in the code.
yes, looks like currently both xavp api doc and xavp pseudo var
wiki devel doc says about avp value:
Generic data value
It allows to store any type of data built in shared memory.
but current modules that use xavp don't seem to do so.
perhaps the wiki text is not up to date. it also uses api function
xavp_add, which does not exist.
and even if the doc
as i mentioned, my proxy is crashing at timer after transaction when
trying to free xavps:
(gdb) where
#0 xavp_destroy_list_unsafe (head=0xb4b07210) at xavp.c:354
#1 0xb68e2283 in free_cell (dead_cell=0xb4b065a8) at h_table.c:240
#2 0xb68fd7c9 in wait_handler (ti=1310418435,
i got rid of the crash by changing
xavp_rm(xavp, xavp_list);
calls to
xavp_rm(xavp, NULL);
where xavp_list is
xavp_list = xavp_get(contacts_avp, NULL);
i.e., pointer to the first xavp with the given name, and xavp is also
pointer to the first xavp in the list.
looks like
if an UA registers an ar two times with same +sip.instance and reg-id,
will registrar replace the earlier one with the new one? this kind of
thing can happen, for example, when the UA has lost connection with
outbound proxy and re-registers.
based on what i have understood from the ob rfc,
i'm trying to use xavps in new version of t serial functions and have
a couple of questions:
- when xavp value of type SR_XTYPE_STR is added using xavp_add_value
function, do i need to make a copy of the string using pkg_malloc? in
normal avps this is not needed, but for some reason a copy
