Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

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 » Multiple (user selectable amount) of calls in parallel to a number for stress testing   XML
 
Author Message
drew.dickenson.ascension.org



Joined: 11/06/2018 17:32:17
Messages: 2
Offline

Howdy everyone,
I've been tasked with developing a fairly simple workflow to send N number of concurrent calls to a single number which I'll front end with a basic web page for the user to add the phone number they want to call and the number of instances of calls to that number.

Originally I planned to just hard code a parallel gateway and individual "make calls" to as many things as I need but they wanted the ability to dynamically change the number of concurrent calls that go out to whatever number...

My first thought on how to tackle this was to just put a loop with a parallel gateway, one going to make call and the other going to an incremented counter and then back to the gateway. Since it's all the same number that seemed like it should work, if kinda messy...

Any way anyone can think that would solve this problem? I tried running this and it makes the first call then fails with "nested exception is: java.rmi.ServerError: Error occurred in server thread; nested exception is: java.lang.StackOverflowError"

I'm assuming that maybe the ucid is being changed with every iteration and therefore parts of the workflow are trying to affect one uuid and it's already changed with the next new call even though the previous call isn't finished maybe?
[Thumb - breezeParallelCaller.jpg]
 Filename breezeParallelCaller.jpg [Disk] Download
 Description No description given
 Filesize 38 Kbytes
 Downloaded:  68 time(s)

This message was edited 3 times. Last update was at 28/06/2021 16:19:55

JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 864
Location: Thornton, CO
Online

I am not exactly sure what services Breeze makes available to you. I am familiar with Communication Services (basically this is exposing TSAPI).

A station device (Communication Manager Station Extension) can only originate one call at a time, unless you place the call on hold, and even then you are limited by the number of call appearances provisioned on that station (max 10).

I suspect you are running into that limitation, but it is not obvious given your 'what am I doing' description.

If you are using a SIP trunk in your application, you don't have to go through the complexity of using stations on communication manager as your originating device, but you will still be limited by the number of members in the trunk group.

I believe you are going to have to register a DMCC station to be used as the originator for each call (or block of 10 calls) you are placing, which means you need a list of station extensions to launch calls from, or use System Management Service to create stations (and remove them when your task completes).
[WWW]
drew.dickenson.ascension.org



Joined: 11/06/2018 17:32:17
Messages: 2
Offline

So Breeze is pretty much a Session Manager / SIP based application. In the example above I'm not even touching CM at all. It takes and sends the calls directly to SM where in SMGR routing we send it out the SBC and carrier SIP trunk. I'm not sure if this comes into play there but it could be some similar limitation...

I wonder if I need to send a different CLID for each call I send out... though I'm seeing multiple calls working just not the number I'm expecting to see.
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 864
Location: Thornton, CO
Online

you used the phrase "make call" and perhaps I fell into a trap. I presumed underneath your method call triggered a particular station to originate a call to your destination number. It dawned on me later that I don't really know what the services on Breeze are using as an originating device. let me ask another pair of eyes to look at your problem statement. It would be helpful to know exactly what method you are using to originate calls with.
[WWW]
 
 
Go to: