[cisco-voip] Does Cisco Jabber (windrows) Conflict with MS Lync

Nazar Shabour nizarshabour at gmail.com
Tue Feb 16 15:05:51 EST 2016


Thanks Benjamin,

So ,they cant go exist and get the same status/update to/from outlook.

Thanks
Nazar

On Tue, Feb 16, 2016 at 6:17 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> Thanks for this.
>
> I've decided to use a different domain for the  services discovery for the
> time being, eg myphone.acme.ca because I may not be able to prevent WebEx
> registration.
>
> SMTP userIDs in my AD are userid at acme.ca
>
> I don't believe I have a proxyAddress configured. Or if I actually need
> one. We'll be moving to Office365 over the summer.
>
> Should I be worrying about this?
>
> What would my JID be in this case?
>
> userID at myphone.acme.ca -or- userID at acme.ca   ?
>
> Does this have anything to do with the fact that whenever I want to dial
> someone from my contacts I have to select from a list? I'd like to be able
> to just dial from contacts. A default destination for example.
>
>
>
> Sent from my iPhone
>
> On Feb 15, 2016, at 3:47 PM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
> Great tip Benjamin!
>
> Along the sames lines, if you *do* want Jabber to take over the Office
> integration, you will need to add to the AD attribute proxyAddresses, the
> following format: SIP:JID
>
> E.g., if my JID was aholloway at company.com, then my entry would be
> SIP:aholloway at company.com
>
> You may even end up with two or more proxyAddresses, depending on what
> else you are doing in AD.  I.e., SMTP:aholloway at company.com  The good
> news is, this is a list of addresses, and you can have multiple entries.
>
> There's actually a tool in the Jabber Admin ZIP file to help you bulk
> update your AD users to include this SIP proxyAddresses value.  You run it
> from a domain controller, and it's a GUI wizard that will generate an
> import file, and then import the file back in.  It defaults to
> SIP:smtpaddress, so if you JID != SMTPAddress, then you'll need to modify
> the import file, and manually import it another way.  The LDIF file
> format is standard
> <https://msdn.microsoft.com/en-us/library/bb727091.aspx#ECAA>.
>
> On Mon, Feb 15, 2016 at 1:57 PM, Benjamin Kenneally <benjamin at kenneally.me
> > wrote:
>
>> Lync and Jabber share a large number of resources and registry settings.
>> If you want Lync to maintain control of all the MS Office integration
>> (you're running Jabber phone only, as an example), install Jabber with the
>> flags
>>
>> msiexec.exe CLEAR=1 /i CIscoJabberSetup.msi CLICK2X=DISABLE
>>
>> and you should be set. This causes it to install without overwriting any
>> of those registry settings, including click to call.
>>
>> Best regards,
>>
>> Benjamin Kenneally
>>
>> On Mon, Feb 15, 2016 at 1:40 PM Nazar Shabour <nizarshabour at gmail.com>
>> wrote:
>>
>>> Dears,
>>>
>>> I found that when  Ms Lync  is working fine with outlook and reflecting
>>> all the IM status OK and then you install Jabber ,the sync is disturbed ,Is
>>> that due to the fact that Jabber overwrites the linkage to MS office and
>>> conflicts with Lync? any such experiences /opinions.
>>>
>>> Best Regards
>>>
>>>
>>> AbuALneez
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160216/c721b7aa/attachment.html>


More information about the cisco-voip mailing list