Account Codes Causing Strange Problem

[DDrop]

Merling Legend R7.0

Recently I added an accounting program and plugged SMDR into it and it works fine. I programmed Forced Account Codes for 5 or 6 extentions with account code entry buttons. If I dial 9 on an SA button and get rejection tone... that's good. If I press account code entry, enter code, press pound, use SA and dial 9 and you get dial tone... that's good. I thought I was done but it turns out if you try to dial a number, it seems to want to connect but after about 5 secs you get a rejection tone.

Outcalling works fine if you do not use account codes. I disabled Forced account codes and dialed out from an extension and entered the code after the call connected. That works fine, however if I dial a number and quickly tap the account code button and enter the code + # before it rings the first time, the call is rejected.

I thought maybe, even though it shouldn't, it might affect the extension's FRL, so I set the ARS FRL for both route 17 and 18 to 0, still no go.

I also went ahead and did a board renumber just for fun, but that didn't change a thing. I've beaten my head against the wall on this one, i mean this is to simple a feature to screw up. I'm almost to the point were I want to backup and default the system but I have a feeling I'll spend a freakin' hour and a half downloading and uploading programming just to end up right where I'm at now.

P.S. Just for info, during dialing the number it displays "OUTSIDE" which means it gets through ARS but has problems when grabbing a channel. I have also tried assigning a pool button to the phone and it works the same way just without dialing 9. This is a PRI which my gut tells me might be some source of this wacky situation.

ANY HELP WILL BE MUCH APPRECIATED
ANY HELP THAT SOLVES THIS WILL BE FOLLOWED BY DISBELIEF AND A FEELING OF STUPIDITY

 

[merlinman]

It sounds as if your Account codes may be being passed to the PRI.

Do you have any NON PRI Lines you could use as a test?

 

[DDrop]

Not at all. That was my assumption but that shouldn't be the case. I tried a few methods of absorbing digits but to no avail. Not to mention, are these digits sent before or after the phone number?

Bottom line, really, is that the account code feature should have nothing to do with any digits sent out of the T1. It just simply tags the call with a number for SMDR. I may try a few other things to try to absorb the digits because I really didn't put alot of effort into this.

I will be there again today and I'll cross one of the 016T/R cards into the first line and give it a shot. Gut feeling says it will work, but that just leaves us with the idea you supplied, it's somehow shipping the digits out over the PRI or it is somehow otherwise changing the digits with a tag or who know's what.

I suppose my best option is to get the PRI provider on the phone and have them monitor the digits that come from my system.

Seems like a lot for something as simple as account codes, but sometimes, that's just a Legend for you. I mean really, I've done complex ARS tables with crazy FRLs and set up about a bagillion PRIs and now account codes are going to be the end of me. Technology is great.

Thanks for taking a minute with me anyway, just hearing someone else say that may just set me in the right direction. I was hoping someone would see this and have a red flag go up in their head but what are the chances someone has seen this before?

I'll try to remember to post what I find out for future reference.

 

[DDrop]

I just did the same thing on a Magix and it works fine. Unfortunately they only have POTS lines so it doesn't tell me much about the other place other than it should work.

 

[Pepperz]

Could you just use regular account codes from those extensions, and enter them "during" the call, but not make them forced?

Pepperz at newper dot net

 

[DDrop]

Yeah, that works but it's pretty awkward to enter it that way.

I did the same thing at another site that had POTS lines and it works fine.

I checked with the PRI provider and they say the calls aren't even hitting their switch when I use account codes so that rules out the extra digits theory. I tried it on a regular line by crossing a tip and ring port over, and it works fine. It seems like there is some strange restriction between account codes and the PRI. Makes me wonder if it would work on a standard T1, or a PRI routed by line appearance.

I used avaya tech support and they had me delete authorization codes from an extension and then try. ????

Of course it didn't work. Im thinking about using another processor but I have the feeling it won't change a thing.

Bottom line, this really sucks.

 

[merlinman]

If you have access to Avaya Support, call back and get a TIER-3 Engineer to help.