Ok, that rules out that one then. Also, I agree with your analysis that this is not related to silence detect. Most likely the calls are dropped because Dialogic is detecting what it believes to be a disconnect event from the PBX. A TAC engineer should be able to confirm this with MiuGeneral 12 and 16 diags. Unfortunately, there's nothing passed through TAPI to Unity that will tell us exactly what sort of event Dialogic thinks it is seeing.
The two main possibilities are a break in loop current or a disconnect tone. Since your NEAX2000 is probably signaling real disconnects with loop current breaks (can you verify this?), you can crank down on the Dialogic's generic disconnect tone definitions without adverse effect. This will reduce the chance of false detects. Here is a common method fo doing this...
- Verify the file name for your active switch file. Probably is NEC00013.INI (look in the registry at HKLM > SOFTWARE > Active Voice > MIU > 1.0 > Initialization > Switch 0 > Switch Configuration File)
- locate your active switch file in the \CommServer\Intlib folder and open it with notepad
- paste the follow tone definitions to the bottom of the file (standard US reorder tone and dial tone).
[Switch Disconnect Tone]
Frequency1=480
FrequencyDeviation1=100
Frequency2=620
FrequencyDeviation2=100
TimeOn1=250
TimeOnDeviation1=60
TimeOff1=250
TimeOffDeviation1=60
Cycles=8
[CO Disconnect Tone]
Frequency1=350
FrequencyDeviation1=100
Frequency2=440
FrequencyDeviation2=100
TimeOn1=4000
- save the changes and restart Unity
