Problem routing to an external # via vector step

**marzahn** · 04-14-2015, 09:20 AM

A Different Way to "route to an external # via vector step"

Sorry for the late reply to your very well documented issue. I had some unavoidable work load and home issues...

Summary: You want to route calls to an external number once certain conditions are met. Before we start, here are two suggestions I would offer:

Start documenting (please see below) your code with the # option.
Use a more modular way to accomplish your goal.

I take a different approach to all “route to” steps. Since the route-to command stops vector processing, I place those steps at the end of my vectors. And I use the “goto step” commands, which do not stop vector processing, throughout the rest of my vectors.

Here is the way I set something like this up:

Set up an entry in the coverage remote table “ch cov rem 1” for the external number.
Set up a coverage path “add cov path next” that points to the new entry in the coverage remote table.
Set up a virtual station pointing to the coverage path.
Write the station number into the vector as below.

15 # "Your Call maybe monitored.........."
16 announcement 691000
17 # Route to Q VDN
18 route-to number 4831 with cov y if unconditionally
19 stop
20 # Routes out to Beacon/Boston, 800-xxx-xxxx
21 route-to number 6680 with cov y if unconditionally
22 stop

**richa164** · 04-16-2015, 06:29 AM

Hi Both,

I have this working exactly as you describe , in fact i have it set so that if CM receives a valid busy signal from the route to number it will continue vector processing , this logic only happens if your route to number has coverage set to N.

However you seem to have something else going on here can you dial this number from a local CM station??

**richa164** · 04-16-2015, 06:35 AM

Also list trace the station that you are dialling the vdn from this will give you more info , this is probably something like COR on the VDN restricting access.

**marzahn** · 04-16-2015, 06:38 AM

Dialing this number from a local CM station??

"However you seem to have something else going on here can you dial this number from a local CM station??"

This is precicely why I do it this way Richa. You can dial the extension internally. Moreover, if you are on a call you want to forward to this external number, it is quite easy to do so. Did that answer you question?

**richa164** · 04-16-2015, 07:15 AM

i was referring to Joe not yourself Bill with the list trace , apologies for any confusion.

**marzahn** · 04-16-2015, 08:46 AM

No worries Richa!

However, perhaps my last answer will show the benefits of this method.

**ssmokinjoe** · 04-16-2015, 08:51 AM

Hello Bill,
Thank you for the reply, I hope that the home issue have gotten better.

I am in the process of putting your suggestion in place; I am able to dial the toll-free number from an CM phone. I will put it in place and test it. I will keep you both posted as to my results.

Although I have been doing this job for a while I still have so much to learn.

**ssmokinjoe** · 04-16-2015, 08:58 AM

Originally posted by marzahn View Post

Sorry for the late reply to your very well documented issue. I had some unavoidable work load and home issues...

15 # "Your Call maybe monitored.........."
16 announcement 691000
17 # Route to Q VDN
18 route-to number 4831 with cov y if unconditionally
19 stop
20 # Routes out to Beacon/Boston, 800-xxx-xxxx
21 route-to number 6680 with cov y if unconditionally
22 stop

Bill, How do I set the description for the commented out line the way you did in the above example? I know that I can comment out a line once a valid command has been entered but not able too otherwise.

Thank you,

Joe

**marzahn** · 04-16-2015, 09:31 AM

How to Comment a Vector Step

I understand that you want to add just a comment lines to an existing vector. If that is not right, please let me know.

Since you are up to CM 6.3 Joe, using GEDI, you can comment a line or even a group of lines by entering a hash/pound (#) and pressing enter. Also since CM 5.x you get up to 99 steps and step management that was heretofore only available in the emulation editor. I can tell you that MADE MY DAY!

Let's say you want to add a new comment step in VEC 22 between 14 and 15. Here's how:

Press the <F6> key. this pops up the "Edit Vector" dialog.
Instead of clicking on the "Comment Line," click on the "Insert before."
Place a number in the "box" to the immediate right just like you do the the "Comment Line" selection and press enter.

Now then . . .How cool is that?

But did a answer your question?

**ssmokinjoe** · 04-16-2015, 01:07 PM

Hi Bill,
That commenting feature is awesome!! I will have to go through my vectors and place a comment where appropriate.. Thanks for that tip..

I made the changes and added what you suggested. I still am losing the call when the option is selected. Am I missing something; I have pated my new vector below for your review.

Vector
Number: 22 Name: MSC_Announcemen
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 2 secs hearing silence
02 collect 10 digits after announcement 5733
03 queue-to split 10 pri h
04 # Annc for BP Xfer
05 Collect 1 digits after announcement 5744
06 # Step for BP Xfer
07 goto step 19 if digits = 5
08 announcement 5707
09 wait-time 10 secs hearing music
10 announcement 5708
11 wait-time 10 secs hearing music
12 announcement 5743
13 wait-time 10 secs hearing music
14 announcement 5709
15 wait-time 20 secs hearing music
16 announcement 5711
17 wait-time 2 mins hearing music
18 goto step 6 if unconditionally
19 route-to number 5780 with cov y if unconditionally
19 stop

5780 is the virtual extension that I created which points to:
Cov pat 28 which points to:
Coverage remote entry 2

If I dial 5780 from a CM phone I get the coverage tone and the call transfers as intended; when I dial into the call center from my mobile phone and press “5” after the announcement the call gets disconnected.

**marzahn** · 04-17-2015, 04:31 AM

A Few Suggestions...

Joe:

Let's tackle the main question first. Then a few details.

First, that route-to should work. However I don't know wha't going on in your switch. And the vector needs work. There are two diaglostic tools that I regularly use on vectors . . .

I start with the "display events" command and select the vector This tells you if the vector is at fault.
Next I would use run: "list trace station 5780" in the emulator to see what happens when vector processing tries 5780.
If that does not would you can also use "li tra vdn 9999" where "9999" = the VDN for vec 22. This lets you watch the vector processing in its entirety until the route-to command runs.

If you want to figure this out yourself, try running through the above before you look at my comments below.
================================================== ==========
01 wait-time 2 secs hearing silence
02 collect 10 digits after announcement 5733 . . . . . . . . {[This is not doing anything--remove or comment]}
03 queue-to split 10 pri h . . . . . . . . . . . . . . . . . . . . . . .{[I usually recommend a pri of "m" so you can escalate later if needed. A RONA vector is a good example.]}
04 # Annc for BP Xfer
05 Collect 1 digits after announcement 5744 . . . . . . . . .{[How many choices are there in this announcement/menu?]}
06 # Step for BP Xfer
07 goto step 19 if digits = 5 . . . . . . . . . . . . . . . . . . . . .{[I would insert a wait-time step here to give the caller a chance to respond. What are these subsequent announcements meant to do?]}
08 announcement 5707
09 wait-time 10 secs hearing music
10 announcement 5708
11 wait-time 10 secs hearing music
12 announcement 5743
13 wait-time 10 secs hearing music
14 announcement 5709
15 wait-time 20 secs hearing music
16 announcement 5711
17 wait-time 2 mins hearing music
18 goto step 6 if unconditionally . . . . . . . . . . . . . . . . . .{[This should goto step 4 as yoiu need to include the collect step for this to work]}
19 route-to number 5780 with cov y if unconditionally
19 stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {[surely this is not a second step 19?]}

If I knew what each announcement said, I might have more suggestions. In any case, it might be better to reorder the vector like so:

01 wait-time 0 secs hearing ringback . . . . . . . . . . . . . . .{[ The way I was taught to do this]}
02 goto step 22 if staffed-agents in skill 1st < 1 . . . . . . . {[This insures there are agents to take calls or the calls go to 5780]}
03 # Q calls at MEDIUM Priority
04 queue-to skill 10 pri m
05 announcement 691015
06 wait-time 10 secs hearing music
07announcement 5707
08 wait-time 10 secs hearing music
09 announcement 5708
10 wait-time 10 secs hearing music
11 announcement 5743
12 wait-time 10 secs hearing music
13 announcement 5709
14 wait-time 20 secs hearing music
15 announcement 5711
16 wait-time 2 mins hearing music . . . . . . . . . . . . . . . . {[2 minutes is a pretty long wait time. This may cause some frustration and abandons]}
17 # BP Xfer announcement and
18 Collect 1 digits after announcement 5744
19 goto step 22 if digits = 5
20 wait-time 5 secs hearing silence
21 goto step 5 if unconditionally
22 route-to number 5780 with cov y if unconditionally
23 stop

**richa164** · 04-17-2015, 06:10 AM

Bills method will work as desired , the only disadvantages are that it consumes a station licence and with your route to statement having coverage Y , it will leave vector processing ,in this scenario if the route to number is busy the call will drop , the original method you tried will retain the call in the vector and you can process to further steps in the vector.

But what ever works best for you.

**richa164** · 04-17-2015, 06:14 AM

What about the COR on the vdn , is that restricting via toll tables or something ??

Dial the VDN from your station and list trace your station and post the results.

**marzahn** · 04-17-2015, 06:50 AM

Possible Disadvantages?

Originally posted by richa164 View Post

Bills method will work as desired , the only disadvantages are that it consumes a station licence and with your route to statement having coverage Y , it will leave vector processing ,in this scenario if the route to number is busy the call will drop , the original method you tried will retain the call in the vector and you can process to further steps in the vector.

Hi Richa good to have you join the discussion. This is turning into quite a lively one.

May I offer these comments. You may not have noticed that I recommented a virtual extension. Plese see attached.

These do not use a station license as no port is required. Also I have never found that this method produces call blocking unless, of course, all trunk group (TG) members are already in use. Does this help?

Attached Files

Virtual_Station.pdf (5.4 KB, 8 views)