RajeshChandrashekar wrote:Hi,
Could you please share the rules configured on Breeze Implicit user profile ? and Engagement Designer routing rules.
Also please let us know the call scenario you are trying what is calling number and called number.



Thanks,
Rajesh

RajeshChandrashekar wrote:I believe the implicit rules you have configured on breeze Implicit user profile(SMGR-->Avaya Breeze-->Configuration-->Implicit User Profile) could be causing this , the instance might be created due to orig and term sequence .

You could try adding Breeze Implicit user profile with onlly called number, so just use the rule for called
Called Number 19171126703 11 11 and delete the calling number rule.


Thanks,
Rajesh

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.

	@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();

	}