[cisco-voip] Does Cisco Jabber (windrows) Conflict with MS Lync
Anthony Holloway
avholloway+cisco-voip at gmail.com
Tue Feb 16 21:31:04 EST 2016
"considering, it's only really used at client configuration, i'm not too
concerned. there are smart URLs that we can use, so that will help as well."
Smart URLs
<http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_01110.html#CJAB_TK_U15F770E_00>
work for all clients
<http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_01110.html#CJAB_TK_U83324CA_00>
except Windows. For Windows you need to modify the MSI with Orca (and MST
file)
<http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_01110.html#JABW_TK_IBE959AA_00>
.
On Tue, Feb 16, 2016 at 3:37 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> nope. no hole. this is great. you raise very valid points.
>
> i won't be able to upgrade for a while. likely mid-2017 or 2018. we've got
> a full plate and i need to justify the time to upgrade.
>
> i've decided to use a different services discovery domain for the reason
> that i do not control the domain, and someone could easily register it with
> WebEx, and I don't want that to screw things up.
>
> considering, it's only really used at client configuration, i'm not too
> concerned. there are smart URLs that we can use, so that will help as well.
>
> i will be using the same domain for IM and SIP/Directory URIs though.
> that's my plan.
>
> my main concern going forward is that in our AD, we have some people who
> have modified their MailID to be an email address with a departmental
> domain attached. i will have to see how that works (or doesn't work).
>
> thanks again!
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> ------------------------------
> *From: *"Anthony Holloway" <avholloway+cisco-voip at gmail.com>
> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca>
> *Cc: *"Benjamin Kenneally" <benjamin at kenneally.me>, "Cisco VoIP Group" <
> cisco-voip at puck.nether.net>
> *Sent: *Tuesday, February 16, 2016 4:21:41 PM
>
> *Subject: *Re: [cisco-voip] Does Cisco Jabber (windrows) Conflict with MS
> Lync
>
> All the more reason to upgrade....I kid, but not really.
>
> Actually, the current CCIE Collab is based on that same version, if memory
> serves, so knowing it to some degree is important, but not anymore for me.
> ;)
>
> Anyway, the Services Domain is simply where Jabber will query for SRV
> records, it does not have to match the IM chat domain. As long as the SRV
> records can be found, you're good to go.
>
> I think the ultimate deployment scenario is when the services domain
> matches the IM chat domain and both of them match the mail domain. This
> way, as an end user, I don't have to know three URIs:
>
> aholloway at chat.company.com
> aholloway at myphone.company.com
> aholloway at company.com
>
> I would strive to make them all the same, so it's a unified experience
> across the board. I'm not saying you're doing three domains, I'm using
> that as a worst case scenario. You might have combined your IM chat domain
> with your mail domain, and they match, leaving only your services domain
> out in the wind.
>
> I think I'm about to start digging myself in to a hole here, so I better
> watch out where I take this conversation. Deployment strategies, multiple
> domains, legacy versions, volunteering, murky waters, and all that.
>
> On Tue, Feb 16, 2016 at 2:49 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>>
>> Interesting... I'm running 9.1.1...
>>
>>
>> - I don't have Advanced Configuration > IM Address Scheme option.
>> - And under System > Cluster Topology > All Assigned Users, I don't
>> have the IM address column.
>>
>>
>> That being said, I just right clicked on a contact and viewed the
>> profile. The IM address does not include the services domain I configured.
>> I'm guessing because Directory URI is an option only introduced in v10,
>> it's either taking my "Mail ID" or it's building it from the userID and the
>> default presence domain I configured in the .xml file.
>>
>> I'll have to take another look at my default calling behaviour.
>>
>>
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst, Network Infrastructure
>> Computing and Communications Services (CCS)
>> University of Guelph
>>
>> 519‐824‐4120 Ext 56354
>> lelio at uoguelph.ca
>> www.uoguelph.ca/ccs
>> Room 037, Animal Science and Nutrition Building
>> Guelph, Ontario, N1G 2W1
>>
>> ------------------------------
>> *From: *"Anthony Holloway" <avholloway+cisco-voip at gmail.com>
>> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca>
>> *Cc: *"Benjamin Kenneally" <benjamin at kenneally.me>,
>> cisco-voip at puck.nether.net
>> *Sent: *Tuesday, February 16, 2016 3:06:51 PM
>> *Subject: *Re: [cisco-voip] Does Cisco Jabber (windrows) Conflict with
>> MS Lync
>>
>>
>> Your JID is made up from whatever is configured in IM&P under Presence >
>> Settings > Advanced Configuration > IM address scheme
>>
>> You can see what everyone is already provisioned for in IM&P under System
>> > Presence Topology > All Assigned Users, and then look at the column
>> labeled IM Address.
>>
>> I don't know anything about Office 365 and Presence integrations, sorry.
>>
>> I don't for certain about default destinations in the Jabber client, but
>> I can tell you that if you hover over the contact, to get the contact card
>> to show, you can one click call them. It looks like in my environment it's
>> choosing the Directory URI over the DN. This wouldn't be the first time
>> Directory URI takes precedence over DN. It does that in Phone Only Mode,
>> and shows up under your name at the top, where it would normally show your
>> status.
>>
>>
>>
>> Multiple Ways to Call (Directory URI and DN)
>>
>> [image: Inline image 2]
>>
>>
>>
>> Contact Card One Click Default Call Option (Directory URI) *Note there is
>> a left and right section of this green call button. The left side is the
>> one click, while the right side is a selection.
>>
>> [image: Inline image 3]
>>
>>
>>
>>
>> On Mon, Feb 15, 2016 at 9:17 PM, 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
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160216/c2c2ad0d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26468 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160216/c2c2ad0d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 41871 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160216/c2c2ad0d/attachment-0001.png>
More information about the cisco-voip
mailing list