Weird Problem with Vectors and VDNs 1

[rtsoi]

I created several vectors and VDNs to route callers off site to cell phones etc.

One specific vector doesn't connect to the designated off site number. It just hangs up on me.

I tried another off site number and the vector works. Its only this specific number that doesn't. Both numbers are local calls.

I can call this problem number on site with no issue.

 

[Sean655]

Trace the vector and see if it's using the same trunk as your successful call.

 

[joe2938]

Try removing and then recreate the vdn and retest, worth a shot

ACSS IP Office AIPS IP Office

 

[rtsoi]

I tried playing around with forwarding an extn to this number and it didn't work.

Even weirder, the call went to coverage.

However, after forwarding and un-forwarding this extn, it suddenly started working.

Going back to my vector, the calls were now routing off site to this number.

 

[rtsoi]

Today, the same problem returned from yesterday.

I tried blanking out the vector and removing the VDN and building it again but no avail.

I tried calling this vector on site, both dialing internally through extn and outside through DID and it seemed to work.

I tried putting in the user's Google Voice number and it seems to work.

 

[joe2938]

Is it working or not working? Another way to do this is through a remote coverage path

ACSS IP Office AIPS IP Office

 

[Sean655]

What's the use case? Do you want certain people to handle certain types of calls and that's why you're using the VDN/vector route? Otherwise, normal call forwarding, cover path remote, or EC500 would work.

I just had an issue where call forwarding was not working for a user and they also wanted their cell phone voicemail to pick up if they missed the call. There's an option on page 2 of the station form to turn off coverage after forwarding. Once turned off, my call got an intercept message telling me not to dial a 1 before the number. Once we removed the leading 1 the calls forwarded successfully and also routed to cell phone voicemail. In short, trunking could be an issue but you may have to trace and test to find the issue.