|
Joined: Apr 2005
Posts: 287 Likes: 1
Member
|
OP
Member
Joined: Apr 2005
Posts: 287 Likes: 1 |
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 forwarded 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. I don't the option of forwarding to the ties via the TAC since we insert over 10 digits with each long distance call over the ties, then the dialed number.
|
|
|
|
Joined: Aug 2002
Posts: 2,608
Moderator-ESI, Shoretel
|
Moderator-ESI, Shoretel
Joined: Aug 2002
Posts: 2,608 |
Just a thought but perhaps the local trunks are in line group 9 and the T1 is in a different line group?
|
|
|
|
Joined: Apr 2005
Posts: 1,138
Member
|
Member
Joined: Apr 2005
Posts: 1,138 |
lets see a list trace both ways.
|
|
|
|
Joined: Apr 2005
Posts: 287 Likes: 1
Member
|
OP
Member
Joined: Apr 2005
Posts: 287 Likes: 1 |
If I make a call from a station by dialing 9 + a long distance number it will route over the T1 (ties). It's when I call a station that's forwared to a long distance number it'll end up going out over the local COs. I'll get a list trace both ways.
|
|
|
|
Joined: Apr 2005
Posts: 287 Likes: 1
Member
|
OP
Member
Joined: Apr 2005
Posts: 287 Likes: 1 |
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 route:PREFIX|FNPA|ARS 16:35:10 term trunk-group 2 cid 0x10f 16:35:11 dial 915185339 route:PREFIX|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 route:PREFIX|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?
|
|
|
|
Joined: Apr 2005
Posts: 1,138
Member
|
Member
Joined: Apr 2005
Posts: 1,138 |
Looks like you have a COR/FRL issue to me. Need to see your setup to be sure.
|
|
|
|
Joined: Apr 2005
Posts: 287 Likes: 1
Member
|
OP
Member
Joined: Apr 2005
Posts: 287 Likes: 1 |
Unfortunately copy & paste from Procomm loses it's line format here, but we can see the basic configuration. Ext. 2331 is COR 2:
COR Number: 2 COR Description: HNPA Toll
FRL: 2 APLT? y Can Be Service Observed? n Calling Party Restriction: none
Route 99 is where LD calls go:
Pattern Number: 99 Pattern Name: Ties
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 1 7 860 1 n user 2: 2 1 1 001300038008 n user 3: 1 1 860 1 n user
Trunk group 2 are the ties, which requires an FRL of at least 1. The first choice, group 1 which are the COs requires FRL 7 which no one has. Choice #3 is in case we lose the ties LD calls would go out on the COs.
|
|
|
|
Joined: Apr 2005
Posts: 1,138
Member
|
Member
Joined: Apr 2005
Posts: 1,138 |
disp trunk group 1. What is the COR and FRL? I'm bet FRL is 7. Change it to 6 and see if that solves the issue.
|
|
|
|
Joined: Apr 2005
Posts: 287 Likes: 1
Member
|
OP
Member
Joined: Apr 2005
Posts: 287 Likes: 1 |
The COR is 1, COR 1's FRL is 1. Sorry again about the formatting. This only happens when a station is forwarded off site to a long distance number, which should go out on trunk group 2. Is there actually an FRL setting in the trunk group? Didn't see one. Thanks
TRUNK GROUP
Group Number: 1 Group Type: co CDR Reports: n Group Name: LOCAL COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Dial Access? y Busy Threshold: 99 Night Service: 4913 Queue Length: 0 Country: 1 Incoming Destination: 4913 Comm Type: voice Auth Code? n Digit Absorption List: Prefix-1? y Trunk Flash? n Toll Restricted? y
|
|
|
Forums84
Topics94,262
Posts638,694
Members49,757
|
Most Online5,661 May 23rd, 2018
|
|
1 members (JBean3329),
114
guests, and
240
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|