intuity and legend integration issue

[jaxjen]

I was wondering if anyone has run into this problem. i have a legend system with an intuity voicemail system. The voice mail system failed and had to be replaced, when this happened we started having issues with any extension with a "1" in the middle of the string. For example 310-319 will not transfer to the phone and routes back to the auto attn, as if the extension doesn't exist. But when you dial internally the call rings the phone and after the set amount of rings it is answered by the voicemail. any one run into this. I am at my wits end on this

 

[phonesrus]

Sounds like you have a dial plan range conflict in the voicemail. What release 4.x or 5.x
When the system was replaced, was it restored from a backup tape or built from scratch? Was the system new from Avaya, or a refurb unit?
Go to switch interface admin>>call data interface>>system translation>>dial plan translation and see what entries are there.
Also from Audix admin do a "list ext" and see if anything unusual exists.
Its Kinda hard to guess what is going on without poking around in the unit, but that is where I would look first.

 

[jaxjen]

The system was refurbished, and it is release 5.x. It was programmed from scratch as the original system was totally dead. The strange thing is that the old system (version 4.x the legend system is version 6.x) was not having this problem. I checked the dial plan translation and it is set to 3 digits and start ext 000 to 999. I have extensions from the Legend ranging from 120 up to 420, and the only problem seems to be the 310 to 319 range. Thanks

 

[ttech]

have you used the monitor feature or put a digit grabber on a port to see what he Audix is sending to the switch?

 

[phonesrus]

Is the Audix transfer restriction set to "subscribers" or "digits"? Default is subscribers, which means that you must have a mailbox for the 310>319 range in order to do a transfer to a phone from an "AA", If Annie says "please wait" and then the transfer fails "transfer cannot be completed" then there is a conflict. Either in the AA, Transfer parameters, or something relating to "31".

 

[jaxjen]

The transfer resriction is set to subscribers, transfer is basic and i am now told we have a problem with extensions now starting with the digit "1". Short of changing every extension to 2XX. The transfer parameters are set to default. Any ideas!!??
Thanks again

 

[phonesrus]

I would say you need to inspect all the allowed/disallowed numbers/ranges in the vm. There has to be something that has been entered or is remaining from the refurb. If it was a fresh load to a formatted drive then it "should" be clean. Since I cannot see into the machine, right now its kinda' "go fish". Look at every parameter and setting in each available field that is administerable, that is what I would do. Also, inspect the event and alarm logs for a few recent days and look for anything out of place.

 

[phonesrus]

I just ran across this while browsing the PCN notices on Avaya support.
This might be a possible cause of your issue.
There have been multiple issues with the 016 T/R (617F34) cards in Legend/Magix systems.

http://support.avaya.com/elmodocs2/qppcn/1288Bu.pdf

Merlin Legend® Esc Code
Merlin Magix™ Esc Code
Description of Problem

LG4423
NA
DID calls using DTMF signaling misroute when the routing digits contain a '1' in the pattern.

Something worth investigating, as the issue relates to a "1" in the DN. And since you have an Intuity with analog Mode-Code integration.

 

[orypecos]

Weren't they able to reload the system with the backup tape?

 

[phonesrus]

I am going to hazard a guess and say they had a 3.x or 4.x machine that failed, and no access to a RUK kit to upgrade to a 5.x. Which would not have been much help in any event if the drive died because you could not upload the upgrade software from the kit and perform an upgrade backup.

 

[jaxjen]

I think now we may be on to something here. The enviroment is a depot, in a nutshell, we have approx 32 merlin legends w/intuity voicemail. So we did a little investigation on the systems that were using the same version of the intuity with the legend that were NOT having the problems with the dial "1" and every one of them are using the 012 boards. the ones that have this problem are using 016 boards with ring gen. Well i am going to change out these boards and see just what happens...Will let you know...

 

[jaxjen]

Nope it didn't work, back to the drawing board. Apparently it has something to do with the 5.1 version. Still investigating, any suggestions?????

 

[phonesrus]

Like I said earlier, look at the alarm and event logs for unusual entries when you attempt a call to one of the problem stations. The 5.1 software is, for the most part,
basically the same as the 4.X software. The exceptions are the 5.X versions are IDE based and the 4.X are SCSI based drives. They are both UNIX devices. Since the 016 boards, according to your statement, did not clear the issue then it has to be something in the VM.
Avaya hid a couple of software wrinkles in the transfer parameters that required tier 3 intervention with default loads, one was in Mode Code. I think I have a Legend Intuity in our lab, but it will be sometime next week before I will have a chance to look at it.