Hi all,

I have a quick question regarding what versions of Spring Frameworks and Spring WS will work with OD 8.1.2

We have an existing OD 7.2 IVR that uses a very old Spring framework s and Spring WS library which utterly fails when run in a OD 81.2 environment (It has been recompiled as an OD 8.1.2 project and all OD runtime JARs are correct)

The Webservice connection tier will need to be re-written to accommodate the transition between Spring framework 4.x and 5.x and the corresponding Spring WS from 2.2.x to 3.1.x

Can anyone confirm the versions that are compatible?

Cheers

Thanks Fergus and Amit

I agree, the way i see this working is a webcall from a widget to a snapin to set the required outbound identity and then use callintercept to apply the preset value to the call

Hi all,

I have a couple of queries regarding Workspace Widgets!
1) is there any other documentation other than the one that is downloaded from the workspaces using the admin login. I've found that and it seems a bit lacking
2) I need to manipulate the outbound presentation number for outbound voice interactions - in a dynamic fashion (by agent choice on a call by call basis). In effect do this from within a widget

@Override  public final void callIntercepted(final Call call)

 {

      call.getCallingParty().setPresentedDisplayName("New display name");

      call.allow();

 }

Is there a way of getting access to the core Breeze API from a widget?

Thanks

Thanks for the reply Joel

Perhaps you could let me know how to get support for the IP office TAPI solution...

Sorry if this is off-topic for this forum, please point me in the direction of the correct one!

Dev env - VS6 C++ / ATL, Windows 2000

I am calling QueryInterface on a valid ITAddress interface to get an ITDivert interface. However I always get an HRESULT of 0x80004002 (No such Interface Supported)

I've looked for the ITDivert interface in OLEview - can't see it, run a search through the registry for the GUID - can't find that either. The same functionlaity doesn't work in the IP office samples either. All this suggests that a component isn't registered - but which one, from where as I have installed TAPI many times...

Any clues?

Thanks

Matt