VDN oviride to second PBX with DCS trunks

[transmit]

We have two call centers one is an 8700 the other a G3si. They are using BSR and have DCS trunks between them. We have an IR at the 8700 site and I am trying to route calls to it from the G3 site for a survey using VDN override. The calls do transfer however when the caller that came from the G3 site is done with their survey they get sent back to the survey again and not disconnected. I have tried to have the VDN override route to a local vector and then route to the other site using coverage n or y but it seams that the G3 continues to hold the call. Any ideas on how to break this cycle would be helpful.

 

[DAVIDPAYNE]

I could be mistaken, but from my understanding.

DCS links the switch’s together, but they are not one switch. Once you send the call to the 2nd switch, that switch has control of the call. The one way I see that you could do this is to DCS the call to the 2nd switch (if the 2nd switch has vectoring) then use VDN / Vector to control the call proces in the 2nd switch, and to send the call back once the call is finished in the 2nd switch. You would have to make a new VND and vector on the 1st switch to receive this calls and process as you need.

 

[transmit]

You are corect DCS is a transltaion feature you can set your trunks to. The problem is that althogh the vector on the second switch does control the call and route it properly on hang up from the IR the 1st switch regains control of the call and once again routes it to that same vdn and vector using the original overid feature.

 

[DAVIDPAYNE]

How are you getting the call to the 2nd switch?
What does the vector look like?

 

[transmit]

The first VDN in the first switch has a local VDN number in the override field. That local VDN goes to a vector that uses the route to option with a VDN number on the other switch. (route-to number 8064 with cov n if unconditionally) In other words when the call in the vector on the first switch is answered, and the answering rep releases the call. The call then gets routed to the local VDN set in the override field and goes to its vector then is routed to the VDN on the other Switch via the DCS trunks.

 

[DAVIDPAYNE]

I route calls off my switch to an outside location in my switch and I do not have a problem with my switch attempting to hang onto the call. Do you have “cvg of calls Redirected off-net” turn on? (You can check by “display system-parameters customer-options”) I do not on my switch, and this might be why you are having a problem.

I am wondering if you change the route to statement to be with coverage, if that would make a dereference. Also, what is the step after the route to statement?

 

[transmit]

Thanks for taking time to look at this. I do have (cvg of calls redirected off-net) set to yes. However I am doing this as our voice mail's are in the lec and I call forward to them. Having the yes allows us to grab a call when its already on its way to voice mail. I have tried the vector with coverage y and n and get the same result, the next step in the vector is disconnect after announcement none.

 

[DAVIDPAYNE]

On the 2nd switch, what are the vector step there? And if you could post both set’s of vectors. There most be something in there that I am missing.

 

[transmit]

Vect on switch 1 =
1 wait 0 seconds hearing ring back
2 route number 8064 with cov n if unconditional
3 disconnect after announcement none

Vect switch 2 =
1 wait 0 seconds hearing ring back
2 announcement 4901
3 convers on skill 3 passing 80 and 1
4 disconnect after announcement none

 

[DAVIDPAYNE]

Those are very simple vectors. I would put stop statements as the very last step in each vector, but it never should get there with the Disconnect steps. Have you changed the vector on switch 2 to have a messages to see if it is really hitting that step. Also, how is your IVR passing the call back to the switch?

 

[transmit]

The vector on the second switch has an announcemnt on step two also the convers-on step means that the pbx vector holds the call. If you call direct from switch 2 you do not get in the loop it only hapens when coming from switch 1

 

[marcell55]

Does the VDN on switch 1 (the one that routes to 8064) have VDN override turned to Y?

Also, make sure that you don't have anything in the "Return Desination" on either of those VDNs (the one on the 1st switch and the one on the second.)

 

[rcrow490]

list trace vector #" might give you some insight into what's going on.

 

[transmit]

marcell55 I do have the VDN overide set to y and I am using the return destination at the first switch to route the call as I want to send call on agent release.

rcrow490 I have done a list trace vector however the trace ends when it leave the switch althogh it seem to regain control of the call when the 2nd swith release the call.

 

[transmit]

Thanks all for your help.
I found a way to break the cycle. I set up the return destination VDN vector to route to a ddc hunt group extension with a coverage path that had a coverage remote set to the VDN at PBX 2. If any one wants aditional detail let me know.