MSYoung

Do a "disp cap" and go to the page that displays your total VDN and vector assignments. Have you maxed either one of those out? There is a system limit.

__________________
Do not meddle in the affairs of dragons for you are crunchy and taste good with ketchup.

Marty

dmhughes

Hi Marty,
If only it was that simple

SYSTEM CAPACITY

System
Used Available Limit
-----------------------

CALL VECTORING/CALL PROMPTING
Total Vector Directory Numbers: 35 477 512
Meet-me Conference VDNs per system: 0 175 175
Vectors Per System: 24 232 256
BSR Application-Location Pairs Per System: 0 1000 1000
Background BSR Poll VDNs: 0 5 5

MSYoung

Oh well, I am going to have to look into it. I'll get back to you.

__________________
Do not meddle in the affairs of dragons for you are crunchy and taste good with ketchup.

Marty

MSYoung

I cannot duplicate your problem, but that is understandable since I am not in your system.

The only time I have ever gotten your error message is when I am exceeding a capacity somewhere or trying to do something that is not enabled in customer options. So lets go back to basics.

What are you trying to do in the vector and have you done this before? When you get the error message, where does the cursor jump back to in the vector? That is what the PBX thinks the problem is.

If the cursor does not jump back and highlight a command in the vector then the problem is somewhere else. I will be surprised if it does not jump to one of the commands in the vector, though.

Please do this for me. Add a new VDN and point it to a new vector, you should have no problem doing this. In the new vector do two things. Add a wait for 2 seconds listening to silence, add an announcement to listen to (I don't care what, as long as it is an existing announcement), add stop. You should have no problem doing this.

Call the VDN and listen to the announcement. Does this work?

__________________
Do not meddle in the affairs of dragons for you are crunchy and taste good with ketchup.

Marty