pbx | Cloud PBX scripts for VoxImplant | TCP library

1. Change your html structure

This is the first error that looks like a lead:

error: value +: is not a member of sbt.io.PathFinder scriptedClasspath ~= { cp => "modules/" +: "customer-modules/" +: cp }

It says that scriptedClasspath is a PathFinder and you're trying to add elements to it as if it was a Seq[String].

Read the docs on how to work with Path Finders and see the Scaladoc for the PathFinder type.

Most probably you will need to adjust it to something like

Figured it out, was not placing the new dropdown class I had created in the correct entry.

I'm no PHP expert, but I guess that exec waits for the external program to finish executing before populating the $output and $return variables and returning.

You say that your sql.pl program "constantly monitors a socket". That sounds like it doesn't actually exit until the user closes it (perhaps with a Ctrl-C or a Ctrl-Z). So, presumably, your PHP code sits there waiting for your Perl program to exit - but it never does.

So I think there are a few approaches I'd investigate.

• Does sql.pl have a command-line option that tells it to run once and then quit?
• Does PHP have a way to send a Ctrl-C or Ctrl-Z to sql.pl a second or so after you've started it?
• Does PHP have a way to deal with external programs that never end? Can you open a pipe to the external process and read output from it a line at a time?

For Programmable Voice, there are usually 2 call legs. With the Twilio client, you have the leg into Twilio (where you tell Twilio via TwiML what to do next) and another leg to the PSTN (your TwiML told Twilio to dial the PSTN). Twilio bridges the two call legs together. Each call leg has a per minute cost associated with it.

In your example, the call leg from the Twilio client to Twilio is always successful/answered. The leg to the PSTN may or may not be successful. If the PSTN leg is busy or not answered, there is no charge for that call leg, only the Twilio client to Twilio leg incurs a cost.

How Much am I Charged for Call Forwarding with Twilio?

For the most part, Elastic SIP Trunking does not have call legs. You do need a call server/PBX to use Elastic SIP Trunks. The call server/PBX handles all the application functionality vs. Twilio with Programmable Voice.

Try using request.form.get("name_of_field") instead of just request.form["name_of_field"].

When you use request.form["name_of_field"], flask assumes that they key will always be there. you canavoid this by using the other one, or the try and except trick.

I think # mean "wait 1 second" so overal time is over 2 second. So "S" should work after D ends.

Try following:

If I understand the issue correctly, you probably want to replace await self.do_recognition() with asyncio.create_task(self.do_recognition()) to make do_recognition execute in the background. If you need to support Python 3.6 and earlier, you can use loop.create_task(...) or asyncio.ensure_future(...), all of which in this case do the same thing.

When doing that you'll also need to extract the value of self._buffer and pass it to do_recognition as parameter, so that it can send the buffer contents independently of the new data that arrives.

Two notes unrelated to the question:

• The code is accessing internal implementation attributes of queue, which should be avoided in production code because it can stop working at any point, even in a bugfix release of Python. Attributes that begin with _ like _finished and _unfinished_tasks are not covered by backward compatibility guarantees and can be removed, renamed, or change meaning without notice.

• You can import CancelledError from the top-level asyncio package which exposes it publicly. You don't need to refer to the internal concurrent.futures._base module, which just happens to be where the class is defined by the implementation.

In other words: According to RTP protocol, is sending back the packet can work, or do I need to reconstruct them?

You need to construct a dedicated RTP header and add the received payload. SSRC and timestamp must be generated in a meaningful way or the receiver may discard those packets.