Hi Joel,

I've done a traceSM and list trace tac on CM. The result is that 603 decline is passed to CM, but it looks like CM does not handle this message correct to drop the ISDN call.
So my thought was same, that it could be a bug on CM.

We have opened an SR 1-13502733249 at Avaya to check this.

Thanks,
Lars

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

Hi,

We need to develop a Realtime Speech to Text Snap-In and can't find any documentation about how to receive the Media Stream from AMS.

Any Hints?

Thanks,
Lars

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

We need to be able to display the forwarding and redirection Information (SIP History-Info) to the JS-Client.

On other Phones and Clients you can see for example the redirecting user or the VDN which was called originally.

But we don't see that with JS-Client. In SDK there is no way to get the History Info out of SIP Invite.

Any Idea?

Thanks,
Lars

SOLVED!

Solution is quiet simple.

Just set value "Privacy: id" with OutgoingSipMessageListener at SIP Request.

AVAYA, why this is not documented anywhere?

Please provide a documentation about these and other features.

Thanks,
Lars

Hi,

We need to develop a Snap-In to Block CPN Number when a dedicated number is dialed.

The CM feature CPN-Block works fine. But the only difference in a traceSM we see is From: "Display Name" instead of "User Name"
and from: "anonymous@anonymous.invalid" instead of from: 344@engelbart.local

But when we do this with a Snap-In the provider replaces an invalid number by the PBX Main Number.
When using CM feature CPN-Block the trace looks identically but the called party see just "private number"

Question is, how can we block the calling party number with a snap-in?

Thanks,
Lars

SDK_IDMS_Package wrote:Hi Lars,

the infrastructure requirements for each package are outlines here:

https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/introduction/

currently, the CIS package requires Oceana.

Best Regards,

IDMS Package Support

Hi,

That answers not really my questions.

What part of Oceana is required to be able to handle Agent Features with the JS Client SDK?
The Customer has CM, SM, SMGR, Breeze, AMS, AADS and AAWG in place.

Thanks,
Lars

Hello,

for a project we need to build a Web-Client with integrated Callcenter (Agent) features for a simple 15 Agent CC Elite Call Center.

Now we struggle if it is possible or not. In the Overview is pointet that Customer Engagement functionality is available only with Oceana, but that is a massive overkill for this customer.

The question is, are the Breeze Connectors for CC Elite available without Oceana, or can this be done with ECC Snap-In?

Thanks for a fast response,
Lars

We have an AES but I'm not sure if we need to use it for this functionality.

So the Server Architecture for this Scenario requires to have SM, CM, Breeze and maybe AES in HA on both sites, right?

SM = N+1 - active-active
CM = SC - active-passive
Breeze = 1 Cluster with 1 server instance on each site
AES = GeoRedundancy (if required)

We could check the incoming call for CC if the same caller has already called within the last hour and route it to the same Agent if not route it to the normal Call Flow. For this I guess we don't need AES.

We have a request for a kind of "Last Agent" Snap-In for CC Elite in a High Availability Scenario.

It is planned to have a Main Site with CM Duplex and a Breeze Cluster with one Server at this site.
At the Branch Site there is a CM Survivable Core Duplex (ESS) with a second Breeze Server in the same Breeze Cluster.

Can Breeze handle to use the Survivable Core Server for CC Elite routing when the WAN to Main location is down?
How can we realize these kind of high availability?

Thanks,
Lars

Hello,

We have several projects where we need to handle internal calls but at the moment it is not supported with Breeze.

For example to manage forwardings or redirections based on the caller ID. In bigger companies there are lot of internal calls and we are not able to handle them.
Or managing calls when a service number is called, play announcements and so on.

Is it possible to use an explicit application to handle the internal calls?
How is Explicit Application Sequencing configured in SMGR and Breeze?

Thanks,
Lars

Thx Craig, that was the point!

It seems that after the SP installation it was disabled, while before it was enabled.

Hello,

all http links to "http://192.168.0.223/smsxml/*" are not working, only https is working.

But then in the wsdl file all links are there with only http and not https.

Any Idea to enalbe the http access?

SW Version: 7.0.1.0.2.15-0

Thanks,
Lars