Configuration objects entered into the child system can automatically be sent to the parent Unified ICM and inserted into the Unified ICM configuration, thus eliminating the need to configure objects twice....
Does this also apply in the other direction? Can you enter objects into the Parent and have it propogate these changes to the child. For example, can I add an agent into the parent and flag it to be used for one of the child systems? Or do all the moves, adds, changes (including scripting changes) have to be made on the child systems? Is there even an AW in the parent location?
2. Can someone provide the best link that describes all the reporting ramifications of parent/child? I am specifically looking for which information is propogated from the child > parent.
3. With Parent/Child are there issues with having overlapping directory numbers between child locations? For example, can DN 5000 exist in one child location as well as another child location? How does this impact reporting?
4. In Parent/Child do the "childs" have the be "System IPCC" or can they be Traditional as well?
Seems to me that for #3, there are potentially issues. I haven't worked with Parent/Child. But I have worked with NAM/CICM. I think if the IVR is CVP, you will want to handle ingress and queueing in the Parent/NAM. And if CVP is involved, you will need a consolidated dial-plan for GK configuration.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...