We have AD-120 126.96.36.199 with D/41 analog boards, NEAX 2400 IPX switch, and a serial configuration key (dongle). <br>The dongle allows only serial integration and the AD-120 is set to use serial integration (that means the settings from the key match the ones from the AD-120, we have serial integration set in both). <br>The NEC 2400 PBX is sending the integration information using the MCI serial connection to the AD-120. We have verified that the information is received by the AD-120 following the steps:<br>- we have captured the serial packets with HyperTerminal and they are exactly as described in MCI documentation fo NEC 2400 IPX, (ICS MCI format) <br>-we have verified that the information is received using the Integration Monitor. Ex of raw data : <br><br><STX>0!J0011601____430011602__0011600__<ETX><br><br>The integration monitor DOES NOT print the message "INVALID PACKET", so we assume that the packets are valid. In fact the message is (under the Reason section) "Direct Call". But this is the only information printed by the Integration Monitor; the Dialed Number, Calling Number and Forwarding Ext sections are empty. <br>Call Viewer acts the same way, it prints all the information about the call except the Dialled Number, Calling Number and Forwarding Station.<br>We have done some tests with Maestro Tools. We have activated the diagnostic 10,11,12 and 13 under the group MiuIntegration and 16 (Event Wait Results) from MiuGeneral. The log shows that the digits from integration are received and that event for LINECALLINFO message is signalled:<br><br>18:31:48:769 (AvMiu_MC,654,MiuGeneral,16) [Thread 0x000005A4] [Port 3] Method CAvMiuLine::CallInit() WaitFor(LINE_CALLINFO) succeeded (Received: LINE_CALLINFO). <br><br>So we assume that the integration packet is received. <br>BUT, the integration does not work, and the AD-120 does not have the information about caller id => Openning Gretting is always played. More than that, in the the logs we have the following message:<br><br>18:31:48:769 (AvMiu_MC,693,MiuIntegration,13) [Thread 0x000005A4] [Port 3] NewCall received no CallInfo from Integration. <br><br>The AD-120 is installed on Win2000 Server and Exchange 5.5.<br><br>Any idea why this is happening ? <br><br>P.S. Anything else it works (we did'nt verified MWI yet, but we will do it). I mean AD-120 works, but it acts like it has no integration information.<br><br>
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...