Ip network Vs IPLC for off-shore call center

By thomaskw ·

I am on a project to implement a offshore Callcentre and would like to know the impacts (advantages and disadvantages) between IP network Vesus IPLC? What other components are involved. Anyone has a infrastructure diagram design? Appreciated for your reply.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

why a offshore Callcentre????

offshore callcentre's put me right off with dealing with a business i only deal with companies were there callcentre's are in the same country in this case the UK.

Collapse -

Apples and Oranges

by glehr In reply to Ip network Vs IPLC for of ...

First we define what the difference is since the same amount of bandwidth can be purchased either way.

IPLC - also known as a dedicated circuit, rides a perscribed "engineered" route and all bandwidth is dedicated to a single customer on those connections. This also means that if there is an outage, like a T1 you use a portion of happens to go down anywhere between sites, than you are affected 100%. any interuption in the direct path equals an outage. this is good, because you can also get redundant paths to protect yourself, and no worries about someone attacking your services.

IP networks. Use a common backbone, and you get what ever bandwidth you pay for. you can use frame relay or ATM and get committed levels of service, but you go into the cloud, and come back out, there is no direct path. the path the first packet takes might be different from the next , or the next. Good thing is you are not dependant on certain facilities, and usual outages are caused by what mort refer to the final mile, into your centers. Also using a cloud service might open you to attacks. wether denial of service, or if over open internet, the regular security concerns for open architecture.

Personally, For a two center scenario, I like IPLC, because my company maintains the equipment on each side, and a single point of contact gets someone to look at your path alone in a faster manner. my experience is it takes a general service cloud outage longer to be acknowledged. and if it is worth having a redundant circuit with another carrier, then I could switch them and no fault scene. If you happen to go VOIP, you can protect yourself by using the IPLC in Multilink between routers and keep a redundant path active at all times.

Some people even go as far as getting the IPLC as a backup to an IP solution, so both sides are covered.

Hope this helps.

Related Discussions

Related Forums