Call drop problem

[michal]

Hello
I try to write TAPI handling in delphi. Everything works correct but i have on
problem. When i want to disconnect external call(call not from our interna
net
nothing happens, phone is still ringing

lineDrop returned x1038b and lineDeallocateCall returned SUCCESS

But when i do the same for internal call everything is ok and call is dropped
Maybe this is some configuration problem? But i dont know what to set

I also try do it on TapiBroswer2 and some sample program for tapi 3.0 but th
effect was the same as in delphi code. I use CallBridge TU V2 R3.0.
optiH324.TSP and phisical phone siemens optipoint 500 standard

Some logs from TB2:
15:36.58.632 : Calling lineGetCallStatu
hCall=x103e
lpCallStatus=x5b2fa
15:36.58.634 : lineGetCallStatus returned SUCCES
LINECALLSTATU
dwTotalSize=x100
dwNeededSize=x3
dwUsedSize=x3
dwCallState=x2, OFFERIN
dwCallPrivilege=x4, OWNE
dwCallFeatures=x80000004, ANSWER SETCALLDAT
tStateEntryTime[0]=x807d
tStateEntryTime[1]=x17000
tStateEntryTime[2]=x24000
tStateEntryTime[3]=x206003
15:37.1.984 : Calling lineDro
hCall=x103e
lpsUserUserInfo=xce6e
dwSize=x1
15:37.1.986 : lineDrop returned x1038
15:37.2.28 : received LINE_REPL
device=x
cbInst=x
param1=x1038b
param2=x0
param3=x0
15:37.7.768 : Calling lineDeallocateCal
hCall=x103e
15:37.8.961 : lineDeallocateCall returned SUCCESS

[Andreas Marschall [exMVP TAPI]]

I try to write TAPI handling in delphi. Everything works correct but i have one
problem. When i want to disconnect external call(call not from our internal
net)
nothing happens, phone is still ringing.
lineDrop returned x1038b and lineDeallocateCall returned SUCCESS.
But when i do the same for internal call everything is ok and call is dropped.
Maybe this is some configuration problem? But i dont know what to set.
I also try do it on TapiBroswer2 and some sample program for tapi 3.0 but the
effect was the same as in delphi code. I use CallBridge TU V2 R3.0.0
optiH324.TSP and phisical phone siemens optipoint 500 standard.
Some logs from TB2:.

michal,
so you are trying to reject an incoming offering call, correct?
It os working for internal incoming and not working for external incoming, correct?
I guess the TB20.log shows the latter scenario since there are no LINE_CALLSTATE messages at all shown, correct?

What HiPath PBX are you using (exact model and software version)?

In CallBridge configuration: which key is configured for call release?
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++ 2003-2008
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
http://www.I-B-A-M.de/Andreas_Marschall's_Toto_Tools.htm
* Please post all messages and replies to the group / forum so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.

[michal]

Andreas Marschall [exMVP TAPI] wrote on 08/30/2013 07:03 ET

Am Donnerstag, 29. August 2013 12:11:24 UTC+2 schrieb michal

Post by michal
I try to write TAPI handling in delphi. Everything works correct but i hav
on
problem. When i want to disconnect external call(call not from our interna
net
nothing happens, phone is still ringing
lineDrop returned x1038b and lineDeallocateCall returned SUCCESS
But when i do the same for internal call everything is ok and call i

dropped

Post by michal
Maybe this is some configuration problem? But i dont know what to set
I also try do it on TapiBroswer2 and some sample program for tapi 3.0 but th
effect was the same as in delphi code. I use CallBridge TU V2 R3.0.
optiH324.TSP and phisical phone siemens optipoint 500 standard

michal
so you are trying to reject an incoming offering call, correct
It os working for internal incoming and not working for external incoming
correct
I guess the TB20.log shows the latter scenario since there are n
LINE_CALLSTATE messages at all shown, correct
What HiPath PBX are you using (exact model and software version)
In CallBridge configuration: which key is configured for call release
Best Regard
Andreas Marschal
Microsoft MVP for TAPI / Windows SDK / Visual C++ 2003-200
TAPI / TSP Developer and Teste
My TAPI and TSPI FAQ
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.ht
My Toto® Tools (a collection of free, mostly TAPI related tools)
http://www.I-B-A-M.de/Andreas_Marschall's_Toto_Tools.ht
* Please post all messages and replies to the group / forum so all ma
* benefit from the discussion. Private mail is usually not replied to
* This posting is provided "AS IS" with no warranties, and confers n
rights

thanks for repl

"so you are trying to reject an incoming offering call, correct?
ye

"It os working for internal incoming and not working for external incoming
correct?
yes and i make another test and i notice that i can't drop call when it i
redirected. When i call direct to my phone i can drop a call but when i cal
from phone A to B and B redirect call to my phone i can't drop the call. But
can answer it and that is realy strange. Similar situation is for externa
incoming..

"What HiPath PBX are you using (exact model and software version)?
siemens hipath 3500 but unfortunatly i don't know the software versio
and also try it on Avaya IP Office 50

"In CallBridge configuration: which key is configured for cal
release?
Where i can check it
Here is my configuration
http://img703.imageshack.us/img703/6122/37e4.pn

"I guess the TB20.log shows the latter scenario since there are n
LINE_CALLSTATE messages at all shown, correct?
there was LINE_CALLSTATE. I can paste full log if it is necessary

15:36.49.519 : received LINE_CALLSTAT
device=x103e
cbInst=x
param1=x2, OFFERIN
param2=x0
param3=x4, OWNE
lineGetCallInfo returned x0, hLine=x1014
15:36.49.532 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x100, ORIGI
param2=x0
param3=x0
15:36.49.535 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x200, REASO
param2=x0
param3=x0
15:36.49.537 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x8000, CALLERI
param2=x0
param3=x0
15:36.49.540 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x40, CALLI
param2=x0
param3=x0
15:36.49.542 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x80, RELATEDCALLI
param2=x0
param3=x0
15:36.49.577 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x100000, DISPLA
param2=x0
param3=x0
15:36.49.632 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x100000, DISPLA
param2=x0
param3=x0
15:36.49.634 : received LINE_CALLINF
device=x103e
cbInst=x
param1=x100000, DISPLA
param2=x0
param3=x0,

[michal]

michal wrote on 08/29/2013 06:11 ET

Post by michal
Hello
I try to write TAPI handling in delphi. Everything works correct but i hav

on

Post by michal
problem. When i want to disconnect external call(call not from our interna
net) nothing happens, phone is still ringing
lineDrop returned x1038b and lineDeallocateCall returned SUCCESS
But when i do the same for internal call everything is ok and call is dropped
Maybe this is some configuration problem? But i dont know what to set
I also try do it on TapiBroswer2 and some sample program for tapi 3.0 but th
effect was the same as in delphi code. I use CallBridge TU V2 R3.0.
optiH324.TSP and phisical phone siemens optipoint 500 standard
15:36.58.632 : Calling lineGetCallStatu
hCall=x103e
lpCallStatus=x5b2fa
15:36.58.634 : lineGetCallStatus returned SUCCES
LINECALLSTATU
dwTotalSize=x100
dwNeededSize=x3
dwUsedSize=x3
dwCallState=x2, OFFERIN
dwCallPrivilege=x4, OWNE
dwCallFeatures=x80000004, ANSWER SETCALLDAT
tStateEntryTime[0]=x807d
tStateEntryTime[1]=x17000
tStateEntryTime[2]=x24000
tStateEntryTime[3]=x206003
15:37.1.984 : Calling lineDro
hCall=x103e
lpsUserUserInfo=xce6e
dwSize=x1
15:37.1.986 : lineDrop returned x1038
15:37.2.28 : received LINE_REPL
device=x
cbInst=x
param1=x1038b
param2=x0
param3=x0
15:37.7.768 : Calling lineDeallocateCal
hCall=x103e
15:37.8.961 : lineDeallocateCall returned SUCCES

there is no solution for this issue?

[Andreas Marschall [exMVP TAPI]]

Post by michal

Some logs from TB2:.
dwCallState=x2, OFFERING
dwCallFeatures=x80000004, ANSWER SETCALLDATA

there is no solution for this issue?

michael, sorry for the delayed answer.

Strictly speaking, the TSP doesn't set the LINECALLFEATURE_DROP in this case, so there might be a reason for this...
You want to check if the feature is set in a scenario where call rejections works.
In general I name it a TSP bug if the TSPs indicates success asynchronously (like seen in TB20.log) on a lineDrop() but actually doesn't drop/reject the call.
So you may want to report the issue to Siemens / Unify.

For a solution you may want to try another of their TSPs: HiPath TAPI 120.
It has an IP connection to the PBX and using CSTA protocol internally.
(AFAIK) it does support lineDrop() on offering calls.
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++ 2003-2008
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
http://www.I-B-A-M.de/Andreas_Marschall's_Toto_Tools.htm
* Please post all messages and replies to the group / forum so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.