[Wengophone-devel] Does WengoPhone allows SRV DNS for not Wengo accounts?
I'm trying to configure a SIP account with a domain that has not a DNS A registry, but a SRV SIP UDP. WengoPhone says me: "Error in network". I can use it in Twinkle softphone without problem. So, does WengoPhone allows SRV DNS for not Wengo accounts? -- Iñaki Baz Castillo [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] wengophone 2.2 Beta
Hi Daniel, Daniel Nylander wrote: > Will there be any new strings to translate? > There is no 2.2 branch in Launchpad translations, only trunk and 2.1. I plan to create the 2.2 release series next week and update the .pot file. I can tell you that there are 124 new strings in the 2.2 branch right now, mostly related to the cobranding work Aurélien did, so relatively easy to translate, I hope. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] wengophone 2.2 Beta
Dave Neary wrote: > Hi all, Hi Dave, > > I'd like to have a new beta release of the WengoPhone 2.2 branch next > week (probably Thursday). > I would just release a new alpha version. I think we should update wengophone to use libpurple instead of gaim before we got to beta state. Normally beta means no more features and just bugfixes. -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] wengophone 2.2 Beta
Dave Neary skrev: > I'd like to have a new beta release of the WengoPhone 2.2 branch next > week (probably Thursday). Hi Dave, Will there be any new strings to translate? There is no 2.2 branch in Launchpad translations, only trunk and 2.1. -- Daniel Nylander (CISSP, GCUX, GCFA) Stockholm, Sweden http://www.DanielNylander.se [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] wengophone 2.2 Beta
Hi all, I'd like to have a new beta release of the WengoPhone 2.2 branch next week (probably Thursday). I'd like to do it for a few reasons: - A lot of changes have gone into the 2.2 branch since the alpha, the app should be more stable, and nicer now (especially around the chat window) - It's been a month since the last release - In the context of the trac clean-up, fix our priorities for 2.2 and get the countdown ticking (our priorities: kill bugs, et to the bottom of the longer-lasting known issues, concentrate on our core functionalities - sound, interoperability, video, presence, not crashing) We have some time to get these things right, but not too much time - it's already been 4 months since the 2.1 release came out, and with CoIP manager and the trunk coming along nicely, I'd like to see us make a usable application over there as soon as possible. Between now and then, I've identified what I think are the highest priority problems to fix: #1748: Crash after several Login/logout After the profile is unloaded & loaded several times, the WengoPhone becomes unstable & crashes. #1724: Crash on resume because of invalid vLineId I get this very frequently, it may be related to ticket #1748 #1743 Deadlock in IM - WengoPhone freezes when changing Jabber contact ID One of a number of issues with IM contacts #1211 Add 333 with the label "Test call" to initial default contact list This must be an easy one to fix, and would be a high-value improvement for first-time users. You could also add 335 as "test video call". Making high priority because I would like to have a string freeze to allow translators to update for the 2.2 branch soon. #1664 Freeze on resume This one has been hanging around for a while - there is a deadlock somewhere in the handling of the contact list on resume. There are lots of stack traces, and it's quite easy to reproduce. If someone could get to the bottom of this one, I'd have their baby. Well, not really - I don't have a womb. There are a couple of other issues with current developments which need addressing, but which don't yet have tickets - Aurélien's changes to the chat dialog aren't working perfectly yet, I don't see the avatars of the other person in the chat dialog, for example. But these are the priorities for the coming week. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Question about call forward ...
Title: TQI Tecnologia e Qualidade em Informática Ltda Hello there! I'm working on a IM and VoIP client that uses Openwengo libraries to make and receive VoIP calls. For this time, our customer's software only allow their users to make calls to each other on a very simple fashion (setup and tear down of single IP-to-IP or IP-to-Phone calls only). Now, they want to sell a complete IP-PBX service and create a new smartphone software to be packaged with it, but still using openwengo software. Considering that, I'm making an analysis of features they want and that are supported by Openwengo libraries, and the best way to do that is using the default Wengophone client. The features I'm checking out are: - Multiple call setup (one working and others on hold state of course); (check limitations too) - Voice Mail; - Call Forwarding - Others... One question that I have by now is about "Call Forwarding" option on Wengophone that is limited to "Wengo Accounts". This is a limitation present only at the application level, or is there any peace of code on the library that will block the use of this feature with a different sip provider? Thank's and best regards, -- At., Technology and Quality on Information Mauro Sérgio Ferreira Brasil Analista de Sistemas + [EMAIL PROTECTED] : www.tqi.com.br ( + 55 (34)3291-1700 ( + 55 (34)9971-2572 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Open tickets for 2.2
I put a vote for my own ticket #1758, "Provide packaging support". This ticket covers the missing files required by the packaging people (README, manpage etc). It's missing among the 19, perhaps by purpose, perhaps because silly me classified it as a 'task'. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Patch for Ticket #1735 (linux.prefered.browser)
On Wednesday 12 September 2007 17:48:57 neokortex wrote: > Good Evening, > > you're completely right. That's a much nicer solution. > Attached another try. > I left out the check, if the linux.prefered.browser value has ben altered, > as this is effectively more effort than call the setBrowser function > each time > the configuration file is saved, or do I miss some important point here I think it's ok. This code is not called that often. > In webBrowser.cpp I created a private function windows_open_url > and placed the windows related code there, so the actuall openUrl only > checks the os and wich function to call... (seemes more logical to me, > because the mac and linux calls are in functions-the windows weren't) Agreed (even if it would have been better to fix this in a separate patch, but I am a nitpicker). > the diff's in the attachment are against the actual revision of the > wengophone-2.2 branch, > because in the trunk, the location of the WebBrowser.cpp and .h moved to > libs/owutils/system...(the trunk have compilations errors on my system > so I used the 2.2 branch...) That's not a problem, we'll take care of this. A few comments though: I changed the static 'defaultBrowser' in WebBrowser.cpp from a char* to a std::string. It's not good to keep a reference to the result of std::string::c_str(), since it won't be valid anymore when the std::string is deleted. It's easier for us if you only send one diff file containing all changes. The simplest way to do so is to run "svn diff" from the root of the project. Note that you will need to generate separate diffs when your changes affect code in svn:externals. In your case you would run one "svn diff" from the root of the project and one other from the "libs/owutil" dir. I committed your patch in r12641 (owutil) and r12642 (wengophone). Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] [Fwd: Re: [Pidgin] #2638: "Message could not be sent because a connection error occurred:" (w/ MSN HTTP Method)]
Hi all,
Good news - there's a one-line fix for the MSN over HTTP problem we've
had for the past few weeks - see below for the report from the ticket in
their trac.
I think we should apply this one-line patch to our private copy of
libgaim, in both the 2.1 and 2.2 branches, and consider upgrading to
libpurple (or consider depending on the system copy of libpurple)
between now and the 2.2 release.
Cheers,
Dave.
Original Message
Subject: Re: [Pidgin] #2638: "Message could not be sent because a
connection error occurred:" (w/ MSN HTTP Method)
Date: Wed, 12 Sep 2007 18:08:52 -
From: Pidgin <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
#2638: "Message could not be sent because a connection error occurred:"
(w/ MSN
HTTP Method)
---+
Reporter: ThorbjornTux | Owner:
Type: defect| Status: new
Priority: major | Milestone: Merge MSNP14 Branch
Component: libpurple | Version: 2.1.0
Resolution:|Keywords:
Pending: 0 |
---+
Comment (by laszlok):
I think I have solved it. This works perfectly for me behind a corporate
firewall that only allows port 80 out.
== Here is the issue: ==
The default value for the msn server address is messenger.hotmail.com. You
can see this is filled in beside "Server:" in the "Advanced" tab of the
"Modify Account" dialog. However this server is only used for non-http
connections. To use HTTP and bypass a corporate firewall, you must use
gateway.messenger.hotmail.com. This address is hard-coded in the
msn_httpconn_connect() function in libpurple/protocols/msn/httpconn.c. So
no matter what host and port are given as arguments to
msn_httpconn_connect(), it will always connect to
gateway.messenger.hotmail.com on port 80.
The problem arises when the msn server tells us to use another host. This
only recently stopped working, so I am guessing up until then microsoft
used the same server for everything. When you want to start chatting to
someone, the client sends a switchboard request to the server:
{{{
XFR 12 SB
}}}
Then the server responds with the information on how to connect to the
switchboard:
{{{
XFR 12 SB 65.54.171.30:1863 CKI 151986110.22113252.20218652
}}}
You can see there is a host and port given for the switchboard in
"65.54.171.30:1863". The other two arguments are authentication method and
session ID. Of course this was designed before the HTTP method was in use,
because as you know we can't connect to port 1863 because of our corporate
firewall; we have to use port 80. However the server still expects us to
connect to the given host on port 80. So we need to connect to
65.54.171.30:80.
The pidgin code parses the host and port nicely, and requests a new
connection to that server, but these arguments are ignored because both
the host and port are hard-coded in msn_httpconn_connect(). It tried to
connect to the switchboard at gateway.messenger.hotmail.com, but that
server is not a switchboard, and sends HTTP 400 Bad Request. Pidgin then
reports this to the user as "Message could not be sent because a
connection error occurred".
== How to fix it: ==
First you have to apply my patch, which removes the hard-coded
gateway.messenger.hotmail.com, and allows it to use the one in the
"Advanced" tab of the "Modify Account" dialog.
It's a simple one line patch:
{{{
--- libpurple/protocols/msn/httpconn.c 2007-08-20 14:12:48.0
-0400
+++ libpurple-http-fixed/protocols/msn/httpconn.c 2007-09-12
13:26:25.0 -0400
@@ -725,7 +725,7 @@
msn_httpconn_disconnect(httpconn);
httpconn->connect_data = purple_proxy_connect(NULL,
httpconn->session->account,
- "gateway.messenger.hotmail.com", 80, connect_cb,
httpconn);
+ host, 80, connect_cb, httpconn);
if (httpconn->connect_data != NULL)
{
}}}
1. Apply the patch to the 2.1.1 release (I haven't tested it out with
anything else).
1. Make, make install.
1. Run Pidgin, and open Account -> Add/Edit. Select you MSN account and
click Modify.
1. Go the the Advanced tab, and change Server to
"gateway.messenger.hotmail.com" without the quotes.
1. Make sure Port is 80, and "Use HTTP Method" is selected.
1. Logout and login again. You should be able to chat now.
--
Ticket URL:
Pidgin
Pidgin
--
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
Tel: +33 9 51 13 46 45
Mob: +33 6 28 09 73 11
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
