Tandberg codec re-boot

[Mark6292]

Can anyone explain why a Tandberg codec (Classic any model) loses the call record log when it re-boots. Why does the codec always re-boot when you re-connect back to the network. I've recently all the codecs to the latest E4.1 and B9.1 releases and TMS 8. I have a number of roll around units that are generally in the one location, but may need to be moved occasionally.

Regards

Mark

[trapehzoid]

the codecs don't boot when connected to a network unless you are booting them to get a new IP address. polycoms and tandbergs both have to reboot to get a use a new IP.

the call log in tandberg codecs isn't persistant.. so it will be lost on power cycle.. but if you are using TMS.. it doesn't matter as tms has the call logs collected

[Mark6292]

the codecs don't boot when connected to a network unless you are booting them to get a new IP address. polycoms and tandbergs both have to reboot to get a use a new IP.

the call log in tandberg codecs isn't persistant.. so it will be lost on power cycle.. but if you are using TMS.. it doesn't matter as tms has the call logs collected

Thanks for the information. The codecs have a static IP address so I can only assume that connecting to the network causes the reboot for the system to make the connection. Unfortunately the system was used while the codec was disconnected from the Ethernet network and therefore call log was not transmitted.

[Sean Lessman]

Thanks for the information. The codecs have a static IP address so I can only assume that connecting to the network causes the reboot for the system to make the connection. Unfortunately the system was used while the codec was disconnected from the Ethernet network and therefore call log was not transmitted.
No, there shouldnt be any automatic reboots when connecting to a network. If you can FTP into the system, download a file called 'event.prm' and email it to me. I would like to have someone take a look at this log which will hopefully tell us why its rebooting.

Email: sean.lessman@tandbergusa.com

Thanks,

Sean

[haneyr]

We had the same problem several years ago when we first started using Tandbergs. We had to put a password in the IP settings page and reboot the system. Don't know if that is still a problem or not.

[Sean Lessman]

We had the same problem several years ago when we first started using Tandbergs. We had to put a password in the IP settings page and reboot the system. Don't know if that is still a problem or not.This instance you are talking about is likely due to that particular codec being hit by a DoS attack, or something that overloads the onboard webserver. Putting the password on the codec adds one more layer of 'defense' before getting to the webserver. You should always IP password protect your systems regardless for security sake.

All TANDBERG equipment has been shipping with default passwords for a few years now.

Sean