Welcome to GotSpeech.NET Sign in | Join | Help

while (speech > milk)

Speech Synthesis and Recognition
And the winner of the Zune is ...

Jesse Jones. For the "Consulted Conferencing - Writing your own SMEX disconnect handler in javascript" tip.  Jesse please reply to the private message with your address and I will get it to you ASAP! Thanks to every one who participated!

Jesse's Tip:  Consulted Conferencing - Writing your own SMEX disconnect handler in javascript.

When doing consulted conference calls sometimes it is necessary to handle the dropping of the consulted or original party in different terms.  A nice way is to use a custom SMEX handler to detect the connection cleared event and determine the dropping party.

EX

var ConferenceCall_TheSmexEl = document.all["_callControlSmex"];

var ConferenceCallControl_OldOnReceive = ConferenceCall_TheSmexEl.onreceive;

ConferenceCall_TheSmexEl.onreceive = ConferenceCall_SmexMsgHandler;

function SmexMsgHandler()

{ 

  var docEl = ConferenceCallControl_TheSmexEl.received;

  var callID;

  var deviceID;  

  var date;
 

  if (docEl.baseName == "ConnectionClearedEvent")

  {

    callID =         getNodeText(docEl.selectSingleNode("/csta:ConnectionClearedEvent/csta:droppedConnection/csta:callID"));

    deviceID = getNodeText(docEl.selectSingleNode("/csta:ConnectionClearedEvent/csta:droppedConnection/csta:deviceID"));

if (ConsultedPartyNum != "" && ConsultedPartyNum == deviceID)

      {

          OnClientConsultedPartyDrop();

      }               

      else

      {               

          OnClientOriginalPartyDrop();                      

      }

   }       

}

Now you can handle each case in its own method and do any specific logging or flow.

 

Posted: Saturday, March 31, 2007 3:42 PM by MichaelDunn
Filed under:

Comments

No Comments

Anonymous comments are disabled