AudioCodes Mediant 500 E-SBC User Manual page 221

User's Manual
4. Mobile number: If the Lync client (or Mediation Server) is unavailable (e.g., SIP
response 404 "Not Found" upon INVITE sent to Lync client), and the PBX / IP
PBX is also unavailable, the device routes the call to the user's mobile number (if
exists in the AD).
5. Alternative route: If the call routing to all the above fails (e.g., due to unavailable
destination - call busy), the device can route the call to an alternative destination
if an alternative routing rule is configured.
6. "Redundant" route: If the query failed (i.e., no attribute found in the AD), the
device uses the routing rule matching the "LDAP_ERR" prefix destination number
value.
Note:
Lync Server, if the PBX / IP PBX system is unavailable or has failed, the device uses
the AD query result for the user's mobile phone number, routing the call through the
PSTN to the mobile destination.
The flowchart below summarizes the device's process for querying the AD and routing the
call based on the query results:
Note:
LDAP Cache' on page
Version 6.8
For Enterprises implementing a PBX / IP PBX system, but yet to migrate to
Figure 15-27: LDAP Query Flowchart
If you are using the device's local LDAP cache, see 'Configuring the Device's
211 for the LDAP query process.
221
15. Services
Mediant 500 E-SBC