[Wengophone-devel] Wengophone gaim_connection_error with Jabber accounts
Dear all, I've just installed WengoPhone-2.2-minsizerel-13085 on Linux/Debian boxes and WengoPhone-2.2-setup-relwithdebinfo-13119-pdb on Windows XP boxes in my LAN. I've added SIP accounts that work very well and Jabber accounts (I have an own Jabber server) with the following problems: 1) When I add a Jabber contact he can't authorize me and so I see him always as disconnected 2) The Jabber contacts I have authorized via another Jabber client (psi) appears as connect and disconnect time after time, and I get this error in console: In WXP: ** (WengoPhone.exe:2676): CRITICAL ** gaim_connection_error: assertion `text != NULL' failed In Linux: ** (process:28909): CRITICAL **: gaim_connection_error: assertion `text != NULL' failed Is there any problem with adding/authorizing Jabber contacts in wengo ??? Which wengo version do I have to use if I want SIP+Jabber running OK ??? Thanks a lot Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Wengophone 2.2 and Asterisk problem
Dinesh Nair wrote: On Thu, 11 Oct 2007 21:32:28 -0300, Alejandro Facultad wrote: But when I establish a call between two Wengophones, I sniffer the communication and I realize that SIP+RTP packets go among clients and Asterisk always (RTP does not bypass Asterisk). asterisk will no do a reinvite when it needs to be in the middle of the media stream for any reason, such as call transfers being activated or call recording being activated. what's the arguments to the Dial application you're giving to asterisk ? (actually, this should be sent to the asterisk mailing lists instead) Hi, I write in name of my colleague Alejandro. We have Asterisk with canreinvite=yes and nat=no for every user of sip.conf file and this is our dialplan you request (with the Dial application): [company] exten = ,1,Dial(SIP/user1) exten = 1112,1,Dial(SIP/user2) exten = 1113,1,Dial(SIP/user3) ... The Advanced options of the Wengophone control panel are by default, and I check/uncheck the Register through proxy account option but it's the same (by the way, we don't know the use of this option and it's not explained anywhere). Any help to get RTP data packets bypassing the Asterisk and go among SIP clients ??? Thanks a lot for your support. Alejandro -- Ing. Alejandro Cabrera Obed Interconexion SINTyS Sistema de Identificación Nacional Tributario y Social Consejo Nacional de Coordinación de Políticas Sociales Presidencia de la Nación Julio A. Roca 782 - Piso 5 Ciudad Autónoma de Bs. As. Tel: (54 11) 4343-0181/89 interno 5172 4334-3676 4342-5648 [EMAIL PROTECTED] NOTA DE RESPONSABILIDAD: -- Este mensaje proviene de Internet,tome los recaudos necesarios en su manejo. El contenido del presente mensaje y sus adjuntos es privado, estrictamente confidencial y exclusivo para su destinatario, pudiendo contener información protegida por normas legales y de secreto profesional. Bajo ninguna circunstancia su contenido puede ser transmitido o revelado a terceros ni divulgado en forma alguna. En consecuencia de haberlo recibido solicitamos contactar al remitente y eliminarlo de su sistema. -- ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Re: WengoPhone-2.2-minsizerel-alsa-12867 problems
Julien Bossart wrote: Aurélien Gâteau a écrit : On Wednesday 10 October 2007 20:38:38 Alejandro Cabrera Obed wrote: Dear Aurelien and people, I've installed the last alpha version of wengophone (WengoPhone-2.2-minsizerel-alsa-12867) on our Debian Etch boxes but we have three problems: 1) The main bar is diffused (the part of the bar where the display name appears does not appear completely). I can attach a print screen image if you like. This has been fixed I think, try a newer version. I just realized the content of the GNULinux/2.2/ dir on download.wengo.com is confusing: the latest one is not the one at the bottom, because we renamed the archives lately. Since there is no more portaudio version, the -alsa suffix has been removed. The latest version at the time I am writing this is WengoPhone-2.2-minsizerel-12991.tar.bz2. Will remove the -alsa to avoid confusion. 2) After I add a Jabber account I can add my Jabber contacts and authorize them very well but I CAN'T read the messages we interchange on the chat window: I type words, then I press Enter but the other client doesn't see anything, the same if he types and sends me a message. Same thing, I think it's fixed now. 3) How can I see in the Wengo window if the call is encrypted or not ??? I don't want to use a sniffer to check it out, I want each user to see his encryption state for security reasons. If encryption is enabled, you will see a green info bar in the phone call tab telling so. Unfortunately, it's quite difficult to get it working right now: - For Wengo account: it just plain won't work until a pending server upgrade is deployed. - For SIP account: your server must make sure it does not drop a special line in the headers, needed to setup encryption. I am not familiar with this part of the WengoPhone, so I can't be more precise. Julien knows more, I am CC'ing him. Aurélien Hi all! So, to give more informations about the encryption, you have to be sure that your SIP router does not remove the encryption key. You can see it in the SDP during an INVITE packet, an attribute header named evrb_key. If during a call session, this attribute is present in both request and reply, the call should be encrypted. On the Wengo network, this feature doesn't work because our router (Cirpack) removes this attribute, but normally with SER or OpenSER, this attribute should not be touched if you don't ask it specifically. I hope that can be helpful for you to understand the encryption process. Julien Thanks Aurelien and Julien, now I will start to download the latest version you say. And for encryption, I tell you I use our own Asterisk 1.2.13 SIP server, and I don't know if it removes the attribute header named evrb_keyso I have to investigate deeper using a sniffer or the sip debug command from CLI. Really thanks, regards !!! Alejandro -- Ing. Alejandro Cabrera Obed Interconexion SINTyS Sistema de Identificación Nacional Tributario y Social Consejo Nacional de Coordinación de Políticas Sociales Presidencia de la Nación Julio A. Roca 782 - Piso 5 Ciudad Autónoma de Bs. As. Tel: (54 11) 4343-0181/89 interno 5172 4334-3676 4342-5648 [EMAIL PROTECTED] NOTA DE RESPONSABILIDAD: -- Este mensaje proviene de Internet,tome los recaudos necesarios en su manejo. El contenido del presente mensaje y sus adjuntos es privado, estrictamente confidencial y exclusivo para su destinatario, pudiendo contener información protegida por normas legales y de secreto profesional. Bajo ninguna circunstancia su contenido puede ser transmitido o revelado a terceros ni divulgado en forma alguna. En consecuencia de haberlo recibido solicitamos contactar al remitente y eliminarlo de su sistema. -- ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] WengoPhone-2.2-minsizerel-alsa-12867 problems
Dear Aurelien and people, I've installed the last alpha version of wengophone (WengoPhone-2.2-minsizerel-alsa-12867) on our Debian Etch boxes but we have three problems: 1) The main bar is diffused (the part of the bar where the display name appears does not appear completely). I can attach a print screen image if you like. 2) After I add a Jabber account I can add my Jabber contacts and authorize them very well but I CAN'T read the messages we interchange on the chat window: I type words, then I press Enter but the other client doesn't see anything, the same if he types and sends me a message. 3) How can I see in the Wengo window if the call is encrypted or not ??? I don't want to use a sniffer to check it out, I want each user to see his encryption state for security reasons. Special thanks, Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Question about Debian package with ALSA build
Aurélien Gâteau wrote: On Wednesday 19 September 2007 11:37:12 Aurélien Gâteau wrote: On Tuesday 18 September 2007 16:20:03 Alejandro Cabrera Obed wrote: But I need one more help: after run alsaconf and alsamixer on my Debian console, I execute LD_LIBRARY_PATH=. ./wengophone and wengophone starts but when I chose the input, output and ringing device as ALSA default but I get this warning message (the audio tests are OK): (warn) 11:13:26 static EnumDeviceType::DeviceType EnumDeviceType::toDeviceType(const std::string): unknown DeviceType= I just fixed a bug which would cause this warning if you selected a different audio device from the config dialog. It's in revision 12703. It should be out on download.wengo.com/nightlybuilds/ soon. We have a problem with the Linux builders right now. I'll let you know when it's fixed. Linux builders are back. You can get the latest version here: http://download.wengo.com/nightlybuilds/binary/NG/GNULinux/2.2/WengoPhone-2.2-minsizerel-alsa-12703.tar.bz2 Aurélien Aurelien, I've installed wengophone-2.2-minsizerel-alsa-12703 in my Linux Debian Etch machines from my Intranet as you told me, I setup alsa sound (alsaconf and alsamixer) and after that I tried to establish a SIP call between two wengo users. We could hear the ringing but we couldn't hear the voice. The audio device was established as ALSA default and Intel ICH5 also but we never hear the voice at any time. The terminal where I executed wengo show this log: [EMAIL PROTECTED]:~/WengoPhone-2.2-minsizerel$ ./wengophone.sh (info) 09:47:42 void QtLanguage::loadLanguageFromConfig(): no Qt translation ava ilable for locale '' (info) 09:47:42 void QtLanguage::loadLanguageFromConfig(): no application transl ation available for locale '' QProcess: Destroyed while process is still running. (info) 09:48:16 Wenbox::Wenbox(): Wenbox dll not loaded (info) 09:48:16 virtual void PhApiWrapper::setCallsEncryption(bool): Set call en cryption to:1 (error) 09:48:43 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:48:44 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:49:06 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:49:06 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone Timer: pthread_create: Success (info) 09:49:24 virtual bool PhApiWrapper::isCallEncrypted(int): Call with callI d 1 has encryption mode 0 I repeat that when I use Twinkle or any other SIP softphone I CAN establish a call and I CAN hear the voice very well. Any suggestion or trick you can tell me ??? Special thanks Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Question about Debian package with ALSA build
Aurélien Gâteau wrote: On Friday 21 September 2007 15:15:24 Alejandro Cabrera Obed wrote: Aurélien Gâteau wrote: On Wednesday 19 September 2007 11:37:12 Aurélien Gâteau wrote: On Tuesday 18 September 2007 16:20:03 Alejandro Cabrera Obed wrote: But I need one more help: after run alsaconf and alsamixer on my Debian console, I execute LD_LIBRARY_PATH=. ./wengophone and wengophone starts but when I chose the input, output and ringing device as ALSA default but I get this warning message (the audio tests are OK): (warn) 11:13:26 static EnumDeviceType::DeviceType EnumDeviceType::toDeviceType(const std::string): unknown DeviceType= I just fixed a bug which would cause this warning if you selected a different audio device from the config dialog. It's in revision 12703. It should be out on download.wengo.com/nightlybuilds/ soon. We have a problem with the Linux builders right now. I'll let you know when it's fixed. Linux builders are back. You can get the latest version here: http://download.wengo.com/nightlybuilds/binary/NG/GNULinux/2.2/WengoPhone -2.2-minsizerel-alsa-12703.tar.bz2 Aurélien Aurelien, I've installed wengophone-2.2-minsizerel-alsa-12703 in my Linux Debian Etch machines from my Intranet as you told me, I setup alsa sound (alsaconf and alsamixer) and after that I tried to establish a SIP call between two wengo users. We could hear the ringing but we couldn't hear the voice. The audio device was established as ALSA default and Intel ICH5 also but we never hear the voice at any time. The terminal where I executed wengo show this log: [EMAIL PROTECTED]:~/WengoPhone-2.2-minsizerel$ ./wengophone.sh (info) 09:47:42 void QtLanguage::loadLanguageFromConfig(): no Qt translation ava ilable for locale '' (info) 09:47:42 void QtLanguage::loadLanguageFromConfig(): no application transl ation available for locale '' QProcess: Destroyed while process is still running. (info) 09:48:16 Wenbox::Wenbox(): Wenbox dll not loaded (info) 09:48:16 virtual void PhApiWrapper::setCallsEncryption(bool): Set call en cryption to:1 (error) 09:48:43 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:48:44 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:49:06 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone (error) 09:49:06 void IMChatSession::typingStateChangedEventHandler(IMChat, IMC hatSession, const std::string, IMChat::TypingState): this session does not kno w [EMAIL PROTECTED]/WengoPhone Timer: pthread_create: Success (info) 09:49:24 virtual bool PhApiWrapper::isCallEncrypted(int): Call with callI d 1 has encryption mode 0 I repeat that when I use Twinkle or any other SIP softphone I CAN establish a call and I CAN hear the voice very well. Any suggestion or trick you can tell me ??? I am going to be out of tricks soon :-(. Can you try this: - Establish a conversion between Twinkle and WengoPhone, see if at least you get sound in one way. - Try to send DTMF sounds from the WengoPhone, to see if they reach the peer. Aurélien Thanks Aurelien, now I can't do this test because the testing machines are busy. But I have a last question: - My SIP clients are in 10.10.x.x network - My SIP server is in 172.1.x.x network - I don't use NAT for clients to get the SIP server When I start wengophone 2.1.2 for windows it launches a HTTP Proxy Server windows to log in, and in the advanced features I see that proxy server is localhost, proxy port is 8080 and user and password are empty.What is this feature ??? Do I have to use it in my scenario ??? Thanks a lot !!! Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Question about Debian package with ALSA build
Aurélien Gâteau wrote: On Monday 17 September 2007 16:20:31 Alejandro Facultad wrote: Dear all, I have the following scenario: - Intranet - Asterisk 1.2.13 (SIP server) - Linux/Debian Etch workstations - Wengophone 2.1.1.dfsg0-4 (Debian package downloaded from contrib builds at http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/DebianUbuntuPackages) In the Debian Etch machines, I run alsaconf and after that alsamixer in order to setup the audio features. After that we configure Wengophone with an Asterisk/SIP account and try to call other person from intranet. When I dial a SIP contact number, we can establish the communication as showing in our softphones screen but we can't get audio nor microphonewe can't listen to each other. Hello Alejandro Unfortunately, Alsa support in 2.1 is still far from perfect. Situation has improved with 2.2. Can you give the nightly builds a try? You can find them in: http://download.wengo.com/nightlybuilds/binary/NG/GNULinux/2.2/ Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel Dear Aurelien, I follow your advice and I remove wengophone package for Debian (apt-get remove --purge wengophone) and then I install in my Debian Etch this Wengo version with ALSA support as you reccomend: http://download.wengo.com/nightlybuilds/binary/NG/GNULinux/2.2/WengoPhone-2.2-minsizerel-alsa-12694.tar.bz2 After that I do: 1) unzip to /home/ale/WengoPhone-2.2-minsizerel 2) change my current directory to/ home/ale/WengoPhone-2.2-minsizerel 3) Type: /LD_LIBRARY_PATH=. ./qtwengophone /But when I type this last command I get Segmentation fault. 4) After that I run ./wengophone.sh and I it starts (¿?) Please can you help me on the segmentatiion fault error and how can I solve this ??? Thanks again Alejandro// ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Question about Debian package with ALSA build
Aurélien Gâteau wrote: On Tuesday 18 September 2007 14:50:15 Alejandro Cabrera Obed wrote: Dear Aurelien, I follow your advice and I remove wengophone package for Debian (apt-get remove --purge wengophone) and then I install in my Debian Etch this Wengo version with ALSA support as you reccomend: http://download.wengo.com/nightlybuilds/binary/NG/GNULinux/2.2/WengoPhone-2 .2-minsizerel-alsa-12694.tar.bz2 After that I do: 1) unzip to /home/ale/WengoPhone-2.2-minsizerel 2) change my current directory to/ home/ale/WengoPhone-2.2-minsizerel 3) Type: /LD_LIBRARY_PATH=. ./qtwengophone /But when I type this last command I get Segmentation fault. 4) After that I run ./wengophone.sh and I it starts (¿?) Please can you help me on the segmentatiion fault error and how can I solve this ??? Did you really run ./qtwengophone, not ./wengophone? This is strange because the name of the binary has changed in the latest nightly builds from qtwengophone to wengophone. Maybe this file was a remaining of a previous installation. If in doubt, rm the WengoPhone-2.2-minsizerel and unpack the archive again. Aurélien Dear Aurelien, you have the reason, with LD_LIBRARY_PATH=. ./wengophone the program starts without segmentation fault. But I need one more help: after run alsaconf and alsamixer on my Debian console, I execute LD_LIBRARY_PATH=. ./wengophone and wengophone starts but when I chose the input, output and ringing device as ALSA default but I get this warning message (the audio tests are OK): (warn) 11:13:26 static EnumDeviceType::DeviceType EnumDeviceType::toDeviceType(const std::string): unknown DeviceType= (info) 11:13:26 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:1 (info) 11:13:26 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:1 (info) 11:13:26 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:1 Nothing about ALSA device appears and I can't listen to the other SIP user I contact in my intranet. What can I do ??? Really thanks, you help me a lot. Alejandro -- Ing. Alejandro Cabrera Obed Interconexion SINTyS Sistema de Identificación Nacional Tributario y Social Consejo Nacional de Coordinación de Políticas Sociales Presidencia de la Nación Julio A. Roca 782 - Piso 5 Ciudad Autónoma de Bs. As. Tel: (54 11) 4343-0181/89 interno 5172 4334-3676 4342-5648 [EMAIL PROTECTED] NOTA DE RESPONSABILIDAD: -- Este mensaje proviene de Internet,tome los recaudos necesarios en su manejo. El contenido del presente mensaje y sus adjuntos es privado, estrictamente confidencial y exclusivo para su destinatario, pudiendo contener información protegida por normas legales y de secreto profesional. Bajo ninguna circunstancia su contenido puede ser transmitido o revelado a terceros ni divulgado en forma alguna. En consecuencia de haberlo recibido solicitamos contactar al remitente y eliminarlo de su sistema. -- ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Wengophone and Jabber
Dear all, I have the following scenario: - Intranet - Asterisk 1.2.13 (SIP server) - Jabberd2 (jabber server) - Linux/Debian wengophone 2.1.1.dfsg0-4 - Windows XP wengophone 2.1.2 rev 12359 SIP voip calls are established OK...the problem is with Jabber communications, I tell you: 1) In each wengophone I add a Jabber account 2) After that I add jabber contacts 3) When I add a contact, he/she is prompted for authorization 4) Finally all the contacts appear as DISCONNECTED in all the Wengophones so I CAN'T send a message Also I check that the Wengo clients are well connected to the Jabberd2 server: tcp0 0 jabber.mydomain:5223 *:* LISTEN 19313/c2s tcp0 0 jabber.mydomain:5223 host1.mydomain:51430 ESTABLISHED19313/c2s tcp0 0 jabber.mydomain:5223 host2.mydomain:44847 ESTABLISHED19313/c2s tcp0 0 jabber.mydomain:5223 host3.mydomain:1230 ESTABLISHED19313/c2s If I use any other Jabber client like Gaim or Psi, I can chat OK. What's the problem with Wengophone and jabber ??? Thanks again Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Wengophone Debian to WindowsXP problems
Ludovico Cavedon wrote: Hi, Alejandro Cabrera Obed wrote: - When I start a SIP call using Wengophone from Windows XP to Debian I succeded !!! - When I start a SIP call using Wengophone from Debian to Windows XP I get this error: WARNING[2709]: chan_sip.c:3602 process_sdp: Unknown SDP media type in offer: video 10702 RTP/AVP 34 31 and anymore Are you using version 2.1.1.dfsg0-3 or greater, right? The Debian package has video support disabled, because video codec support has been removed from Debian's ffmpeg because of patent issues :( However the problem you are describing should not happen. I'll debug it ASAP. It would be great if you could open a bug against the Debian package. Thank you! Regards, Ludovico Cavedon Dear Ludovico, I've rebooteed all my servers and workstations and now I can talk using SIP/Asterisk between my Linux/Debian and Windows XP Wengophone clients. But I still have a problem: in wengophone I set up Jabber accounts (against my own jabberd2 server), add jabber intranet contacts, but we always see the contacts OFFLINE being that they are logged in my jabberd2 succesfully. And so I can't chat to any jabber contact anytime. I have these Wengo versions: Windows XP Wengophone 2.1.2 rev 12359 Linux/Debian Etch Wengophone 2.1.1.dfsg0-4 Is there any trouble to use Jabber accounts with a private jabberd2 server from Wengophone ??? Any tip ??? Really thanks Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Wengophone Debian to WindowsXP problems
Dear all, I'm new at wengophone so I'm testing the software nowadays. I have an Asterisk 1.2.13 and a Jabberd2 running both OK, using clients like Twinkle (SIP) and Psi (jabber). Now I have to use a Wengophone client in order to unify both SIP and Jabber clients into my intranet: Linux/Debian clients - Wengophone 2.1.1.dfsg0-4 for ALSA (installed with apt-get) Windows XP clients -- Wengophone 2.1.2 (last revision) But I have 2 problems: 1st problem) - When I start a SIP call using Wengophone from Windows XP to Debian I succeded !!! - When I start a SIP call using Wengophone from Debian to Windows XP I get this error: WARNING[2709]: chan_sip.c:3602 process_sdp: Unknown SDP media type in offer: video 10702 RTP/AVP 34 31 and anymore 2nd problem) I create a Jabber account (against my own jabberd server) in each Wengophone client, after that I log in and I see the Online green light status. But when I add a contact I always see him as OFFLINE, so they can't chat to each other. What can be the problems I have ??? Is it possible that Wengophone Debian package is not working OK Thanks a lot Alejandro ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
