Hello.
In our company we using SFB 2016 and i try to configure pigin-sipe to work on non-domain Linux (Fedora) machine.
And now i have issue with search contact -i have exact error like in this post - https://sourceforge.net/p/sipe/discussion/688534/thread/40edc143/?limit=25#b581
Is it limitations of sipe plugin or it's disabled in SFB config?
I use
pidgin-2.13.0-15.fc31.x86_64
pidgin-sipe-1.25.0-2.fc31.x86_64
libpurple-2.13.0-15.fc31.x86_64
Last edit: stevemayster 2019-12-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SfB should not use old-style address book, but EWS (Exchange Web Services). That is usually autoconfigured via setup information provided by your IT admins, but if it fails you can configure the email settings in the advanced tab by hand.
F.ex. what happens if you go to the SIPE context menu and select "publish calendar"? Do you get an error message?
If you can provide a detailed(!) --debug log (see FAQ) from your login process theb I can have a look what might be going wrong. Usually it is a mis-configuration in your auto-discovery information and/or installation, especially if you don't use a M$ hosted solution like SfB from Office 365.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good day,Stefan.
Sorry for long delay.
Log in attachment started from when i try to search somebody
I forgot to answer,sorry
*F.ex. what happens if you go to the SIPE context menu and select "publish calendar"? Do you get an error message? * - I didn't get any error. I click Republish Calendar without any error.
Hello,Stefan.
We found some users can search contact and some not.
In logs when search was succefull i found this line:
MESSAGE START <<<<<<<<<< SIP(0x5574335) - 2019-12-18T12:55:38.975947Z
SIP/2.0 488 Not acceptable here
ms-diagnostics: 2165;reason="Contact subscription is not allowed as the user's contact list has migrated to Exchange." -- and then pigin goes to exchange server for contact.
But in my logs i can't find something similar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
But the log only shows the broken functionality (i.e. SIPE tries addressbook via SIP, not EWS search), not why it doesn't use EWS. That would happen at login time,
The error 488 that you see in the other (working) logs happens when SIPE tries to subscribe to the contacts list event (vnd-microsoft-roaming-contacts). The next log line will tell you no contact list available - assuming Lync 2013+ and Unified Contact Store (UCS), i.e. SIPE will switch to Lync 2013+/UCS mode.
You'll need to find from your log the corresponding part: search for a SUBSCRIBEmessage for that event and then search the log for messages with the same Call-ID: from that message.
I have a hunch that some accounts were not (correctly?, completely?) migrated to UCS and therefore don't reject the SUBSCRIBE with 488. Or there is no response to the SUBSCRIBE at all for those accounts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also vaguely remember that the M$ client has some builtin magic that triggers the account migration from old contact list to UCS when the organization moves to the new system. I don't know what that magic is, hence SIPE can't trigger it.
If your account is "old" and your organization moved to a newer installation then you could try to start the M$ client, login with your account and afterwards try if address search works with SIPE.
If I remember correctly that should be visible in the log when searching for <contactList .... ucsMode="XXX">. The value in the XXX placeholder indicate the UCS state for the account.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
In our company we using SFB 2016 and i try to configure pigin-sipe to work on non-domain Linux (Fedora) machine.
And now i have issue with search contact -i have exact error like in this post - https://sourceforge.net/p/sipe/discussion/688534/thread/40edc143/?limit=25#b581
Is it limitations of sipe plugin or it's disabled in SFB config?
I use
pidgin-2.13.0-15.fc31.x86_64
pidgin-sipe-1.25.0-2.fc31.x86_64
libpurple-2.13.0-15.fc31.x86_64
Last edit: stevemayster 2019-12-13
SfB should not use old-style address book, but EWS (Exchange Web Services). That is usually autoconfigured via setup information provided by your IT admins, but if it fails you can configure the email settings in the advanced tab by hand.
F.ex. what happens if you go to the SIPE context menu and select "publish calendar"? Do you get an error message?
If you can provide a detailed(!)
--debuglog (see FAQ) from your login process theb I can have a look what might be going wrong. Usually it is a mis-configuration in your auto-discovery information and/or installation, especially if you don't use a M$ hosted solution like SfB from Office 365.Good day,Stefan.
Sorry for long delay.
Log in attachment started from when i try to search somebody
I forgot to answer,sorry
*F.ex. what happens if you go to the SIPE context menu and select "publish calendar"? Do you get an error message? * - I didn't get any error. I click Republish Calendar without any error.
Last edit: stevemayster 2019-12-17
Hello,Stefan.
We found some users can search contact and some not.
In logs when search was succefull i found this line:
MESSAGE START <<<<<<<<<< SIP(0x5574335) - 2019-12-18T12:55:38.975947Z
SIP/2.0 488 Not acceptable here
ms-diagnostics: 2165;reason="Contact subscription is not allowed as the user's contact list has migrated to Exchange." -- and then pigin goes to exchange server for contact.
But in my logs i can't find something similar
Thanks for the log.
But the log only shows the broken functionality (i.e. SIPE tries addressbook via SIP, not EWS search), not why it doesn't use EWS. That would happen at login time,
The error 488 that you see in the other (working) logs happens when SIPE tries to subscribe to the contacts list event (
vnd-microsoft-roaming-contacts). The next log line will tell youno contact list available - assuming Lync 2013+ and Unified Contact Store (UCS), i.e. SIPE will switch to Lync 2013+/UCS mode.You'll need to find from your log the corresponding part: search for a
SUBSCRIBEmessage for that event and then search the log for messages with the sameCall-ID:from that message.I have a hunch that some accounts were not (correctly?, completely?) migrated to UCS and therefore don't reject the
SUBSCRIBEwith 488. Or there is no response to theSUBSCRIBEat all for those accounts.I also vaguely remember that the M$ client has some builtin magic that triggers the account migration from old contact list to UCS when the organization moves to the new system. I don't know what that magic is, hence SIPE can't trigger it.
If your account is "old" and your organization moved to a newer installation then you could try to start the M$ client, login with your account and afterwards try if address search works with SIPE.
If I remember correctly that should be visible in the log when searching for
<contactList .... ucsMode="XXX">. The value in theXXXplaceholder indicate the UCS state for the account.Hello,Stefan
At last we found root of error. Not for all users account enabled option to save contact in Exchange.
Many thanks for your support))