Making more alls on one card

Discussion:

(too old to reply)

Gerhard Gaugusch

2005-12-13 09:43:01 UTC

Hi!

I am trying to make more than one call with my Eicon Server Card. But I have
some problems. There is no problem with 2 calls.
But as soon as I start my 3th or 4th call there is an error in CAPI2032.dll.
Location 0x100025B9. In the call stack there are no functions before listed.
So I think the error comes from the driver (So it must be an IND or CONF
message). Is this guess correct? (The crash doesn't happen emedatly. It
takes a few seconds)

I have contacted Eicon and they are trying to help me. But as time goes by I
have no time to wait for an answer from them.

The application crashes with these lines in the logfile from eicon tracer:
---
INFO IND AppID 0x0003 MsgNr 0x00f7 PLCI: 0x00000302
Info number: 0x007e (Q.931 info element)
Information type: 0x7e (User User Info)
Info element (0x8): 31 36 CA D7 58 E2 67 72

10:19:39.576 C 4 22:1597:283 - SIG-R(014) 08 01 9F 20 7E 08 31 36 CA D7 58
E2 67 72
Q.931 CR9f USER_INFO
User User Info 31 36 ca d7 58 e2 67 72
10:19:39.606 X 7 CAPI20_GET(015)
0x0000 03 00 08 82 F8 00 02 03 00 00 20 80 00 ....x..... ..
---
INFO IND AppID 0x0003 MsgNr 0x00f8 PLCI: 0x00000302
Info number: 0x8020 (Q.931 network event)
Event: 0x20 (user information)
Info element (0x0):

10:19:39.606 X 7 CAPI20_PUT(012)
0x0000 03 00 08 83 F7 00 02 03 00 00 ....w.....
---
INFO RESP AppID 0x0003 MsgNr 0x00f7 PLCI: 0x00000302

10:19:39.616 X 7 CAPI20_PUT(012)
0x0000 03 00 08 83 F8 00 02 03 00 00 ....x.....
---
INFO RESP AppID 0x0003 MsgNr 0x00f8 PLCI: 0x00000302

10:19:43.081 D 3 22:1600:780 - D-R(004) 02 81 01 6F
10:19:43.081 D 3 22:1600:781 - D-X(004) 02 81 01 77
--
10:19:49.090 D 4 22:1606:781 - D-R(004) 02 81 01 2F
10:19:49.090 D 4 22:1606:781 - D-X(004) 02 81 01 37
10:19:53.075 D 3 22:1610:762 - D-X(004) 00 81 01 77
10:19:53.086 D 3 22:1610:774 - D-R(004) 00 81 01 6F
--
10:19:59.104 D 4 22:1616:780 - D-R(004) 02 81 01 2F
10:19:59.104 D 4 22:1616:781 - D-X(004) 02 81 01 37
10:20:02.108 D 3 22:1619:781 - D-R(004) 02 81 01 6F
10:20:02.108 D 3 22:1619:781 - D-X(004) 02 81 01 77
--
10:20:09.099 D 4 22:1626:762 - D-X(004) 00 81 01 37
10:20:09.119 D 4 22:1626:773 - D-R(004) 00 81 01 2F
10:20:12.123 D 3 22:1629:781 - D-R(004) 02 81 01 6F
10:20:12.133 D 3 22:1629:781 - D-X(004) 02 81 01 77
10:20:12.133 D 3 22:1629:782 - D-X(004) 00 81 01 77
10:20:12.143 D 3 22:1629:800 - D-R(004) 00 81 01 6F
--
10:20:18.142 D 4 22:1635:780 - D-R(004) 02 81 01 2F
10:20:18.142 D 4 22:1635:780 - D-X(004) 02 81 01 37
10:20:22.147 D 3 22:1639:781 - D-R(004) 02 81 01 6F
10:20:22.147 D 3 22:1639:781 - D-X(004) 02 81 01 77
10:20:22.147 D 3 22:1639:783 - D-X(004) 00 81 01 77
10:20:22.167 D 3 22:1639:799 - D-R(004) 00 81 01 6F

Does anybody know how to read/interpret the last lines? What do you think?
Is it a Eicon problem or have I mixed something up in my code?

TIA
Gerhard

Danilo Kempf

2005-12-14 23:13:28 UTC

Permalink

Hi,

Post by Gerhard Gaugusch
I have contacted Eicon and they are trying to help me. But as time goes by
I have no time to wait for an answer from them.

Strange problems you are experiencing. I don't think there's anybody besides
Eicon being able to help you there.

However, if a timely solution is of more concern than elegance and the
reason for the faults you are experiencing is indeed the DLL and neither
the driver nor the application, you could always try out another
CAPI2032.DLL.

CAPI is specified in two pieces -- first, there's the device driver
interface which can be used either by other drivers or by adventurous
applications and then there's the DLL interface which is bolted on top of
the driver interface and provides a somewhat easier (albeit more limiting)
environment to work with.

The communications between the DLL and the driver are specified by CAPI
(sure thing, it's the standard driver-level interface), so you could simply
swap out the Eicon-DLL (which we've never had any problems with, by the
way) for another vendors DLL and everything should work out of the box.

I'm sure you can find some other DLL to try out -- there's certainly one
included with every freely downloadable driver package or one of the
software-only VoIP-CAPIs(TM)(R)(C) of which I'm sure you can get
demo-versions for free.

Still I assume using such a DLL in a production environment would be
prohibitively illegal.

Post by Gerhard Gaugusch
10:20:18.142 D 4 22:1635:780 - D-R(004) 02 81 01 2F
10:20:18.142 D 4 22:1635:780 - D-X(004) 02 81 01 37
10:20:22.147 D 3 22:1639:781 - D-R(004) 02 81 01 6F
10:20:22.147 D 3 22:1639:781 - D-X(004) 02 81 01 77
10:20:22.147 D 3 22:1639:783 - D-X(004) 00 81 01 77
10:20:22.167 D 3 22:1639:799 - D-R(004) 00 81 01 6F
Does anybody know how to read/interpret the last lines?

Those lines look like Layer 2-data. Probably pretty much unrelated to your
problem.

Post by Gerhard Gaugusch
What do you think?
Is it a Eicon problem or have I mixed something up in my code?

Honestly -- in fact I do think you mixed something up. The Eicon stuff is
pretty solid, normally.

Best regards,

Danilo

Johann Deutinger

2005-12-15 09:22:51 UTC

Permalink

Post by Danilo Kempf

Those lines look like Layer 2-data. Probably pretty much unrelated to
your problem.

This Layer-2 data looks strange; it's all receive-ready (RR)
with the same TEI but with gaps in N(R). Do you have more
than one piece of equipment connected to the same interface?
If yes, they should have different TEIs.

Regards,
Johann

Gerhard Gaugusch

2005-12-15 11:13:35 UTC

Permalink

Post by Johann Deutinger
This Layer-2 data looks strange; it's all receive-ready (RR)
with the same TEI but with gaps in N(R). Do you have more
than one piece of equipment connected to the same interface?
If yes, they should have different TEIs.

My scenario looks like this:
4 NTs connected to my Diva Server V 4BRI card. There is no other equipment
connected to the NTs

Gerhard Gaugusch

2005-12-20 12:03:17 UTC

Permalink

Finnaly I solved my problems by changing vom Eicon Diva Server V 4 BRI card
to an FRITZ C4. Without any Software changes everything works fine.

Post by Gerhard Gaugusch

4 NTs connected to my Diva Server V 4BRI card. There is no other equipment
connected to the NTs