Showing posts with label como. Show all posts
Showing posts with label como. Show all posts

Wednesday, July 14, 2010

Important update: Microsoft Office Communicator Mobile 2007 R2

This is actully not just a fix/patch, it’s an update, I have missed the “call via work” from the normal dialpad for a long time, now this works on Windows 6.5, sorry dont know for all other mobiles.

Download here and description here: and remember that you always can download directly from the phone here http://getcomo.com

New version is:6906.29

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.

Saturday, February 13, 2010

Microsoft Office Communicator 2007 R2 Group Policy Field Guide

The Microsoft Office Communicator 2007 R2 Group Policy Field Guide is an essential guide for administrators who are responsible for setting Group Policy or configuring registry settings for Communicator users. It uses clear explanations and practical examples to illustrate how and why you would use a policy in your organization.

get it here

Sunday, September 27, 2009

New: Office Communicator Mobile 2007 R2 for Java (Nokia S60 240X320 resolution)

Brief Description

Microsoft Office Communicator Mobile for Java is an enterprise client software for Microsoft Office Communications Server 2007 R2 optimized for Java enabled cell phones. The client allows you to view colleagues availability using presence status, initiate single/multi-party IM sessions and get updated contact information from your company directory.

Get it here

Remember that you need CWA running for the Mobile Java client to work and you need to point the client to that (CWA) website and not the Edge server.

more info here

Sunday, August 23, 2009

Communicator for Iphone or Ipod

What is iDialog?

Microsoft Office Communications Server is revolutionizing the way workers communicate and collaborate.

iDialog is an exclusive product from Modality Systems that enables users to find and communicate with their Microsoft Office Communications Server (OCS) contacts using Apple iPhone or iPod Touch devices.

image

iDialog supports the following features:

  • Display OCS contact list and presence information
  • Set presence information, including custom note and location data
  • Search corporate Global Address List (GAL)
  • Send and receive Instant Messages (IM)
  • Add multiple participants to an IM conversation
  • Manage and participate in multiple IM conversations simultaneously
  • Control incoming OCS Voice calls (forward/redirect an incoming OCS call to another device, such as an iPhone, voice mailbox, or another phone number)
  • Call a phone number listed on a contact card (This feature is not available on iPod Touch devices)
    Send an email to an address listed on a contact card
Deployment Requirements

iDialog is supported on Apple iPhone and iPod Touch versions 2.0 and higher. The user must also have an account that can sign-in to a corporate or hosted OCS 2007 or 2007 R2 system. An OCS Communicator Web Access (CWA) Server must be deployed to support iDialog connectivity. No proprietary server infrastructure is required.

get more info:

http://www.modalitysystems.com/blog/?p=92

and

http://www.modalitysystems.com/idialog/

Monday, July 27, 2009

CoMo and CLIP SA: (Calling Line Identification Presentation Special Arrangement)

Problem/issue regarding “caller number” when using simultan ringing and Calling Line Identification Presentation Special Arrangement  (CLIP SA).

When you have that service (CLIPSA) from your Telco provider, you have the possibility to see the Originate Caller number displayed on your Mobile phone.
But in OCS R2 it depend on if you are logged in to CoMo or not.

Problem:
Originate Caller number not sent to the mobile when logged in on CoMo, then it’s my company number (DID) as the caller number.
But the Originate Caller number is sent  when  not logged in on CoMo.

It’s not a problem if you see the “popup/toast” on your mobile, here you can see who the caller is, but if you like to use your call history on you mobile you will only see your own DID as caller ID. Okay then you can use the “last contact” in CoMo, but you haven’t any call detail (date-time) so this “last contact” list isn’t that useful.

Read more about CLIP SA here:

http://www.cept.dk/F580A011-3400-4C40-AB6E-40CAFE055F57?frames=no&

http://www.erodocdb.dk/Docs/doc98/Official/Pdf/ECCRec0301.pdf

http://www.anacom.pt/streaming/en_300089v030101p.pdf?categoryId=115679&contentId=201615&field=ATTACHED_FILE

http://www.niccstandards.org.uk/files/current/nd1202_2000_01.pdf?type=pdf

Friday, July 24, 2009

Mobile Communicator vs Communicator

I often get this questions why isn’t it the same phone numbers that I see on my Company contact on my Mobil Communicator and my Communicator.
Or questions like this: on my Mobile Communicator I can’t see any phone number at all on company contact, but in my Communicator I can see Work-Mobile-Privat.

My quick answer is: The Mobile Communicator doesn’t have a Global adresse list locally. and the “publish this phone number” in Communicator isn’t set.

Conclusion: If you like other users to see your phone number, you must use the “Publish this phone number” and the “level of access” to choose what number they can see in Mobile Communicator, regardless of they are users from your AD/organization/OCS system.
This is not like the way “PC” Communicator normaly interact!

The way that the Mobile Communicator get phone number is when it’s gets the contactcard in the Presence XML document on its contacts, at logon or update.

This table show what you see and don’t see when numbers are publish in Active Directory, and have set the “publish this phone number” in communicator, in combination with access level.

image

This behavior is like when one of you contact is a Federated contact and you like them to be able to see your phone numbers.

In the presence XML Document that users publish to the front-end server is all the information on what the Mobile Communicator can see and can’t see.

Use Snooper to trace:

SIP Snooper trace of a posted presence XML document from client where no numbers have set the “publish this phone number” (notes the <publish>FALSE</publish> )

image

<userInformation xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation"><phones>

<phonetype="work"><publish>false</publish><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>

<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>

<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>

<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>

image

******************************************************************************

Snooper trace: this XML post is when work number is set to “publish this phone number” (notes the missing <publish>FALSE</publish> on work number)image

<userInformation

xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation">

<phones><phonetype="work"><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>

<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>

<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>

<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>
</category>

Snooper trace: This part of the contactcard is what mobile Communicator get from the front-end server (notes the work number is in this)

</contactCard>
</category>
<category name="contactCard" instance="3" publishTime="2009-07-24T14:22:00.127">
<contactCard xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard">
                <phone type="work">
                    <uri>tel:+4589490123</uri>
                </phone>
            </contactCard>

image

Here you can read a bit more on setting phone option.

In the text below from this link, it says that you can’t unpublish this number when its provided from Activ directory, thats not the case when you are using Mobil communicator, only when using “PC”Communicator, On Mobile Communicator you can’t see any numbers on your contacts if they haven’t set this “publish”

Text from link *********
About Active Directory and why some phone numbers cannot be modified or unpublished

Phone numbers that are provided to Communicator from Active Directory will appear in the Phones tab as inactive fields and cannot be edited. Additionally, these numbers cannot be unpublished. Clearing the Publish check box for numbers provided from Active Directory will not unpublish the number.

Setting access level

Snooper trace where a user set's access level for jan@ocsblogs.eu to Personal

Message-Body: <setContainerMembers xmlns="http://schemas.microsoft.com/2006/09/sip/container-management"><container id="400" version="8"><member action="add" type="user" value="jan@ocsblogs.eu"/></container></setContainerMembers>
$$end_record

Container ID Description 
100 Presence is accessible by all federated users.

200 Users from the same company can access the presence data of the publisher.

300 The team members of the publisher can access the presence data of the publisher.

400 Specified subscribers have unrestricted access to the presence data, including sending a potentially interruptive IM invitation when the publisher's status is displayed as Do Not Disturb.

32000 The specified members are blocked to view the presence data. The category instances should be empty category elements.

Tuesday, July 14, 2009

update for Communicator Mobile 2007 R2: July 2009 (kb969816)

Issues that this hotfix package fixes
  • Homescreen support for new homescreens in Windows Mobile 6.5+ phones.
  • Integration within the phone dialer for Windows Mobile 6.5+ phones.
  • Communicator Mobile 2007 R2 now recognizes when the phone is roaming, and by default does not sign in to roaming networks.
  • Additional support for joining conference calls from a Windows Mobile appointment. To do this, press Menu, and then press Join Conference.
  • Enables users to log on with a username of the format user@example.com, in addition to domain\user.
  • When placing Call via Work calls, callbacks are now automatically accepted.
  • Microsoft Installer (MSI) installation on Windows XP Service Pack 3 (SP3) fails. In this situation, users should install Communicator Mobile 2007 R2 by using a .Cab installation.
  • AT&T FUZE devices set for High-Speed Downlink Packet Access (HSDPA) connection cannot handle voice and data at the same time. This causes Call via Work calls to fail unless the device is reverted to 3rd Generation (3G) by disabling HSDPA.

get it here

FYI:
If you upgrade the old version of COMO and you have set remember password and the Mobile number for call back are reset/removed!