Bug with TServer and Attach Data?

[Vic]

Hi,

I am using TServer 7.0.206 for Avaya and I came across the following problem:

attach data is not being delivered along with EventRinging, instead it is delivered right AFTER it with EventUSerDataChanged

Here is the flow:

IVR>twostep ransfer>VDN1(Attach data 1,2,3)>VDN2(attach data 4,5,6)>agent

we are using LDS, but I do not think it matters... (at least not yet)

URS is set to routconsultcall = true

The problem is that when the call arrives at agent's place, EventRinging contains attach data 4,5,6 no prob, but it only has 1 for attach data from VDN1 and no 2 or 3. The problem disappears if I add 2 second delay before VDN1, thus making sure that IVR completes the transfer before routing the call.



What makes things weirder:

1. when call arrives at VDN2, EventRouteRequest contains attach data 1,2,3 no problem.

2. EventRouteUsed from VDN2 to agent contains 4,5,6 and only 1
3. EventPartyChange for two step happens somewhere during VDN1 or during VDN2, but ALWAYS before URS sends the call to the agent.
4. Desktop is informed of 2,3 come AFTER EventRinging through EventUSerDataChanged (100 ms after original EventRinging)

What is going on? Has anyone seen this behaviour before?

It seems like TServer has trouble with handling consult call attachdata. I am using "joint" for consultcall attach data, therefore, calls added to consult call should also be reflected in the original call.

Any ideas?
Vic

[ecki]

Hi Vic,

Obviously the problem is related to consult call. I think the two last requests to attach data to conuslt call connid failed because coincidentally in the same time the consult call ceased to exists from Switch point of you as well as from TS point of view. Thus TServer could not handle these requests and I would guess you will find in logfile EventError as a response for both reqeusts. Just check it. But I could be wrong as well.