VoiceGuide IVR Software Main Page
Jump to content

Voice Modem Transfer Failing On Xp

Recommended Posts

This past weekend I moved my network card and my modem card from a dying win98 machine to a dell XP machine. At the same time I upgraded to v 4.9. Now I cannot get the modem to transfer calls, even though this was successful on the old machine using 4.8. I understand from the many posts that a dialogic card is better for transfers, but I have been using the same voice modem on the phone line for the past year successfully. I am looking into a dialogic card, but need to get this system up and running while I order a dialogic card.

 

What may have changed between v 4.8 and 4.9 or win98 and XP to make this not work properly now? Below is my event log. Any assistance to get this working is appreciated.

 

 

38781 1 tapie callstate OFFERING 66407 0 4

38781 1 tapie ring 1

38781 1 Answer the call

38781 1 lineAnswer(66407) => 66424

38781 1 tapie callstate ACCEPTED 66407 0 0

44171 1 tapi Reply 66424 0

44171 1 tapie callstate CONNECTED 66407,0,0

44171 1 WorkingModeTAPI=

44171 1 WorkingModeScript=

44171 1 Inband detection not enabled

44171 1 [Opening Greeting] Playing

44171 1 [Opening Greeting] Playing (C:\Phone system\QTS Main Greeting.wav)

44250 1 PlaySoundStart ok [C:\Phone system\QTS Main Greeting.wav]

44250 1 RunModule PLAY end

50109 1 tapie monitordigits 56 2

50109 1 LsPlayMsg [8]

52484 1 PlaySoundStop ok

52921 1 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

52921 1 [Lori Christianson] Blind Transfer to 769-0118 (Generate)

52921 1 tapic lineGenerateDigits(66407,!3) => 0

53984 1 tapie generate LINEGENERATETERM_DONE

55078 1 LsXferStart EV_TAPI_GENERATE

56171 1 LsXferPlayVts EV_HOOKFLASHFINISHED

56171 1 tapic lineGenerateDigits(66407,769-0118) => 0

57078 1 tapie generate LINEGENERATETERM_CANCEL

58156 1 LsXferPlayVts EV_TAPI_GENERATE

59250 1 LsXferPlayVts EV_TIMEOUT_HANGUP

59250 1 PlaySoundStop ok

59250 1 HangupCall called from []

59250 1 Hanging up call...

59265 1 PlaySoundStop ok

59265 1 fnHangupCall end

59500 1 tapie callstate DISCONNECTED 66407,1,0

59500 1 LsAwaitingCalls EV_REMOTEPARTY_DISCONNECT

59500 1 PlaySoundStop ok

59500 1 HangupCall called from []

59515 1 Hanging up call...

59515 1 PlaySoundStop ok

59515 1 fnHangupCall end

59515 1 tapie callstate IDLE 66407 0 0

59531 1 WorkingMode@Idle=

59531 1 set EV_TIMEOUT_TIMETOREINITLINE 2

59531 1 tapi Reply 66305 0

59546 1 tapi Reply 66202 0

60531 1 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

60531 1 ReinitTelephony due to IDLE start

60531 1 tapic lineDeallocateCall(MainCall:66407) 0

61453 1 lineOpen(1) => 0

61453 1 Waiting for a call...

61453 1 lineOpen(1)LineHandle=66185

Share this post


Link to post

There have been some reports of some modems behaving differently depending on what version of Windows they are used under - different versions of Windows may use different entries from the modem's ".inf" file and therefore may end us sending slightly different AT commands to the modem - which it looks like in some cases ends up affecting the modem's hookflash length...

 

Apparently some users have been able to use the "Country/Region" setting for the Location that is used (see Phone and Modem options applet in Control Panel - Dialing Rules tab) to change the length of hookflash as well - there have been claims that selecting different countries can select different hookflash lengths on some modems...

 

Call transfers are very hit and (mostly) miss with voice modems... Dialogic cards are highly recommended...

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×