Serial integration error

[admin_2]

We have an AD-120, multiple integration on the key, NEAX2000 IVS2 and some D42NE cards inside AD-120 system.<br>We selected serial integration in SA. Everything seems to be fine, serial settings are OK, MWI is lighting if new message arrives, but...<br>Integration is not really serial performed. If the serial cable is unplugged, caller ID is sent via digital ports, but MWI is not working. In other words, integration works only in one sense.<br>We captured from serial monitor packets over the cable. Here is a problem: AD-120 expects some packets starting with "0!", but NEAX2000 do not send packets in this way. For this reason, integration monitor says "invalid packet" for any call.<br>Here is a sample. <NUL><NUL> is the cause of invalid packet error. 0!A6307 means that this is a MWI information and is OK (MWI for #307).<br><br><STX><NUL><NUL>J001300_____43001304____________<ETX><br><STX><NUL><NUL>J001300_____43001304____________<ETX><br><STX><NUL><NUL>J001301_____43001307____________<ETX><br><STX>0!A6307_________<ETX><STX>0!A6307_________<ETX><br><STX>0!A6307_________<ETX><STX>0!A6307_________<ETX><br><STX><NUL><NUL>J001300_____43001307____________<ETX><br><STX><NUL><NUL>J001301_____43001304____________<ETX><br><STX><NUL><NUL>J001300_____43001307____________<ETX><br><STX><NUL><NUL>J001300_____43001304____________<ETX><br><STX><NUL><NUL>J001300_____43001307____________<ETX><br><STX><NUL><NUL>J001301_____43001304____________<ETX><br><STX><NUL><NUL>J001302_____43001307____________<ETX><br><STX><NUL><NUL>J001300_____43001304____________<ETX><br><STX>0!A2307_________<ETX><STX>0!A2307_________<ETX><br><STX>0!A2307_________<ETX><STX>0!A2307_________<ETX><br><STX><NUL><NUL>J001300_____42001307___001304___<ETX><br><STX><NUL><NUL>J001302_____43001307____________<ETX><br><br><br>Any suggestions?<br><br>Thanks<br><br>Ciprian<br><br>

[#2]

Every NEAX2000 I have seen has sent packets starting with 0!. If this one isn't, try opening \Commserver\Intlib\AvMci.avd and removing the "0!" from the packet definitions listed there and then restart Unity. From the looks of the remainder of the packet that the PBX is sending, it should match.

Steve Olivier
Software Engineer
Cisco Systems

[#3]

We already tried this solution.
Everything appears to be out of error, but in the integration monitor window, the caller has no ID listed.
We are not sure if called ID is actually decoded by serial integration using this trick...

Thanks,
Ciprian

[#4]

It's not. It's getting it from the D42 board. The integration monitor only shows serial stuff. Check the CallViewer. That will show call info regardless of how it came to the system.

Steve Olivier
Software Engineer
Cisco Systems

[#5]

CallViewer works fine, but since I selected serial integration, I expected to take caller ID information from serial connection.
The hardware key has multiple integration, but what if the key was serial integration only?

[#6]

I think it's still going to look at the D42 info. What version of AD-120 is it? Is there a problem with caller ID?

Steve Olivier
Software Engineer
Cisco Systems

[#7]

The AD-120 version is 2.4 build 2.4.6.135
I don't understand why since the selected integration is serial and via VM integration the call signalling is carried out, why caller ID is taken from digital ports?
OK, for the user point of view, there is no problem if the system is informed about caller, no matter how.
But this dual information way souds a little bit strange. For instance, what if our hardware key is serial integration only? Caller ID info must be taken from serial connection, I suppose.
In our AD-120/multiple integration key/D42NE2 boards serial connection is used only for MWI, even integration is serial.

Thank you!

Ciprian

[#8]

This integration is probably the most confusing. What's even more confusing is that with AD-120, there are multiple things that need to be considered:

1. Integraton bit on the system key
2. Integration type in the switch file
3. MWI type in the switch file
4. TSP type (i.e. D41 or D42)

Each deal here has multiple values, so imagine the number of permuations that we have, that's what makes this so confusing.

I took a quick look at the code (2.4.6.135 based) and it should work like this:

Direct Digital OR Multiple Integraiton Type on the system key = Incoming integration of D42 and MWI type user configurable depending upon what is in the switch file.

Serial Integration on the system key = Incoming integration of serial and MWI type serial.

Steve Olivier
Software Engineer
Cisco Systems