EasyManuals Logo

AudioCodes Mediant 800 User Manual

AudioCodes Mediant 800
1482 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #903 background imageLoading...
Page #903 background image
CHAPTER37 Advanced SBC Features
Mediant 800 Gateway & E-SBC | User's Manual
The device enables outgoing calls from all equipment that share the same line
simultaneously (usually only one simultaneous call is allowed per a specific shared
line).
You can configure whether REGISTER messages from secondary lines are
terminated on the device or forwarded transparently (as is), using the
SBCSharedLineRegMode parameter.
The LED indicator of a shared line may display the wrong current state.
To configure BroadSoft's Shared Line feature:
1. In the IP Groups table (see Configuring IP Groups), add a Server-type IP Group for the
BroadWorks server.
2. In the IP Groups table, add a User-type IP Group for the IP phone users and set the 'SBC
Client Forking Mode' parameter to Parallel so that the device forks incoming calls to all
contacts under the same AOR registered in the device's registration database.
3. In the IP-to-IP Routing table (see Configuring SBC IP-to-IP Routing Rules), add a rule for
routing calls between the above configured IP Groups.
4. In the Inbound Manipulations table (see Configuring IP-to-IP Inbound Manipulations), add a
manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register to
the device's database under the primary extension contact (e.g., 600):
'Manipulation Purpose': Shared Line
Match:
'Request Type': REGISTER
'Source IP Group': IP Group that you created for the users (e.g., 2)
'Source Username Pattern': Represents the secondary extensions, e.g., 601 and 602
Action:
'Manipulated URI': Source (manipulates the source URI)
'Remove From Right': "1" (removes the last digit of the extensions, e.g., 601 is
changed to 60)
'Suffix to Add': "0" (adds 0 to the end of the manipulated number, e.g., 60 is changed
to 600)
Configuring Call Survivability for Call Centers
The device supports call survivability for call centers. When a communication failure (e.g., in the
network) occurs with the remote voice application server responsible for handling the call center
application (such as IVR), the device routes the incoming calls received from the customer (i.e.,
from the TDM gateway) to the call center agents.
In normal operation, the device registers the agents in its users registration database. Calls
received from the TDM gateway are forwarded by the device to the application server, which
processes the calls and sends them to specific call center agents, through the device. Upon a
failure with the application server, the device routes the calls from the TDM Gateway to the agents.
The device routes the call to the first available user it founds. If the call is not answered by the user,
the device routes it to the next available user. The SBC can handle a sequence of up to five users,
after which the session is timed out and the call is dropped.
- 863 -

Table of Contents

Other manuals for AudioCodes Mediant 800

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes Mediant 800 and is the answer not in the manual?

AudioCodes Mediant 800 Specifications

General IconGeneral
ProtocolsSIP, H.323
Digital Interfaces1/2 E1/T1 PRI
ManagementWeb, CLI, SNMP
Mounting19-inch rack
CodecsG.711, G.729, G.722, G.723.1
Power Supply100-240V AC
Operating Temperature0 to 40°C
Storage Temperature-25 to 70°C
Humidity10% to 90% non-condensing

Related product manuals