New sipx admins who set up HA (High Availability) are often disappointed when
they realize that only the commserver
(proxy/registrar) provides redundancy. The sipx roadmap calls for creating
redundancy of other components (voicemail,
auto-attendant, MWI, RLS/BLF, ACD, sipxconfig) but those improvements are a
ways off. Regardless, even the commserver redundancy is
of little use if the primary target for inbound calls to sipx is an
auto-attendant, which is a common configuration (as opposed to
having DID to individual sipx users). If the primary server is down then so is
the auto-attendant, which means inbound calls never
get delivered even though the distributed server is up.
Has anyone found a good way to deal with this limitation? One thought I've had
is to configure sipx so that inbound calls go to a
dummy extension which does serial call forwarding, first to the auto-attendant,
and then directly to an operator's line or hunt
group. For example:
- gw sends inbound calls to x900 (which is NOT the alias of an AA)
- x900 is configured with a serial User Call Forwarding list:
1) x100 (AA)
2) local operator's extension, or hunt group of appropriate users
Will that work? Does anyone have better/different ideas?
If we come up with a good way to deal with this issue then in it might be
worthwhile to find a way to express it in the sipxconfig
GUI, so it's clear to sipx admins without them having to ask the questions I'm
asking.
Thx, -m
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
