MAPD issue/ question

[sway06]

We have a call recording adjunct and it's experiencing some communication issues with our G3r.

The call recording vendor is saying that due to the fact that his equipment is running at 100 base T full duplex and that the PBX MAPD is running at 10 half, there MAPD is causing a network bottle neck.

He's suggesting that we set the MAPD card at 100. Unfortunately, that cannot be done because the MAPD cannot go faster than 10 mbps.

Anyone has had the same type of issue? Any suggestions?

 

[nohuhu]

sway06,

i apologize but that's complete bullshit. map-d board is used for cti integration ONLY, it doesn't pass voice path. and internal mapd-to-switch limitations do not allow passing more than 220 (afair) asai events per second either way. considering that asai event messages are a couple hundred bytes at most, what benefit is there to be had from 100 mb/s network connection?
however, if you have call traffic large enough that one map-d board can't pass all cti traffic (and that's possible) you should consider bying an additional map-d. if you can find one.

 

[Definity]

Sway06,
I have worked in the past on similar issues, the very first thing a call recording vendor would push the problem is on MAP-D card. MAD-D is providing the CTI feed to the recording platform & they mentioned "the CTI feed is intermittent which is causing the issue". but that's not always true..

As Dwalin mentioned, What's the size of your call centre? I doubt if the traffic would be high on MAP-D to miss the switch messages?

Try setting the MAP-D to 10M if it is set to 'auto-negotiate' on your network switch.

 

[pat1960]

The Mapd and the port should be locked to 10 MB, half-duplex. Once you go to AES then the port settings can go to 100 MB full-duplex.

Avaya remommends that the connection be on it's own network, isolated from all LAN traffic.

 

[Cti4all]

MAPD eth driver is not capable of configuration, UNIXWARE in those days did not support 100mbps rates. Therefore, if CTI server configured to talk to the MAPD, or eth switches/routers/hubs are auto or hard set at 100, packets must be re-packaged due to packet size differences between 10 and 100 mbps. The buffers on the network appliances have difficulty keeping up in busy times when having to re-package as a sustained 200 ms delay will bring a link down.

Further, the auto-negotiate adds a discovery packet to the network every few seconds. Again, UNIXWARE does not know what this is, so it causes an exception every time a discovery is sent to the MAPD.

Keep the MAPD client and all network applicances hard-set at 10mbps and if possible, isolate MAPD network segment so no other hosts running at 100 will broadcast packets to MAPD.

To illustrate why 10mbps is more than enough, recent lab tests with AE Services running at 720+ messages per second over multiple CLANs put <2% network load on the ethernet port on AES. AES uses 100mbps to communicate with CLAN so at 2%, this would be 2mbps or 20% of the 10 mb MAPD pipe. So, a MAPD would never come close to max on network bandwidth and your recording vendor is correct!

 

[phonegoober]

Cti4all,

Quick question on this. We are installing a MAPD for CTI to work with a Call Recording system.
We have having a big problem where we won't take a
/23 subnet in the Subnet Mask and Default Router.
Ever heard of that on these boards and if so, what can we do?

thx

 

[FoneFun]

I suggest you take the MAPD and put it in a different VLAN.

When we had the MAPD on our normal network, it would get a boatload of broadcasts from other machines. Yes it's on a switched port, but still get broadcasts for things like Master Browser or something like that.

So put your MAPD and the CTI server (or whatever is talking to your MAPD) in a separate VLAN.
If your network equipment is not capable of a separate VLAN, you could also consider doing a connection directly from your MAPD to the CTI server using a cross-over cable.

In our CTI server we put 2 network cards, one for our normal network, one for the connection to the MAPD VLAN.

A 3rd option is to put your CTI server and your MAPD in it's own IP range/subnet, different than your normal network. Yes it requires 2 network cards, or you can put 2 IPs on 1 NIC card depending on your OS, but a NIC card is not expensive so get a 2nd one.

You have no choice but to set the MAPD at 10/half as that is the only speed that is supported. I have about 200 agents connected via Avaya CT server to the MAPD and the 10/half is not a problem.