Plivo Conference Issue about plivo-node HOT 5 CLOSED

Just to clarify...
We need the CallUUID at the browser end that should be sent at the time that we transfer a call to our server end.

If we can get the CallUUID at the browser end through the plivo JSON object at the time of calling a external number then it will solve our problem.

from plivo-node.

Currently we do not expose the call uuid through the web sdk. Your endpoint has an associated Plivo application which has an answer url. When your endpoint makes a call, Plivo makes an http request to that url with the call uuid, destination phone number, etc. 
An upcoming update to the web sdk will expose the call uuid. 

CHARLIE CHRISMAN | CUSTOMER SUCCESS ENGINEER
Plivo, Inc. 340 Pine St, San Francisco, CA 94104
+1-415-993-8809 | www.plivo.com | @plivo

    _____________________________

From: benne2jp [email protected]
Sent: Thursday, September 29, 2016 7:05 AM
Subject: Re: [plivo/plivo-node] Plivo Conference Issue (#46)
To: plivo/plivo-node [email protected]

Just to clarify...
We need the CallUUID at the browser end that should be sent at the time that we transfer a call to our server end.

If we can get the CallUUID at the browser end through the plivo JSON object at the time of calling a external number then it will solve our problem.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from plivo-node.

Another method to achieve what you are trying to do would be to put the incoming call directly in a conference and make an outbound call API request to the agent and when answered put them in the conference then make another call API request to the 3rd party and put them directly in the conference. Then you don't have to deal with transferring anyone.

CHARLIE CHRISMAN | CUSTOMER SUCCESS ENGINEER
Plivo, Inc. 340 Pine St, San Francisco, CA 94104
+1-415-993-8809 | www.plivo.com | @plivo

    _____________________________

From: benne2jp [email protected]
Sent: Thursday, September 29, 2016 6:01 AM
Subject: [plivo/plivo-node] Plivo Conference Issue (#46)
To: plivo/plivo-node [email protected]

We are currently creating a call center application. One of the basic functions is for a phone agent to create a conference call.

So far, we have successfully created a conference call by 1) calling from an external phone number (my cell phone) to our app, where a phone agent in our app answers, thus creating the A leg, 2) using conference to make a call to a 3rd party, thus creating the B leg which 3) conferences in all 3 parties (the external caller, the phone agent, a third party).

Notice the direction of the phone call in step 1. A cell phone calls in to our Plivo-powered app and a uuid is provided. The issue surfaces when our "Phone Agent" initiates a call to, let's say, a cell phone or land line number.

My question is -- how do we get a uuid, which is needed to conference, when the phone agent calls an external number?

If you need to see a 5 minute demo of what we have that is working (and what's not), I am in Central time and can be reached at 251-654-1830.

Thanks in advance!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from plivo-node.

@cachrisman @benne2jp is there any updates on this?? I got the same issue so can you provide the sample code?
p.s. : I have already gone through plivo api docs and did the same as mentioned in that.

from plivo-node.

This issue has been marked as stale because it has not had recent activity and is now closed. Please open the issue if the solution is not found yet.

from plivo-node.