[cisco-voip] IPCC Design considerations

[CarlosOrtiz at bayviewfinancial.com]

Yes, but in this case since the calls are only for agents in this location 
it would work out well.  If there is a WAN outage all they require is a 
hunt group setup to predefined extensions.  I just wanted to make sure 
there were no techincal reasons why this wouldn't be done for this 
scenario.  Thanks for the feedback.

Carlos



Matthew Saskin <matt at saskin.net> 
01/28/2008 04:12 PM

To
CarlosOrtiz at bayviewfinancial.com
cc
cisco-voip at puck.nether.net
Subject
Re: [cisco-voip] IPCC Design considerations






The main con (which is the same for all sites) is that you have no call 
distribution if the WAN link goes down.  The upside to this setup is 
that since you have local PSTN instead of sending calls across the WAN, 
you can use CCME for SRST along with the B-ACD tcl scripts to do minimal 
local prompting/queueing/call distribution in failover mode.

I've set up multiple clients with similar infrastructure for larger IPCC 
Enterprise installs - CallManagers/IPCC servers centalized in data 
center(s), remote sites with PSTN connectivity and gateways configured 
for CCME for SRST and B-ACD.

-matt

CarlosOrtiz at bayviewfinancial.com wrote:
> 
> We primarily have a distributed IPCC setup with agents across a few 
> sites.  From our central HQ site salls are then distributed to agents 
> locally and over the WAN.   We do have one call center that is fully 
> contained at a remote location.  Is there any problem or drawbacks to 
> delivering calls directly to this location's gateway with the 
> centralized IPCC server at HQ?  Can someone explain the pros and cons 
> for these scenarios.
> 
> Carlos
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080128/e7c8125a/attachment.html