|
Joined: Oct 2006
Posts: 101
Member
|
OP
Member
Joined: Oct 2006
Posts: 101 |
I've looked all through the documentation and can't find this error "ARS Busy". All of our lines were busy except for one and when I pressed OUTGOING I got this error. I could manualy select the available line and dial though.
Any thoughts?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
Are all of your trunks listed in the trunk groups? Check System\Trunks to make sure each trunk has been assigned a trunk group. You can also check to see that all extensions are included in the extension list (System\Devices and Feature Codes\Extension Lists\Station) that are assigned to the trunk groups (System\CO Trunk Groups). Finally, do all station use the proper outgoing associated extension? The easiest way to change that is to copy an extension, paste it to all other extensions while only choosing to paste the "Outgoing Extension".
If I'm wrong, you have a lot of more knowledgeable guys here to help.
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
ARS is busy will happen in the following instances:
All trunks assigned to a particular facility group are busy. If the trunks were out of service you would get ARS is UNAVAILABLE.
I would check your Route Group/Facility Group programming just as a precaution to verify what trunks are used for specific call types. The route group defines what dial pattterns match that group and dictates what facility group the call is sent out on. The facility group defines the CO trunk group or Node TG connection that the call will go out on and any digit manipulations to be sent to the Telco. If there are no TGs CO or Node defined for the matching facility group, you would get a message saying Cannot Route Call.
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
BTW that last post is assuming that you are fairly current software wise. Older Axxess/Axxents did not have route groups/facility groups, you simply added CO TGs and or Node Connections groups to ARS (assuming Axxess in networked environment)
|
|
|
|
Joined: Jun 2004
Posts: 224
Member
|
Member
Joined: Jun 2004
Posts: 224 |
Had this sort of problem at a site where specific channels on the PRI were out. In our case it was 23-21. Determined issue by direct accessing channels. Took bad ones out of service until carrier fixed what they said wasn't broken. Good luck.
|
|
|
|
Joined: Oct 2006
Posts: 101
Member
|
OP
Member
Joined: Oct 2006
Posts: 101 |
Thanks for the responces. Our system is much simpler then your describing above. We have 6 analog trunks and no other nodes just one rack on the wall. Axxess v8.2
Under call routing tables there is 1-15 listed with "Trunk Number" under call routing key.
4 trunks are assigned to one department and the other 2 trunks to a different department. This is done under CO Trunk Groups Outgoing Access.
Everything works fine up untill 3 of the 4 trunks are used then when you press OUTGOING to dial out on the 4th trunk and it says ARS busy. Almost like it is saving that last trunk for a incoming call.
I don't see anywhere how it even selects which trunks to dial from when you press OUTGOING (what order to dial from). The work around is to press the 4th trunk button and dial it's just odd that it will not work from the OUTGOING button.
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
The way outgoing calls work is from the bottom up in the trunk group. You should have a trunk group numbered 92001. Within that TG you will have your LS trunks listed in the trunk list. Whatever order those are in is the order in which they are used. You will want your main LDN at the top of the list in order if the LDN hunts from the telco to roll-overs. With this config inbound start at the top and work down and outbound start at the bottom and work up. This is to lessen the chance of glare. The system will not reserve any trunk for inbound calls meaning it wont allow outbound dialing on it by default. You can configure it that way by creating two trunk groups, 92001 and 92002 and modify ARS to only use 92002 for outbound calls leaving 92001 for inbound only. In that case you would put your LDN trunk in 92001 and the remainder in 92002. You would need to modify the Facilty group trunk list to only order 92002 as by default the only TG listed for each route group is 92001.
|
|
|
|
Joined: Oct 2006
Posts: 101
Member
|
OP
Member
Joined: Oct 2006
Posts: 101 |
This sytem seems to be set up different.
CO Trunk Groups 92001 92002 92003 92004 92005 92006 PP011 Seems like there is a trunk group for each line.
With the system idle and you press OUTGOING it selects 92002 first. Not sure what order it goes from there. I know the telco rolls forward and backward on incoming calls.
What does LS and LDN stand for? Is LS loop start?
|
|
|
|
Joined: Jun 2004
Posts: 224
Member
|
Member
Joined: Jun 2004
Posts: 224 |
Looking in System / Numbering Plan / Facility groups, look an the various group types (local, toll-local, etc) and see what trunk groups you have assigned. I'm guessing that in one of those groups that is used all the time, one of the trunk groups is not assigned. We have a customer that is set up similar to yourself. Four businesses on one system, each with their own lines, shared for outgoing. By using ARS, they were able to keep open lines for incoming and distributing their outgoing to achieve that. (And as an aside,by dialing 396 and hitting the outgoing button, you'll be able to really tell if it is ARS or outgoing.) You are getting closer to solving the mystery. Good luck.
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
Yes LS = Loop Start, LDN = Main Directory Number. BaKaatz is on the money, your facility groups are jacked up somewhere. Put your TGs in the TG list in the order you want them used for each facility group. So for example: LOCAL Facility Group 92006 92005 92004 92003 92002 92001
PP011 is for unused trunks
|
|
|
Forums84
Topics94,291
Posts638,809
Members49,767
|
Most Online5,661 May 23rd, 2018
|
|
1 members (justbill),
126
guests, and
391
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|