Thanks. Yes, myself and one other engineer reviewed the syntax on multiple attempts and see no errors.

What are the limitations to an extension list in the Breeze UCA Store?

I am trying to import extensions that total 11,073 that are in numerical order, separated by commas with no spaces, starting with CM name. There are 121,852 characters.

The click to dial operation that uses this list fails.


However, when I copy over an extension list with 9997 extensions, 110,016 characters, it works just fine.

My Breeze version: 3.2.0.1.16320111
Deployment Type: Medium

Format: CMA:11155,13893;CMB:14001

I'm wondering if this has been updated yet? An automated way to add extensions to UCA Store that doesn't require manually entry into SMGR. I want ADFS to dump extensions into Breeze.

Currently I have to stop the service on Breeze through Putty then restart the server through SMGR. Is there a scripted way to restart Breeze so I don't have to manually do this? I am on Breeze 3.2 and the reason for the restarts is to update the extension list in the UCA store.

Thanks Dinesh. Has the 25k max subscription limit for each CM been tested yet?

For a MEDIUM profile, was it tested to work with 200 ECC call events/notifications per second? Or was that LARGE?

In regards to the EventingConnector, is there a way to setup subscriptions for all extensions at once or do we have to do it for each extension one by one?

There is a user field that is mandatory when filling out a subscription and filling this out for 16,000 extensions can be tedious.

"user (in the filter) Mandatory The address for which you are interested for call events"


Also I just wanted to reaffirm that Breeze can handle 15k Subscriptions per CM, so with 2 CMs, it could do 30k Subscriptions? Our Breeze is using a Medium size profile.

Is there a way to setup subscriptions for all extensions at once or do we have to do it for each user one by one?

This is in regards to the EventingConnector snap-in subscritpion creation.

I checked Breeze and it's actually set to Medium so I have access to 30k extensions, 2700 simultaneous calls, 15 calls per second, and 10 subscription requests per second.

Does that mean for an application such as Click to Dial (ECC), I can perform this operation via Breeze to 30k extensions on one CM or am I limited to 15k extensions?

I wanted to revisit this topic one more time. With 15k extensions in the environment sending hundreds to thousands of events each day, is there any kind of performance issues we should be concerned about with Breeze. We plan to create subscriptions to each station and have their events (on a call, dropped call, etc.) picked up by our developer server. Our Breeze cluster is built with two instances and the recommended hardware specs.

Thanks John, the endpoints are H.323 IP phones, so no SIP stations involved. We are leveraging the ECC snap-in on Breeze. Breeze is local to one CM that has these stations registered to it.

This is a general question regarding Breeze and Session Manager.

When Breeze needs to access CM to setup an extension call, is the order of servers leveraged follow like so: Breeze --> AES --> Session Manager --> CM. I'm trying to understand the basic architecture between the different Avaya servers we have. I realize there is a lot more detail as to what is occurring but would be satisfied just receiving the basic outline.


We are using Breeze in tandem with a Developer server to perform click to dial between an internal extension and an external phone number for an example.

Okay thanks for the response.

The Breeze UCA CM(VOICE) Resources is limited to 15,000 extensions. I currently have to manually enter them in via SMGR 7. If I want my dev server to automatically dump these extensions into the Breeze UCA CM(VOICE) Resources field, what would it needed to be pointed to? The manually process of entering these in can be tedious.

We found the issue to be UCID. The two CMs using Breeze needed unique UCID Network Node IDs and the Send UCID to ASAI needed to be changed to YES. Both under System-Parameters Features in ASA, pages 5 and 13.