Number of CSTA-monitors/object

[bj2592]

Hi!
Does anybody know if there are any limitation in number of CSTA-monitors per object (like KS/EX-extention). If so, is it possible to read out from the memory how many CSTA-monitors that currently are active towards a extention.
In ALEX I read that there is a limit of 1000 monitors per LIM, but are there a limit per extention as well?
Our MD110 is at the moment a BC10/CNA143, so the BC12-command CSTMP are unfortunately not avaliable for us(yet).. :-(.
Best regards bj2592

 

[robsod]

You can monitor all ADN/ODN:s onces. Even if you have two different link groups you cant initiate the same monitoring twice. There is a license for how many different monitors you can make.
CSTLP; to see how many active moniters you have running.

 

[fidde]

From a AL perspektiv you can have as many clients you whant to monitor one extension. AL is starting only one monitor in MD then it take care of the logic.

Though if you have two AL servers (meaning two LGRP) they can NOT monitor the same exstension. This is a limit in the MD.

 

[cuneyt2020]

Hi bj2592
there is a patch for bc10 which enables cstmp command for md.. We use it in our bc10 system
But i forgot the patch number now. And you can ask to your local partner or anyone here may help you about it.

but on that command you can see only the active monitors(DNs such as extension,ACd groups)and also place of NIUs in which the DN was registered on
such as
4450 NIU1
4540 NIU2

If you want to register the same DN with two Application Links (two link groups) you will get an error like " object monitor limit exceeded")

Also for third party applications there are default values for Md Application link
Here is the values for genesys below. This is application link and the pbx perfomance limitations i think...



link max-request-rate (maximum number of requests per second that can be sent to the switch.. default value 60)

link maximum outstanding device request maximum number of requests that can be sent to the switch on behalf of a phone set before recieiving any confirmations or rejections.Any additional requests are queued. Default value 1)

link request delay (specifies the interval in miliseconds that tserver waits before attempting to send a feature request to the same device default value 200)

link maximum outstanding request ( maximum number of requests that can be sent to the switch before receiving any confirmations or errors default value 4)Al4 supports up to 16

link request timeout (Specifies the time interval in seconds, that genesys waits for request confirmation or error default value 20)

force snapshot interval (Defines a timeout in miliseconds after which Tserver will query the switch for the status of devices after completion of transfers in which the primary call was on ADN and consult call was on ODN default value 1000)

device snapshot interval Specifies the time in seconds that Tserver scans the list of devices for their states default value 60 , maximum 120 and we use 90 "0" (zero), turns the option off)