| Way2call telephony device is your ultimate telephony integration solution! |
Detecting hangup |
Post Reply 
|
| Author | |
doronsh 
Way2call 
Joined: Mar 16 2009 Status: Offline Points: 95 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Detecting hangupPosted: Nov 16 2009 at 1:20pm |
|
The Hi-Phone TAPI drivers detects the call disconnect by four ways. 1. Loop current drop 2. Disconnect tone 3. Silence for a define period of time. 4. Detection of defined tone From the report you have sent itâ?Ts not clear what the scenario is. To check if itâ?Ts an issue with then Hi-Phone, or your application, please download the Hi-Phone test application from www.way2call.com >>> developers This application presents all the commands and events, as detect by the Hi-Phone. If you donâ?Tt see the loop current drop or disconnect tone detected, please send an email to support@way2call.com and we can check it by login in to your PC. |
|
 |
|
|
jconde
Newbie 
Joined: Oct 12 2009 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: Nov 16 2009 at 11:02am |
|
It's been a couple of weeks again, just wondering if you've had a chance to look into this problem yet. It would be nice if this box could eventually work as it's supposed to.
John |
|
|
|
|
jconde
Newbie
Joined: Oct 12 2009 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 29 2009 at 4:10pm |
|
Thanks for the reply but that is how I've had it setup, as I mentioned in my first message.
I just checked again that the setup was correct, as you specified, and called in. Below is the log it produced. 201-210 is it picking up the phone and talking to me. 211-212 is me talking and then hanging up. The rest is the device listening to the beeping. My event handler never detects a TE_CALLSTATE event with a value of CS_DISCONNECTED. I am detecting, and handling, CS_OFFERING and CS_CONNECTED. Should a CS_DISCONNECTED been sent when it detected the warning tone? Am I listening for the wrong event? Any ideas? John 201 16:51:27:687 [1016] » Dev#0 Command: Start Analysis 202 16:51:27:718 [1228] New PCM Buffer! 203 16:51:27:734 [1228] New PCM Buffer! 204 16:51:27:937 [1228] New PCM Buffer! 205 16:51:28:296 [1228] New PCM Buffer! 206 16:51:28:687 [1228] New PCM Buffer! 207 16:51:29:046 [1228] New PCM Buffer! 208 16:51:29:390 [1228] New PCM Buffer! 209 16:51:29:750 [1228] New PCM Buffer! 210 16:51:29:937 [1228] New PCM Buffer! 211 16:51:32:718 [1016] » Dev#0 Event: Call answered: Voice detected. ExData 0x0000, TID: 0x0204 212 16:51:32:718 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line 213 16:51:46:343 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 214 16:51:47:890 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 215 16:51:49:359 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 216 16:51:50:890 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 217 16:51:52:375 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 218 16:51:53:906 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 219 16:51:54:984 [1016] » Dev#0 Event: Call answered: Speech detected. ExData 0x0000, TID: 0x0204 220 16:51:54:984 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line 221 16:51:55:375 [1016] » Dev#0 Event: Warning tone detected, Operator Intervening PABX. ExData 0x0000, TID: 0x0204 222 16:51:56:406 [1016] » Dev#0 Event: Call answered: Speech detected. ExData 0x0000, TID: 0x0204 223 16:51:56:406 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line 224 16:51:58:765 [1016] » Dev#0 Event: Call answered: Speech detected. ExData 0x0000, TID: 0x0204 225 16:51:58:765 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line 226 16:52:01:125 [1016] » Dev#0 Event: Call answered: Speech detected. ExData 0x0000, TID: 0x0204 227 16:52:01:125 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line 228 16:52:03:500 [1016] » Dev#0 Event: Call answered: Speech detected. ExData 0x0000, TID: 0x0204 229 16:52:03:500 [1016] » Dev#0 Command: Switch: Phone - Audio Stream - Line |
|
|
|
|
doronsh
Way2call
Joined: Mar 16 2009 Status: Offline Points: 95 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 29 2009 at 11:46am |
|
The wave you have sent is a standard 480,620 Hz .25 second reorder, which should be detected by the Hi-Phone. When using TAPI applications, you should setup the disconnect tone option. The default is loop current drop detection. Please go to start menu >>> programs >>> Way2call multiple Hi-Phone device drivers >>> Way2call TAPI setup Configure Advanced Check the disconnect tone fast busy OK OK Close The Hi-Phone is setup to detect fast busy as a disconnect tone |
|
|
|
|
jconde
Newbie
Joined: Oct 12 2009 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 29 2009 at 9:05am |
|
I haven't heard from you since I sent you the wav file, has there been any progress on detecting the hangup (reorder) tones?
John |
|
|
|
|
doronsh
Way2call
Joined: Mar 16 2009 Status: Offline Points: 95 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 13 2009 at 9:22am |
|
Please email the recorded disconnect tone wave files to support@way2call.com Make sure it is recorded at 8 kHz 16 bit mono. You can use the way2call test application for recording |
|
|
|
|
jconde
Newbie
Joined: Oct 12 2009 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 13 2009 at 8:54am |
|
Thanks for the quick reply, unfortunately the beta code seems to have the same problem. Would it help if I emailed you a wave of the tones I'm getting?
John |
|
|
|
|
doronsh
Way2call
Joined: Mar 16 2009 Status: Offline Points: 95 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 12 2009 at 11:03am |
|
There are some tone detection issues with this TAPI version (2.00.95) Please try to use the beta drivers from www.way2call.com >>> developers (2.01.02 beta) |
|
|
|
|
jconde
Newbie
Joined: Oct 12 2009 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: Oct 12 2009 at 10:47am |
|
I'm using a way2call USB box with a C++ program accessing it through TAPI. Everything seems to be working fine except that the user hang-up is never detected. The phone service is through a company called Lingo, the box they provided is a Linksys SPA-2102. It's reorder tone is 480,620 Hz .25 second on and off. I've actually recorded the beeps and verified this is being produced. I've tried both the "reorder" setting and the custom setting in the TAPI setup but it still never detects the hangup. I've actually watched the log while hanging up to verify it's not just my software missing the event. I've copied my driver information below in case that helps.
Am I missing something obvious? John Conde Way2call Drivers Information: Package Version: 2.00.95 OS version: 5.1.2600 Service Pack 3 Device Information: 1. Hi-Phone Desktop USB 000872 Firmware Version: 4.02.33 P/N: HD00USGR01 S/N: 1010-07-000872 Software Components: File: w2cUSBM.dll Description: Way2call Multiple Hi-Phone Devices DLL Version: 1.3.6.9 Build: b009 File: ScTspML.tsp Description: Way2call Multiple Hi-Phone Devices TSP Version: 2.00.88 Build: 0 File: w2cMultiOcx.ocx Description: Way2call Multiple Hi-Phone Devices OCX Version: 1.0.0.4 Build: 0 File: TestWiz.exe Description: Way2Call Multiple Hi-Phone Devices Test Wizard Version: 2.00.34 Build: 0 File: w2cMdSound.exe Description: Way2call Multiple Devices As Sound Cards Version: 1.0.0.7 Build: 0 File: scwiz32.exe Description: Way2Call Multiple Hi-Phone Devices PBX Wizard Version: 2.00.34 Build: 0 File: w2cTspSetup.exe Description: Way2call TAPI Setup Version: 1.0.0.2 Build: 0 File: \drivers\ScIPTsa.sys Not required - For RS232 devices. File: w2cRS232Wave.drv Not required - For RS232 devices. File: w2cUsb.dll Description: Hi-Phone User Mode Device Driver Version: 2.0.9.2 Build: b0001 File: ml_setup.exe Description: Way2call Multiple Hi-Phone Devices Drivers installer Version: 2.0.0.42 Build: b001 File: w2cMultiInfo.exe Description: Way2call drivers infromation Version: 1.0.0.4 Build: 0 Audio IN devices: 0. Hi-Phone Desktop USB Aux 1. SoundMAX Digital Audio 2. Hi-Phone Desktop USB Audio OUT devices: 0. Hi-Phone Desktop USB 1. SoundMAX Digital Audio |
|
|
|
Topic Options|
Post Reply
|
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.120 seconds.