Coverage Not working for External calls

[sivaprakash]

Hello there!

I am using the Avaya CM 5.0(recently upgraded) and trying to setup the coverage for station. Coverage works for internal calls, it doesnt work for external calls..When i take the history for external calls, its saya coverage 0 and point 0 where as internal call ts says cverage number and it does the routing. Any Clue what went wrong here?

Internal calls
13:12:30 Calling Number & Name NO-CPNumber Engineers tes
13:12:30 dial 465587
13:12:30 ring station 465587 cid 0x567
13:12:45 no answer station 465587 cid 0x567
13:12:45 coverage-path 748 point 1 cid 0x567
-----------------
External calls

14:48:07 Calling party trunk-group 460 member 114 cid 0xa1a
14:48:07 Calling Number & Name NO-CPNumber NO-CPName
14:48:07 dial 465587
14:48:07 ring station 465587 cid 0xa1a
x
x
x
14:48:22 coverage-path 0 point 0 cid 0xa1a
VOIP data from: 164.12.120.22:49250
14:48:28 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:0 Avg:0
14:48:28 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0

Thanks,
Siva

 

[AvayaTier3]

cut and paste your cover path 748 here

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

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[sivaprakash]

COVERAGE PATH

Coverage Path Number: 748
Cvg Enabled for VDN Route-To Party? n 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: 3
All? n n
DND/SAC/Goto Cover? y y
Holiday Coverage? n n

COVERAGE POINTS
Terminate to Coverage Pts. with Bridged Appearances? n
Point1: r748 Rng: Point2:
Point3: Point4:
Point5: Point6:

 

[AvayaTier3]

display cover remote for 748

so you are trying to route the calls back out of the switch?

There can be many things that stop that from working.

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

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[Mitch672]

I agree AvayaTier3, if "Trunk-to-Trunk Transfer" was disabled in the upgrade, there is one place it can be stopped.



Mitch

AVAYA Certified Expert

 

[sivaprakash]

Hi Thanks for the reply How ever i can not understand when the external call comes, why the coverage path says 0 in trace? (I have attached), But internal calls it says cov path 748 and routing properly.
Many Thanks,
Siva

 

[AvayaTier3]

external call will not follow the cover path because of some restriction. You may want to clear events, make a call, and display events to see if an event will tell you why it won't cover.

More than likely your system is restricting trunk to trunk calling.

whatever the number is in cover remote 748 is not being allowed on the incoming trunk to go out again on an outgoing trunk and tie the 2 trunks together. As Mitch stated, this could be trunk to trunk transfer or COR restrictions for either trunk-group, etc.
There is not enough information posted here for someone to help more than this.


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

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com