Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Here are the configuration steps for a typical way to use the AudioCodes Stand-Alone Survivability (SAS) Feature with sipXecs 4.0.

Introduction

The SAS feature can be useful for a branch office that has a local AudioCodes Gateway, but uses a remote sipXecs server.  In "Normal" mode the AudioCodes Gateway transparently proxies the SIP messages between the phones and sipXecs server.  It also sends periodic "keepalive" messages to the sipXecs server in order to confirm connectivity.  If connectivity to the sipXecs server is lost then the AudioCodes Gateway goes into "Emergency" mode allowing branch phones to make calls out the PSTN and to each other.  Once connectivity is restored, the AudioCodes Gateway switches back to "Normal" mode.

The instructions below are based on the results of my testing with an AudioCodes FXO MP-118 (5.4 40 firmware), a Polycom SoundPoint IP 430, and an LG-Nortel 6830.

Configuration Steps

sipXconfig Phone Profiles

To have a phone use SAS, configure its Outbound Proxy values as follows:

...

The profile of course also needs to be re-generated and sent to the phone.

sipXconfig Dial Plan

The Dial Plan must be constructed so that all digits dialed by the user are passed to the AudioCodes Gateway.  i.e. None of your PSTN rules can have prefixes that are dropped before the call is sent to the gateway.

This means you cannot use the built-in "Local" or "Long Distance" rules, and you will need to construct "Custom" rules instead.  The "Emergency" rule may be used, although you should test that it works in both Normal and Emergency mode.

sipXconfig AudioCodes Gateway Profile

Only two changes need to be made to the AudioCodes Gateway Profile to enable SAS:

...

The profile of course also needs to be re-generated and loaded into the AudioCodes Gateway.

AudioCodes Gateway IP -> Tel Destination Number Manipulation

After loading the profile into the AudioCodes Gateway there is some configuration that must be done through the gateway's Web interface.  These settings are not currently available in the sipXconfig AudioCodes Gateway Profile.

...

Unfortunately all configuration added through the AudioCodes gateway's Web interface will be lost each time you reload the profile.  Once you've got your AudioCodes IP -> Tel number manipulation working, be sure to write it down somewhere and re-program it whenever you reload a new profile.

Limitation affecting Polycom SoundPoint IPs

There is a known limitation affecting Polycom SoundPoint IP phones in Emergency mode ([http://track.sipfoundry.org/browse/XTRN-535 XTRN-535].)  The AudioCodes seems to have problems recognizing when a Polycom is dialing another branch phones, and instead treats the digit string as a PSTN call.  This means Polycoms cannot dial other branch phones in Emergency mode.  This problem does not affect Normal mode.

...