Odd routing issue

[campyracr]

I noticed a day ago inbound calls were getting dumped after dialing the extension. Since it was me, I chalked it up to fat fingers.

Today, I am getting notification of calls going to the wrong extension all together. Any suggestions as where to start? It appears to be random.

 

[lopes1211]

Is it an Audix auto-attd or a route-to-digits step in a vector? -CL

 

[definityman]

Have you tried to check if the extension called hasn't a call forward to another number activated?


Hope this helps

 

[telcoguy]

You should be able to test where it goes by using the "list trace station xxxx" command.
Issue this on your own set and than dial the numbers reported as being the ones with problems.
This should tell you exactly what happens.
If it comes in through a vector that is misconfigured,
you should also be able to trace it via the "display events" command

Rob

 

[mcopini]

Maybe you could be more specific in this matter:
-are there coverage paths / vectors / hunt-groups / call-forwarding / etcetera involved?
-if really 'random': what did the events tell you?

One hint: always blame end-users first before taking action

Please let me know what comes up and I'll be glad to help! Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let fellow members know if their post was of any help-

 

[campyracr]

Sorry I've been installing an ISDN circuit.

Lopes 11211 - I am not sure what that means, but I can tell you the dumped calls were dumped on the first ring to that extension. No call fwding on, per the user. The wrong extension calls could be chalked up to "stupid user tricks", as the vector has been working correctly for years without error.

Definityman - per the user, it was not on

tecloguy - I'll have to try that command.

Mcopini - I always blame the enduser first. The wrong extension is a vector. The "main number" is shared between two organizations. Simple press 1 for x & 2 for y. callers related they pressed 2 and got x. No one has been in to change the vector from what I can tell. (li hist) No covg path/hunt group or call fwd on that issue.

The first issue with the extension being dropped. there is a covg path, and covering ext. The specific extension was not a memeber of a hunt group. It should ring 3x at the extension then go to covg path which is vmail.

 

[mcopini]

Could you drop a screendump of the vector here?
Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let fellow members know if their post was of any help-

 

[campyracr]

I'll see what I can do.