webRTC phoneGap plugin using Licode as signalling server

Hi,

I have an up and running Licode environment and starting from the PhoneRTC
github project I’ve developed a similar phoneGap iOS native plugin.

The developed functionality was tested using apprtc.appspot.com and
google’s mechanism for TURN and signalling servers.

If I want to use Licode environment instead apprtc.appspot.com, what
changes should I perform in my javascript code in order to get the
signalling server?
At top level the plugin usage is:

phonertc.call({
isInitator: true, // Caller or callee?
turn: {
host: ‘turn:turn.example.com:3478’,
username: ‘user’,
password: ‘pass’
},
sendMessageCallback: function (data) {
// PhoneRTC wants to send a message to your target, use
// your signaling server here to send the message.
signaling.sendMessage(target, {
type: ‘webrtc_handshake’,
data: data
});
},
answerCallback: function () {
alert(‘Callee answered!’);
},
disconnectCallback: function () {
alert(‘Call disconnected!’);
}});
signaling.onMessage = function (message) {
if (message.type === ‘webrtc_handshake’) {
// when a message is received from the signaling server,
// notify the PhoneRTC plugin.
phonertc.receiveMessage(message.data);
}};

In this case signalling represent the signalling server and I don’t know how to instantiate it using Licode.

Best regards,

Dorin

Hi guys,

I will be working on this subject in the next weeks. Any progress on your
side ?On Thursday, July 10, 2014 1:32:00 PM UTC+2, Geoffry Nagy wrote:

Hi Simina,

we are currently investigating the possibility to run Licode inside a
Phonegap application for Android.
It would be nice if you could share your findings with your project, it
looks really interesting!

On Wednesday, June 18, 2014 12:42:40 PM UTC+2, Simina Dorin wrote:

Hi,

I have an up and running Licode environment and starting from the
PhoneRTC github project I’ve developed a similar phoneGap iOS native plugin.
GitHub - alongubkin/phonertc: WebRTC for Cordova apps - No longer active

The developed functionality was tested using apprtc.appspot.com and
google’s mechanism for TURN and signalling servers.

If I want to use Licode environment instead apprtc.appspot.com, what
changes should I perform in my javascript code in order to get the
signalling server?
At top level the plugin usage is:

phonertc.call({
isInitator: true, // Caller or callee?
turn: {
host: ‘turn:turn.example.com:3478’,
username: ‘user’,
password: ‘pass’
},
sendMessageCallback: function (data) {
// PhoneRTC wants to send a message to your target, use
// your signaling server here to send the message.
signaling.sendMessage(target, {
type: ‘webrtc_handshake’,
data: data
});
},
answerCallback: function () {
alert(‘Callee answered!’);
},
disconnectCallback: function () {
alert(‘Call disconnected!’);
}});
signaling.onMessage = function (message) {
if (message.type === ‘webrtc_handshake’) {
// when a message is received from the signaling server,
// notify the PhoneRTC plugin.
phonertc.receiveMessage(message.data);
}};

In this case signalling represent the signalling server and I don’t know how to instantiate it using Licode.

Best regards,

Dorin

Hi,

we are currently using Licode in a Cordova app. We haven’t developed any
plugin for this.
To access the camera, we use the crosswalk project. This implements a
chrome webview to work in, instead of the default android webview.On Friday, August 29, 2014 3:59:03 PM UTC+2, Yannick Modah Gouez wrote:

Hi guys,

I will be working on this subject in the next weeks. Any progress on your
side ?

On Thursday, July 10, 2014 1:32:00 PM UTC+2, Geoffry Nagy wrote:

Hi Simina,

we are currently investigating the possibility to run Licode inside a
Phonegap application for Android.
It would be nice if you could share your findings with your project, it
looks really interesting!

On Wednesday, June 18, 2014 12:42:40 PM UTC+2, Simina Dorin wrote:

Hi,

I have an up and running Licode environment and starting from the
PhoneRTC github project I’ve developed a similar phoneGap iOS native plugin.
GitHub - alongubkin/phonertc: WebRTC for Cordova apps - No longer active

The developed functionality was tested using apprtc.appspot.com and
google’s mechanism for TURN and signalling servers.

If I want to use Licode environment instead apprtc.appspot.com, what
changes should I perform in my javascript code in order to get the
signalling server?
At top level the plugin usage is:

phonertc.call({
isInitator: true, // Caller or callee?
turn: {
host: ‘turn:turn.example.com:3478’,
username: ‘user’,
password: ‘pass’
},
sendMessageCallback: function (data) {
// PhoneRTC wants to send a message to your target, use
// your signaling server here to send the message.
signaling.sendMessage(target, {
type: ‘webrtc_handshake’,
data: data
});
},
answerCallback: function () {
alert(‘Callee answered!’);
},
disconnectCallback: function () {
alert(‘Call disconnected!’);
}});
signaling.onMessage = function (message) {
if (message.type === ‘webrtc_handshake’) {
// when a message is received from the signaling server,
// notify the PhoneRTC plugin.
phonertc.receiveMessage(message.data);
}};

In this case signalling represent the signalling server and I don’t know how to instantiate it using Licode.

Best regards,

Dorin

Hi Simina,

we are currently investigating the possibility to run Licode inside a
Phonegap application for Android.
It would be nice if you could share your findings with your project, it
looks really interesting!On Wednesday, June 18, 2014 12:42:40 PM UTC+2, Simina Dorin wrote:

Hi,

I have an up and running Licode environment and starting from the PhoneRTC
github project I’ve developed a similar phoneGap iOS native plugin.
GitHub - alongubkin/phonertc: WebRTC for Cordova apps - No longer active

The developed functionality was tested using apprtc.appspot.com and
google’s mechanism for TURN and signalling servers.

If I want to use Licode environment instead apprtc.appspot.com, what
changes should I perform in my javascript code in order to get the
signalling server?
At top level the plugin usage is:

phonertc.call({
isInitator: true, // Caller or callee?
turn: {
host: ‘turn:turn.example.com:3478’,
username: ‘user’,
password: ‘pass’
},
sendMessageCallback: function (data) {
// PhoneRTC wants to send a message to your target, use
// your signaling server here to send the message.
signaling.sendMessage(target, {
type: ‘webrtc_handshake’,
data: data
});
},
answerCallback: function () {
alert(‘Callee answered!’);
},
disconnectCallback: function () {
alert(‘Call disconnected!’);
}});
signaling.onMessage = function (message) {
if (message.type === ‘webrtc_handshake’) {
// when a message is received from the signaling server,
// notify the PhoneRTC plugin.
phonertc.receiveMessage(message.data);
}};

In this case signalling represent the signalling server and I don’t know how to instantiate it using Licode.

Best regards,

Dorin

Hi Yannick,

that’s right, currently our focus is on Android only.
iOS is on the roadmap but with iOS deliberately hitting the brake for HTML5
based apps, I have little confidence for iOS.On Friday, August 29, 2014 5:00:53 PM UTC+2, Yannick Modah Gouez wrote:

Oh this means you’re building for android only ?

Did you try to have something working with ios ?

On Friday, August 29, 2014 4:25:39 PM UTC+2, Geoffry Nagy wrote:

Hi,

we are currently using Licode in a Cordova app. We haven’t developed any
plugin for this.
To access the camera, we use the crosswalk project. This implements a
chrome webview to work in, instead of the default android webview.

Hi,

the signaling is totally wrapped by client API of licode. Here (
https://github.com/ging/licode/blob/master/extras/basic_example/public/script.js)
you will find our basic example demo in which every client that connects to
a room publish its stream and subscribe to others. As you can see the
signaling is implicit in publish and subscribe methods.

I hope this helps.

BR2014-06-18 12:42 GMT+02:00 Simina Dorin dorin.simina@gmail.com:

Hi,

I have an up and running Licode environment and starting from the PhoneRTC
github project I’ve developed a similar phoneGap iOS native plugin.
GitHub - alongubkin/phonertc: WebRTC for Cordova apps - No longer active

The developed functionality was tested using apprtc.appspot.com and
google’s mechanism for TURN and signalling servers.

If I want to use Licode environment instead apprtc.appspot.com, what
changes should I perform in my javascript code in order to get the
signalling server?
At top level the plugin usage is:

phonertc.call({
isInitator: true, // Caller or callee?
turn: {
host: ‘turn:turn.example.com:3478’,
username: ‘user’,
password: ‘pass’
},
sendMessageCallback: function (data) {
// PhoneRTC wants to send a message to your target, use
// your signaling server here to send the message.
signaling.sendMessage(target, {
type: ‘webrtc_handshake’,
data: data
});
},
answerCallback: function () {
alert(‘Callee answered!’);
},
disconnectCallback: function () {
alert(‘Call disconnected!’);
}});
signaling.onMessage = function (message) {
if (message.type === ‘webrtc_handshake’) {
// when a message is received from the signaling server,
// notify the PhoneRTC plugin.
phonertc.receiveMessage(message.data);
}};

In this case signalling represent the signalling server and I don’t know how to instantiate it using Licode.

Best regards,

Dorin


You received this message because you are subscribed to the Google Groups
“lynckia” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lynckia+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Álvaro

Oh this means you’re building for android only ?

Did you try to have something working with ios ?On Friday, August 29, 2014 4:25:39 PM UTC+2, Geoffry Nagy wrote:

Hi,

we are currently using Licode in a Cordova app. We haven’t developed any
plugin for this.
To access the camera, we use the crosswalk project. This implements a
chrome webview to work in, instead of the default android webview.