Re: [Wengophone-devel] Speex in nightlies

[Mathieu Stute]

On Monday 12 March 2007 19:21, Mathieu Stute wrote:
> On Monday 12 March 2007 19:11, michel memeteau wrote:
> > Hi I 've seen tou've updated the build environnement few weeks ago , But
> > now On any platform it seems that Speex is not here , then PCMU is used
> > all the time .
> >
> > Is this a feature not to include speex ?
>
> No, this is a bug, thx for the input (phamrplugin is missing too)

This is fixed for the latest builds: 
http://wengofiles.wengo.fr/nightlybuilds/binary/NG/GNULinux/2.1/
-- 
Mathieu Stute 
GPG: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3EE62B4D


pgpNAzTFdHtDa.pgp
Description: PGP signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Speex in nightlies

[michel memeteau]

On 13/03/07, Mathieu Stute <[EMAIL PROTECTED]> wrote:


On Monday 12 March 2007 19:21, Mathieu Stute wrote:
> On Monday 12 March 2007 19:11, michel memeteau wrote:
> > Hi I 've seen tou've updated the build environnement few weeks ago ,
But
> > now On any platform it seems that Speex is not here , then PCMU is
used
> > all the time .
> >
> > Is this a feature not to include speex ?
>
> No, this is a bug, thx for the input (phamrplugin is missing too)

This is fixed for the latest builds:
http://wengofiles.wengo.fr/nightlybuilds/binary/NG/GNULinux/2.1/



I just tested last revision 10240 on WindowsXP  , in the config audio page,
no speex . Is speex included in all platforms ?

I've Checked in program files , but no speex Dlls , maybe it found my
already present speex in C:\windows\system32 ?  I guess No


--
%<--->%
Michel memeteau
VOIP: sip:[EMAIL PROTECTED]
0491886375 0624808051
jabber/GoogleTalk : [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Speex in nightlies

[Mathieu Stute]

> I just tested last revision 10240 on WindowsXP  , in the config audio page,
> no speex . Is speex included in all platforms ?
Yep, speex is included in all plateforms, actually speex's name is replaced by 
G726-64wb/16000 (Wengo network specific issue)
I'll add a gui hack to present speex to the end user, thanks for this.

> I've Checked in program files , but no speex Dlls , maybe it found my
> already present speex in C:\windows\system32 ?  I guess No
Our speex share library is called (lib)phspeexplugin.[so|dll] and is a dynamic 
plugin for phapi (like phamrplugin)

Regards,
-- 
Mathieu Stute 
GPG: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3EE62B4D


pgpR9jFQEVVVE.pgp
Description: PGP signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Speex in nightlies

[michel memeteau]

Great ! Thanks for all the infos , I should have checked in the directory a
name contening speex ...

I did not really understood how G726 and speex are close but I'll check
about it . As long as it works with another softphone thta has speex in
highest codec priority list, It's good

Thanks Mathieu , Hope to advise Wengophone around me soon ...

On 13/03/07, Mathieu Stute <[EMAIL PROTECTED]> wrote:


> I just tested last revision 10240 on WindowsXP  , in the config audio
page,
> no speex . Is speex included in all platforms ?
Yep, speex is included in all plateforms, actually speex's name is
replaced by
G726-64wb/16000 (Wengo network specific issue)
I'll add a gui hack to present speex to the end user, thanks for this.

> I've Checked in program files , but no speex Dlls , maybe it found my
> already present speex in C:\windows\system32 ?  I guess No
Our speex share library is called (lib)phspeexplugin.[so|dll] and is a
dynamic
plugin for phapi (like phamrplugin)

Regards,
--
Mathieu Stute 
GPG: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3EE62B4D





--
%<--->%
Michel memeteau
VOIP: sip:[EMAIL PROTECTED]
0491886375 0624808051
jabber/GoogleTalk : [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Collecting contrib binary builds

[Dave Neary]

Hi all,

I'd love to collect links to contributed binary builds for varioous
Linux distributions in the wiki (following GlaDiaC's lead for OpenSuse).

Have a look at http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki and
if you have a link to a .rpm or .deb for your distribution, then please
add a link to it to the list (including a small logo if you have it).

I'm eager to keep the list down to the biggest distributions at the
moment - Debian testing/unstable, Ubuntu (6.06/7.04/Feisty
pre-releases), OpenSuse (already covered thanks to Andreas), Fedora Core
 and Mandriva.

Gianluca, Marco, Nicolas, Jeff, any chance you've gotten around to
making binaries for your distros?

Thanks!
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] RE: SIP Generic bug

[michel memeteau]

On 07/03/07, Lukas Oberhuber <[EMAIL PROTECTED]> wrote:


 I've seen problems like this where the other proxy was wanting to
register and the proxy you are registered is not able to respond. Are you
sure this is not the case here?



Sorry do you mean , if I use a SIP account and the wengo account in the same
time ?

Here my tests are quite basic  :

- I log  in wengo with my username through their hhtp tunnel to their SIP
proxy . I can call any wengo adress  and any SIp number such as 17476005010

- When I try to call [EMAIL PROTECTED] or any [EMAIL PROTECTED] , it seems to 
call
only toto  and log in the history only toto etc .

So briefly , lukas showed us that the call was really made , but are we sure
that it's not only the number that is resolved and the server address is not
resolved ?

Ok I'm gonna be a bit rude :

Do you really think the wengo team can release a 2.1 RC1 and advertise that
it supports standard etc ...  If the wengophone behave like that ?   I'll
open tickets about it later 

With this can of problem , Wengo is just another skype thing 


--


*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *michel
memeteau
*Sent:* 07 March 2007 13:24
*To:* wengophone-devel@lists.openwengo.com
*Subject:* Re: [Wengophone-devel] RE: SIP Generic bug



Hi , I just test today the 10164 windows Build over a http proxy :

   - when calling a sip URI through a contact or though the "address
   box" , the call is working but the call id display is still only the first
   part of the SIP URI , and call history does not show the sip server either .

   - Call to a sipphone adress [EMAIL PROTECTED] succeed
   but calls to [EMAIL PROTECTED]  or [EMAIL PROTECTED] does not (
   either no sound or the call just hang )  , I was wondering if it could be a
   codec problems or a generic SIP adress handling one ?


My point of view : a lot of efforts have been done in interoperability for
SIP in the wengo dev team . But if it's still not easy to  call/add a SIP
address , then wengo won't be used as a SIP softphone such as ekiga and
xlite , and most of the users will only do wengo to wengo calls . ...

On 01/03/07, *Lukas Oberhuber* <[EMAIL PROTECTED]> wrote:

Also, the fix to modify the SIP account didn't work. It still crashes with
the latest revision as of midday. I think there are some UI files missing,
etc.



-Lukas
  --

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Lukas
Oberhuber
*Sent:* 28 February 2007 14:26
*To:* 'Xavier DESJARDINS'
*Cc:* wengophone-devel@lists.openwengo.com
*Subject:* [Wengophone-devel] RE: SIP Generic bug



Xavier,



Just tested on the new build:



I dialled:

sip:+61892880790@ aarnet.edu.au



Everything in the UI shows +61892880790, but the call is dialled
correctly. On redial, the call was made to sip:[EMAIL PROTECTED]
So I can confirm the fix works.



However, I feel like the UI should probably show the full URI in cases
where the server is not a match, no?



Also, would be great if the installer would have an option to set up sip:
links to open wengophone and dial (probably present the option to the user
to choose…). Here is a page to use to test:
http://www.voip-info.org/wiki/view/Phone+Numbers



-Lukas



*Lukas Oberhuber** *
   --

*From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf
Of *Xavier DESJARDINS
*Sent:* 28 February 2007 09:37
*To:* Lukas Oberhuber
*Cc:* wengophone-devel@lists.openwengo.com
*Subject:* Re: SIP Generic bug





2007/2/28, Lukas Oberhuber < [EMAIL PROTECTED]>:

-   When editing a contact, SIP ID (in simple mode), does not
appear

-  Call history (all histories) do not store the full SIP uri when
the call is not to an account of the same server: i.e.
sip:[EMAIL PROTECTED] would get recorded as +456789 and on
subsequent calls would dial that





-Lukas



*Lukas Oberhuber*


Hi Lukas,

The probleme with call history is fixed in rev10004.

 I'll look at contact editing.

Xavier






___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel




--
%<--->%
Michel memeteau
VOIP: sip:[EMAIL PROTECTED]
0491886375 0624808051
jabber/GoogleTalk : [EMAIL PROTECTED]





--
%<--->%
Michel memeteau
VOIP: sip:[EMAIL PROTECTED]
0491886375 0624808051
jabber/GoogleTalk : [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[JP Renaud]

> Date: Tuesday 13 Mar 2007 
> From: Dave Neary <[EMAIL PROTECTED]>
> Gianluca, Marco, Nicolas, Jeff, any chance you've gotten around to
> making binaries for your distros?

Gialu,

Although I still have many issues with my debug build, I'd be happy to build a 
FC6 rpm for x86_64 from your rpm src when it is ready. Just shout.

-- 
JP Renaud

http://www.jprenaud.info
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] RE: SIP Generic bug

[Lukas Oberhuber]

Michel,

 

To clarify what I wrote below: I've tested with recent builds and the
history for your examples will show only 500 or toto. (I'm not logged into
Wengo when I do this, but into sipalive.com), so I'm not sure if wengo (the
service, not the phone) supports calling to other SIP providers.

 

When I look at the logs on my server, the calls are going to
sip:[EMAIL PROTECTED] or sip:[EMAIL PROTECTED], even when I select them from the
history which only says 500 or toto.

 

I do think it's a problem that we have to guess that the number is correct
and have to look at the server logs to check if the call went through, but
as far as I can tell, the functionality works. With only wengophone, there
is no good way to check if you made a call to the right address.

 

The next problem, is that *some* service providers do not allow incoming
calls from other networks (for fairly obvious reasons such as spam) and
therefore require a peering agreement. The peering agreement means that each
network can call the other.

 

In practice, when I try to call a network that requires a peering agreement,
and sipalive doesn't have one, the sipalive asterisk server gets back a SIP
authentication request when it makes the call (sip 'invite' I believe) to
the other network. Since the sipalive asterisk server doesn't have any
credentials for the other network (no peering agreement), it hangs up the
call to the other network, and the call fails.

 

Obviously, you don't have access to the server logs at Wengo, and there is
no "Error: peering agreement lacking" so it is hard to diagnose from your
side.

 

Hope this helps explain.

 

-Lukas

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of michel
memeteau
Sent: 13 March 2007 12:33
To: wengophone-devel@lists.openwengo.com
Subject: Re: [Wengophone-devel] RE: SIP Generic bug

 

 

On 07/03/07, Lukas Oberhuber <[EMAIL PROTECTED]> wrote:

I've seen problems like this where the other proxy was wanting to register
and the proxy you are registered is not able to respond. Are you sure this
is not the case here?


Sorry do you mean , if I use a SIP account and the wengo account in the same
time ? 

Here my tests are quite basic  : 

- I log  in wengo with my username through their hhtp tunnel to their SIP
proxy . I can call any wengo adress  and any SIp number such as 17476005010

- When I try to call [EMAIL PROTECTED]   or any
[EMAIL PROTECTED] , it seems to call only toto  and log in the history only
toto etc . 

So briefly , lukas showed us that the call was really made , but are we sure
that it's not only the number that is resolved and the server address is not
resolved ? 

Ok I'm gonna be a bit rude : 

Do you really think the wengo team can release a 2.1 RC1 and advertise that
it supports standard etc ...  If the wengophone behave like that ?   I'll
open tickets about it later  

With this can of problem , Wengo is just another skype thing  
 

 


  _  


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of michel
memeteau
Sent: 07 March 2007 13:24
To: wengophone-devel@lists.openwengo.com
Subject: Re: [Wengophone-devel] RE: SIP Generic bug

 

Hi , I just test today the 10164 windows Build over a http proxy : 

*   when calling a sip URI through a contact or though the "address box"
, the call is working but the call id display is still only the first part
of the SIP URI , and call history does not show the sip server either . 
*   Call to a sipphone adress [EMAIL PROTECTED] succeed
but calls to [EMAIL PROTECTED]  or [EMAIL PROTECTED] does not ( either
no sound or the call just hang )  , I was wondering if it could be a codec
problems or a generic SIP adress handling one ? 


My point of view : a lot of efforts have been done in interoperability for
SIP in the wengo dev team . But if it's still not easy to  call/add a SIP
address , then wengo won't be used as a SIP softphone such as ekiga and
xlite , and most of the users will only do wengo to wengo calls . ... 

On 01/03/07, Lukas Oberhuber < [EMAIL PROTECTED]
 > wrote:

Also, the fix to modify the SIP account didn't work. It still crashes with
the latest revision as of midday. I think there are some UI files missing,
etc.

 

-Lukas


  _  


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lukas
Oberhuber
Sent: 28 February 2007 14:26
To: 'Xavier DESJARDINS'
Cc: wengophone-devel@lists.openwengo.com 
Subject: [Wengophone-devel] RE: SIP Generic bug

 

Xavier,

 

Just tested on the new build:

 

I dialled:

sip:+61892880790@ aarnet.edu.au  

 

Everything in the UI shows +61892880790, but the call is dialled correctly.
On redial, the call was made to sip:[EMAIL PROTECTED] So I can
confirm the fix works.

 

However, I feel like the UI should probably show the full URI in cases where
the server is not a match, no?

 

Also, would be great if the installer would have an opt

Re: [Wengophone-devel] Collecting contrib binary builds

[Gianluca Sforna]

On 3/13/07, Dave Neary <[EMAIL PROTECTED]> wrote:

I'd love to collect links to contributed binary builds for varioous
Linux distributions in the wiki (following GlaDiaC's lead for OpenSuse).


Are you also willing to host them? I surely have not enough BW avaliable...



Gianluca, Marco, Nicolas, Jeff, any chance you've gotten around to
making binaries for your distros?


My attempt to build 2.1rc1 failed because of the missing 3rdparty
subtree so I don't have it ready. Did you fix this or should I export
the sources on my own (like I believe Andreas did)?

in the latter case, can you confirm the URL to "svn export" for having
the sources of 2.1rc1?
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Pirmin Walthert]

Hi

For everyone who wants to make packages for Ubuntu 7.04 (Feisty):

Before you also loose hours on getting compilation to work on Feisty
I've a few notes for you:

- As you may know from older discussions Gcc-4.1 doesn't like Boost! =>
Boost-Libraries seem to compile ok but do not work correctly!

=> So the way is normally to use GCC-3.4 or 4.0.

=> But with Feisty there came up more problems as, I had to realize
yesterday when I first tried to compile wengophone on a fresh
Feisty-Installation: Feisty uses Binutils 2.17. GCC-3.4 and 3.3 had a
bug that was fixed in the 4.0 releases and doesn't affect libraries
linked with binutils2.16.

So now 4.1 doesn't work because of the problems with Boost (tried again
with the 4.1 version of Feisty yesterday) and 3.4 doesn't work because
of Binutils2.17 (linking of libboost_serialization fails). And the other
thing is: For x86 Gcc-4.0 is no longer included with Feisty!

=> The best thing to get it working is to compile GCC-4.0 yourself and
use this version to build both and WengoPhone.

Also note that, if you want to build with scons instea of cmake, you
can't use the Scons-Version delivered with Feisty without changing some
Scons-scripts. got it working by installing scons 0.96.1 and forcing it
to use python2.4 instead of python2.5!

Cheers, Pirmin

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Dave Neary]

Hi,

Gianluca Sforna wrote:
> Are you also willing to host them? I surely have not enough BW avaliable...

For you? Probably ;)

>> Gianluca, Marco, Nicolas, Jeff, any chance you've gotten around to
>> making binaries for your distros?
> 
> My attempt to build 2.1rc1 failed because of the missing 3rdparty
> subtree so I don't have it ready. Did you fix this or should I export
> the sources on my own (like I believe Andreas did)?
> 
> in the latter case, can you confirm the URL to "svn export" for having
> the sources of 2.1rc1?

Yes - you should svn export. The URL is
http://dev.openwengo.org/svn/openwengo/wengophone-ng/tags/release/2.1/2007-03-08-wengophone-2.1-rc1

In general, all released builds will be tagged in
http://dev.openwengo.org/svn/openwengo/wengophone-ng/tags/release - this
directory will contain references for the release series in question.

Cheers,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Dave Neary]

Hi,

Pirmin Walthert wrote:
> For everyone who wants to make packages for Ubuntu 7.04 (Feisty):

7.04 is Edgy Eft, Feisty Fawn is the future 7.10 release.

> - As you may know from older discussions Gcc-4.1 doesn't like Boost! =>
> Boost-Libraries seem to compile ok but do not work correctly!

I've seen this come up several times - does anyone have a link to the
bug report against Boost so that we can track the progress of this bug,
please?

Cheers,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Dave Neary]

Dave Neary wrote:
> Hi,
> 
> Pirmin Walthert wrote:
>> For everyone who wants to make packages for Ubuntu 7.04 (Feisty):
> 
> 7.04 is Edgy Eft, Feisty Fawn is the future 7.10 release.

Oops - of course, I'm getting ahead of myself, and this is wrong. 7.04
is indeed Feisty 6.10 was Edgy, and 6.06 is LTS (also Dapper).

Hiding my head,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Pirmin Walthert]

Hi Dave

Here is the link you already know (because you made an entry there):


On Die, 2007-03-13 at 14:22 +0100, Dave Neary wrote:
> Hi,
> 
> Pirmin Walthert wrote:
> > For everyone who wants to make packages for Ubuntu 7.04 (Feisty):
> 
> 7.04 is Edgy Eft, Feisty Fawn is the future 7.10 release.
> 
> > - As you may know from older discussions Gcc-4.1 doesn't like Boost! =>
> > Boost-Libraries seem to compile ok but do not work correctly!
> 
> I've seen this come up several times - does anyone have a link to the
> bug report against Boost so that we can track the progress of this bug,
> please?
> 
> Cheers,
> Dave.
> 

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Pirmin Walthert]

Sorry, wrong key pressed and mail sent instead of inserting the link :)

Here is the link: 

https://launchpad.net/ubuntu/+source/gcc-4.1/+bug/75724

I did this test with the Feisty 4.1-GCC and with my self-compiled
4.0-GCC. With 4.1 the same error, with 4.0 it worked.

I have my 4.0-version from here:
https://launchpad.net/ubuntu/+source/gcc-4.0/
=> ubuntu-patches applied and compiled. The apt-get compilation doesn't
work because it's officially no longer supported on x86!

Cheers, Pirmin

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Wengophone2.1 RC1 features, etc.

[Philippe BERNERY]

Hi Atanas,

Thanks for your report, it will help to improve WengoPhone. Could you  
create Trac tickets for bugs you reported on http:// 
dev.openwengo.org. This is the best way to report bugs. However be  
sure that there is not already a ticket describing a bug.


Regards

--
Philippe BERNERY <[EMAIL PROTECTED]>
http://dev.openwengo.org


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Gianluca Sforna]

On 3/13/07, Pirmin Walthert <[EMAIL PROTECTED]> wrote:

Sorry, wrong key pressed and mail sent instead of inserting the link :)

Here is the link:

https://launchpad.net/ubuntu/+source/gcc-4.1/+bug/75724


I think what we really need is a bug filed _upstream_. If we are sure
this is a boost problem, it should problably be here:

http://sourceforge.net/tracker/?group_id=7586&atid=107586

otherwise, better to also file one at:

http://gcc.gnu.org/bugzilla


Please note this is also a blocker for an eventual submission on Fedora
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Collecting contrib binary builds

[Marco Nenciarini]

On Tue, Mar 13, 2007 at 01:26:07PM +0100, Dave Neary wrote:
> 
> Hi all,
> 
> I'd love to collect links to contributed binary builds for varioous
> Linux distributions in the wiki (following GlaDiaC's lead for OpenSuse).
> 
> Have a look at http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki and
> if you have a link to a .rpm or .deb for your distribution, then please
> add a link to it to the list (including a small logo if you have it).
> 
> I'm eager to keep the list down to the biggest distributions at the
> moment - Debian testing/unstable, Ubuntu (6.06/7.04/Feisty
> pre-releases), OpenSuse (already covered thanks to Andreas), Fedora Core
>  and Mandriva.
> 
> Gianluca, Marco, Nicolas, Jeff, any chance you've gotten around to
> making binaries for your distros?
> 

I'm working on it, I've a package, but it does not follow many debian
requirements about linking/rpath. I'll upload it to the debian
unstable archive as soon as I solve these problems.

Ciao

-- 
-
|Marco Nenciarini| Debian/GNU Linux Developer - Plug Member |
| [EMAIL PROTECTED] | http://www.prato.linux.it/~mnencia   |
-
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4



signature.asc
Description: Digital signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] SIP messages while registering.

[Mayank Otia]

Hi,
 
I was looking at the SIP message flow from Wengophone, using WireShark,
and I saw a REGISTER message which contains "nobody@" in the From and To
filed. This occurs everytime I Login with Wengo. Can anybody explain me
why is it sending without my wengo account name?
 
Thanks,
Mayank Otia
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] SIP messages while registering.

[Minh Phan]

Hi Mayank,

 

That message is sent in order to detect local network configuration. It is
not the REGISTER for your Wengo SIP account. If we receive a response from
the server in reply to that register message, we then know that we can
connect directly to the SIP server. Otherwise, we may need to use HTTP
tunnel to reach the server. The real REGISTER message with your user name
will be sent once the local network config has been detected.

 

Regards,

 

Minh

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mayank
Otia
Sent: mardi 13 mars 2007 18:06
To: wengophone-devel@lists.openwengo.com
Subject: [Wengophone-devel] SIP messages while registering.

 

Hi,

 

I was looking at the SIP message flow from Wengophone, using WireShark, and
I saw a REGISTER message which contains "nobody@" in the From and To filed.
This occurs everytime I Login with Wengo. Can anybody explain me why is it
sending without my wengo account name?

 

Thanks,

Mayank Otia

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] SIP messages while registering.

[Minh Phan]

Now one quick question.So, it is not concerned with registration process
(which is REGISTER(without credentials)->407->REGISTER(with
credentials)->200), right?

 

Yeah, nothing to do with that sequence.

 

Minh

 

  _  

From: Mayank Otia [mailto:[EMAIL PROTECTED] 
Sent: mardi 13 mars 2007 18:58
To: Minh Phan
Subject: RE: [Wengophone-devel] SIP messages while registering.

 

Thanks Minh,

 

Thanks for your detailed explanation, I was thinking that if we get "404 Not
found" then, why are we sending nobody? but your explanation solves my
question.

Now one quick question.So, it is not concerned with registration process
(which is REGISTER(without credentials)->407->REGISTER(with
credentials)->200), right?

 

Thanks,

Mayank Otia

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Minh Phan
Sent: Tuesday, March 13, 2007 1:45 PM
To: Mayank Otia; wengophone-devel@lists.openwengo.com
Subject: RE: [Wengophone-devel] SIP messages while registering.

Hi Mayank,

 

That message is sent in order to detect local network configuration. It is
not the REGISTER for your Wengo SIP account. If we receive a response from
the server in reply to that register message, we then know that we can
connect directly to the SIP server. Otherwise, we may need to use HTTP
tunnel to reach the server. The real REGISTER message with your user name
will be sent once the local network config has been detected.

 

Regards,

 

Minh

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mayank
Otia
Sent: mardi 13 mars 2007 18:06
To: wengophone-devel@lists.openwengo.com
Subject: [Wengophone-devel] SIP messages while registering.

 

Hi,

 

I was looking at the SIP message flow from Wengophone, using WireShark, and
I saw a REGISTER message which contains "nobody@" in the From and To filed.
This occurs everytime I Login with Wengo. Can anybody explain me why is it
sending without my wengo account name?

 

Thanks,

Mayank Otia

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] SIP messages while registering.

[Mayank Otia]

Thanks, Minh...
 
Mayank



From: Minh Phan [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 13, 2007 3:22 PM
To: Mayank Otia
Cc: wengophone-devel@lists.openwengo.com
Subject: RE: [Wengophone-devel] SIP messages while registering.



Now one quick question.So, it is not concerned with registration process
(which is REGISTER(without credentials)->407->REGISTER(with
credentials)->200), right?

 

Yeah, nothing to do with that sequence.

 

Minh

 



From: Mayank Otia [mailto:[EMAIL PROTECTED] 
Sent: mardi 13 mars 2007 18:58
To: Minh Phan
Subject: RE: [Wengophone-devel] SIP messages while registering.

 

Thanks Minh,

 

Thanks for your detailed explanation, I was thinking that if we get "404
Not found" then, why are we sending nobody? but your explanation solves
my question.

Now one quick question.So, it is not concerned with registration process
(which is REGISTER(without credentials)->407->REGISTER(with
credentials)->200), right?

 

Thanks,

Mayank Otia

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Minh
Phan
Sent: Tuesday, March 13, 2007 1:45 PM
To: Mayank Otia; wengophone-devel@lists.openwengo.com
Subject: RE: [Wengophone-devel] SIP messages while registering.

Hi Mayank,

 

That message is sent in order to detect local network configuration. It
is not the REGISTER for your Wengo SIP account. If we receive a response
from the server in reply to that register message, we then know that we
can connect directly to the SIP server. Otherwise, we may need to use
HTTP tunnel to reach the server. The real REGISTER message with your
user name will be sent once the local network config has been detected.

 

Regards,

 

Minh

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mayank Otia
Sent: mardi 13 mars 2007 18:06
To: wengophone-devel@lists.openwengo.com
Subject: [Wengophone-devel] SIP messages while registering.

 

Hi,

 

I was looking at the SIP message flow from Wengophone, using WireShark,
and I saw a REGISTER message which contains "nobody@" in the From and To
filed. This occurs everytime I Login with Wengo. Can anybody explain me
why is it sending without my wengo account name?

 

Thanks,

Mayank Otia

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel