Tandberg Gateway registration with CCM

[Scottie]

We have successfully set up calls to route thru CCM to the tandberg MXP 323 endpoints but have been unsuccessful in making calls from actual Tandberg units to a remote IP phone 7941 series.

Any suggestions

[DRI]

Hi,

What version is the CCM? Do you have Tandberg GK involved here and if so, what sw version is it? Or, are the Tandberg EPs skinny clients, i.e. SCCP? If not, what type and sw version are Tandberg EPs?

The following document may prove helpful:

http://www.tandberg.com/collateral/documentation/White_Papers/TANDBERG%20and%20Cisco%20CallManager.pdf

[Scottie]

We have:

- Gatekeepr
- TMS
- MPS
- EP's = 3000MXP
- CCM = v4.1

We can dial into conferences from our Voip phones (cisco 7941), and have no problem mapping the route plans in CCM to dial into individual VTC EP's either. The problem is where do we configure the static mapping for dialing VTC to Voip phone? And when we start a conference only the phones can dial in, not the VTC's. Thanks!

[DRI]

Hi Scottie,

Take a look at the document that I referred to you above. It's throughly explained what you need to do to 'marry up' the H323 world to the SIP world, i.e. via building a trunk from the CCM to the Tandberg GK (builds a service on the GK) and also discusses what the CCM config should be.

DRI

[James Flockton]

Hi Scottie,

Take a look at the document that I referred to you above. It's throughly explained what you need to do to 'marry up' the H323 world to the SIP world, i.e. via building a trunk from the CCM to the Tandberg GK (builds a service on the GK) and also discusses what the CCM config should be.

DRI
DRI/Scottie,

CCM4.1 does not support SIP from endpoints. SIP Gateways are the only SIP devices supported using the SIP call signalling protocol. I have built quite a lot of CCM's and H323 endpoints work perfectly directly registering to the CCM as a H323 device. I personally have never used a Tandberg Gatekeeper as a H225 trunk, I have only used Cisco MCM to do this but that worked perfectly.

Make sure that the Tandberg Gatekeeper is using a new version of software and the document DRI linked above will work perfectly.

James

[Sean Lessman]

...and H323 endpoints work perfectly directly registering to the CCM as a H323 device. I personally have never used a Tandberg Gatekeeper as a H225 trunk, I have only used Cisco MCM to do this but that worked perfectly.

The benefit of using a gatekeeper (TANDBERG or otherwise) instead of registering direct to CCM is to maintain many of the features that people find useful (dual streams, encryption etc). If you register directly to CCM, you lose all the features that CCM does not inheritently support.

Sean

[James Flockton]

The benefit of using a gatekeeper (TANDBERG or otherwise) instead of registering direct to CCM is to maintain many of the features that people find useful (dual streams, encryption etc). If you register directly to CCM, you lose all the features that CCM does not inheritently support.

Sean

Sean, are you talking about a SCCP/SIP endpoint registering to CCM?

Are you sure you loose H.239/H.235 when the device is a H323 unit registered to Call Manager? I did not mess around with CAPS of the endpoints when I directly registered with CCM, but I did not test them either.

I thought the entire H.245 process would have been transparent to CCM, I suspected it was only involved in H.225 component of the call setup. Even the Cisco IP phones have built in Codecs to support a variety of Codec's which can be enabled/disabled based on location/WAN limits, but that is SCCP. I cannot see a reason why it would, the only thing I would understand is if you wanted to disable video functionality of the endpoints... I know if you get a SCCP load on a Tandberg you will loose those features as SCCP does not support the 'Duo video/Encryption'.

The only devices I have seen that break Duo video/Encryption is Cisco IPIPGW and Cisco PIX.

[dswash]

Hi James have you been able to use the internal MCU function on the Tandberg endpoints whilst registered to the ccm

[Sean Lessman]

Are you sure you loose H.239/H.235 when the device is a H323 unit registered to Call Manager? I did not mess around with CAPS of the endpoints when I directly registered with CCM, but I did not test them either.

Pretty sure. At least if there is a different way to do it, let me know as it is pretty much accepted between TANDBERG and Cisco that this is the way it works.

I thought the entire H.245 process would have been transparent to CCM...

It basically works in routed mode which means the CCM has to be able to interpret the H.245, and if it cannot, you don't get that feature.

Sean

[James Flockton]

I'm a little busy at work atm playing with Movi, VCS and IPIPGW. I will have a look at these CCM questions a little later in the week and report back here.

JF