Author Message
Wilder
Joined: Aug 6, 2018
Messages: 29
Offline
Hello,

I have two labs where one runs an sdk snapin and a workflow instance occurs at the same time. The other lab the workflow kicks in first but the sdk snap-in only kicks in when the call is allowed by the workflow. What should be expected when a snapin and a workflow are set to intercept a call.

thanks
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Hi. Call Intercept invocations are always sequentially processed. The order is determined in the Calling/Called Party Service Invocation Order on the Service Profile page. You likely have a different order in your lab than on your customer site.

It is good hygiene in all call intercept snap-ins to include an invocation of allow, divertTo or terminate. If you don't do so, however, the call should be implicitly allowed. If that doesn't appear to be the case, you might try putting logs at the enter/exit points to your IncomingSipMessageListener and CallListener methods. It's likely that there is something within your code itself that is hanging in one of the environments.
Go to:   
Mobile view