Well, that's some great news for me on my next to last day at Avaya! I'm moving on tomorrow, and this was a good note to leave DevConnect on. Well done!

Sorry, I need to correct / clarify a few of the statements from my previous reply. First, I've been told that there isn't in fact a Breeze Application Router timer(X) that protects against failed snap-ins. If the thread returns without a snap-in having invoked allow(), divertTo, or terminate(), then the Application Router will by default allow the call to continue. If the thread never returns, then the call will not proceed.

Regarding the SM timer (Y), this timer will help in the case of an INVITE having been sent to a Breeze that is already offline. It will NOT help in the case of any INVITEs that are being processed by Breeze at the time of a failure. Breeze sends a 100 TRYING message back to SM as soon as it receives an INVITE, and this cancels the timer that SM sets to reroute INVITEs in the case of a failure. Calls that Breeze and its snap-ins have started to process but not yet completed at the time of a failure will not succeed. In fact, this window of vulnerability extends until the call has been answered (200 OK) and ACK’ed by the caller.

There are timeouts at several levels that protect against failures for calls in progress (the above information was regarding behavior during stable established calls).

The Breeze Application Router has a timeout where it will allow a call to proceed if a snap-in hasn't responded in X seconds. Session Manager also has a timeout if it sends a call to Breeze and there's no response within Y seconds. I don't remember what X and Y are, but I'll ask somebody to respond with that information.

If it's Breeze that has timed out and there is a cluster of Breeze servers, Session Manager will remove that Breeze server from the pool until it responds affirmatively to an OPTIONS message.

Regarding phones registered to Session Manager, everything here applies to SIP stations registered to SM. The big factor is whether Communication Manager is in the sequence vector for the user (and in nearly all cases, it will be).

The behavior if Breeze goes down is as follows:

* Media will continue to flow, but no further control operations (hold, unhold, transfer, conference) will be able to happen on the call
* If control operations are attempted before Communication Manager puts the call in "media preservation mode" (usually sometime between 0-10 minutes), the call will drop.
* If control operations are attempted after CM puts the call in media preservation mode, the operation will fail but media will continue to flow.

Hello. The answers to your questions are:

1) Yes, that's still the latest

2) Unfortunately this is still not supported nor planned for a future release

3) No, even though the clients would be remote from CM, they'd still be served by the same CM and therefore this counts as an intra-CM call and therefore cannot be intercepted.

4) See the "Administering Communication Manager" section in the Breeze Deployment Guide: https://www.devconnectprogram.com/site/global/products_resources/avaya_breeze/releases/3_7/docs/deploying/index.html. Don't worry if you have an earlier version than 3.7. That section hasn't changed for many releases.

Which "Designer" are you trying to use? Based on what you've said, I suspect it's Dialog Designer (Experience Portal application development) rather than Engagement Designer (Breeze web-UI workflows). If it's Dialog Designer, this is the wrong forum and I can move it to the correct forum for you.

Regarding the question on the database, we have a Cluster Database that's available for your use. I believe that it was available on 3.4, but I'm not sure. Is there any chance of an upgrade to a more recent Breeze version? If you can't find any documentation in the 3.4 developer guide, check the latest developer guide. I believe we've improved our documentation in the more recent releases.

If you are looking for traditional CTI (Make Call, Answer Call, Hold Call, Transfer Call, see call state on phones / soft clients) Application Enablement Services is what you should be looking at.

Dirk, I'm so sorry for the absurdly late response to this question. Unfortunately, there is not a way for a Breeze snap-in to leverage speech to text transcription using Nuance (or any other speech engine).

To be clear, you would do the Forward Call or Add Participant task, wait for answer, then do the new task that invokes the removeServiceFromCall API.

Hi Horaci, Breeze 3.6 added the ServiceManager.removeServiceFromCall() method. This API causes Breeze to do the attended transfer flow of Experience Portal, sending a REFER-Replaces to the caller side with the result being that Breeze is removed from the signaling path. A new ED task was added for this feature, but I'm afraid that I don't remember the task name. Hopefully Anurag can tell us what that is. I think that this will accomplish what you want.

Just to be clear, I think you're still having problems with stopping the media on a participant rather than on a call, is that right? To be honest, I'm surprised that you're not still having problems even with media on a call. The problem is that Breeze doesn't support cross-server media invocations. If a call lands on server A in a 2 server cluster, than a HTTP request comes into server B to perform some media action on that same call, the invocation will fail. You need to either redirect the incoming HTTP request to the server A (doing something like Suzhen suggested), or you need to have your snap-in on server B ask its server A instance to perform the action.

Hi, I'm not sure what you mean by CCMS database. Do you maybe mean CMS (Communication Manager reporting)? If so, we don't directly support direct access to CMS from Breeze.

Hi Octavio, for this sort of thing you wouldn't be able to use the high-level SchedConf API. Instead you'd need to use the SchedConfFactory to create a ScopiaRequest instance, and use the "raw" XML interface. You'd want to create an XML request along the following lines. Apologies that the forum tool doesn't appear to preserve indentation.

<Schedule_Conference_Request>
<RequestID>19694</RequestID>
<Conference>
<MemberId>999</MemberId>
<UserId>1</UserId>
<Number>70002</Number>
<ServiceTemplateId>BUILT-IN-AMS-AO-WC</ServiceTemplateId>
<ServicePrefix>N/A</ServicePrefix>
<AllowStreaming>OFF</AllowStreaming>
<Attendee>
<ThreeG>false</ThreeG>
<RestrictedMode>false</RestrictedMode>
<VoiceOnly>false</VoiceOnly>
<PartyInLayout>
<LayoutName>Main</LayoutName>
<PositionId>-1</PositionId>
</PartyInLayout>
<PartyInLayout>
<LayoutName>Customer</LayoutName>
<PositionId>-1</PositionId>
</PartyInLayout>
<PartyOutLayout>
<LayoutName>Main</LayoutName>
</PartyOutLayout>
<DialIn>true</DialIn>
<NeedOnMaster>false</NeedOnMaster>
<UserId>1</UserId>
<Email>admin@mail.com</Email>
<LastName>admin</LastName>
<Host>true</Host>
<Organizer>true</Organizer>
<Panelist>true</Panelist>
</Attendee>
<ReservedPorts></ReservedPorts>
<BlockDialIn>false</BlockDialIn>
<AutoExtend>false</AutoExtend>
<WaitingRoom>false</WaitingRoom>
<AdvancedProperties>
<EnableMCUCascading>false</EnableMCUCascading>
<AllowDynamicGrow>false</AllowDynamicGrow>
<DurationAfterLeft>P0Y0M0DT0H10M0.000S</DurationAfterLeft>
<AlertDurationBeforeTermination>P0Y0M0DT0H10M0.000S</AlertDurationBeforeTermination>
<TerminationCondition>AFTER_ALL_PARTIES_LEFT</TerminationCondition>
</AdvancedProperties>
<OneTimePINRequired>false</OneTimePINRequired>
<Layout>
<LayoutName>Main</LayoutName>
<LayoutType>0000</LayoutType>
<Dynamic>false</Dynamic>
<NoSelfSee>false</NoSelfSee>
<LayoutMax>0</LayoutMax>
</Layout>
<Layout>
<LayoutName>Customer</LayoutName>
<LayoutType>0000</LayoutType>
<Dynamic>false</Dynamic>
<NoSelfSee>false</NoSelfSee>
<LayoutMax>0</LayoutMax>
</Layout>
<StartTime>2019-11-15T05:00:00.000Z</StartTime>
<EventConference>false</EventConference>
<Duration>P0Y0M0DT0H2M0.000S</Duration>
<LocationId>AUTO</LocationId>
<TestOnly>false</TestOnly>
<SendingNotification>true</SendingNotification>
<RecordingMeetingWhenStart>false</RecordingMeetingWhenStart>
<ReccurencePatternChanged>false</ReccurencePatternChanged>
<RecipentsChanged>false</RecipentsChanged>
<AddRecipents>false</AddRecipents>
<RemovePersonalTerminals>false</RemovePersonalTerminals>
<CheckTerminalConflicts>false</CheckTerminalConflicts>
</Conference>
</Schedule_Conference_Request>
</Request>
</MCU_XML_API>

That's great to hear, Andrew. Thanks for the update and I hope the demo goes well tomorrow!