Archive for VOIP

July 2010 Update for CoMo

Microsoft just released a compelling update for it’s Communicator Mobile client. See the KB article for a full list of improvements. The update brings the current CoMo version to 6906.29.

Download the Smartphone package.

Download the Pocket PC package.

Issues that this hotfix package fixes

  • Provides home screen support for new home screens in Windows Mobile 6.5+ phones.
  • Provides integration within the phone dialer for Windows Mobile 6.5+ phones.
  • Enables Communicator Mobile 2007 R2 to recognize when the phone is roaming and by default prevents Communicator Mobile 2007 R2 from signing in to roaming networks.
  • Provides additional support for joining conference calls from a Windows Mobile appointment. To do this, press Menu, and then press Join Conference.
  • Lets users log on by using a user name in the user@example.com format, in addition to the domain\user format.
  • Enables the functionality by which callbacks are now automatically accepted when the user uses the Call via Work option.
  • Resolves the problem in which the Microsoft Installer (.msi) installation fails on a Windows XP Service Pack 3 (SP3)-based computer. In this situation, users should install Communicator Mobile 2007 R2 by using a (.cab) installation.
  • Fixes the problem in which AT&T FUZE devices that are set for a High-Speed Downlink Packet Access (HSDPA) connection cannot handle voice and data at the same time. In this situation, calls that use the Call via Work option fail unless the device is reverted to 3rd Generation (3G) by disabling HSDPA.
  • End User License Agreement (EULA) update to allow OEMs pre-install Communicator Mobile 2007 R2 in addition to Standalone Web downloads.

Comments

Can’t Call Exchange UM Auto Attendant from OCS

I ran into an issue trying to call a new Exchange UM Auto Attendant from OCS today. Calls to the AA’s DID kept failing and the only error in the OCS Log (Snooper) was “The application specified an invalid request-uri”. The issue ended up being a problem with the name of the Exchange UM Auto Attendant. The Auto Attendant must be created without any spaces in the name. To fix the issue, delete the Auto Attendant and the associated OCS Contact object, recreate the Auto Attendant with no spaces in the name, e.g. “My Auto Attendant” -> “MyAutoAttendant”, and then rerun OCSUmUtil.exe and recreate the contact object.

Comments

Great Article on OCS E.164 aka RFC 3966

Normalization and dial plans was one of those topics that took me a awhile to fully understand. I think this is true for many people who are being introduced to the telephony world for the first time by attempting to implement Enterprise Voice with OCS. This article does a good job of explaining the how and why of E.164 (RFC 3966) normalization. Highly recommended read.

http://blogs.technet.com/dougl/archive/2009/06/25/phone-numbers-in-OCS.aspx

Comments

Grandstream GXP-2000 Label Template

I saw post on trixbox.org where someone had shared a PDF version of their GXP 2000 label template.

http://www.trixbox.org/forums/vendor-specific-unmoderated/grandstream/label-template-gxp-2000-feature-buttons

So I decided to share my Excel version which I like better since the PDF version wouldn’t allow you to enter data on multiple lines per extension.

Grandstream GXP-2000 MS Excel Label Template

Comments