Off site forwarding to wrong trunk group

[keyset6]

On a G3siV6 I've enabled a phone to call forward off site. Usually 1+area code calls route over the T1 ties. When I forward the phone via *2 9-1-NXX-XXX-XXXX the phone will forward, but the call goes out over the local COs. This even happens if I dial the forwared phone internally. When I make a 1+area code call from the phone it goes over the tie trunk group as it should. I wonder what would make the call route differently only when forwarded? Same thing happens on our G3csiV12.

 

[mikeydidit]

Try a remote coverage path and see if it still happens. (ch cov rem 1) .



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

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

 

[keyset6]

I may end up doing that as I'm 99% sure that method went on the correct group last time I tried it. It would be nice to selectivley determine the forwarding target from the phone. But.. it could be considered easier just by pressing a button to send calls to the pre-determined number.

 

[AvayaTier3]

station x to station y (forwarded) will use the same route pattern as station y calling the forward to destination for station to station calls.

I am guessing your route pattern sends calls to the tie-trunk, and second choice is the local trunks.

Now, if station y is called DID on an incoming trunk and going out on an outgoing trunk, the incoming trunk COR may have an FRL that makes the call use the 2nd choice in the route pattern.

You can also use forwarding destination with a TAC instead of an ARS dial access code. This way it will always use the Tieline or return busy if trunks are not available.

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

 

[keyset6]

I've forwarded x2124 to 9-1-518-533-9940. The first trace shows calling that number from 2124, the call went out as it should. That 00130 number is a code we insert on all long distance calls over the ties.

LIST TRACE
time data

16:35:08 tone-receiver 01A0203 cid 0x10f
16:35:08 active station 2124 cid 0x10f
16:35:10 dial 91518533 routeREFIX|FNPA|ARS
16:35:10 term trunk-group 2 cid 0x10f
16:35:11 dial 915185339 routeREFIX|FNPA|ARS
16:35:11 route-pattern 99 preference 2 cid 0x10f
16:35:11 seize trunk-group 2 member 8 cid 0x10f
16:35:16 dial 915185339940 routeREFIX|FNPA|ARS
16:35:16 outpulse done 00130003800815185339
16:35:24 active trunk-group 2 member 8 cid 0x10f

GENERAL STATUS
Administered Type: 6424D+ Service State: in-service/on-hook
Connected Type: 6424D+ Parameter Download: complete
Extension: 2124 SAC Activated? no
Port: 01A0914 User Cntrl Restr: none
Call Parked? no Group Cntrl Restr: none
Ring Cut Off Act? no CF Destination Ext: 915185339940
Active Coverage Option: 1

EC500 Status: N/A Off-PBX Service State: N/A
Message Waiting:
Connected Ports:

This trace shows calling 2124 from 2331. Trunk group 1 is the local CO group. I got suspicious when testing, the call when out unusually fast for a long distance call and the quality was better than usual.

LIST TRACE

time data

16:37:28 tone-receiver 01A0205 cid 0x118
16:37:28 active station 2331 cid 0x118
16:37:31 dial 2124
16:37:31 term station 2124 cid 0x118
16:37:31 call-forwarding 91518533
16:37:31 term trunk-group 1 cid 0x118
16:37:32 call-forwarding 915185339940
16:37:32 route-pattern 99 preference 1 cid 0x118
16:37:32 seize trunk-group 1 member 3 cid 0x118
16:37:35 call-forwarding 915185339940
16:37:35 outpulse done 15185339940

When I dial 9-1-518-533-9940 from 2331 it goes out on trunk group 2 like 2124 did on the first trace display. Route pattern 99's 1st preference is the COs but requires FRL 7 which no one's COR has. I'm not sure why it's even in there as the 1st choice, but for some reason that's the preference is a station is forwarded off site. Maybe I'll remove that 1st preference. Could it be a call forwarded off site disregards the calling stations COR/FRL?

 

[foneladyz]

Has anyone experienced this and how did you resolve it...When dialing an internaiional long distance calls only our G3siV12 is insertng a "#" at the end of the dialstring,when checking the lis trace the LD carrier sees it as a "c" and the call will not complete. See below:

LIST TRACE

time data

09:31:19 dial 90114962213780# route:ARS
09:31:19 route-pattern 15 preference 1 cid 0x1d4
09:31:19 seize trunk-group 3 member 21 cid 0x1d4
09:31:23 dial 90114962213780# route:ARS
09:31:23 outpulse done 0114962213780#
09:31:36 active trunk-group 3 member 21 cid 0x1d4
09:31:39 idle station 2999 cid 0x1d4
09:31:42 active station 2999 cid 0x1d8
09:31:42 dial 9011496221 route:ARS
09:31:42 term trunk-group 3 cid 0x1d8
09:31:42 G711MU ssff ps:20 rn:1/1 10.1.2.111:2048