Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - stevemdavis1980

Pages: [1]
1
Hello everyone, I have the following environment.

1. Mxe at Main Location.  PRI. All users are homed here are Primary. All calls and all phones register here.
2. Cx at secondary locations for SRST. Used for resiliency. Analog / LS lines for outbound calls when users are failed over to these controllers
3. All controllers connected via fiber. All calls go out main controller PRI and analog LS at Cx controllers is only used during failover

For each site, i have a dedicated DID and Ring Group which then rings specific Reception phones.  Resiliency on Ring Groups and Phones works great. Outbound calls during resiliency works great.

I am looking for suggestions on automating inbound resiliency of calls.  If communication goes down between the primary and secondary controller, I would like to automate a forwarding of the DID (or ring group extension) to the external LS lines at the secondary sites.  With Cisco phone systems, they use Call Forward Unregistered features on the phones.

For example, calls for Site 2 come in on the DID at Site A,  Controller A sees ring group and extensions are unregistered (as they are failed over), this triggers an external redirect/reroute/call forward of the DID to Controller 2's POTS lines.

I know that I can do a manual forward by using Call Rerouting and Night mode, or possibly manually change the DID termination number during an outage...but does anyone have an idea to automate this, similar to Cisco's Call Forward Unregistered feature.

thanks for any assistance or direction.
Steve

Pages: [1]