I found it...
It was a COR issue where we were limiting the VM ports from calling 911, but Direct IP Route for the other Clusters also used the same COR Group Number. So in blocking 911, we also blocked the VM ports from calling other Cluster extensions. [banghead]
A big thank you to Ralph...
Site A
MiCollab 7.3.0.204
MiContact Center 8.1.3.0
MiVoice Business 8.0 SP1
Site B
MiVoice Business 8.0 SP3 PR2
In my Call-Flow on MiCollab, I have a Blind Transfer to the Gathered Digits (4 digit ext). This works fine for any extensions that are local to the MiVoice Business but you get an...
Thank you, that was just what I needed. It looks like the Zone ID will be the way to go.
The only downside is - NOTE: A hot-desk user who is logged into a set uses the zone settings that are assigned to the physical set DN, not the zone settings that are assigned to the hot desk DN.
Thank you for your response. It confirms what I was seeing in testing.
I currently have it "working" as outlined below.
TFN -> Site A MiCollab -> Site A Sys Speed -> Site B ACD Path -> Site B ACD Agent
The issue is that none of the information shows in Site A MiContact Center. How hard...
Site A
MiCollab 7.3.0.204
MiContact Center 8.1.3.0
MiVoice Business 8.0 SP1
Site B
MiVoice Business 8.0 SP3 PR2
Is there a way to get an Agent at Site B in a ACD Skill Group at Site A?
In my testing, I could make Site B Agent's Secondary Element Site A which then allowed me to add Site B...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.