Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Does anyone have their ICM located on their corporate LAN/WAN?

I've worked for a company that did, and now work for a company that doesn't. Currently, our connectivity is so slow b/c we're connecting via 56k lines, versus network connections. Just curious if anyone has an opinion on either of the set-ups?

Thanks,

Julietta

2 REPLIES
New Member

Re: Does anyone have their ICM located on their corporate LAN/WA

There are pros & cons to both... it is hard to argue with the fact that more bandwidth is better for the application. However, if you are fighting for space with other applications, it is hard to support. We run over our corporate LAN/WAN, but we have copious bandwidth and our LAN/WAN engineers have prioritized our traffic so that we don't compete for bandwidth or switching/routing resources. This setup has worked well for us.

One note on your other thread with regard to long update times on changes to your ICM config.... my first thought is that Router/Logger pairs are busy. That *could* be a bandwidth issue if messages are queued up, but be sure to check hardware, too.

Good luck...

RR

New Member

Re: Does anyone have their ICM located on their corporate LAN/WA

We are on the corporate WAN and have craved out dual PVCs for ICM use only. Our bandwidth varies by site but is between 128 and 512. The LANs at each site have VLANs configured for all "voice applications" such as ICM, IEX, PBX, etc....

We are currently using static routing on the WAN, so when one of the circuits goes down, we have to manually re-route the traffic. At the time of our implementation this was the only way we could keep our PGs connected to the Central Controller. We were having OSPF issue which have since been corrected with an upgrade to our router OS.

93
Views
0
Helpful
2
Replies