Author Topic: Cluster transfer / re-routing issue  (Read 813 times)

Offline adambpa

  • Contributer
  • *
  • Posts: 15
  • Country: us
  • Karma: +0/-0
    • View Profile
Cluster transfer / re-routing issue
« on: March 28, 2020, 10:31:16 AM »
Hello all,

We are currently working to find a solution to an issue in a clustered environment where calls present into a SIP trunk on a MiVB 9.0 controller, pass through Nupoint call director AA, and are ultimately answered by an attendant station pinned to another cluster member and then are transferred to a stations pinned to either the same or another cluster member.  We have certain stations that are using business schedules to apply call rerouting rules to reroute calls originating from DID and CO to voicemail during daytime hours but allowing TIE and Internal calls.    Our goal is to make it so that direct outside calls cannot be made to these DNs during daytime hours, but transfers of outside callers from an attendant would be allowed.   We are relying on the COS option "Use Held Party Device for Call Re-routing" being set to "No" in order to allow this to happen with our rerouting rule.  It works great if both the attendant and receiving DN are registered to the same controller, but if the call is being transferred to stations with different primary controllers, the call rerouting rule applies regardless of the COS option being set to no.  We've tried setting the "Use Held Party device for call re-routing" option to "No" on COS 100 as we are using Direct IP vs XNET trunks.   We've also tried cutting NuPoint out of the equation and result is the same.   We had one suggestion to try this using XNET instead of Direct IP, but I'm hesitant to start making changes of that magnitude in production environment for testing.   I'm just wondering if anyone in the community has any insight on what the issue may be and how to fix it.

Thank you!
Adam


 

Sitemap 1 2 3 4 5 6 7 8 9 10