Unity 4.0(2) + Avaya Definity G3 Si Integration Issues

[calmichael]

System info: New Unity 4.0(2) Install on MCS with Dialogic D/120-JCT-LS,

PBXLink 48, and Avaya Definity G3 Si (System 9 software).

The PBXLink digital line is assigned to DN 4065, which is bridged to eight

analog lines that are associated with the lines going into the Dialogic card.

We have followed the integration notes, and those included in the PBXLink

package without full success; we are having two major issues and one

minor issue not attributed to the integration of the systems.

One, a call from an Avaya set to a Unity subscriber will get the default Unity

greeting everytime. Integration Monitor seems to display accurate SMDI

information with reason, calling number, and forwarding extension info

populated every other line. However, the call viewer utility is not showing

information as every call seems to be labeled as external with no calling,

dialed, or forwarding information.

We are receiving a "No numbers in user names" warning on the PBXLink.

We reviewed the doc on CCO that talks to setting the MsToWait to 4000

and that did not help. Our SE told us to add a entry of DoNotStripZero=

to our Avaya0002.ini file (restarting everything) which also did not provide

positive effect.

On a good note, we can call Unity, leave a message after entering the Unity

subscriber from the handler, and MWI enables / disables timely.

We think that it is something simple we are overlooking. . .

Two, when we retrieve a subscriber message via TUI, when the message is

playing and the user touches "7" to delete before the message is finished,

the volume decreases significantly. We are using optional conversation 1.

In the reference materials for optional conversation 1, "7" is not assigned

to an decrease volume - or anything, while "8" does increase the volume

back.

This seems like a unannounced feature. . .

Three, not tied to integration, is when the adminstrator tries to import an

Exchange User from SA, and the business phone field in Exchange has

an entry with a hyphen character in it, Unity seems to get upset. If you

highlight the bad character and try to delete it, Unity does not allow the

correction. Only when the admin highlights the whole entry and then

deletes it does Unity allow a change.

Is this expected behavior?

--- Thanks ---

[oliviers]

On the first problem, make a call to the first port of Unity with both the Integration Monitor and the CallViewer open. Do the port numbers listed in both apps match? If not, the analog lines aren't plugged into the voice board correctly. If they do match, what's on the system key for integration?

On the second problem, I have no idea.

On the third problem, what exactly do you mean by get upset? Does the SA generate an error? If the hyphon is removed from AD, does it work? I'll also try this on my server to see what happens.

[calmichael]

Issue 1 has been resolved by TAC, and it was similar to what you began to

key on that the port number was not showing up as 1 thru 8 in integration

monitor.

In the PBX Link, the LTNs were set to the extensions that would correspond

to our analog links (actual DNs). On a whim, we changed these eight entries

to 0001 . . . 0008, and this corrected the issue. Extension means port # not

analog line extension. . .

On Issue 3, the Exchange "Business Phone" field was populated with

xxx-xxx-xxxx. When you import from Unity SA a user with that in it, it will not

allow you to delete the - character at all unless you highlight the full field

and delete it. A partial delete will make Unity respond with an illegal

character entered error message even though you are trying to delete the

disallowed characters; annoying - but not show stopping.

I would like to know if issue 2 has been detected by anyone though.

--- ----- ---

[cairns-a]

I have the same setup you have. I was getting the same issue with the default greeting, but it was the fact that I had the Call Manger configured first in the ports on Unity. I started over and added the Avaya ports first then the Call Manager and everything worked fine.

The one issue I have now is that the Avaya side has low volume. The Call Manager sounds good and loud. But the Avaya side is very low volume compared to the Call Manager. I was wondering if you had the same issue and if so what did you do to correct it?

Thanks in advance.

Trae