Hi Moshe,

What happens when a script with "multi selection" is used? Is it always "destroying" a route and how?

if someone select go to IVR voice menu which is a "multi selection" script and presses by mistake 2 menus the route is destroyed (i bumped in to more but dont remeber it now, if you want me to list it for you i would gladly do it lmk)

so if you could allow multi selection only at something where multi selection is allowed like multi device or ring groups otherwise just have a "dropdown selector"

multidevice should NOT be selectable as a script for inbound routes. This is supposed to be an extension script like userexten and stdexten.

Whatever! This is some you have to take up with alex

My point is,any script that runs only a single setection should only have a dropdown single selector option not a multi selector option

Btw what would be the downside of clone multi device extension for inbound routes only adding a line for taxt to prepend

Whatever! This is some you have to take up with alex

My point is,any script that runs only a single setection should only have a dropdown single selector option not a multi selector option

Btw what would be the downside of clone multi device extension for inbound routes only adding a line for taxt to prepend

the fact that it calls tl-userexten-base and there is no extension number called to parse ASTDB entries for settings like CFNA FMFW etc.

a 'inbound route' version of multi-device extension is called 'go to huntlist'

I do agree that it would be nice to allow multiple or only one item to be selected when the scripts are used - the problem is that this will require adding more attributes to the scripts (to specify whether an argument can have multiple values or not) and will get complicated things even more complicated.

Until this could be worked on - just use common sense and do your best asking customers to do the same :).