merged-user-data

[victor]

Hello,

can someone please explain to me merged-user-data? I am not very clear as to all those options available for it? What happens when you have the same key but different data? Which option does what? What happens if you add a new key during consult call?

Thanks,
Vic

[Timur Karimov]

Hi, Vic!

It's easy =) Based on value of this options:
main-only = T-Server attaches user data from the remaining call only.
merged-only  = T-Server attaches user data from the merging call. 
merged-over-main = T-Server attaches user data from the remaining and the  merging call. In the event of equal keys, T-Server uses data  from the merging call. 
main-over-merged = T-Server attaches data from the remaining and the merging  call. In the event of equal keys, T-Server uses data from the  remaining call.

But, the valuse of the merged-user-data option setting does not affect the resulting data for merging calls if  the consult-user-data option is set to joint.
For this case T-Server stores user data for an original call and a consultation call in one  structure. The user data structure is associated with the original  call, but the parties of both the original and consultation calls can  see and make changes to the common user data.

All of this things based on T-Server reference guide and my practice is confirm it.

WBR Thaler.