Station forwards and does not wait for number of rings before doing so 2

[Mugsiensedgwick]

G3si V11 R011i.02.0.110.4
I have a station that, when called goes directly to the cov pat assigned to it without waiting for the requisite number of rings. I unforwarded it (though apparently it was not forwarded) and that did nothing.
Trace was not revealing anything except that it was going immediately to cov pat.
I looked at the status and it has a download status of "pending".
So I saved translations and it still says pending.
Then, because I had 6 phones this had appearances on with ringing, I removed all of the "per button ring control" on those stations. I was thinking there may be a limit that I exceeded.
Still says pending and goes to cover.
This station is on a coverage time-of -day then to cov pat.
Any ideas on how to get this to wait to forward?

 

[mikeydidit]

Check the coverage path to see if "all calls" is checked. If so it's not going to wait the x number of rings. Also if that doesn't do it, remove that coverage path and try another. TOD coverage may be activated.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594

 

[Mugsiensedgwick]

I did a test station and it responds with error codes 3 on test 16 and 5 on test 17.
I changed cov pats and that had no effect.

 

[AvayaTier3]

display coverage path and post here

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[Mugsiensedgwick]

There is not a phone on this port. When I started on this problem it was assigned X, but thinking that the problem could be the port assignment X, I assigned it to an unused port.

 

[mikeydidit]

That will do it every time..

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594

 

[AvayaTier3]

x port, virtual station, port without a phone all represent nowhere to terminate and calls will immediately cover because there is no reason to wait for an answer

post your coverage path

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[Mugsiensedgwick]

disp sta 2362
STATION

Extension: 2362 Lock Messages? n BCC: 0
Type: 6408D+ Security Code: TN: 1
Port: 01B0303 Coverage Path 1: t2 COR: 3
Name: 2362 Help Desk Coverage Path 2: COS: 5
Hunt-to Station:

STATION OPTIONS
Loss Group: 2 Personalized Ringing Pattern: 1
Data Module? n Message Lamp Ext: 2444
Speakerphone: 2-way Mute Button Enabled? y
Display Language: english

Media Complex Ext:
IP SoftPhone? n
Remote Office Phone? n
disp cov tim 2
TIME OF DAY
COVERAGE TABLE: 2

Act Cvg Act Cvg Act Cvg Act Cvg Act Cvg
Time Path Time Path Time Path Time Path Time Path

Sun 0:00 84 : : : :
Mon 0:00 84 7:00 4 17:00 84 : :
Tue 0:00 84 7:00 4 17:00 84 : :
Wed 0:00 84 7:00 4 17:00 84 : :
Thu 0:00 84 7:00 4 17:00 84 : :
Fri 0:00 84 7:00 4 17:00 84 : :
Sat 0:00 84 : : : :

Disp cov pat 4
COVERAGE PATH

Coverage Path Number: 4
Hunt after Coverage? n
Next Path Number: Linkage

COVERAGE CRITERIA

Station/Group Status Inside Call Outside Call
Active? n n
Busy? y y
Don't Answer? y y Number of Rings: 4
All? n n
DND/SAC/Goto Cover? y y

COVERAGE POINTS

Terminate to Coverage Pts. with Bridged Appearances? n

Point1: h8 Rng: Point2: Point3:
Point4: Point5:

 

[Mugsiensedgwick]

I'll grab a phone & let you know,
Thanks guys.

 

[AvayaTier3]

Try changing Busy Inside Call and Outside Call = "n"

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[Mugsiensedgwick]

I found the problem.
Typical HUA stuff.
SAC=y
Thanks for all your good help. I learned some more stuff on this one.

 

[Mugsiensedgwick]

Just for grins I changed it back to port x and it's working fine.
Thanks again all.