What steps will reproduce the problem?
1. Compile call example using a Tigase server as the XMPP server.
2. Attempt to run program.
3.
What is the expected output? What do you see instead?
***********************************************************************
I expect to see this - only here I am using TLS == DISABLED :
***********************************************************************
nicholas@thebeast:/libjingle/trunk/out/Debug$ ./call
JID: admin@tigase.xmpp.server.com
Password:
Logging in to tigase.xmpp.server.com as admin@tigase.xmpp.server.com
Available commands:
roster Prints the online friends from your roster.
friend user Request to add a user to your roster.
call [jid] [bw] Initiates a call to the user[/room] with the
given JID and with optional bandwidth.
vcall [jid] [bw] Initiates a video call to the user[/room] with
the given JID and with optional bandwidth.
calls Lists the current calls
switch [call_id] Switch to the specified call
join [room_jid] Joins a multi-user-chat with room JID.
ljoin [room_name] Joins a MUC by looking up JID from room name.
invite user [room] Invites a friend to a multi-user-chat.
leave [room] Leaves a multi-user-chat.
nick [nick] Sets the nick.
priority [int] Sets the priority.
getdevs Prints the available media devices.
quit Quits the application.
OpenSSLAdapter::OnConnectEvent
logging in...
logged in...
Warning(webrtcvoiceengine.cc:267): SetTraceCallback() failed, err=0
WebRtc VoiceEngine codecs:
ISAC/16000/1 (103)
ISAC/32000/1 (104)
PCMU/8000/1 (0)
PCMA/8000/1 (8)
Warning(webrtcvoiceengine.cc:313): Unexpected codec: PCMU/8000/2 (110)
Warning(webrtcvoiceengine.cc:313): Unexpected codec: PCMA/8000/2 (118)
Warning(webrtcvoiceengine.cc:313): Unexpected codec: opus/48000/1 (120)
opus/48000/2 (111)
CN/8000/1 (13)
CN/16000/1 (105)
CN/32000/1 (106)
CN/48000/1 (107)
telephone-event/8000/1 (126)
WebRtcVideoEngine::WebRtcVideoEngine
Warning(webrtcvideoengine.cc:565): SetTraceCallback(0x26baee8) failed, err=0
WebRtcVoiceEngine::Init
WebRtc VoiceEngine Version:
VoiceEngine 4.1.0
Build: svn:Unavailable(issue687) Dec 13 2012 18:35:33 d
External transport build
External recording and playout build
Applying audio options: AudioOptions {aec: 1, agc: 1, ns: 0, hf: 0, swap: 0,
typing: 1, conference: 0, agc_delta: 0, }
Warning(webrtcvoiceengine.cc:618): SetTypingDetectionStatus(1) failed, err=8003
Adjusting AGC level from default -3dB to -3dB
Disabling Conference Mode audio processing
WebRtc VoiceEngine codecs:
ISAC/16000/1 (103)
ISAC/32000/1 (104)
opus/48000/2 (111)
PCMU/8000/1 (0)
PCMA/8000/1 (8)
CN/48000/1 (107)
CN/32000/1 (106)
CN/16000/1 (105)
CN/8000/1 (13)
telephone-event/8000/1 (126)
WebRtcVoiceEngine::Init Done!
WebRtcVideoEngine::Init
WebRtcVideoEngine::InitVideoEngine
WebRtc VideoEngine Version:
VideoEngine 3.15.0
Build: svn:Unavailable(issue687) Dec 13 2012 18:34:38 d
External transport build
VideoEngine Init done
Creating default VideoCapturer
Enumerating V4L2 devices
V4L2 device metadata found at /sys/class/video4linux/
Found V4L2 capture device /dev/video0
Trying /sys/class/video4linux/video0/name
Name for video0 is USB2.0 UVC 2M WebCam
Total V4L2 devices found : 1
Applying audio options: AudioOptions {aec: 1, agc: 1, ns: 1, hf: 1, swap: 0,
typing: 1, conference: 0, agc_delta: 0, }
Warning(webrtcvoiceengine.cc:618): SetTypingDetectionStatus(1) failed, err=8003
Adjusting AGC level from default -3dB to -3dB
Disabling Conference Mode audio processing
Setting microphone to (id=0, name=Default device) and speaker to (id=0,
name=Default device)
Set microphone to (id=0 name=Default device) and speaker to (id=0 name=Default
device)
Creating default VideoCapturer
Enumerating V4L2 devices
V4L2 device metadata found at /sys/class/video4linux/
Found V4L2 capture device /dev/video0
Trying /sys/class/video4linux/video0/name
Name for video0 is USB2.0 UVC 2M WebCam
Total V4L2 devices found : 1
Selected ALSA sound system
Selected ALSA sound system
Enumerating V4L2 devices
V4L2 device metadata found at /sys/class/video4linux/
Found V4L2 capture device /dev/video0
Trying /sys/class/video4linux/video0/name
Name for video0 is USB2.0 UVC 2M WebCam
Total V4L2 devices found : 1
Adding to roster: admin@tigase.xmpp.server.com/call
********************************************************************
This is what I am seeing - when using TLS == REQUIRED :
********************************************************************
nicholas@thebeast:/libjingle/trunk/out/Debug$ ./call
JID: admin@tigase.xmpp.server.com
Password:
Logging in to tigase.xmpp.server.com as admin@tigase.xmpp.server.com
Available commands:
roster Prints the online friends from your roster.
friend user Request to add a user to your roster.
call [jid] [bw] Initiates a call to the user[/room] with the
given JID and with optional bandwidth.
vcall [jid] [bw] Initiates a video call to the user[/room] with
the given JID and with optional bandwidth.
calls Lists the current calls
switch [call_id] Switch to the specified call
join [room_jid] Joins a multi-user-chat with room JID.
ljoin [room_name] Joins a MUC by looking up JID from room name.
invite user [room] Invites a friend to a multi-user-chat.
leave [room] Leaves a multi-user-chat.
nick [nick] Sets the nick.
priority [int] Sets the priority.
getdevs Prints the available media devices.
quit Quits the application.
OpenSSLAdapter::OnConnectEvent
logging in...
BeginSSL: tigase.xmpp.server.com
SSL_connect:before/connect initialization
SSL_connect:SSLv3 write client hello A
SSL_connect:error in SSLv3 read server hello A
What version of the product are you using? On what operating system?
I am using the libjingle/trunk
Ubuntu 12.10 x86_64
Please provide any additional information below.
I installed the Tigase server using the defaults for the application. It does
use STARTTLS and uses a SELF SIGNED CERTIFICATE in .PEM form.
I just edited the call_main.cpp and changed the settings at the top of the
class. I them compiled the application and ran the call example.
I am guessing that the issue lies in the fact that it is self signed. It is
probably asking for us to accept the use of the certificate, but I know of no
way to check or accept the certificate. I want to use TLS and need to figure a
way around this current limitation, maybe there is already a solution that I
have overlooked? Please advise.
Original issue reported on code.google.com by nicho...@monstersoftwarellc.com on 14 Dec 2012 at 9:37
Original issue reported on code.google.com by
nicho...@monstersoftwarellc.com
on 14 Dec 2012 at 9:37