Cisco VC Dialer

Getting my new iPad this weekend, I got to try the Cisco (Tandberg) VC Dialer from Sping BV on some of my endpoints. It seems to be working perfectly! It is basically an app that can dial any number from any MXP, C, EX or E series endpoint. You can get it from the AppStore, search for VC Dialer (it is an iPhone app originally). The app is free for a limited number of downloads, after which it will be priced €4.99

The dialer screen
Last calls screen
Choose endpoint
Add endpoint screen

 You need to be able to reach the endpoints on http (s?), and you need the admin password of the endpoint to be able to control it.

You can only make calls and hang up with the app, it is not a full remote control of the endpoint, but I can still se uses for this. 

Factory reset of Cisco E20

To reset Cisco E20 to factory defaults, press:

** -> PC/Presentation -> ##

in less than three seconds

or

log in to the TSH CLI via telnet or SSH and enter the following:

xCommand systemunit Configuration ResetToFactoryDefaults Settings: All

Service records and ports, VCS Express

Here are the service records needed to use the Tandberg VCS:

_h323ls._udp.company.com      srv     1 0 1719 vcs-e.company.com.
_h323cs._tcp.company.com      srv     1 0 1720 vcs-e.company.com.
_sip._udp.company.com              srv     0 0 5060 vcs-e.company.com.
_sip._tcp.company.com               srv     0 0 5060 vcs-e.company.com.
_sip._tls.company.com                 srv     0 0 5061 vcs-e.company.com.
_sips._tls.company.com               srv     0 0 5061 vcs-e.company.com.
_sips._tcp.company.com             srv     0 0 5061 vcs-e.company.com.

There should also be an a-record pointing to the vcs express. (in this example, vcs-e.company.com)

Also, should anyone ever need it, here are the ports that an endpoint needs opened outbound if it is registering directly to a VCS express:

TCP/2776 (Q931/H245 for external traversal endpoints)
UDP/2776 (RTP Media from external traversal endpoints)
UDP/2777 (RTCP Media control traffic from external traversal endpoints)
UDP/1719 (H323 RAS signaling from gatekeepers/VCSes and traversal endpoints)
TCP/1720 (Q931/H.225 call connect signaling)

UDP/5060 (SIP signaling)
TCP/5060 (SIP signaling)
TLS/5061 (Encrypted SIP signaling)

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 TCEP Day 2

Todays topic is Bandwith and call control

There will also be a test today.

To be able to call out on the internet on the VCS, you need to add the DNS Zone. It should only be added on the Express, not on the control. It will not be there by default. On the Gatekeeper/BorderController this is not necessary.

If you are neighboring gatekeepers, you need to use a pattern type to reach the endpoints on another gatekeeper. It will work fine without, but if you plan to use bandwith control the call will not be in the correct link if you don’t use a pattern. This is possibly a bug, and will probably be fixed in version X3.

SIP <-> H.323 interworking will also work when contacting an endpoint on the outside, but it will consume 1 ekstra traversal license because of the interworking, so it will use 2 traversal licenses.

And I passed the TCEP as well 🙂

Tandberg TCEP Day 1

Todays topic is Call Control Components – GK, VCS-C, VCS-E

When you factory reset these units, all option keys will disappear.

When a CCC is in routed mode, RAS. Q931 and H.245 info will go through the device, as opposed to non-routed mode, where only RAS will pass through the device. In SIP, all calls are in routed mode, but with H.232 this is optional. The VCS is always in routed mode though.

The VCS has a SIPH.232 interworking feature. Note that using this interworking feature will count as 1 traversal call.

For the sake of redundancy, there is a possibility to set up alternate Gatekeepers. When using this, the endpoint will recieve a list of alternate gatekeepers. If the gatekeeper the endpoint is registered to goes down, the endpoint will connect to the next endpoint on the list. Be sure to set the H.323 TTL down to something shorter than 1800 seconds if the environment demands faster recovery from an outage. Note that a gatekeeper can only be alternate to another gatekeeper, and a bordercontroller can only be alternate to another bordercontroller, a gatekeeper can not be alternate to another bordercontroller and the other way around. This also applies to VCScontrol/express.