Check if target exists before routing (URS 7.6)

[tech12]

Hi guys,

Long time lurker here.. so finally something came up that I can't seem to resolve or find a discussion on.

I have a strategy that collects digits and then attempts to route to an Agent (per digits) or his VM (TRoute if Agent isn't Available). All is well, unless the caller enters digits that do not exist.

Currently, there is only a length check in place for digits entered, but I would like to check if the target exists in config before attempting to route.

Ultimately, the goal is to send them into a loop to enter digits again, if the target doesn't exist.

Any ideas? Am I missing something obvious?

[kubikle]

Posible options (may be):
- direct access from strategy to config server data base (through db server)
- or upgrade to 8.1.1 where functions TargetState and GetConfigObject are exposed)

[tech12]

Thanks for the reply.

Upgrading isn't an option at the moment(however, it would be ideal ).

I was debating about the query to the config db as well. I might just do that. Should be a simple db dip.

I was also looking at possibly using a statistic as a workaround, i.e. [i]if stat != '', then continue routing, else loop back to prompt[/i]. Only I can't seem to think of a proper stat to use.

The assumption is that if the stat doesn't exist, then the agent doesn't exist. However, this raises another concern. If for some reason the StatServer stops monitoring an agent, I might get a blank stat for him...

[tech12]

Decided to go with DB dip. Least painful solution.

[147_Keys]

Looks like you might have already found a solution, but here's what we do:

-create an Agent Group that contains all the extensions this call could potentially route to (can be a Virtual Agent Group based on Skill)
-use the ExpandGroup function against this Agent Group to get a comma-delimited list of all "valid" agents. Assign this output to a variable.
-use the StrStr function with the variable as Source and the CED from the extension prompt as To Find.  We Cat '@' after the CED to make sure we are finding the full extension, but if you've already checked for the correct length then you may not have to do this.

Good luck!
John

[tech12]

Sounds interesting. This is similar to what I was considering in the first place. However, if we 'forget' to assign a skill to  an agent, he will not be routed to.

Granted, this is unlikely to happen , but I would rather not take chances with human error. In my environment there are too many people who can modify agent skills, so the probability of error is there for sure.

If the db dip will not work out, this will be my next option.

Thanks for your input, 147_Keys.