OLE problem during transfer

General Discussion
1

There is a new bug which we were able to confirm and have Genesys looking into which has to do with OLE 5.1 functionality.

We have been using a modified OLE sample application for this testing: we have added a hold button.

Here is a call flow scenario:

  1. DN A places a call to DN B.

  2. DN B initiates a transfer to DN C.

  3. While DN B and DN C are connected with a consult call, DN A hangs up.

  4. DN B tries to place the current consult call on hold and fails.

Looking into the log, we have noticed that RequestHoldCall issued by DN B uses the ConnID of the original call and not of the consult call, which leads to an error, since original call has already hung up.

We were unable to duplicate the same problem using Active sample.

Anyone else who noticed this?

A.N.

2

This has been fixed with the later releases of OLE. A new connID will be created everytime a call is transferred or conferenced with another DN. If you would check the DN events for the two DN’s you should see the call control flow between the 2 DN’s using the connID’s. Hope this helps. ;D