If you intend to be an Outsourcer/Service Provider then you pay a specific price and get "NAM" software.
If you are a big customer with a number of business units that want to manage as individual entities (i.e. instances) then you pay a different price and get "ICM" software.
There are a few technical details relating to the Network-side ICM (called NAM Instance) and the customer-side ICM (called the CICM Instance(s)) and things like security and AW design but you distilled it down nicely.
(If you intend to be an Outsourcer/Service Provider then you pay a specific price and get "NAM" software)
so you mean that i should move to hosted edition and enterprise does not satisfy outsourcing by its ICM instances..!
then, my question in other words, if i have enterprise edition, and there are 5 customers, each customer has his own ICM and IP-IVR and they want to connect to my ICM Ent. then is this applicable? do i need to add IPCC gateway for each customer or just i have to add ICM instance for each customer?
also, what is the added vlaue for a customer has his own ICM and IVR to connect to a ICM hosted-edition service provider?
You said, "so you mean that i should move to hosted edition and enterprise does not satisfy outsourcing by its ICM instances..!"
How the product is designed and functions may be dramatically different than how it is licensed and I guess that was my intention of the last post. I would suspect that if you are an outsourcer and you are providing ICM services to other customers then Cisco will be charging you NAM licensing.
To get even more basic, consider the following: There is no difference between 5 ICM customers with 5 ICM systems installed on separate servers than 5 ICM customers with 5 Instances installed on the same servers - they're still not communicating with each other. One is a stand-alone model and the other is a semi-hosted model but they are very much independent entities. One has the physical boundaries of server separation and the other has the logical boundary of instance separation.
NAM as well as using the ICM instances as you describe essentially puts you in a âcommand and controlâ mechanism over all the instances. If you just want to connect two ICM systems, i.e. you have one and a partner has one then connect them via ICM to ICM Gateway to share call routing data. If you want âcommand and controlâ then install NAM with reliant Customer ICMs.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...