Re: How to end a consultation call and reconnect to held party
Tapan Bhatt <[email protected]> Tue, 7 Nov 2006 17:06:47 +0530
| Newsgroups | gmane.comp.java.sun.jtapi |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_3334_29600856.1162899407729 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Thanks to for the mail.but I'm new to this technology.I tried to call on normal telephone using the code that's given along with JTAPI spec. but One Exception was thrown that is for PEER I hope that this is due to I dont have EPBX with my phone. *Now I've VOIP Adapter with me. Can you tell me that would be enough to make a call from my machine?* ** *What Components I've are * *P-IV machine with XP running on it*. *I've Installed JTAPI and configured it b making jar file of all class file of jtapi package.* *one treditional telephone and one VOIP Adapter of CISCO Co.* *Is it enough to develop 'caller system' with a these components.* *any other thing I need other then that I've.* ** *kindly reply me,its urgent for me!* ** *Thanks * *Tapan Bhatt* On 11/7/06, Dean Jesson <[email protected]> wrote: > > Hi, > > I would like to know how in Jtapi one is supposed to end a consultation > call and reconnect to the held party. The use case is as follows. > > I have an application which creates a consultation call via Jtapi and then > wants to end it: > - terminal A is in a normal call with B and they are talking; > - then terminal A makes a consultation call to C and B goes on hold; > - because C does not answer, terminal A would now like to reconnect to B, > meaning that the consultation call should end and the call to B should be > taken off hold so that A and B are once again connected in a normal call. > > How can one achieve the reconnect in Jtapi? The required function is a > transition from a consultation call to a normal call with the party which > was on hold during the consultation. > > Is it sufficient to call disconnect() on A's Connection to the call to C? > or will this leave B still on hold? If B does get left on hold, can I simply > take B explicitly off hold by calling unhold() on the > CallControlTerminalConnection on A's Connection to the A/B call? > > I have my doubts about this disconnect()+unhold() combination for the > following reason. If I do try disconnect() then unhold() my Jtapi > implementation will send a CSTA-ClearConnection request to the switch > followed by a CSTA-RetrieveCall. I have already tested the effect of this on > the switch and it does not lead to the desired behaviour. The desired switch > behaviour can only be triggered by sending a CSTA-ReconnectCall (to replace > both CSTA-ClearConnection and CSTA-RetrieveCall). > > I conclude then that for my switch, reconnect cannot be brought about by > disconnect()+unhold(), because a special protocol command has to be sent to > the switch as early as the disconnect() stage. If any implementation of > Jtapi can be written which can work with this switch, the sequence of Jtapi > commands required must therefore be different. Instead, I see two > alternatives: > 1. disconnect() must be sufficient to perform the entire reconnect > operation, and that the Jtapi implementation will have to be intelligent > enough to recognise that disconnect() is being called on a consultation > connection and in this case send a CSTA-ReconnectCall to the switch instead > of a CSTA-ClearConnection; > 2. some other Jtapi interface function should be used, which explicitly > requests a reconnect. > > The problem with (1) is that the function does more than the user has > asked for. This may mean a loss of functionality with other switch types > which do support two-stage reconnect. The problem with (2) is that it - so > far as I know - is not part of the Jtapi standard. > > So, does anyone know what the intended sequence of Jtapi commands is for > performing the reconnect? > > Thanks, > Dean > > > =========================================================================== > To unsubscribe, send email to [email protected] and include in the > body > of the message "signoff JTAPI-INTEREST". For general help, send email to > [email protected] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [email protected] and include in the body of the message "signoff JTAPI-INTEREST". For general help, send email to [email protected] and include in the body of the message "help". ------=_Part_3334_29600856.1162899407729 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <div>Hi,</div> <div> Thanks to for the mail.but I'm new to this technology.I tried to call on normal telephone using the code that's given along with JTAPI spec.</div> <div>but One Exception was thrown that is for PEER</div> <div>I hope that this is due to I dont have EPBX with my phone.</div> <div><strong>Now I've VOIP Adapter with me. Can you tell me that would be enough to make a call from my machine?</strong></div> <div><strong><u></u></strong> </div> <div><strong><u>What Components I've are </u></strong></div> <div><font color="#330099"><strong>P-IV machine with XP running on it</strong>.</font></div> <div><font color="#330099"><strong>I've Installed JTAPI and configured it b making jar file of all class file of jtapi package.</strong></font></div> <div><font color="#330099"><strong>one treditional telephone and one VOIP Adapter of CISCO Co.</strong></font></div> <div><strong><font color="#330099">Is it enough to develop 'caller system' with a these components.</font></strong></div> <div><strong><font color="#330099">any other thing I need other then that I've.</font></strong></div> <div><strong><font color="#330099"></font></strong> </div> <div><strong><font color="#ff0000">kindly reply me,its urgent for me!</font></strong></div> <div><strong><font color="#ff0000"></font></strong> </div> <div><strong><font color="#330099">Thanks </font></strong></div> <p><strong><font color="#330099">Tapan Bhatt</font></strong></p> <div><br> </div> <div><span class="gmail_quote">On 11/7/06, <b class="gmail_sendername">Dean Jesson</b> <<a href="mailto:[email protected]">[email protected]</a>> wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I would like to know how in Jtapi one is supposed to end a consultation call and reconnect to the held party. The use case is as follows. <br><br>I have an application which creates a consultation call via Jtapi and then wants to end it:<br>- terminal A is in a normal call with B and they are talking;<br>- then terminal A makes a consultation call to C and B goes on hold; <br>- because C does not answer, terminal A would now like to reconnect to B, meaning that the consultation call should end and the call to B should be taken off hold so that A and B are once again connected in a normal call. <br><br>How can one achieve the reconnect in Jtapi? The required function is a transition from a consultation call to a normal call with the party which was on hold during the consultation.<br><br>Is it sufficient to call disconnect() on A's Connection to the call to C? or will this leave B still on hold? If B does get left on hold, can I simply take B explicitly off hold by calling unhold() on the CallControlTerminalConnection on A's Connection to the A/B call? <br><br>I have my doubts about this disconnect()+unhold() combination for the following reason. If I do try disconnect() then unhold() my Jtapi implementation will send a CSTA-ClearConnection request to the switch followed by a CSTA-RetrieveCall. I have already tested the effect of this on the switch and it does not lead to the desired behaviour. The desired switch behaviour can only be triggered by sending a CSTA-ReconnectCall (to replace both CSTA-ClearConnection and CSTA-RetrieveCall). <br><br>I conclude then that for my switch, reconnect cannot be brought about by disconnect()+unhold(), because a special protocol command has to be sent to the switch as early as the disconnect() stage. If any implementation of Jtapi can be written which can work with this switch, the sequence of Jtapi commands required must therefore be different. Instead, I see two alternatives: <br>1. disconnect() must be sufficient to perform the entire reconnect operation, and that the Jtapi implementation will have to be intelligent enough to recognise that disconnect() is being called on a consultation connection and in this case send a CSTA-ReconnectCall to the switch instead of a CSTA-ClearConnection; <br>2. some other Jtapi interface function should be used, which explicitly requests a reconnect.<br><br>The problem with (1) is that the function does more than the user has asked for. This may mean a loss of functionality with other switch types which do support two-stage reconnect. The problem with (2) is that it - so far as I know - is not part of the Jtapi standard. <br><br>So, does anyone know what the intended sequence of Jtapi commands is for performing the reconnect?<br><br>Thanks,<br>Dean<br><br>===========================================================================<br>To unsubscribe, send email to <a href="mailto:[email protected]">[email protected]</a> and include in the body<br>of the message "signoff JTAPI-INTEREST". For general help, send email to<br><a href="mailto:[email protected]">[email protected] </a> and include in the body of the message "help".<br></blockquote></div><br> =========================================================================== To unsubscribe, send email to [email protected] and include in the body of the message "signoff JTAPI-INTEREST". For general help, send email to [email protected] and include in the body of the message "help". ------=_Part_3334_29600856.1162899407729--