White Paper - TANDBERG and Cisco Call Manager

TANDBERG and Cisco CallManager
____________________________________
TANDBERG
D13907.01
This document is not to be reproduced in whole or in

part without the permission in writing from:
TANDBERG
TANDBERG TANDBERG and Cisco CallManager
1 Table of content
1 Table of content............................................................................................................................... 2
2 Introduction ..................................................................................................................................... 3
3 TANDBERG video endpoints for Cisco CallManager ...................................................................... 4
3.1 Requirements .......................................................................................................................... 6
3.2 Install the TANDBERG CallManager Plug-in on the CallManager server ................................ 6
3.3 Configuring the TANDBERG video unit for registration to the CallManager ........................... 6
3.4 Configuring the TANDBERG SCCP video endpoint in the Cisco CallManager ....................... 7
3.5 Configuring the TANDBERG video endpoint manually in the Cisco CallManager................... 7
4 TANDBERG H.323 endpoints and Cisco CallManager .................................................................. 12
4.1 Registering a TANDBERG H.323 endpoint to the CallManager ............................................ 13
4.2 Configuring an H.323 Endpoint in the Cisco CallManager ..................................................... 14
5 TANDBERG Gatekeeper and Cisco CallManager.......................................................................... 18
5.1 Adding a Gatekeeper into the Cisco CallManager .................................................................. 19
5.2 Registering a CallManager trunk to a TANDBERG Gatekeeper............................................. 22
5.2.1 Configuring the Cisco CallManager with an H.225 trunk (Gatekeeper controlled).............. 23
5.3 Call routing ........................................................................................................................... 27
5.3.1 Configuring the Cisco CallManager route group................................................................ 27
5.3.2 Configuring the Cisco CallManager route list .................................................................... 29
5.3.3 Configuring the Cisco CallManager with a Route Pattern .................................................. 35
6 TANDBERG Expressway and Cisco CallManager......................................................................... 39
7 TANDBERG Gateway and Cisco CallManager.............................................................................. 40
8 TANDBERG MPS and Cisco CallManager.................................................................................... 44
9 TANDBERG MCU and Cisco CallManager .................................................................................. 45
10 TANDBERG Management Suite and Cisco CallManager .............................................................. 46
11 Summary ....................................................................................................................................... 46
D13907.01 2
2 Introduction
TANDBERG and Cisco have for several years been working closely together to provide a video solution
that can be combined with an existing IP telephony service managed by Cisco CallManager. As a result of
this TANDBERG can offer a unique range of video products that works together with the Skinny Call
Control Protocol (SCCP) equipment. In addition to the standard H.323 video endpoints TANDBERG has
developed special video endpoints exclusively for Cisco CallManager. These endpoints combine support
for Cisco CallManager phone features along with the familiar user interface of the Cisco IP phones, while
providing parts of the TANDBERG video functionality. This document will discuss how these endpoints
are integrated in with Cisco CallManager and will provide example solutions to provide a sample
configuration.
Additionally, this document will overview how the TANDBERG infrastructure and management products
can work together with the Cisco CallManager to provide a total solution for voice and video on the SCCP
and H.323. Figure 1 shows an example network overview featuring both SCCP and H.323 endpoints
Internet
SCCP network H.323 network
CallManager Gatekeeper Border Controller
T1000 MXP
Gateway
T770 MXP
MCU PSTN
Figure 1: The total solution
D13907.01 3
3 TANDBERG video endpoints for Cisco CallManager

Most of the products in the TANDBERG product portfolio are developed for networks using the H.323,
H.320 or SIP protocol. One exception to this, however, are the TANDBERG video endpoints for Cisco
CallManager as these endpoints do not directly support these networks, but rather support the proprietary
Cisco protocol, SCCP, used in a Cisco CallManager environment. These products support a wide range of
Cisco IP telephone features, such as direct call control, directory and XML services provided by
CallManager. Very similar to the Cisco IP telephones, the TANDERG video endpoints for CallManager
are directly managed by CallManager itself.
Cisco 7970
CallManager
T1000 SCCP
T770 MXP SCCP

Cisco 7970
Figure 2: TANDBERG Video endpoints for Cisco CallManager integrated into the Cisco CallManager
network.
The TANDBERG endpoints for Callmanagers are based on two hardware platforms the MXP and the
Classic. The following TANDBERG endpoints have support for the SCCP protocol:
MXP platform:
TANDBERG 550 MXP for Cisco CallManager
TANDBERG 770 for MXP Cisco CallManager
Classic platform:
TANDBERG 550 for Cisco Callmanager
TANDBERG 1000 for Cisco Callmanager
D13907.01 4
To provide the users with the familiar interface the TANDBERG endpoints for Cisco CallManager has a
graphical interface and remote control that is specifically designed to match the Cisco IP phones user
interface. Figure 3 shows and example of an screen shot from the TANDBERG MXP unit; please note the
existence of the ‘soft buttons’ at the bottom of the screen that allow the system to provide the advanced
functionality of Cisco CallManager. These buttons are then activated by pressing the corresponding ‘quick
keys’ at the top of the TANDBERG remote control 2, as demonstrated in Figures 3 and 4 below
Figure 3: Screenshot from TANDBERG MXP Figure 4: TANDBERG remote control
The user interface on the Classic endpoints has three soft buttons with the colors green, yellow and blue in
the bottom of the screen. These soft buttons can be activated by pressing the colored quick keys at the top
of the TANDBERG remote control, as demonstrated in figure 5.
Figure 5: Screen and remote control of a Classic endpoint for CallManager
D13907.01 5
3.1 Requirements
The TANDBERG endpoints listed previously can be easily integrated with Cisco CallManager software
versions 4.0 and later. Additionally, the TANDBERG Video Endpoint software plug-in must be installed
on the CallManager servers.
3.2 Install the TANDBERG CallManager Plug-in on the CallManager

server
1. Download "TANDBERG_CallManager_Plugin.exe" from

http://ftp.tandberg.net/pub/software/endpoints/cisco_call_manager_series
2. Run the plug-in on the Call Manager server
3. Follow the on-screen instructions
Note: It is not necessary to reboot the server after the installation
3.3 Configuring the TANDBERG video unit for registration to the

CallManager
The TANDBERG video endpoints for CallManager supports DHCP and option 150, meaning your DHCP
server can provide the unit with the IP address of the CallManagers TFTP server in addition to the DNS
server IP address, the units IP address, subnet mask and default router.
1. Connect Ethernet to your TANDBERG video endpoint for Callmanager and then power on the
unit
2. Enter the network settings menu
3. Choose IP-assignment: DHCP/static (boot to take effect)
If IP-assignment = DHCP:
If the DHCP server provides the CCM TFTP address in the "TFTP-SERVER-NAME" option, you
should be up and running.
You can also provide the CCM TFTP address yourself by choosing "Alternate TFTP Server" YES,
and typing in the TFTP address in the TFTP configuration menu.
If IP-assignment = static:
1. Enter preferred IP-address
2. Enter the correct subnet mask and default router
3. Enter the CCM TFTP address in the TFTP configuration menu
4. Enter the Domain Name and DNS address(es) in the DNS configuration menu*
5. Boot your TANDBERG endpoint to have the changes take effect
6. The TANDBERG endpoint should now register with the Call Manager
For more information on the Network configuration see the Network settings in the TANDBERG endpoint
user manual.
Note: The TANDBERG SCCP endpoint has to be configured with a DNS server IP address. If there is no
DNS server present in the network, configure the TANDBERG endpoint with a fictitious DNS IP address.
D13907.01 6
3.4 Configuring the TANDBERG SCCP video endpoint in the Cisco

CallManager
The TANDBERG video endpoints for the Cisco CallManager are inserted into the CallManager similarly
to the way this is done for the Cisco IP phones. There are two ways of doing this, either by allowing for
auto registration of endpoints to the CallManager, or inserting the endpoints manually. The following
example will show you how to configure an endpoint manually in the Cisco CallManager.
3.5 Configuring the TANDBERG video endpoint manually in the Cisco

CallManager
Add a new phone:
1
2
1. Select phone from the device drop down menu.

2. Click on the “Add a New Phone”.
D13907.01 7
Select the “TANDBERG Video Endpoint” from the “Add a New Phone”
3. Select the phone type.
Note: The TANDBERG video plug-in has to be installed to get this option.
D13907.01 8
8
4. Insert the MAC address of the TANDBERG unit.

5. Insert a description of the TANDBERG unit (optional).
6. Select the Device Pool.
7. Select the phone button template (default set to Standard TANDBERG Video).
8. Click on the “Insert” button.
D13907.01 9
A pop up will appear and ask you if you want to add the directory number, click “OK” to enter the
Directory number configuration page.
Configuring the phone directory number:
12
9
10
11
9. Insert the phone number of the unit in the Directory Number field.
10. Choose the partition from the drop down menu (optional).
11. Select “Auto Answer with Speaker” phone or “Auto Answer off”.
12. Click on the “Add” button.
D13907.01 10
If the configuration in TANDBERG unit and the Cisco CallManager is correct the phone number of the
video unit should appear in the upper right corner of the video units screen, and the unit should appear as
registered in the phone list.
Search for the phone in the phone list:
The TANDBERG video endpoint for Cisco CallManager is now ready for use. You will be able to use this
unit both for video and voice calls. For more information on how to use the TANDBERG endpoints for
Cisco CallManager please see the user manual.
For interoperability see the TANDBERG software appropriate software release nots for the TANDBERG
H, I and M-series endpoints.
D13907.01 11
4 TANDBERG H.323 endpoints and Cisco CallManager

At the moment the H.323 protocol is the most mature protocol for visual communications over an IP
network. Most of today’s video conferencing vendors have support for the H.323 protocol in their
products. As such, users of professional video conferences most often choose equipment that provides
support for H.323 because this protocol offers high video resolution, multiple video streams, high quality
audio, secure content and other features that make H.323 more attractive than other protocols.
In order to bridge H.323 and SCCP together, Cisco has included support for H.323 within CallManager,
thereby allowing endpoints that support each type of communications protocol to interoperate with each
other and allow for visual communications across disciplines. There are two ways of configuring the
network to allow for calls between a H.323 endpoint and a SCCP endpoint. You can either register the
H.323 endpoints directly to the CallManager or you can register the H.323 endpoint and a CallManager
trunk to a Gatekeeper, the differences between these two configurations will be discussed later in this
chapter.
No H.323 endpoint supports SCCP directly, meaning it is not possible to use these endpoints the same
way as you do with a Cisco IP phone. For example, these endpoints will not be able to transfer a call,
place a call on hold, park a call, access services on CallManager or take advantage of the other features
made possible by Cisco CallManager. However, H.323 endpoints that support Empty Capabilities Set
(ECS) will be able to fully function in conjunction with SCCP devices by supporting the ability for the far
end to place it on hold, transfer it, etc. By supporting ECS, an endpoint will allow the far end to terminate
all active audio and video streams to that site without having the overall call fail (the endpoint will just sit
idle waiting for these streams to re-establish). By supporting ECS, an H.323 endpoint will be able to
connect to an endpoint that supports SCCP and the SCCP unit itself will not notice a discernable
difference between the two protocols. Because of the lack of ability to support the advanced features such
as hold and transfer, any endpoint that supports ECS should not be mistaken for an endpoint that supports
SCCP directly.
Note: All TANDBERG MXP video endpoints support Empty Capability Set
D13907.01 12
4.1 Registering a TANDBERG H.323 endpoint to the CallManager

Some H.323 endpoints (including TANDBERG) have the option of registering directly to Cisco
CallManager and utilize CallManager to provide Gatekeeper/H.323 control functionality; a suitable
configuration for those networks with a small endpoint install-base. This type of solution allows for the
endpoints’ E.164 alias to be fully integrated into the telephony dial-plan. However, there are several
disadvantages when registering an endpoint directly with CallManager when compared to registering the
systems with a fully functional H.323 gatekeeper. The Cisco CallManager only supports H.323 version 2,
and because of this several of the features used in professional video meetings will be lost in a call
between two H.323 units that are registered to the Cisco CallManager.
For example, any call involving these endpoints will not be able to utilize expanded functionality such as
TANDERG Duo Video, H.239, H.235 encryption, H.264, high quality audio (AAC-LD) and high video
resolutions like 448P. Additioanlly, it will not be possible to use most of H323 infrastructure products
available, as CallManager does not support registration of these devices including the TANDBERG
gateway, MCU and MPS. It is because of these limitations that it is recommended to integrate an H.323
gatekeeper into CallManager through the creation of an H.323 trunk in CallManager. The integration of
an H.323 gatekeeper will allow communication between H.323 and SCCP endpoints as well as provide the
ability for the H.323 endpoints to implement all of the advanced features such as encryption, H.239 and
others.
However, if a direct registration from the MXP endpoint to CallManager is desired, a few settings will
need to be configured properly within the MXP endpoint in order to ensure compatibility between the two
systems. Using the TANDBERG remote control navigate to Control Panel > Administrator Settings >
Network > LAN Settings > H.323 Settings and select CallManager for H323 Call Setup, go into the
CallManager settings and enter the IP address of the CallManager. For more information about the
TANDBERG MXP endpoints see the TANDBERG MXP User Manual.
Note: Because CallManager is not a Gatekeeper the endpoints will not get any feedback on the
TANDBERG MXP that it is registered, and the unit will not show its e.164 alias in the top of the screen as
it does when it is registered to a gatekeeper
D13907.01 13
4.2 Configuring an H.323 Endpoint in the Cisco CallManager

The Cisco CallManager has no control of the H.323 endpoints directly registered, but rather a mapping of
the E.164 alias (phone extension) to the specific IP address of the endpoint. Unlike a gatekeeper the
CallManager has no way of telling if this endpoint is reachable or not as there is not any active registration
between the endpoint and CallManager.
Figure 6 shows and illustration of a TANDBERG H.323 video endpoint that is registered to the Cisco
CallManager:
CallManager
MXP H.323 SW
T1000 MXP SCCP
T770 MXP SCCP
Figure 6: TANDBERG H.323 endpoint registered to the Cisco CallManager
D13907.01 14
When adding an H.323 endpoint to CallManager, simply match the extension configured for this endpoint
to the IP address assigned to the system. This process is illustrated by the example below:
Add a new phone:
1
2
1. Select “Phone” from the device drop down menu.

2. Click on “Add a New Phone”.
Select the phone type:
3. Select the “H.323 Client” from the phone type drop down menu.
D13907.01 15
Inserting the H.323 client configuration in the CallManager:
4
5
4. Insert the H.323 video units IP address in the “Device Name” field.
5. Insert a description in the “Description” field (optional).
6. Select the device pool.
7. Make sure the signaling port is set to 1720.
A pop up will now appear and ask you if you want to add the directory number. Click OK to enter the
directory number configuration page.
D13907.01 16
Configuring the H.323 client directory number:
10
9. Insert the H.323 video units E.164 alias (phone number) in the “Directory Number” field.
10. Click the “Add” button.
To verify that the unit has been inserted into the CallManager you can look it up in the CallManager’s
phone list.
You have now inserted an H.323 client into the Cisco CallManager and should be able to dial to and from
this unit using phone numbers.
D13907.01 17
5 TANDBERG Gatekeeper and Cisco CallManager

As discussed previously, registering H.323 endpoints to the Cisco CallManager will limit the functionality
of the H.323 endpoint. These limitations can be prevented, however, by integrating an H.323 gatekeeper
into the SCCP setup instead of the endpoints directly. The gatekeeper is installed into CallManager by
configuring an H.225 trunk and registering the trunk directly to the gatekeeper.
Note: A gatekeeper is central part of the H.323 infrastructure. It provides address translation to the
network for H.323 terminals, Gateways and MCU’s.
There are no specific requirements for the configuration of the TANDBERG Gatekeeper to be able to
register a CallManager trunk to it. But be aware that authentication is not supported in this setup and if the
gatekeeper is configured with an allow/deny list make sure that the Trunk is registered in this list or it will
cause the gatekeeper to reject the registration. This chapter describes how to configure the CallManager so
that it is possible to place calls between the H.323 network and the SCCP network, to do this the following
settings has to be configured within Cisco CallManager:
H225 trunk (gatekeeper controlled)
Route group
Route list
Route pattern
Note: Routing calls between H.323 and SCCP is done by prefixes and route patterns, so before you start
doing the necessary configurations on the CallManager it is recommended to make a number.
D13907.01 18
5.1 Adding a Gatekeeper into the Cisco CallManager

Before you configure the CallManager with a H.225 trunk it is necessary to insert the gatekeeper address
and name into the CallManager. When this is done you will be able to select this gatekeeper as the
gateway for the H.225 trunk.
Add a Gatekeeper into the Cisco CallManager:
Select gatekeeper from the Device drop down menu.
Click on “Add a New Gatekeeper”.
D13907.01 19
Insert the Gatekeeper:
1
2
1. Insert the Gatekeepers IP address in the “Host Name/IP Address” field.

2. Fill in the description in the “Description” field.
A pop-up will now appear and tell you that you need to reset the gatekeeper for changes to take affect.
Click on “OK” and then click on the reset button in the gatekeeper configuration page (this will not reset
the TANDEBERG Gatekeeper)
D13907.01 20
To verify that the Gatekeeper is inserted into the CallManager list all the gatekeepers and check that the
name and IP address can be found in the list.
D13907.01 21
5.2 Registering a CallManager trunk to a TANDBERG Gatekeeper

CallManager provides the ability to configure an H225 trunk (gatekeeper controlled). When configured,
the trunk will register directly with an H.323 gatekeeper along with a prefix (similar to an H.323-to-H.320
gateway), thereby routing all calls that begin with the specified prefix to be routed between the two
networks.
Figure 7 shows an illustration of the trunk between the SCCP network and the H.323 network.
CallManager Gatekeeper
T1000 MXP SCCP
T770 MXP SCCP
Trunk
Figure 7: Registering an H.225 trunk to the TANDBERG Gatekeeper
D13907.01 22
5.2.1 Configuring the Cisco CallManager with an H.225 trunk (Gatekeeper

controlled)
Add a new trunk:
1 2
1. Select “Trunk” from the device drop down menu.

2. Click on “Add a new Trunk”.
Select the trunk type:
3. Select the H.225 trunk (Gatekeeper Controlled) from the trunk type drop down menu.
D13907.01 23
Configure the Trunk:
4. Configure the name and description of the trunk.

5. Choose the device pool.
6. Disable “Wait for Far End H.245 Terminal Capability Set”.
D13907.01 24
7. Choose the number of significant digits.

8. In Gatekeeper Information select the gatekeeper, set the Terminal Type to Gateway, insert the
wanted prefix that the trunk should register to the gatekeeper with and insert the name of the zone.
9. Click on the “Insert” button in the top of the web page.
D13907.01 25
The Trunk should now register to the gatekeeper. To verify the success of this registration, consult the
active registrations on the gatekeeper. This can be done on the TANDBERG gatekeeper through the
administrative web interface through System Status > registration. The trunk, when registered, should
appear with the trunk name and the IP address of CallManager. To verify the correct prefix for the trunk,
click on the trunk registration and select the ‘Details’ button at the bottom of the registration page..
Verify that the prefix to call to the SCCP units is in the Gateway Prefix.
For more information on the TANDBERG Gatekeeper see the TANDBERG Gatekeeper user manual.
D13907.01 26
5.3 Call routing

To be able to call from the SCCP network to the H.323 network the CallManager will need to be
configured with a Route Group and Route Pattern that will forward all calls beginning with a specific
prefix to the gatekeeper. Configure a Route Group with the H323trunk(s) and the Route List with the
Route Group. Below, please find an example that will illustrate how to configure a Route Group, Route
List and Route Pattern to forward calls to an H.323 network. For more detailed information about these
functions use the “Help for this page” function in the CallManager web interface or see Cisco’s
CallManager documentation e.g. Cisco CallManager fundamentals.
5.3.1 Configuring the Cisco CallManager route group

A Route Group can contain several gatekeeper trunks.
In the Route plan drop down menu select “Route/Hunt” and click on “Route Group”
Add a new Route Group:
Click on the “Add a New Route Group”
D13907.01 27
Configure the Route Group:
1. Give the Route Group a describing name

2. Select the Gatekeeper trunk and click on ”Add to Route Group” (the trunk should now appear in
the “Current Route Group members window”)
3. Click on the “Insert” button to add the route group
If you do not have any specific requirements for the distribution algorithm you should leave it to the
default setting, Circular. For more information on these choices use the CallManager’s help for this page.
D13907.01 28
5.3.2 Configuring the Cisco CallManager route list

A route list can contain several route groups
In Route plan drop down menu select “Route/Hunt” and click on “Route List”
Add a new Rout List:
Click on the “Add a New Route List”
D13907.01 29
Configure the Route List:
1. Insert a Route List Name.

2. Select the “Cisco CallManager group”.
3. Click on the “Insert button”.
A pop up will now appear, click “OK” to add a Route Group.
D13907.01 30
Add a Route Group into the Route List:
Click on “Add Route Group” to select the route group you which to use (the Route List Detail
Configuration page should now appear)
D13907.01 31
Select Route group:
1. From the “Route Group” drop-down list choose the Gatekeeper route group and add it to the route
list.
When the “reset the route list for change” pop up appears click “OK”.
D13907.01 32
Reset the Route List to update the CallManager Route List Configuration:
Click on the “Reset” button to update the Route List.
D13907.01 33
Find Route List in the CallManager configuration:
To verify that the Route List has been created us the “Find and List Route List”, the Route List should
appear in this list with the name and status.
D13907.01 34
5.3.3 Configuring the Cisco CallManager with a Route Pattern

The Route Pattern is used to locate a destination (e.g. a gatekeeper in the H323 Network). When a user
dials a number, CallManager looks at all the Route Patterns locally configured to verify whether or not
one of the patterns matches the number that has been dialed. Route Patterns can use wildcard as digit
placeholders, providing for easy management. For example, if the H.323 number range is from 9000 to
9999 it is not necessary to specify each of these dialing number in number pattern, but rather configuring
the pattern with ‘9XXX’ instead to match the first digit of ‘9’ and simulate wildcards for all others. An
additional wildcard of ‘!’ can be used to simulate that all calls after the specified prefix should be routed to
this specific pattern, no matter the number of digits. The following example will illustrate the
configuration for a route pattern of ‘9!,’ thereby routing all calls beginning with a ‘9’ to the H.323
network
Note: CallManager looks for the best single match when searching through the route patterns.
In the Route Plan drop down menu select “Route/Hunt” and click on “Route Pattern”.
D13907.01 35
Add a new Route Pattern:
Click on the “Add a New Route Pattern”.
D13907.01 36
Configure a Route Pattern:
1. Insert the Route Pattern.

2. Choose the H.323 gatekeeper route list from the “Gateway or Route List” drop down menu.
D13907.01 37
To verify that the Route Pattern was inserted you can look at the list of Route Patterns that are configured
in the CallManager (from the example below you see that there are several different route patterns that are
pointing at the same route list)
Note: The H.323 support in the CallManager is limited to H.323 version 2, because of this the calls
between the SCCP endpoints and the H.323 endpoints will be using H.261 or H.263 even thought both
endpoints support H.264 (H.264 is not supported in H.323 version 2)
The configuration of the routing rules and trunk between the CallManager and the Gatekeeper is now
completed and you should be able to place calls between the SCCP network and the H.323 network.
D13907.01 38
6 TANDBERG Expressway and Cisco CallManager

The TANDBERG Expressway solution is an enabling technology that will allow H.323 endpoints to
securely traverse a firewall. The TANDBERG Border Controller is the key component of this technology
by serving as the traversal server within the solution. Using the TANDBERG Border Controller in
conjunction with the TANDBERG Gatekeeper will allow endpoints that don’t support the Expressway
technology to traverse a Firewall.
By implementing the Border Controller on a network, all SCCP endpoints can make use of the traversal
technology through integration with a TANDBERG gatekeeper and complete H.323 calls with endpoints
outside of the local firewall. To make use of the Expressway solution, CallManager must first be
configured to register an H.225 trunk to the gatekeeper. Expressway will then be utilized as part of the
normal H.323 network deployment.
When connecting a call from an SCCP endpoint to an H.323 endpoint outside the network, call setup will
first go through CallManager, to the TANDBERG Gatekeeper, through the Border Controller to the
endpoint outside the firewall. For more information on the TANDBERG Expressway, reference
documents D13381 TANDBERG Gatekeeper and D13691 TANDBERG Border Controller user manual.
Figure 8 show an illustration of the SCCP and H.323 network with an Expressway solution to traverse a
firewall.
Internet
CallManager Gatekeeper Border Controller
T1000 MXP SCCP
T770 MXP SCCP
Trunk
Figure 8: TANDBERG Expressway and Cisco CallManager
D13907.01 39
7 TANDBERG Gateway and Cisco CallManager

The TANDBERG Gateway provides a means of connecting H.323 endpoints to H.320 endpoints located
on remote or local ISDN circuits. By registering CallManager to an H.323 gatekeeper through an H.225
trunk, SCCP endpoints can now take advantage of any gateway resources located within the same H.323
network by including the gateway prefix within the dial string.
Figure 9 shows an illustration of the SCCP network that is connected to H.323 network with a
TANDBERG gateway.
PSTN
CallManager Gatekeepe TANDBERG
T1000 MXP SCCP
T770 MXP SCCP
Trunk
Figure 9: TANDBERG Gateway and Cisco CallManager
Note: The TANDBERG Gateway does not support Empty Cap. Set, this means that you can not transfer,
hold or park a video call; if you try to do this you will lose the video.
D13907.01 40
To be able to place calls from SCCP units through the TANDBERG Gateway the CallManager has to be
configured with a routing pattern that routes the call to the Gateway via the Gatekeeper, meaning the route
for the ISDN Gateway has to point at the Gatekeeper. The Gateway has to be configured with a prefix for
the H.320 service, e.g. if the prefix for dialing an outside ISDN line is 0, the gateway has to be configured
with a H.323 service prefix 0.
Configuring the TANDBERG Gateway with an H.323 service:
1 5
In the H.323 service menu:

1. Click on “Create new”.
2. Service description.
3. Service prefix.
4. Max. call bandwidth.
5. Click on “Save Changes”.
D13907.01 41
The TANDBERG Gateway has to be configured with ISDN dial in setting that specifies how it should
handle incoming calls from ISDN. In the “ISDN Dial In” menu it is possible to specify the following
setting:
IVR
DID
TCS4
Dial in number
Max dial in bandwidth
Permission to dial in
2
3
1. Set the extension dial in, in this example both IVR and TCS4 is enabled.
2. Insert the ISDN dial in number
3. Set the max dial in bandwidth.
4. Enable incoming phone calls.
5. Click on the save button in the bottom of the screen
For more information on the TANDBERG Gateway, reference document D13187 TANDBERG Gateway
User Manual
D13907.01 42
To be able to route calls from the SCCP network an H.323-to-H.320 Gateway, configure CallManager
with a Route Pattern to forward a gateway service prefix to forward the call to the H.323 gatekeeper. At
this point, the gatekeeper will then forward the call to the gateway for connection. An example of this
configuration is below, routing all calls beginning with the service prefix of ‘0’ to the H.323 network for
connectivity.
Configuring the CallManager with a Route Pattern for Gateway calls:
1. Insert the Route Pattern, in this example 0 followed by !, meaning any number starting with 0
2. Choose the H.323 Gatway Route List (see chapter 5.3 Call Routing for more information about
Route Pattern, Route List and Route Group).
3. Click on “Insert”.
Both the CallManager and the TANDBERG Gateway is now configured with the necessary setting and
you should now be able to place calls between the SCCP network and the ISDN network.
D13907.01 43
8 TANDBERG MPS and Cisco CallManager

A Multipoint Control Unit (MCU) is used for combining multiple video and/or audio streams together into
the same conference to aid in the collaboration amongst many different remote sites. In a multipoint
conference all the endpoints connect to the MCU; the MCU will transmit the voice and video to all
participants, the layout on this video stream depends on the configurations of the MCU.
The TANDBERG MPS is an MCU for Enterprises and Service providers. The capacity on the MPS is up
to 40 conferences and a total of 160 site connections. The recourses on the MPS can be used for
conference calls with H.323 endpoints, SIP endpoints, H.320 endpoints, SCCP endpoints or a conference
with a mix of all these endpoints. Through the H.225 trunk established earlier, any SCCP endpoint can
now join any H.323 MCU (or H.320 MCU by way of the gateway).
Figure 10 shows an illustration of the SCCP network connected to a H.323 network with a TANDBERG
MPS.
PSTN
CallManager Gatekeeper TANDBERG MPS
T1000 MXP SCCP
T770 MXP SCCP
Trunk
Figure 10: TANDBERG MPS and the Cisco CallManager
Note: The SCCP clients will not be able to utilize all the H.323 feature supported by the MPS but it will
send and receive audio and the main video stream.
For more information about the TANDBERG MPS, reference document D13373 MPS User Manual.
D13907.01 44
9 TANDBERG MCU and Cisco CallManager

The TANDBERG MCU is an MCU for small to medium enterprises. There are two versions of the
TANDBERG MCU, 8 video calls and 8 voice calls or 16 video calls and 16 voice calls. The recourses on
the MCU can be used for conference calls with SCCP clients and a mix of SCCP clients and H.323 clients.
To be able to place a call between the MCU and a SCCP endpoint the MCU and a CallManager trunk has
to be registered to the Gatekeeper.
Figure 11 shows an illustration of the SCCP network connected to a H.323 network with a TANDBERG
MCU.
PSTN
CallManager Gatekeepe TANDBERG MCU
T1000 MXP SCCP
T770 MXP SCCP
Trunk
Figure 11: TANDBERG MCU and the Cisco CallManager
Note: The TANDBERG MCU do not support out of band signaling
For more information about the MCU, reference document D12911 TANDBERG MCU User Manual
D13907.01 45
10 TANDBERG Management Suite and Cisco CallManager

TANDBERG Management Suite (TMS) is a web-based management system primarily used for
controlling, scheduling, upgrading and maintaining H.323 and H.320 units. However, with TMS 11, TMS
is now capable of supporting upgrades of the TANDBERG MXP endpoints for Cisco CallManager. In a
Cisco CallManager environment the CallManager manages all the SCCP endpoints. The CallManager
uses TFTP to upgrade the SCCP endpoints; the TANDBERG MXP systems for CallManager do not
support upgrade over TFTP and can therefore not be upgraded via the Cisco CallManager, thereby
creating a void between the video systems and the IP telephones located in an enterprise; TMS fills this
void.
Note: TMS has a scheduling function that makes it possible to schedule calls from TANDBERG H.323
devices TMS do not support scheduling of SCCP units, but it is possible to include them in a scheduled
call from a TANDBERG H.323 device.
11 Summary
This document described how to configure the CallManager for registration of TANDBERG MXP
endpoints for Cisco CallManager, and what software is needed on the CallManager to be able to do this. It
also described how to register a TANDBERG H.323 endpoint to the Cisco CallManager.
Registering the TANDBERG H.323 endpoint to the CallManager will give several limitations compared
to TANDBERG H.323 endpoints that is registered to a Gatekeeper, the reason for this is that the
CallManager only supports for H.323 version 2. In a call between two H.323 units this will cause some of
the H.323 version 4 and 5 features to fail. To be able to keep all the H.323 features in a call between two
H.323 endpoints and still be able to place calls between a SCCP unit and a H.323 unit you have to register
all the H.323 units to a Gatekeeper and make link between the H.323 network and the SCCP network.
This document showed you how to do this by configuring the CallManager with an H.225 trunk and
registering it to a Gatekeeper.
Once the CallManager has registered a trunk to the Gatekeeper it will be possible to place calls between
all the TANDBERG H.323 units and the units in the CallManager Network, this means that the SCCP
endpoint can use several of the recourses on the H.323 network. In this document it has been described
how to configure the network to allow a SCCP endpoint to use resources on the TANDBERG Gateway,
TANDBERG MPS, TANDBERG MCU and the TANDBERG Expressway solution.
The last chapter in this document provided information on management of units on these two networks,
there are no software that can manage both the SCCP network and the H.323 network so the
recommendation is to use TMS to manage the H.323 equipment and use the Cisco CallManager to manage
the SCCP equipment.
D13907.01 46

White Paper - TANDBERG and Cisco Call Manager

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

White Paper - TANDBERG and Cisco Call Manager

Uploaded by

Copyright:

Available Formats

TANDBERG and Cisco CallManager

This document is not to be reproduced in whole or in

CallManager Gatekeeper Border Controller

Figure 1: The total solution

3 TANDBERG video endpoints for Cisco CallManager

T770 MXP SCCP

Figure 3: Screenshot from TANDBERG MXP Figure 4: TANDBERG remote control

Figure 5: Screen and remote control of a Classic endpoint for CallManager

3.2 Install the TANDBERG CallManager Plug-in on the CallManager

1. Download "TANDBERG_CallManager_Plugin.exe" from

Note: It is not necessary to reboot the server after the installation

3.3 Configuring the TANDBERG video unit for registration to the

3.4 Configuring the TANDBERG SCCP video endpoint in the Cisco

3.5 Configuring the TANDBERG video endpoint manually in the Cisco

Add a new phone:

1. Select phone from the device drop down menu.

3. Select the phone type.

4. Insert the MAC address of the TANDBERG unit.

Configuring the phone directory number:

Search for the phone in the phone list:

4 TANDBERG H.323 endpoints and Cisco CallManager

4.1 Registering a TANDBERG H.323 endpoint to the CallManager

4.2 Configuring an H.323 Endpoint in the Cisco CallManager

SCCP network H.323 network

T1000 MXP SCCP

T770 MXP SCCP

Figure 6: TANDBERG H.323 endpoint registered to the Cisco CallManager

Add a new phone:

1. Select “Phone” from the device drop down menu.

Select the phone type:

Inserting the H.323 client configuration in the CallManager:

Configuring the H.323 client directory number:

5 TANDBERG Gatekeeper and Cisco CallManager

5.1 Adding a Gatekeeper into the Cisco CallManager

Add a Gatekeeper into the Cisco CallManager:

Select gatekeeper from the Device drop down menu.

Click on “Add a New Gatekeeper”.

Insert the Gatekeeper:

1. Insert the Gatekeepers IP address in the “Host Name/IP Address” field.

5.2 Registering a CallManager trunk to a TANDBERG Gatekeeper

SCCP network H.323 network

T1000 MXP SCCP

T770 MXP SCCP

5.2.1 Configuring the Cisco CallManager with an H.225 trunk (Gatekeeper

Add a new trunk:

1. Select “Trunk” from the device drop down menu.

Select the trunk type:

Configure the Trunk:

4. Configure the name and description of the trunk.

7. Choose the number of significant digits.

5.3 Call routing

5.3.1 Configuring the Cisco CallManager route group

Add a new Route Group:

Click on the “Add a New Route Group”

Configure the Route Group:

1. Give the Route Group a describing name

5.3.2 Configuring the Cisco CallManager route list

Add a new Rout List:

Click on the “Add a New Route List”

Configure the Route List:

1. Insert a Route List Name.

A pop up will now appear, click “OK” to add a Route Group.

Add a Route Group into the Route List:

Select Route group: