T1700 keeps on reboot when ethernet cable plugged in

[kekfoong]

Hi all,

I just wonder if any of you out there encounter similar problem as describe above. If yes, are you able to resolve it without having to send it back to Tandberg for RMA?

[DRI]

Hi,

Have you tried setting it back to factory defaults, e.g. via CLI? The command is defvalues set factory. Keep in mind, this option will erase the option key, erase the eeeprom and format the flash disk. Therefore, take note of your option keys so that you can re-enter them after you defvalued it.

[Sean Lessman]

Hi all,

I just wonder if any of you out there encounter similar problem as describe above. If yes, are you able to resolve it without having to send it back to Tandberg for RMA?

You could also try putting a password on the webserver (IP password in the menus). I have seen in the past where the webserver if under attack will trigger the codec to reboot. This is in response to a perceived DoS attack and the reaction of the codec is to reboot and restore normal operation. By putting a password on the codec, it keeps the attack from reaching the webserver.

Sean

[kekfoong]

Thanks DRI/Sean,

I had solved the issue by upgrading the system F6.0 to F6.3. I do not understand why but it just worked fine after i upgraded.

:surprised

[senthil]

There is bug in the version 6.0 working with H.245 for audio signals in DHCP mode and new version resolves that issue.

You might used DHCP right?


Senthil.

[Sean Lessman]

Thanks DRI/Sean,

I had solved the issue by upgrading the system F6.0 to F6.3. I do not understand why but it just worked fine after i upgraded.

:surprised

I don't suppose you use Avaya IP phones?

Sean

[kekfoong]

Ya, my client was using DHCP during that time and there is when the reboot issue came about.

I not sure whether are they using Avaya IP phones or not, cause i only handle their Tandberg video conference systems only.

So does that mean Tandberg F6.0 cannot works with Avaya IP phone?

[Sean Lessman]

Ya, my client was using DHCP during that time and there is when the reboot issue came about.

I not sure whether are they using Avaya IP phones or not, cause i only handle their Tandberg video conference systems only.

So does that mean Tandberg F6.0 cannot works with Avaya IP phone?

Before 6.1 we were using the same DHCP option (to get the TMS management address) as the Avaya phone and this caused a conflict, which to make a long story short caused the codec to reboot. With the latest software, we changed the option number so it shouldn't be a problem anymore.

Sean

[robertk]

Before 6.3 we were using the same DHCP option (to get the TMS management address) as the Avaya phone and this caused a conflict, which to make a long story short caused the codec to reboot. With the latest software, we changed the option number so it shouldn't be a problem anymore.

Sean

And why isn't this information written with LARGE RED letters in the release notes?

Changing such a function would possible break a needed function for large customers. I'm lucky since none of my customers have opted for having this function implemented in their networks.

//Robert

[Sean Lessman]

And why isn't this information written with LARGE RED letters in the release notes?

Changing such a function would possible break a needed function for large customers. I'm lucky since none of my customers have opted for having this function implemented in their networks.

//Robert

http://www.tandberg.com/collateral/documentation/Upgrades_and_Diagnostics/TANDBERG%20Software%20Release%20-%20MXP%20Endpoints%20(F6).pdf

Page 30

IP (DHCP)
Improvements were made when handling option 242 within the DHCP response. Previously, this option
would conflict with the Avaya IP telephony system, causing the system to restart unexpectedly.

The change was made in F6.1.

Sean

[robertk]

The change was made in F6.1.

Sean


Doh... Fair enough... :)


//Robert

[sjuris]

Sean or others.....

I'm interested in the DHCP option...

Do I understand the operation correctly...

#1 - DHCP servers are configured to provide the TMS address to any system that requests a particular option (e.g. Option 255 = TMS...)
We have dozens around the country....

#2 - When a Tandberg system is connected to an Ethernet port and sends a DHCP address request broadcast, it receives an IP addr, GW, Mask, etc and the TMS IP address.
(Does the request for Option XXX get included in the original broadcast or in a subsequest exchange with the DHCP server?)

#3 - After the TB system gets the TMS address...... ???
Does the system show up as a rouge system in TMS ???

How many enterprises use this DHCP option trick?

Is this process documented by TB anywhere?

Thanks

[robertk]

Yes it's documented and well described in the manual:

Page 11. 3.3 How pre-registration works

http://www.tandberg.com/collateral/documentation/User_Manuals/TANDBERG%20Management%20Suite%2011.7%20Administrat ors%20Guide.pdf


//Robert

[Sean Lessman]

I think I am going to owe Robert a few beers pretty soon.

Sean

[robertk]

I think I am going to owe Robert a few beers pretty soon.

Sean

Hehe... don't worry... I have had, and have my share of beers that go on the TANDBERG rep-account :)

//Robert