Where does WDE collect the consultuserdata AttributeExtension?

[PFCCWA]

hello,
i am trying to work out where WDE (v8.5) is changing an attributeextension for consultuserdata.
So in our call scenario, inbound call is answered then the agent initiates a two step transfer.
but when they do this, i see an AttributExtention for 'consultuserdata'='separate'.  i cannot find where this is configured as the update seems to be limited to just WDE (other agent desktops) do not experience it.
The TServer applications (avaya cm) have the option as 'joint' which is what i expect it to be if anything but not sure where this option is being taken from in WDE.

thanks

[Kubig]

AFAIK this was introduced into WDE few versions back - so, now the WDE sends natively ConsultUserData with value "separate" which takes higher priority than configuration on app level (TServer).

[PFCCWA]

[quote author=Kubig link=topic=12228.msg54623#msg54623 date=1642176417]
AFAIK this was introduced into WDE few versions back - so, now the WDE sends natively ConsultUserData with value "separate" which takes higher priority than configuration on app level (TServer).
[/quote]

Hello,

just returning to this as it is causing us issues.  the issue being we need the consult user data to match the tserver option (=joint).
is there a way to resolve it through a WDE application option?
or will need custumization?

thanks.

[Kubig]

There is no such configuration option on WDE (unfortunately). You need to achieve it via WDE customization or in case you transfer via routing, you can override it via ExtensionUpdate within routing