Re: transfer a call (tapi 3)

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Andreas,

Thank you for detailes description.

- lineAnswer() this incoming call

Seems I do something wrong. lineAnswer returns LINEERR_NOTOWNER. But I have called lineOpen with the OWNNER | MONITOR parameter. I double checked it. This is the generated log:

8:3.2.609 : Calling lineInitializeEx
lphLineApp=x2729d8
hInstance=x1000000
lpfnCallback=x10158df
lpszFriendlyAppName=x6f500
lpdwNumDevs=x6f4d8
lpdwAPIVersion=x6f56c
->dwAPIVersion=x20000
lpInitExParams=x6f4c0
->dwOptions=x3
8:3.2.609 : lineInitializeEx returned SUCCESS
num line devs = 9
8:3.25.812 : Calling lineGetDevCaps
hLineApp=x800003ff
dwDeviceID=x8
APIVersion=x20000
dwExtVersion=x0
lpLineDevCaps=x273fd8
8:3.25.812 : lineGetDevCaps returned SUCCESS
LINEDEVCAPS
dwTotalSize=x1000
dwNeededSize=x148
dwUsedSize=x148
dwProviderInfoSize=x6
dwProviderInfoOffset=xfc
79617641 xxxx0061 xxxxxxxx xxxxxxxx Avaya.
dwPermanentLineID=x4e42b120
dwLineNameSize=x15
dwLineNameOffset=x108
4f205049 63696666 68502065 3a656e6f IP Office Phone:
30313720 xxxxxx00 xxxxxxxx xxxxxxxx 710.
dwStringFormat=x1, ASCII
dwAddressModes=x1, ADDRESSID
dwNumAddresses=x1
dwBearerModes=x3, VOICE SPEECH
dwMediaModes=x14, INTERACTIVEVOICE DATAMODEM
dwGenerateToneModes=x8, BEEP
dwGenerateDigitModes=x2, DTMF
dwMonitorToneMaxNumFreq=x1
dwMonitorToneMaxNumEntries=x1
dwMonitorDigitModes=x6, DTMF DTMFEND
dwDevCapFlags=x1c0, DIALBILLING DIALQUIET DIALDIALTONE
dwMaxNumActiveCalls=x9
dwAnswerMode=x1, NONE
dwRingModes=x1
dwLineStates=x14406ce, RINGING CONNECTED DISCONNECTED
INSERVICE OUTOFSERVICE OPEN CLOSE REINIT TRANSLATECHANGE
REMOVED
dwUUIAnswerSize=x64
dwUUIMakeCallSize=x64
dwUUIDropSize=x64
dwUUISendUserUserInfoSize=x64
dwUUICallInfoSize=x64
dwLineFeatures=x9, DEVSPECIFIC MAKECALL
dwDeviceClassesSize=xb
dwDeviceClassesOffset=x132
xxxx6174 xxxxxxxx xxxxxxxx xxxxxxxx ta
6c2f6970 00656e69 xxxxxx00 xxxxxxxx pi/line..
8:3.54.875 : Calling lineOpen
hLineApp=x800003ff
dwDeviceID=x8
lphLine=x272af0
APIVersion=x20000
dwExtVersion=x0
dwCallbackInstance=x0
dwPrivileges=x6
dwMediaModes=x10
lpCallParams=x0
8:3.54.875 : lineOpen returned SUCCESS
8:4.27.31 : received LINE_APPNEWCALL
device=x10351
cbInst=x0
param1=x0,
param2=x1001c,
param3=x2, MONITOR
8:4.27.31 : received LINE_CALLSTATE
device=x1001c
cbInst=x0
param1=x2, OFFERING
param2=x0,
param3=x0,
8:4.27.31 : received LINE_CALLINFO
device=x1001c
cbInst=x0
param1=x11c35e, DEVSPECIFIC BEARERMODE RATE MEDIAMODE
CALLID ORIGIN REASON TRUNK CALLERID CALLEDID DISPLAY
param2=x0,
param3=x0,
8:4.29.328 : received LINE_CALLSTATE
device=x1001c
cbInst=x0
param1=x4000, DISCONNECTED
param2=x1, NORMAL
param3=x0,
8:4.29.328 : received LINE_CALLSTATE
device=x1001c
cbInst=x0
param1=x1, IDLE
param2=x0,
param3=x0,
8:4.29.328 : lineGetCallStatus returned SUCCESS
Call x1001c deallocated on IDLE
8:4.41.250 : received LINE_APPNEWCALL
device=x10351
cbInst=x0
param1=x0,
param2=x101b7,
param3=x2, MONITOR
8:4.41.250 : received LINE_CALLSTATE
device=x101b7
cbInst=x0
param1=x2, OFFERING
param2=x0,
param3=x0,
8:4.41.250 : received LINE_CALLINFO
device=x101b7
cbInst=x0
param1=x11c35e, DEVSPECIFIC BEARERMODE RATE MEDIAMODE
CALLID ORIGIN REASON TRUNK CALLERID CALLEDID DISPLAY
param2=x0,
param3=x0,
8:4.53.578 : Calling lineAnswer
hCall=x101b7
lpsUserUserInfo=x6f478
dwSize=x12
8:4.53.578 : lineAnswer returned LINEERR_NOTOWNER
8:5.4.437 : received LINE_CALLSTATE
device=x101b7
cbInst=x0
param1=x4000, DISCONNECTED
param2=x1, NORMAL
param3=x0,
8:5.4.437 : received LINE_CALLSTATE
device=x101b7
cbInst=x0
param1=x1, IDLE
param2=x0,
param3=x0,
8:5.4.437 : lineGetCallStatus returned SUCCESS
Call x101b7 deallocated on IDLE

--
rgds, Wilfried
Microsoft MapPoint MVP
.

Relevant Pages

  • Re: What is the typical flow when cancel transfer?
    ... Is it strictly defined by TAPI? ... 19:33.33.341: Calling lineInitializeEx ... 19:33.33.341: lineInitializeEx returned SUCCESS ... Call x10055 deallocated on IDLE ...
    (microsoft.public.win32.programmer.tapi)
  • Re: lineDrop - state does not return to idle...
    ... Calling lineInitialize ... lineInitialize returned SUCCESS ... Calling lineMakeCall ... behaves nicely and transitions to IDLE. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: Long delay before LINECALLSTATE_IDLE (Cisco CM 4)
    ... in this case (given that no other TAPI applications are active and holding a ... and IDLE events at the end of the trace. ... 17:44.48.234: Calling lineInitialize ... 17:44.48.234: lineInitialize returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)
  • Long delay before LINECALLSTATE_IDLE (Cisco CM 4)
    ... If an invalid extension number is used in a lineMakeCall to a Cisco Call ... IDLE events at the end of the trace. ... 17:44.48.234: Calling lineInitialize ... 17:44.48.234: lineInitialize returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)
  • Re: What does your PBX signal when you pickup a phone handset?
    ... 21:22.44.156: Calling lineInitializeEx ... 21:22.47.762: lineInitializeEx returned SUCCESS ... dwCallerIDFlags=x6c, NAME ADDRESS UNKNOWN UNAVAIL ... 21:24.36.858: lineGetLineDevStatus returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)