ARS configuration 8.1

[nickburns31]

Hello friends,
I have had an issue with an Avaya IP 500 8.1 config with outgoing phone calls. I have been trying to narrow it down to see which outside line is causing the issue or perhaps its in the ARS configuration. I have 7 CO analog lines dialing out and every now and again a recording comes on that says a "long distance access code is required." I have tried to deal with Fairpoint thinking it was their issue but they are saying no. I am back to square one thinking maybe something isn't right in the ARS.

 

[smokinjoe2938]

no this is a provider issue for sure! test each line to find out which one is giving you this message, also once you find out which line you could change the outbound line id so it doesn't grab that line going forward, but that is only a bandaid until provider issue is resolved

 

[holdmusic34]

1) Go across the trunks one at a time with your buttinksy and make a long distance call.
2) Find out when the error is occurring from the customer and under what conditions. Only when they call Nebraska?
3) You can create a create time stamp short code which will stand out in a running monitor trace. Leave ars filters enabled.

 

[nickburns31]

Thanks for the quick replies... Seems I can dial out on all the lines BUT I checked the status and I see errors on their main line with "loop current not detected." I am wondering if this is causing an issue with there switch... Any ideas?

 

[smokinjoe2938]

could be a bad port or a bad co line,use system status and make test calls and make sure all lines test ok

 

[TouchToneTommy]

Use a butt set on the lines before they hit the IP Office and be sure that there is a long distance carrier on each, and does not require an account code for long distance.

 

[nickburns31]

Hey Touchtone... I confirmed this that I can dial out on each one...

 

[TouchToneTommy]

a recording comes on that says a "long distance access code is required." [/quote}

That recording is not coming from the IPO, so you're going to have to determine which of the 7 analog lines is being used when a user encounters that message. Either the ARS is modifying the outgoing string of numbers in some way that the carrier does not like, or that particular line has been programmed at the CO without a long distance carrier or requiring an account code.

 

[smokinjoe2938]

As ttt says, one of the lines needs a long distance pic code at the central office, you would have to make an long distance call from each line to isolate the line that fails the ld call and then open up a ticket with the line provider

 

[nickburns31]

Yes ... TTT is right on which is my thoughts that the ARS is modifying a string of numbers.. I verified that I can dial out on all the lines on the CO side of the system. It may be in the short cuts that I am overlooking? This is a basic setup that doesn't require special short cuts other than the basic 9N... Do you know te lines of short cuts I should have in the ARS?

 

[smokinjoe2938]

Not ARS but no long distance pic code on one of your lines

 

[nickburns31]

Amazingly , Fairpoint came out and said that they don't think the issue is their problem.. BUT they did say if you dial the digits slower it will help alleviate the issue. I am leaning to restore the ARS to as simple as possible. Do you know what lines I should have in there? Also does it matter whether or not its a capital N or lower case as well as the X's?

 

[smokinjoe2938]

Do you know what lines I should have in there? how would we know what type of lines you have? and yes use a capital N and lower case for the x's