All,
we have migrated a customer to Webgateway R3.5.

After migration we got as follows:

calls from the client to external did go

internal calls from the client did not go (station and agent)

calls from the client to a VDN go but are not getting distributed

station and agent login went without problems

Customer has the following setup

Breeze 3.4

Breeze Client SDK 3.4

Within the Product Compatibility Matrix we have seen that Breeze Client SDK 3.2 is specified. Is this correct and we really have to downgrade?
https://secureservices.avaya.com/compatibility-matrix/menus/product.xhtml?name=Avaya+Aura+Web+Gateway&version=3.5

Thanks for your feedback
Dirk

Can Breeze recognize the lifting of the telephone receiver?

All,
We got the feedback from AVAYA SE that extensions logged in via the Webgateway can not be monitored by AES and as such AVAYA WFO can not perform call recording for these extensions.

Can you please confirm this?

Thanks
Dirk

Perhaps a kind of stupid question. How many stations can register simultaneous at the Web Gateway?
Is there any limitation?

Hello Artem,
thanks for the hint, we have implemented as follows:

if (call && !call.getUserToUserInfo()) {
????????call.startRinging();
?}

This is now working fine on our environment.
Client stays ringing till Rona time gets activated.

For some reason this is still not working on the customer environment.
Call is still within the call list of the client, but call is not longer active.
So perhaps an issue between the AAWG call list and the CM?

Customer is on AAWG 3.4 our is 3.1
Rona is deactivated on customer side.

Could this be an issue?
Dirk

Hello Tsarev,
Thanks for your feedback.

The problem is when a call is coming in thru a VDN and is not answered by an agent within that skill group within a certain time the call goes into queue and is then assigned to the next available agent. This continues until an agent upon receiving such a call answers within the given time (RONA settings). At the customer side this time is at the moment 5 seconds - around 2 times a ringing tone.

When we trace the call we can see as follows:
- When answering the call with sip agent for desktop we can see the call set-up as expected: 100 Trying, 180 Ringing, 200 OK.
- When trying to answer the call with our JavaScript SDK based Soft Client we do not see this 180 Ringing Status. Therefore after 5 seconds the RONA is getting in place (see above).

Is there a way that we can set this 180 Ringing Status of the call via the JavaScript SDK?

Thanks Dirk

All,
we actually have the issue that a 180 ringing status (RONA) is not handled by the Webgateway.
Is this a supported feature in the JavaScript SDK?

Thanks Dirk

Is there a way to find out via Breeze if the called party is busy or not available (mobile phone without network coverage etc.) using the network operators feedback?

Hello Team
For one of our SnapIns we need to know if a call is incoming or outgoing.

First we are logging some events about the call using a call intercept:

logger.info(
format("UCID %s: Call from %s to %s. isCalledPhase: %s, isCallingPhase:
%s",
call.getUCID(),
call.getCallingParty().getHandle(),
call.getCalledParty().getHandle(),
call.isCalledPhase(),
call.isCallingPhase())
);

For call.isCalledPhase() and call.isCallingPhase() we are getting always TRUE as return value.
This is for incoming and outgoing calls.

Can this be a routing issue or how Breeze is involved in the call flow?

Thanks for some feedback.

We are facing issues with WWS.
Our solution has been build against Web Gateway 3.1.02

Since customer has updated to release 3.3 we are facing issues with the websocket connection (WSS) .


The HTTPS (POST) connection to provide credentials to the Avaya Web Gateway seems to work without any problems.
But the creation of the WSS connection to the Avaya Web Gateway doesn't establish. So no signaling is possible between client and Avaya Web Gateway.

Has there been any change on Web Gateway 3.3?

Thanks

While trying to join a Scopia Bridge we are getting the following error using the Java Script Sample Client:

{"error":[{"errorCode":"ERC_INTERNAL_SERVER_ERROR","displayMsg":"Internal server error","errorMsg":"There is no socket connection ready in local socket server."}]}

Within the Sample Client the Scopia Brigde Checkpoint is selected and the Brigde ID is used.

Can you please give us an indicator where this error is coming from?

Thanks

Hello Team,
is it possible to intercept and controll incoming calls to a AVAYA Meet Me Conference Number?
We have to mute / drop users in certain cases.

Thanks
Dirk

Hello,
we have to create CDR giving the following additional information:
- Duration of Ring Time
- Not answered /missed Calls

For external calls this is working fine using AVAYA Breeze.
Internal call we can not monitor.

Could the Engagement Call Control Snap-in be an option?
Can we create CDR using this Snap-In?

Thanks
Dirk

Hello Team,
perhaps we are a little bit blind at the moment.

We need to find out the IP Address of the phone initiating a call.
Actually we can not see this IP Address within the SIP Header.

Devices are both H.323 and SIP as well as One-X Communicator

Any hints?

Hello Joel,
customer has installed the latest patch - it is now working.

Regards
Dirk