Problems with my call model
- From: "Beat Kiener" <Beat Kiener@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 2 Oct 2005 14:05:02 -0700
Hello
I have some problems with my TAPI implementation.
In frame of my diploma thesis, i integrate TAPI into the software of my
employer (i work for a software house)
Now, i’m using VB.NET and TAPI3.x with the VS.NET generated Interop.dll. The
TAPI implementation is used with a PBX and during the implementation I use a
Siemes Hicom 150 PBX.
The following functionality has to be implemented:
- The software has to initialize calls
- Indicate incoming calls with their number
- No others call controls
My TAPI implementation functioned well, but there are still some problems
with the call handling.
It is possible, that a telephone has several calls openly (conferences,
knocking calls as offering call during a connected call, redirecting a call).
I implemented a call model, which note the call states an call informations
about all calls from his phone device. Because I found no other possibility,
to asign informations to the correct call. Sample: I’m connected with the
phonenumber 30 and a person with number 40 tries to call me. The call from
number 40 signals as knocking call on my phone and the TAPI signals an
offering message and many InfoEvents about the call. When i don’t answer the
call and the call terminate by phone 40, a TAPI disconnect message arrives
from TAPI to me.
Now I must be able to assign the disconnect message to a call.
A simply version of these implementation functioned. But, in special cases,
such as conference and redirecting calls, the call model doesn’t work
correctly.
Is there another solution to generic transferable to other PBX’s.
My Questions:
Is there a consideration error? It is necessary to have the phonenumber of
the current connected call in the application on remove the phonenumber when
the call disconnected.
Is this problem connected with the VS.NET interop.dll problem?
I tried to use the TAPI Wrapper of Helen Warn. But I received an error
during initialize her wrapper. Can this wrapper also be also for PBX's?
My testing PBX (Siemens Hicom 150E Office) send during a redirecting no
RelatedCallID information. Are there no absolute essentials for the ID for
identification?
Is it better to use Version TAPI2.x to implement this?
I read much and argue for 3 months with it. I do not get ahead now.
I hope of some helpful answers
Many thanks and best regards
Beat Kiener
kiener at glauxsoft dot com
.
- Follow-Ups:
- Re: Problems with my call model
- From: Andreas Marschall [MVP TAPI]
- Re: Problems with my call model
- From: Matthias Moetje
- Re: Problems with my call model
- From: Helen Warn
- Re: Problems with my call model
- Prev by Date: Re: Any API other than MIcrosoft TAPI
- Next by Date: Re: Any API other than MIcrosoft TAPI
- Previous by thread: Re: Siemens TAPI 120 - CSTA
- Next by thread: Re: Problems with my call model
- Index(es):
Relevant Pages
|
