Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » Avaya Breeze™ » Forward & Redirect Information for JS-Client   XML
 
Author Message
Lars



Joined: 28/04/2016 10:42:02
Messages: 13
Offline

In JavaScript Client we are not able to see the called VDN nor any redirect Information.
Maybe its a but of JS-SDK but we tried to have a Snap-In for that to display the called VDN to the JS-Client.

Here we have a problem that Breeze is not triggering the Snap-In.

CallFlow:

External Caller from ISDN calls a VDN 3700, Vector does a queue to Skill 5900 and routes call to an Agent 5701 logged in at Extension 3701.

EXTERNAL USER -> ISDN G430 -> CM add prefix-> SM -> Breeze -> CM -> VDN -> Agent -> Extension -> Breeze...

When the call comes first time to Breeze, we don't have History-Info what is logical.
When call comes to Breeze 2nd time we see History-Info in SIP Invite, but Snap-In is not triggered to read out that Info.

Is that Scenario / Routing supported?

How can we get the History-Info Out of the Invite???

Thanks,
Lars
JoelEzell



Joined: 15/11/2013 10:26:35
Messages: 449
Offline

Hi Lars, sorry for the delayed response. I was in meetings all of last week. I don't how Breeze is invoked the second time. Is this because Breeze is in the called party sequence vector using implicit sequencing? If so, we unfortunatley don't support that flow. This flow would have Breeze applications trying to execute logic when CM has already completed its term processing. This is why the snap-in isn't invoked. This is why our documentation states that Breeze sequencing is only supported on trunk to station or station to trunk calls. We probably should also explicitly exclude calls on the "other side" of the Vector (between VDN and agent).
Lars



Joined: 28/04/2016 10:42:02
Messages: 13
Offline

Hi Joel,

Yes, the scond time Breeze is in the call flow is because of the Terminating Station Extension with existing implicit rule.

If that is not supported, how can we get and display the Called VDN Name to the Agent / Extension?

Any other idea?

Thanks,
Lars
 
 
Go to: