Genesys TServer Extension Registeration limitations

[steven.eti]

Howdy all,

Can anyone tell me if there are any known limitations or maximum number of Extension/DN registration requests a third party client application can send to a TServer using PSDK 8.XX? Or can anyone point me toward any documentation that might describe this sort of thing?

I see that there is a 'max-registration-per-sec' option the TServer has as indicated in (http://www.sggu.com/smf/index.php/topic,1910.msg6304.html#msg6304), for TServer 6.5.X, but that appears to be for ADDP timeout/connectivity.

Regards,
Steven

[cavagnaro]

Shouldn't be any aside from processing speed.
What issues are you facing?


Enviado de meu E6633 usando o Tapatalk

[steven.eti]

Using PSDK 8.1, I'm doing development work on a TServer Client app. I've got 20-40k DNs/extensions given to me all at once, that the client app is attempting to register with the TServer in order to receive CTI. I'm sending a 'RequestRegisterAddress' through the TServer connection protocol for every extension.

As it turns out a good number of those DNs given to my application are not associated w/ the TServer I'm connected to, so they fail registration, and retried again another 10 times. This seems to have killed the TServer I was connected to. I'm planning on throttling the number of 'RequestRegisterAddress' that I send per minute or per second, as well as filtering those extensions for association to the TServer I'm connected to.

My concern here is that even with these changes, I might overwhelm whatever TServer I'm connected to, and as such wanted to know if there were any known limitations for 'X' number of 'RequestRegisterAddress' requests to the TServer per 'Y' time period.

I understand that the environment the TServer is deployed to/running in is going to impact these numbers, but do you or does anyone else know of a rule of thumb to adhere to for these registration requests?

[cavagnaro]

[quote author=steven.eti link=topic=11112.msg50582#msg50582 date=1536520413]
[font=Verdana][size=2px]retried again another 10 times.[/size][/font]
[/quote]


why??? If you got an error you shouldn't try again...makes no sense, object is just out. when it comes back will let you know, if comes back ever.


Technically there are not, but as said, you will create a high number of CPU and memory resources to be consumed. So if your TServer is not on a good HW you will face issues.


Maybe try to register 100 by 100 and so on. Wait for an answer back but don't try again...makes no sense again.

[Kubig]

Do i understand well, that you are trying to attempt register more than 20k DNs?

[steven.eti]

@cavagnaro, I want to be clear, my application was not attempting to retry failed DN Registration requests, the TServer owner is telling me that each failed request was repeated another 10 times. Nothing in my code attempts to retry any registration request, if it fails I just move on.

@Kubig, yes. I was provided with +20k DNs, some of them associated with the TServer I was connected to and some of them not. I'm now currently filtering those DN's and checking to see if they're associated (through the TServer Application Name and the TelephonySwitchDbId) with the TServer I connect to. While this should drastically reduce the number of DNs I attempt to register for in the future, I'm concerned if there is a definitive limit as to how frequently I can request a registration for an DN for a certain period of time. Ex: instead of attempting to register for lets say 1000 DNs as soon as possible, is there a preferred rate at which I request those registration say 1 registration request per 150ms? Also is there a known limit to the number of DNs a single TServer pair will service?

[cavagnaro]

Ask your customer to check who sends those re-register attempts. He should be able to easily identify it.
And there is no limit for requests, again. Will depend on your customers server infrastructure. Requests are done in fifo, you can't send 10000 requests at single request. Also they are async requests. You send and TServer does. There is a inner processing unit for that at TServer.
But if you put 10000 objects in memory and TServer server doesn't have enough memory for it or cpu then well it will cause a possible exception. But not because your requests, but because of your customers server.
Say you request to register a DN, but this is out of service because is disconnected. Then TServer will let your application when this DN is back. This is normal scenario for example at Voip environments.
Other thing is to request against a non created DN, in which case TServer will respond a different error code.
This last one will not consume license, while first will do.


Enviado de meu E6633 usando o Tapatalk

[steven.eti]

Thank you for the input folks. This has helped.