Genesys CTI User Forum > Genesys CTI Technical Discussion

Losing attached data on meridian

<< < (2/3) > >>

James:
Is this the option you are looking for?

'consultuserdata'

default is 'separate'
Options are separate, inherited, joint
Becomes active immediately when changed

Description
Specifies the method that will be used to handle
user data in a consultation call.
When set to 'separate', user data for original and
consultation calls are stored in separate
structures.
When set to 'inherited', user data is copied from
an original call to a consultation call when the
consultation call is established; after that, user
data is stored separately for the original and the
consultation call.
When set to 'joint', user data for an original call
and a consultation call is stored in one structure.

MBoertien:
I'll try to tell you as soon as i can (don't have it with me at the moment)......

Victor:
No, I do not think this is the right one, because it only works with inbound call to consult call and, maybe back. This is call type 2 to call type 1.

The problem we have here is when a call is routed from one CDN to another, TServer generates a new connid for each leg of the call. And, correct me if I am wrong, the call is of type 2 (inbound), so consultuserdata is not the right approach.

I do recall having the same problem about a year ago, I think it was one of the scd options. Aargh, I do not even remember how I found it!

Vic

James:
I wasn't sure if this was the same if you have fast transfer set to '2step', as recommended for meridian release 23.

Victor:
That's it! But how in the world did you find it? Looking through the manual for this options, I found only the following description:

dtacleanuporig r: Specifies whether TServer will check the
Origination DN information after receiving the RouteRequest message.

How is it related to creating a new ConnID????!!!! Am I the only one confused ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page