limits on remote node set supervision?

[tjm0852]

It seems like there is a limit to the number of sets that can set supervise a particular extension from a remote node. Is that correct, if so where would I find the parameter to determine my limits.

Everytime I try to add set supervision of an extension at a remote node I get this error:
Processing Failure
OBJECT -1: Directory Number: Supervisor exists in remote node

Any help would be great, thanks!

[oldboy]

You are right there is a limit i think it is a 1000 or so. I have had this error before and it is a problem in your supervision table....to fix it you need to run a a multitool REPAIR.. remember to turn the mao off first. and this should fix the issue.

[Eliott_DUP]

OBJECT -1: Directory Number: Supervisor exists in remote node

Check also Specific Telephone Services - Go down - Supervised User ...
The limit can be found in the product limits. Maximum 8000.
R8.0:
Supervision keys per Node = 15.000
Supervisors for one DN = 20
Supervisions in network, per signalling link :
9600 b/s = 150
16 Kb/s = 150
64 Kb/s D channel = 500
64 Kb/s B channel = 8.000
IP = max. 8.000 depending on bandwidth

PS: multitool CHECK REPAIR should be started in /usr3/mao

[pavel]

Hello !
Got the same error recently on a networked oxe. oldboy's advice not helped. Anything else I can do ?
Thanks in advance.

[oldboy]

Pavel, after you ran multitool CHECK can you show up the output of the errors?

[pavel]

oldboy, thanks for reply.
Here is question - multitool CHECK gets me to some menu - can you please specify what output do you asking me to show ?
Anyway got some progress - badly need some guru advice.
So there are 2 ABC networked pbx A & B (both R9.0).The issue appeared after a deletion of a A's pbx set (user 1000) who got set supervision keys of pbx B users (user 2000).
After recereation of user 1000 of A pbx and an attempt to programm exactly the same set supervision keys again we got OBJECT -1: Directory Number: Supervisor exists in remote node.
Ok so I read some manuals and this forum which led me to cuser tool. After applying cuser on node B with "select * from superv;" I found some records of user A which should not be there and kind of stuck.
The table superv has 5 fields
here is some records for example:
mcdu_visor mcdu_vised key_id num_tab_vised mark_audit num_tab_viseur
'1000' '2000' 1 1 0 0
'1000' '2001' 2 2 0 0
So i deleted one of this records. After this I was able to recreate set supervision key on user 1000 of A pbx.
The updated superv of node B looks like
mcdu_visor mcdu_vised key_id num_tab_vised mark_audit num_tab_viseur
'1000' '2000' 1 3 0 0
'1000' '2001' 2 2 0 0

The value in corresponding field num_tab_vised has changed automatically to new value 3. Hence the question - what does this value mean and what are the consequences ?

Regards,
Pavel.

[oldboy]

Hello !
Got the same error recently on a networked oxe. oldboy's advice not helped. Anything else I can do ?
Thanks in advance.

So what did you exactly do when the advice didnt help???

Concerned that you are now playing around in cuser and i would recommend highly that you dont proceed any further.

So run the command cdmao
then multitool CHECK option 8 and give us the output!

[pavel]

then multitool CHECK option 8 and give us the output!

it's clean on both nodes - no errors concerning involved sets.

[Eliott]

Still unsolved?