Calls going to attendant

[maverick2689]

G3v9.5csi

I have this strange problem. Calls that cover to one of my DID extensions (5070, as if that matters), end up going to our attendant, which is on another switch.

There is no coverage path on 5070, if I do a list trace, everything looks fine until the call ends up at 5070, then after 11 seconds, it outpulses a "0" and sends it down to the attendant at another facility, thus making the operator loonie.

I don't see anything in sys feat, or routing patterns that's obvious to me. Any suggestions on what to look for?

This started happening after we converted our Tie between switches from T1 to PRI, which doesn't seem like it should have any effect on calls local to this switch.

Any help is much appreciated.

We must all hang together, or assuredly we shall all hang separately.

 

[4merAvaya]

Try putting a trace up on station 5070 (list trace station 5070) and place an incoming call. see what the trace shows as to why it is being redirected. Are you using UDP or DCS to tie the switches together?

Kevin

 

[maverick2689]

DCS.

It doesn't happen on incoming calls, just calls transferred to it, or covering to it.

We must all hang together, or assuredly we shall all hang separately.

 

[maverick2689]

A typical list trace looks like this, from a different station:

active station 5083
dial 5004
ring station 5004
transfer station 5083
no answer station 5004
coverage-path 4 point 1
ring station 5070
dial 0
seize trunk group 21 member 7
setup digit 0


I'll try and get one happening at 5070 as well. Thanks for the help. Even Denver hasn't been any help yet. :\

We must all hang together, or assuredly we shall all hang separately.

 

[maverick2689]

Resolved.

Turned out being on page 2 of ch console-parameters. Even though there is no console at the remote site.

The entry under "return transfer" (or something close to it) was set to 30, needed to bump it to 300.

We must all hang together, or assuredly we shall all hang separately.