RajeshChandrashekar wrote:Let me take an example
Calling party is 1000 and called party is 1001
now if we specify both calling and called party in Implicit user profile rules, this means that for both calling and called party the sequencing should happen .
When calls comes to SM, SM sends it to breeze for sequence, in this case Breeze(EngagementDesigner) would be sequenced in both the numbers, one time for Calling(1000) and the other time for called (1001) Because EngagementDesigner would be sequenced on both orig and term and you have a rule in ED saying if called party is 1001 then the instance will be invoked one time when 1000 dials the number which will be orig and in term sequence for 1001, so you will be seeing 2 instances.
so we recommended to use just the called party sequence.
thank you for the explanation. Now that I have that issue with engagement designer resolved. I created a simple call intercept svar snapin which logs the called number.
@Override
public final void callIntercepted(final Call call) {
String calledParty = call.getCalledParty().getHandle();
if(calledParty == "19171126703") {
logger.fine("Call to 19171126703 was intercepted ");
}
// call.suspend();
}
so, when I call the number, the workflow from engagement designer gets initiated once, the timer pauses the call for 10 seconds then allows call.
at the same time, the SDK snapin intercepts the call and shows the log, but as soon as the allow call initiates in the engagement designer workflow instance, the SDK snapin gets triggered again.