Assigning Trunk Access Codes to a certain station

[jayfray]

We are a call center with 24 seats using a G3. We have 3 T1 lines. 1 is for business lines, 1 for data and the other for voice calls for the call center. I want to make all 24 users in the call center makes calls over one T1 line only. Right now the users have to dial a TAC (802)to dial out over that certain T1 line. I dont want the users to have to dial that code, besides sometimes they forget and we get charged alot per call. Does anyone have any suggestions on how I can do this? By the way, the phones they are using are headsets and not Lucent phones. Thank you in advance for your help.

 

[vaoldschl]

Why don't you just set up your ARS to use the trunk you're looking to use? I would pull down the admin manual from Avaya if you don't have a copy and look into setting up ARS. I could try and give you help here but you'll really need the manual to get all the steps.

 

[jayfray]

Thanks maxg. The problem is, they are making calls from a calling list that changes area codes every 2 days. Wouldnt I have to setup the ARS for each and every possible area code they are calling?

We also have regular business users who dont need to use that certain T1 line.

I do have the Lucent manual but I cant find the help I need there.

 

[Armo2]

Hi,

You could possibly do it by COR - set 2 stations with different COR. Set up the ARS tables to use the same route pattern for a particular area code and setup the 2 trunks with matching CORs to the stations in the route pattern. If you set the first trunk with the highest COR - the first station will use this and (hopefully) complete the call, the second station will drop down to the second trunk as it won't have a high enough COR.

This should exactly what your looking for,

Hope this helps

Chris

 

[jayfray]

Thanks Chris,

I will try that. The only problem is that I will have to change the ARS table on a semi-daily basis because of the calling list.

 

[Armo2]

Hi,

No, everything in the ars table should only point to 1 route pattern - that route pattern should have two trunks and these should have the different CORs.

Any more questions then just give me a shout,

Hope this helps,

Chris

 

[jayfray]

Thanks again Chris,

Someone else set this switch up and left the company so of course now Im in charge of figuring it all out. I will try t point to 1 route using the 2 trunks.

Thanks again.

 

[98Converter]

You can do this based on COR and Partition Route Tables. Change the Time of Day (1-8)(choose 8)on a new COR screen and make the call center agents have that new COR. Then create a new route pattern with the trunk group that you want --- in GRP No. 1 field with the appropriat FRL NPA etc... Then in your partition route tables go to column PGN 8 and under that put in the new route pattern. Bingo, every call they make should now go out that route pattern using that trunk group. give a try and let me know... I just tested it, it should work. THanks

 

[jayfray]

Thank you! I will certainly try that. I will let you know if I run into any other problems.

Thanks again!

 

[98Converter]

As a side note as well, if you're DCS'd with other PBX's this works as a great way to supply redundancy with your telephony network. Meaning if your local or LD t-1 goes down, you can route over your DCS network to go out over your other PBX's local or LD trunks and deliver the call that way. If you don't have DCS in place today, this is just information...

Thanks

 

[jayfray]

Im getting those "Tri-Tones" when trying to make a call after I changed the stations to COR 8 and changed time-of-day 8. Maybe Ive missed a step. I'll keep trying. I really do appreciate all the help.

I can administer 2 route patterns and cant add anymore. I tried changing route pattern 2 to point to trunk group 2 but something is not working.

Again, THANK YOU.

 

[98Converter]

Hrmm.. thats odd. Do a "list trace station xxxx" when you try to place the call and watch the digits it pulsing and the trunk group its accessing. This will at least let you know if its accessing the correct trunk. I'm not infront a switch right now, so I can't trouble shoot accurately to figure out what you might be missing. I also think if you just do a "change rout x" and pick a route pattern like 25 or something it should work, rather than trying to "add". ie: change route-pattern 25, then you should be able to put in your trunk info.. hope this helps...

 

[jayfray]

Thanks, I will be trying that tonight. Hopefully this will fix this once and for all. Thanks again for all your help.