Losing attached data on meridian

[MBoertien]

At the moment i'm working with a meridianswitch and when i do a mutetransfer to a routingpoint the call gets routed, but the attached data is lost. When i look in the tserver log file it creates a new connection id and the last event with attached data is Eventreleased. Does anyone have any idea how to solve this problem? Thanks in advance...

[Akiko]

Did you find out the option to prevent a new connid being generated between routing points?

Akiko

[MBoertien]

I managed to find the option, it works fine now......

[Victor]

What was it?

[Kent]

Hello, MB! How are you?

Inquiring minds want to know what is the option?

[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 ?

[mboertien]

Victor, i asked the question to Genesys support and they came with this answer. I didn't get it either, but it does have something to do with the connection id as well. I think this option makes it check if attached data was there, and then if it is it also makes sure this information stays with the call. When i changed the option the calls got routed through with the attached data still there....

[Keth]

There is an option in TServer which defines whether or not a new call is being created when a call is passed from routing point A to routing point B. I will check. I think it was rr something ot scd something. Sorry for not being able to give any mroe info. I will try to get the info by tomorrow

[mboertien]

The option is : dtacleanuporig r = off