Endless Vector? 2

[glenng3]

I've been working on my first vector and am a little apprehensive that something might go wrong. For instance, what if the vector doesn't have a stop command in it? Does it just keep going and occupy some memory in the system until the next reboot? What if a user starts a vector and hangs up before it stops? Our system is a R013x.01.5.642.3. Thanks. -G.

 

[Tolson]

Don't worry about it, if the vector goes beyond the end of programming without a stop it will look at the next line and then the next until it runs out of lines (32 steps for your version) and then the call will be disconnected.

Second item, no problem the system will stop processing the vector for that call when the caller hangs up.

 

[wmainc]

If the call somehow gets stuck in a loop, it will stop processing at 1000 steps anyway.

 

[Yemine]

So it is not so important to use "stop" such satndart vector issues.

http://tirustbuy.com/godaddy/

 

[Tolson]

Although it is not a requirement to use the stop statement, it does make vector reading much easier and is a good practice to do it. depending on where you are in a vector it can be very important to have the stop statement.

 

[mikeydidit]

Yemine

Something that I do when I get through writing vectors is to setup a dummy VDN for it. Then in the switch do a "list trace station xxxx" (your extension number). The call the vdn and press the different options. The trace shows you what steps are taken and what they route to.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594

 

[VoipMenace]

Hi
I would recommend the stop statement as the vector remains "open" always and always "code correctly" the less risk you run of a mishap like a hack