Provision phonebook in Tandberg Management Suite

To be able to add Movi2 endpoints to phonebooks on systems registered in TMS, TMS should automagically create an external source and a provisioning phonebook when the provisioning key is installed on the system. If this for some reason does not happen, here’s how to add one: (or to verify that the phonebook was installed correctly)

In TMS, go to: Phone Book > Manage External Source

If there is an external source there that is called “Provisioning Source”, chances are that the phone book was installed correctly. If not, add a new external source and select “TANDBERG Provisioning Directory” as source type.

The rest of the fields should be like this:

Connection Details
Name Provisioning Source
Default Bandwidth for Imported Entries 384 kbps
Force Default Bandwidth (all entries, not only Auto entries) Unchecked
IP Address/DNS localhost
Username CN=Directory Manager
Password TANDBERG
Advanced Connection Details
LDAP Port Number Blank
Search Base (DN) dc=provisioning
Search Scope Recursive
Custom LDAP Filter Blank
Field on User Object to Prefix Display Name in TMS displayName

With this setup, movi users are added to the phone book on the format “<firstname> <lastname> <provisioningprofile>”. I will try some different settings to see if I can filter and change the format in the phonebook. I will add this in a later post.

After this, create a new phonebook and connect it to the new external source.

Source: Tandberg Deployment guide: Provisioning. february 2009

Connection Details
Name
Provisioning Source
Default Bandwidth for Imported Entries
384 kbps
Force Default Bandwidth (all entries, not only Auto entries)
Unchecked
IP Address/DNS
localhost
Username
CN=Directory Manager
Password
TANDBERG
Advanced Connection Details
LDAP Port Number
Blank
Search Base (DN)
dc=provisioning
Search Scope
Recursive
Custom LDAP Filter
Blank
Field on User Object to Prefix Display Name in TMS
displayName

Tandberg TMS install

If you get a “404 – Not Found” message when trying to access TMS after a fresh install, try enableing ASP 2.0 in IIS. The installation software might not have been able to enable it.

Tandberg TCAP Day 2

Tandberg MPS is the topic of the day

The MPS is a gateway and a MCU in the same box. Comes in two versions, MPS 200 and 800. The 200 is a 3U box with 2 module spaces. The 800 is a 9U box with 8 module spaces.

It supports transcoding, which is translation between different codecs. If one system uses H.264 with G.722 and the other uses H.263+ G.722, the MPS will translate this.

It will also do ratematching, so in a multiconference, users can connect with different speeds. One can be 384kbps, one can be 512kbps and another one can be 768kbps. One conference can only use 2 different speedgroups, so if one user connects with 384kbps, and the next connects with 768kbps, a user that connects with 512kbps will get 384kbps back. He will send with 512kbps though. The two groups of speeds will always be the highest and the lowest of the speeds connected. This means that if you have one group with 768kbps and one with 512kbps, if a user connects with 384kbps, the user with 512kbps will be downgraded to 384kbps.
There is also a third group, but this is reserved for cellular systems.

Use chart on slide 37 for MPS capacity and scaling information.

Installation
Even though the MPS is 10/100 capable and has autosensing, it is smart to force switch and MPS media cards to 100 full duplex. This is due to different implementations of the autosensing feature from different switchmanufacturers. With normal computers, this is normally not noticed, because you seldomly use realtime traffic, but with videoconferencing, more or less all traffic is realtime and because of this duplex mismatch problems are more severe.

Use
When creating a conference where the MPS/MCU will call out to a TCS-4 system, put the main number in the number field, and the extension in the SubAddress field.

It is important to create a good numberplan before implementation begins. You need several prefixes for functions as conferences and outgoing connections, and they cannot crash with each other.

In the gateway settings, do not set the “percent of total bandwith” to zero. This will obviously render the gateway useless.

Troubleshooting

The MPS has two modes on commandline. In addition to the commandline that exists on all Tandberg systems, it has also got a UNIX subsystem that contains files and folders, where the eventlog will be as txtfiles. To enter the UNIX system, use ‘root’ as a username in stead of ‘administrator’.

In an environment where there are a lot of different systems, when users experience problems with the conferencing system, check Fast Update Requests, FUR. The MPS will not handle them very well.

We managed to get in a bit of TMS at the end of the day as well

To manage Tandberg classic endpoints, you need to run version B4 and later.

Fun fact: On an endpoint, press the phonebook key 10 times, and you will get a menu filled with games 😀