Hi Juha,
I will try an implementation in the next days and see how we can work
with it and what else is missing.. ;)
regards,
bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
> the nat_flag will probably remain a MSG flag and not a UL flag (in the
> usrloc set of flags), otherwise you will loose the branch capability.
> So, going back to alternatives I listed:
> 1) already works
> 2) as the flags will be per contact (not per AOR), a lookup will may
> bring several contacts, each with its one UL flags. the registrar module
> will push it to the MSG flags to corresponding branch (according to
> "use_branch_flags" param).
>
> so, I see no problem in any of the cases.
ok with me as long as can use one of the usrloc flags as mediaproxy flag
that then upon lookup gets pushed into msg flags of the the
corresponding branch.
now manual reads:
1.3.19. use_branch_flags (integer)
If enabled (has a non zero value), the NAT flag for the additional
branches will be pushed in branch flags (in dset/branch
array). Otherwise it will be pushed in the message flags. In both cases,
the NAT flag for the RURI will be push into message flags.
this would then need to get extended so that also select new usrloc
flags (not just nat flag) could get pushed to MSG flags of the branch.
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
