Re: tapi3 program receives call events, but 3% of time sees no call data... continued
From: Andreas Marschall [MVP TAPI] (Andreas.Marschall_at_I-B-A-M.de)
Date: 06/16/04
- Next message: Andreas Marschall [MVP TAPI]: "Re: Call Center application in Visual Basic"
- Previous message: Andreas Marschall [MVP TAPI]: "Re: How to transfer call in Dialogic D/4PCI"
- In reply to: Justin: "Re: tapi3 program receives call events, but 3% of time sees no call data... continued"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Jun 2004 17:35:22 +0200
"Justin" <justinh@xacom.com.au> schrieb im Newsbeitrag
news:79d6eaa0.0406030308.680c6de5@posting.google.com...
> I've upgraded my windows sdk and the updates where significant. I've
> therefore made a new version of my program and will test it tomorrow.
Justin, sorry for the late reply.
What was the result of this test?
>
> However, duplicating the error where call data is missing is not
> practical when I need to manually query the data. The call volume is
> too high and I can't manually query the calls fast enough.
> Is there a method of automation I can use?
None that I'm aware of.
>
> To solidify my understanding of the call process here are some
> questions:
> If the tapi3 call volume is high (eg. more than 5 calls per second),
> is it possible that the ITCallInfo data associated with a call event
> expires. ie. If 5 separate call events are relayed by the tapi server
> in quick succession, and my program queries the 3rd call event for
> it's ITCallInfo data after the 5th call event has been relayed by the
> tapi server, then would the ITCallInfo data for the 3rd call event
> still be available?
Yes, this should be the case.
But it depends primarily on the robustness of the TSP.
I regard the TAPISRV and the TAPI2 part of the OS a very stable. TAPI3 works
on top of it.
So if you want to exclude TAPI3 from the equation for testing you might want
to consider writing a small TAPI2 test application.
I guess it is not possible to use another PBX / TSP for testing?
>
> The reason I ask is that I assume that the call data relayed via the
> tapi server would not sit in the tapi server indefinitely. ie. If a
> program registers for call events, how long after the call event has
> been relayed does the call data stay available?
It should be available as long as any TAPI app has any reference to that call.
But again this depends primarily on the robustness of the TSP.
>
> Hmm, perhaps the answer to my last question is that the tapi call data
> is only extracted from the Symposium PABX at the request of the tapi
> server relaying a request from my program. In which case the call data
> availability of previously triggered call events would depend upon
> storage of call data within the Symposium PABX and not the tapi
> server. Does this sound correct?
I don't know the internals of the call data storage of that TSP / PBX
combination.
You should contact the manufacturer on this, only they will know.
For comparison: I've developed a 3rd party TSP for a PBX where the call data
is stored solely in the TSP.
The PBX is not required for this. Call data is available on every TAPI line
device / address that has a reference to this call at least until the call
clears within the PBX from every station that has a TAPI reference to this
call. After this call clearing the call data is disposed in the TSP after some
time.
-- Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK TAPI / TSP Developer and Tester http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm * Please post all messages and replies to the newsgroup 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.
- Next message: Andreas Marschall [MVP TAPI]: "Re: Call Center application in Visual Basic"
- Previous message: Andreas Marschall [MVP TAPI]: "Re: How to transfer call in Dialogic D/4PCI"
- In reply to: Justin: "Re: tapi3 program receives call events, but 3% of time sees no call data... continued"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|