Filter
Top Products
Post Installation Configuration 35
Different conference types may require different routes. For example, if
users dial the prefix 76 to call Ad Hoc conferences and 74 to call other
conferences, then one route is required for dial pattern 76 and another is
required for dial pattern 74.
3 Program the Conference Attendant extension number. For example, to
program extension 7501, enter:
4 Program a route for conferences. For example:
5 Program a destination route entry for the NBX extension of the 3Com IP
Conferencing Module. For example:
Add Trusted SIP
Interfaces
Trusted SIP Interfaces may be SIP gateways, other NBX systems, 3Com
VCX telephone systems, Call Processors, or other trusted interfaces. Each
interface you add and how you configure it affects your device licensing.
Each audio path trusted end point requires one system device license.
You do not add telephones as trusted interfaces. For information about
how to add 3Com telephones and generic SIP telephones to the NBX SIP
mode system, see the NBX Administrator’s Guide.
To add or modify a trusted SIP interface:
1 See the NBX Administrator’s Guide for more information about the
details in these steps.
2 Log in to the NBX NetSet utility using the administrator login ID and
password.
3 Click SIP Applications > Trusted SIP Interfaces.
4 Click Add to add a new trusted interface or click an extension from the
list to modify that trusted interface.
5 See the online Help for detailed information about each field.
Command ID Entry Digit Min Max Class Priority Route
TableEntry Create 1 33 7501 4 4 Internal 0 8
Command Route Description
DestinationRoute Create 8 Conferences
Command Route Entry DestinationExtension
DestinationRouteEntry Create 8 1 7500