Well then un-delete it, as this is a packaging problem, see [bugs:#365]
Well then un-delete it, as this is packaging problem, see [bugs:#365]
Well then un-delete it, as the this is packaging problem, see [bugs:#365]
Doesn't build anymore
Already fixed by the following commits utils: add sipe_utils_memdup() core: replace g_memdup() with sipe_utils_memdup() It is the task of a package maintainer to pick up such fixes, f.ex. as was done in Fedora Closing as INVALID.
pidgin-sipe is in the AUR: https://aur.archlinux.org/packages/pidgin-sipe But i requested its deletion since it won't build. pidgin-sipe-git builds instead
Dead link for Arch Linux
Looks like pidgin-sipe was dropped from Arch Linux. Closing as WONTFIX.
Doesn't build anymore
Dead link for Arch Linux
Hi, is there a way to share a file with all buddies in a chat at the same time? I have only found the option to share a file with one participant at a time. pidgin 2.13.0 with pidgin-sipe 1.25.0-2 Best, Stefan
Hi, how can one start a conference call? I can open a chat conference, but don't find an option to start a phone conference? A chat member using Skype can simply start a conference call via a button in the group chat window, but I don't see anything like this in Pidgin (also no menu option). pidgin 2.13.0 with pidgin-sipe 1.25.0-2 Best, Stefan
Hi, how can one start a conference call? I can open a chat conference, but don't find an option to start a phone conference? pidgin 2.13.0 with pidgin-sipe 1.25.0-2 Best, Stefan
Hi, How could I make audio calls via dialing voip numbers form inside pidgin? I've seen a dial pad in Accounts -> <myaccount> -> Test call, but acn't utilize it to dial sip number. I also tried "call a phone number..." inside athe same menu, but it returns an error and doesn't recognize a valid number.</myaccount> Thanks
I mixed up the terms. Both us and the customer are using Teams. Perhaps I've accidentally managed to connect my Pidgin to our Office 365 / SfB, assuming it is connected to Teams :).
Are you sure your customer actually uses SfB (Skype for Business) and not Teams? I'm not aware that there are "workspaces" in SfB. Office 365/SfB and Teams are two separate things. SIPE can only talk to SfB.
Hi, We have our own Office 365/Teams subscription and I'm able to connect to it just fine with Pidgin. However, I've also been invited to a customer workspace. In the official Teams webui/app I can switch between our own and the customer workspace. How would I join a group chat in the customer workspace in Pidgin? Do I just need to create a new chat and if so, what parameters should I feed it? The list rooms button in Pidgin gives me nothing from our own account or the customer account.
There was nothing misleading about the information I provided and I followed what I thought was the process for contributing. You obviously have very little interest in new people contributing. Didn't expect you to be like that. That's fine, learned my lesson.
That's just the web site in an electron wrapper. With a real teams plugin for sipe one could get it into pidgin or bitlbee etc. and have plaintext conversations without using even a gigabyte of ram …
There is an client out by M$. Of course, it's closed source and therefor I wouldn't use it. But there is also a Projject on github: https://github.com/IsmaelMartinez/teams-for-linux. (The link doesn't work. I don't know why. But search in Github with the terms Ismael Martinez teams). This works very well (Debian 10) and will not stay in the background (and probably spies you out) as the M$ client when closed. Give it a try. Al
There is an client out by M$. Of course, it's closed source and therefor I wouldn't use it. But there is also a Projject on github: https://github.com/IsmaelMartinez/teams-for-linux. This works very well (Debian 10) and will not stay in the background (and probably spies you out) as the M$ client when closed. Give it a try. Al
MS Teams is a completely different beast. It would not be a good idea to graft a completely different implementation onto the existing code base. 2nd thing (which I have to admit I haven't look into at all): is the MS Teams API public and documented? M$ could probably just say "we do the same thing as Slack, etc. Just use the web app...".
Any chance we might see at least chat support for MS Teams?
... or install a proxy on your local machine and point Pidgin to it. The proxy must fulfill three requirements it must be able to tunnel proxy request to another HTTP CONNECT proxy it must have a black or white list to decide when to pass on to the proxy or connect directly (i.e. proxying by itself) be transparent (well more transparent then the HTTP CONNECT proxy you obviously have)
Well, if login.microsoft.com is the only address that you would need proxying for, then you could try to hard-code the name in /etc/hosts to address 127.0.0.1 and then run a proxy tunnel script on port 443 on your local machine. The tunnel would then need to talk to the real HTTP CONNECT proxy to get outside. I.e. https://login.microsoft.com:443/ -> script on localhost -> HTTP CONNECT proxy -> outside.
Nope, it does not as I mentioned in the last sentence of my previous post.
Yes, the response indicates that you have an ADFS setup: <STSAuthURL>https://adfs.us.DUMMYCOMPANY.com/adfs/services/trust/2005/usernamemixed</STSAuthURL> So in your setup only HTTP would need to be proxied, which libpurple currently doesn't support. I also checked the libpurple API again and there is no programmatical way to disable proxy settings for a certain connection, i.e. so that SIPE could request no proxy for SIP connections. I don't have Pidgin in front of me, but I'm assuming that the proxy...
The values returned by the response look reasonable to me. See the attachment. After some further discussion with some coworkers, I think we're hitting the limits of pidgin's proxy configuration abilities. Specifically, I think this enhancement would improve our situation: https://developer.pidgin.im/ticket/3034. If pidgin allowed us to control which hosts required the proxy or not, that's probably how to fix this.
Guessing from your latest log I fear the HTTP CONNECT proxy isn't transparent enough for SIP connections. The connection is dropped while the first SIP response is received: MESSAGE END >>>>>>>>>> SIP(0x16b98d0) - 2020-08-26T14:45:57.039861Z (09:45:57) sipe: transport_input_common: new buffer length 4096 (09:45:57) sipe: transport_input_common: new buffer length 8192 (09:45:57) sipe: Server has disconnected Can you post the XML response from https://login.microsoftonline.com/getuserrealm.srf?login=DUMMYUSER@DUMMYCOMPANY.com&xml=1,...
I fear this might be caused by our network's proxy intefering with the connection. Entering the proper loginid I was able to open that URL in Firefox and get a successful response. If I disable the proxy the connection to that URL fails. So I attempted to configure pidgin-sipe to use our proxy with the HTTP proxy setting in the Proxy tab in Pidgin. However, it fails to make a successful connection to sipdir.online.gov.skypeforbusiness.us. Not clear why to me the connection failed. Log attached.
The SIP server is probably correct now. SIPE tries to query the following URL https://login.microsoftonline.com/getuserrealm.srf?login=DUMMYUSER@DUMMYCOMPANY.com&xml=1 to determine the ADFS setup for your account. Your network prevents that. As I don't know your real email address I can't tell what the response is.
That got me further along in the process, but I feel this might be a network configuration issue now... Looking at the attached log it looks like it couldn't make a connection to a login server. I fear this might be caused by our company's proxy server. This particular log doesn;t have the User-Agent set as you suggested, but setting it did not change the error.
webdir.online.gov.skypeforbusiness.us:443 is a HTTP server, that can't be the correct server. Try sipdir.online.gov.skypeforbusiness.us:443 or :5061 (unlikely though...) , both ports seem to answer. Please also set the User Agent field. I'm not aware of any Lync installation that allows non-M$ clients.
I got in contact with someone in the IT department and was told to use webdir.online.gov.skypeforbusiness.us. Connection still failed, and this time it appears to have rejected the initial registration request from sipe.
While the 2nd attempt looks in general more successful it is in the end rejected with User is not provisioned in this deployment. i.e. the system rejects the given SIP URI. If you are sure that you are using the correct SIP URI then another suggestion indicated by both logs would be that the server auto-discover doesn't work in your case. Lync auto-discover fails in both logs, and the older DNS method results in sipint1.008f.federal.lync.com:5061 which rejects your login attempts (the port number...
While the 2nd attempt looks in general more successful it is in the end rejected with User is not provisioned in this deployment. i.e. the system rejects the given SIP URI. If you are sure that you are using the correct SIP URI then another suggestion indicated by both logs would be that the server auto-discover doesn't work in your case. Lync auto-discover fails in both logs, and the older DNS method results in sipint1.008f.federal.lync.com port: 5061 which rejects your login attempts (the port...
Pretty sure my email address is my SIP URI. I tried using the actual email and not the alias I had been using. Also added my domain account to the login setup. Attaching another log file.
Thanks for the log. According to the log, attempts to acquire an authentication ticket are rejected with Error 500 and the message The SIP URI in the claim type requirements of the web ticket request does not match the SIP URI associated with the presented credentials. Your account is set up only with your E-Mail address. Are you sure your E-Mail address is also your SIP URI? Maybe it has been changed during the ugrade. The E-Mail address (as login name) & password seem to be correct, because NTLM...
Our company recently upgraded our Skype backend to use Office 365, specifically the Microsoft 365 GCC (Government Cloud Community) High Security platform. Since this upgrade I have not been able to connect to Skype. The error returned is "Web ticket request to https://we1.008f.federal.lync.com:443/CertProv/CertProvisioningService.svc failed". I am running sipe 1.25.0 under pidgin 2.10.11-8 with libpurple 2.10.11 on RedHat Enterprise Linux 7. I've attached a debug log to hopefully help troubleshoot...
pidgin 2.14.0 has been released now, maybe this feature could be impl. now?
I don't get it. Why should that be relevant? I just followed the bug reporting instructions.
Understandable. The Organiazation I work for is dropping support for Skype for Business.
Sipe suddenly stopped working.
Closing as INVALID.
Sipe suddenly stopped working.
I have now installed the packages from debian testing including pidgin, and now joining a meeting with voice works. The packages are: Pidgin 2.13.0 (libpurple 2.13.0) SIPE: 1.25.0 An invitation to establish a voice call is sent as if someone will get a voice call with you.
I have now installed the packages from debian testing including pidgin, and now joining a meeting with voice works. The packages are: Pidgin 2.13.0 (libpurple 2.13.0) SIPE: 1.25.0 An invitation to establish a voice call is sent.
Hello First, thank you for the SIPE plugin. It is fantastic. I use pidgin 2.13.0 with libpurple 2.13.0 and sipe 1.25.0.2 on Debian 10. I can establish a voice call and join a scheduled conference (A new window opens showing a chat). But there is no media possiblle. A click on Conversation->Media shows a grayed Audio Call and is therefore not available. Is there another way to have voice in a scheduled conference (Skype meeting). Skype WebApp doesn't work in linux. Thank you Al
a detailed SIPE log with libnice git HEAD will show that the private IPs are no longer returned as valid candidates by libnice Indeed, there were no longer any "c=IN IP4 192.168.178.42" lines in the log with the git HEAD version. However, the following still showed up: a=candidate:1 1 UDP 2028994815 192.168.178.42 50054 typ host a=candidate:1 2 UDP 2028994814 192.168.178.42 50030 typ host a=candidate:10 1 TCP-PASS 174326015 185.106.25.8 59245 typ relay raddr 192.168.178.42 rport 50032 a=candidate:10...
I'm taking an educated guess here: a detailed SIPE log with libnice git HEAD will show that the private IPs are no longer returned as valid candidates by libnice, i.e. they will no longer be included in the INVITE sent by SIPE when your side initiates the call. a detailed libnice log will show that the ICE handshakre requires roughly 15 seconds to determine that the private IPs are no valid candidates. IMHO your issue is solved then.
Correction: Actually, there is some improvement with the HEAD version: connection can now be initiated from either side (issue #1) ... only the set up time remains slow (15 seconds) (issue #2). With my trap-bind.c workaround, connection setup is instantaneous.
It can still be reproduced with git HEAD (downloaded April 10th 16:33 CET)
libnice 0.1.14 is obsolete. I doubt they will act on the report unless you can reproduce it with 0.1.16 or even better git HEAD.
I reported it just now to libnice: https://gitlab.freedesktop.org/libnice/libnice/-/issues/108
libpurple API does not support IPv6, hence the code was replaced, see commit purple: update sipe_backend_transport_ip_address(). The code determines the IP address from the SIP connection socket which in your log shows f.ex.: (15:36:32) sipe: transport_get_socket_info: 10.202.77.9:55432(0x55eab8fae430) So as far as I understand from your report SIPE does use the correct IP internally, e.g. in SIP message creation. The rest of the issues you describe are most likely related to libnice, not SIPE. That...
libpurple API does not support IPv6, hence the code was replaced, see commit purple: update sipe_backend_transport_ip_address(). The code determines the IP address from the SIP connection socket which in your log shows f.ex.: (15:36:32) sipe: transport_get_socket_info: 10.202.77.9:55432(0x55eab8fae430) So as far as I understand from your report SIPE does use the correct IP internally, e.g. in SIP message creation. The rest of the issues you describe are most likely related to libnice, not SIPE. That...
libpurple API does not support IPv6, hence the code was replaced, see commit purple: update sipe_backend_transport_ip_address(). The code determines the IP address from the SIP connection socket which in your lock shows f.ex.: (15:36:32) sipe: transport_get_socket_info: 10.202.77.9:55432(0x55eab8fae430) So as far as I understand from your report SIPE does use the correct IP internally, e.g. in SIP message creation. The rest of the issues you describe are most likely related to libnice, not SIPE....
SIPE currently ignores the local IP address configured in Pidgin, making it impossible to use with a corporate server that is reachable only via VPN
libpurple API does not support IPv6, hence the code was replaced, see commit purple: update sipe_backend_transport_ip_address(). The code determines the IP address from the SIP connection socket which in your lock shows f.ex.: (15:36:32) sipe: transport_get_socket_info: 10.202.77.9:55432(0x55eab8fae430) So as far as I understand from your report SIPE does use the correct IP internally, e.g. in SIP message creation. The rest of the issues you describe are most likely related to libnice, not SIPE....
SIPE currently ignores the local IP address configured in Pidgin, making it impossible to use with a corporate server that is reachable only via VPN
No, not really, as there is no information to go on, e.g. version numbers of the relevant SW packages. Have you considered studying the FAQ page?
In order to prepare for an upcoming teleconference on Skype for business I'm trying out the pidgin SIPE plugin on our internal server with a colleague (let's call him Paul). There are 4 issues here: I cannot call Paul. After a while I see a popup "User sip:paul@ourcompany.lu is not available" and he sees "User rejected call" Fortunately, he can call me. However, it takes a certain time until the window to accept or reject the call appears on my screen. After accepting the call, it takes some more...
Is there any good reason why automake has to be 1.16?
I don't remember the exact reason, but this was part of the configure.ac cleanup for i18n tools. None of the tested platforms has an issue with that and normal users should use a prebuilt package or the release tarball, not build from git. Closing as NOTABUG.
Is there any good reason why automake has to be 1.16?
Removing the login name helped. Thanks very much
Yeah, log shows that you can't authenticate with that account information to Office 365. You probably have to talk to your IT admins: what kind of Lync installation do you use? Internal (i.e. on company servers) or external (i.e. Office 365)? if external: what is your account for that (your log shows that you are trying to use some internal Windows AD account for authentication, which most likely won't work, because Offcie 365 doesn't have an ADFS for the given account domain) if external: have you...
I tried setting the server, but sadly it didn't help.
Thanks for the log. User name and password seem to be correct, at least when trying to authenticate with NTLM against the HTTP server uccweb.ruag.com. What does not seem to work is the Lync autodiscover process. There are timeouts, that's why it takes so long (> 2 minutes according to the log). It then falls back to the old autodiscover method, which detects sips4b.ruag.com:443 as server. SIPE tries to run the authentication handshake but that fails: (11:17:42) sipe: sipe_http_parse_uri: host 'uccweb.ruag.com'...
Hi, I try to connect to Skype for Business Office 365 from my company. Pidgin always response with a message like that the certificate request failed (original message in german: Zertifikatsanforderung bei https://uccweb.ruag.com/CertProv/CertProvisioningService.svc/WebTicket_Proof_SHA1 fehlgeschlagen). Unlike the user BTJ (https://sourceforge.net/p/sipe/discussion/688534/thread/1890026c/) I don't get the message that my password is wrong. Also the login at login.microsoftonline.com works fine. I...
Hi to all, i'm using sipe plugin with pidgin, and it work fine. I found a problem with desktop sharing. When i'm sharing my desktop all work fine, and my colleagues see my desktop. When they share their desktop, i accept the sharing, but after some minute, they recive a message that say: device not correclty configure. Can someone help me? I set remote desktop client to remmina. (see attachment). Thanks in advance
Sipe audio call test always fail with message: audio test service not available
That's normal behaviour, i.e. the feature isn't available in your installation. I'm not sure if this is visible from the provided configuration information, i.e. if it would be possible to hide the menu. Jakub would maybe know. But as new feature development is on hold I doubt that it would ever be implemented. Closing as NOTABUG.
Sipe audio call test always fail with message: audio test service not available
The functionality you are looking for isn't SIPE specific. Hence you need to look up the correct libpurple DBus interface and call that in your script.
Hi. I would like to connect by commandline to a simple sip chat without conference. For conference I found the script sipe-join-conference-with-uri.pl It works well for sip full conference. The command line is /usr/local/contrib/dbus/sipe-join-conference-with-uri.pl 'sip:first.last@company.com;gruu;opaque=app:conf:focus:id:36KJD34R?required-media=audio' I tried to do the same with a shorter 'sip:first.last@company.com' URL but it fails. I opened the SIPE scripts located in /usr/local/contrib/dbus...
Hi. I would like to connect by commandline to a simple sip chat without conference. For conference I found the script sipe-join-conference-with-uri.pl It works well for sip full conference. The command line is /usr/local/contrib/dbus/sipe-join-conference-with-uri.pl 'sip:first.last@company.com;gruu;opaque=app:conf:focus🆔36KJD34R?required-media=audio' I tried to do the same with a shorter 'sip:first.last@company.com' URL but it fails. I opened the SIPE scripts located in /usr/local/contrib/dbus and...
Are you sure you are using plain xfreerdp client instead of remmina? Have you tried starting the remmina client and play with its settings, probably before startin a screen sharing session?
Hello, Many thanks for this wonderful software it really rocks! For me most of the required features works out of the box. I mean joining and talking in meetings + screen sharing client and server. However one thing I wonder if could be controlled. When I share a screen, the client (even being on local network) see glitches and poor performance. In other hand it seems like the xfreerdp or whatever underlying tool is used is set for best profile. The client is able to see full resolution with lots...
I can confirm that version 1.25.0-2 works as expected, and does not have the issue described earlier. Thanks!
Most likely the same issue as [bugs:#359]
Hi All, I have been using Sipe Plugin 1.24 for a while now with great success As soon as i updated that plugin to 1.25, I no longer have any way to join a Conference Call or Show Presentation when joining a SFB Meeting In fact, the only item available when you go to CONVERSATION --> MORE is "Meeting Entry Info" The other options there for "Join Conference Call" or "Show Presentation" are missing. Is there something else I should be doing outside of just the plugin upgrade? System Info is below (It...
I guess the collab PPA is dead. Have you tried the link to Open Build System link from the project web page?
Hi, I get the Read Error when trying to connect to Lync I have already tried the solution from FAQ (export NSS_SSL_CBC_RANDOM_IV=0) but it makes no difference. I have tried to search the forum but it seems all issues are a bit different or BEAST related. Is there some sort of fix? Thanks in advance. Best regtards, Sebastian The plugin is used with Pidgin 1.23 on Debian 9.6 Debug: (14:55:06) prefs: Reading /home/localuser/.purple/prefs.xml (14:55:06) prefs: Finished reading /home/localuser/.purple/prefs.xml...
Stefan, I think I may have found the issue (or at least it coincidently is now fixed). Either it was a reboot required, or the fact that the DNS records were not correct for autodiscover. Apparently our name server was converted to a new provider and the DNS records were not updated for Office 365. One or both of these seemed to have fixed the issue. Yay! This does however, bring up another point though. I got the latest version of SIPE via the collab PPA which pulls down 1.24. Where would I point...
Just to make sure: what does About SIPE plugin... say? Does it include Application Sharing in the feature list? If it does, then your description doesn't sound like a missing client, but more like a network connection that can't be established. That would point to nice/farstream/gstreamer. Please make sure to read the FAQ page for a list of required gstreamer plugins. Your package list indicates several outdated components that could be causing this issue. Compare your versions with the ones available...
I have installed and configured Pidgin and SIPE as well as Remmina and xfreerdp. I am running into an issue with screen sharing. I can connect to a meeting as well as communicate with users on Skype for Business just fine. However, when they attempt to do a screenshare, I get the Accept/Decline notification, but then after a few minutes I get a timeout. I have both xfreerdp and remmina installed, but in the advanced tab, I don't get a dropdown, only a text box for the rdp client. Leaving blank or...
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))
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...
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 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...
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
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.
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.
Good day,Stefan. Sorry for long delay. Log in attachment started from when i try to search somebody
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...
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