detect outgoing calls?

[Bernd Specht]

Is it possible to detect outgoing call established by other equipment?

I mean, can an application that runs on my pc, detect when I do a (outgoing)
call from my phone? How?

[mm]

Hi Bernd;

No, I don't think so.

The only thing you could try, is to 'poll' the availability of the isdn
lines.
Assuming you have a BRI line, then you have two outgoing lines.
If one/two lines are occupied and your application tries to ring your
own local number you will get an error, like 'no channel available'.
But of course if nobody uses the phones, it will probably ring every
time you 'poll', which might be a bit annoying :)

Bye
Michael

Post by Bernd Specht
Is it possible to detect outgoing call established by other

equipment?

Post by Bernd Specht
I mean, can an application that runs on my pc, detect when I do a (outgoing)
call from my phone? How?

[Bernd Specht]

Post by mm
Hi Bernd;
No, I don't think so.
The only thing you could try, is to 'poll' the availability of the isdn
lines.
Assuming you have a BRI line, then you have two outgoing lines.
If one/two lines are occupied and your application tries to ring your
own local number you will get an error, like 'no channel available'.
But of course if nobody uses the phones, it will probably ring every
time you 'poll', which might be a bit annoying :)
Bye
Michael

Post by Bernd Specht
Is it possible to detect outgoing call established by other equipment?
I mean, can an application that runs on my pc, detect when I do a
(outgoing) call from my phone? How?

I've heard that AVM equipment is able to listen at the d-channel and so get
more information than normal capi messages. Anyone know about it?

[Bernd Spari]

Post by Bernd Specht
I've heard that AVM equipment is able to listen at the d-channel and so get
more information than normal capi messages. Anyone know about it?

Yes, it is achieved by special manufacturer messages to Capi.
Have a look at the K-ISDN-Watch sources to figure out the encoding.
But if i recall correct it is only possible to detect the status of the
lines
and not to get more information like D-Channel traces from other ISDN
Equipment.

regards,

bernd spari

[Bernd Specht]

Post by Bernd Spari

Post by Bernd Specht
I've heard that AVM equipment is able to listen at the d-channel and so
get more information than normal capi messages. Anyone know about it?

Yes, it is achieved by special manufacturer messages to Capi.
Have a look at the K-ISDN-Watch sources to figure out the encoding.
But if i recall correct it is only possible to detect the status of the
lines
and not to get more information like D-Channel traces from other ISDN
Equipment.
regards,
bernd spari

Thanks, I will have a look at it.

[Michael Meiwald]

Hi

Just a few questions :)

I tried this with an AVM Fritz card;
I am not quite sure what to send in the manufacturer data struct
though.
What sort of data are you supposed to send ?
And what to receive ?

Apart from the getBChannelInfo function are there anymore 'known'
functions ?

How far are the first bits of the manufacturer req..conf messages
standardized ? Is it always manufacturer id, class, function, data
struct,
even if you send it to non AVM cards ? Is there any info on that
anywhere ? I don't seem to find anything.

Did AVM release any documentation for the manufacturer messages ?

Bye
Michael

Post by Bernd Spari

Post by Bernd Specht
I've heard that AVM equipment is able to listen at the d-channel and so get
more information than normal capi messages. Anyone know about it?

Yes, it is achieved by special manufacturer messages to Capi.
Have a look at the K-ISDN-Watch sources to figure out the encoding.
But if i recall correct it is only possible to detect the status of the
lines
and not to get more information like D-Channel traces from other ISDN
Equipment.
regards,
bernd spari

[Bernd Spari]

Post by Michael Meiwald
Hi
Just a few questions :)
I tried this with an AVM Fritz card;
I am not quite sure what to send in the manufacturer data struct
though.
What sort of data are you supposed to send ?
And what to receive ?
Apart from the getBChannelInfo function are there anymore 'known'
functions ?
How far are the first bits of the manufacturer req..conf messages
standardized ? Is it always manufacturer id, class, function, data
struct,
even if you send it to non AVM cards ? Is there any info on that
anywhere ? I don't seem to find anything.
Did AVM release any documentation for the manufacturer messages ?

First i have to say that I have never implemented this feature so i just
could give you some hints.
As far as i know is the channel status info the only public known
manufacturer message
and it works of course only for avm cards.
Personally i think it would be better to get this information in a
manufacturer independent way.
(Probably a reasonable new workitem for the Capi-Assoziation)

I suppose you have already downloaded the sources at
ftp://ftp.avm.de/tools/k_isdn_watch.linux/kisdnwatch-01.00.08.tar.gz

To understand them it is usefull to be familiar with the avm software
development kit
because they are written in the same programming style wich is kind of
difficult to understand.

After a first glance i would suggest to look at the m_bChannelInfo[] byte
array
in the /kavmmon/ccapiinfo.cpp file.

regards,

bernd spari

[Michael Meiwald]

Thanks Bernd;

I will have a closer look.

Michael

Post by Bernd Spari

Post by Michael Meiwald
Hi
Just a few questions :)
I tried this with an AVM Fritz card;
I am not quite sure what to send in the manufacturer data struct
though.
What sort of data are you supposed to send ?
And what to receive ?
Apart from the getBChannelInfo function are there anymore 'known'
functions ?
How far are the first bits of the manufacturer req..conf messages
standardized ? Is it always manufacturer id, class, function, data
struct,
even if you send it to non AVM cards ? Is there any info on that
anywhere ? I don't seem to find anything.
Did AVM release any documentation for the manufacturer messages ?

First i have to say that I have never implemented this feature so i just
could give you some hints.
As far as i know is the channel status info the only public known
manufacturer message
and it works of course only for avm cards.
Personally i think it would be better to get this information in a
manufacturer independent way.
(Probably a reasonable new workitem for the Capi-Assoziation)
I suppose you have already downloaded the sources at
ftp://ftp.avm.de/tools/k_isdn_watch.linux/kisdnwatch-01.00.08.tar.gz
To understand them it is usefull to be familiar with the avm software
development kit
because they are written in the same programming style wich is kind of
difficult to understand.
After a first glance i would suggest to look at the m_bChannelInfo[] byte
array
in the /kavmmon/ccapiinfo.cpp file.
regards,
bernd spari