capisuite does not get incoming calls...

[Joern Nettingsmeier]

hi gernot, hi everyone!


first of all, thanks for a really cool tool!
it does not work for me yet, but the design and the docs are so nice
that i like it nonetheless :-D

i have a fritz pci card running on a dual-p3 machine with suse 9.2.

the card seems to be ok, capiinfo prints detailed information.
isdnlog logs all outgoing and incoming calls, so i assume the card is
running fine.

however, capisuite does not see any incoming calls... although i raised
the log level to 3, all i see is idlescript entries.

the card is connected to the s0 out of an eumex 306 (the docs say it's
wired directly to the external s0 bus).

i've tested the setup by dialling my own number (maybe that's the problem?)


my first assumption was that i must tell the isdn card which msns it
should respond to, but the yast configuration does not allow this,
neither does the capisuite main config file.
so i deduced that capisuite is probably listening to all numbers by
default and decides by the numbers in the fax and answerphone configs
whether to take or ignore a call - correct ?


this is probably a very simple isdn blunder on my part, but i'm really
clueless at this point. i'd welcome some generic test tools (i.e. make
the card dial a number etc.).
the suse setup is very complicated and breaks since my primary interface
is a dsl link....


best regards,


jörn



==> /var/log/capisuite.log <==
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: CapiSuite 0.4.4 started.
Wed Feb 23 23:53:02 2005 Capi 0x816b680: Capi object created
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x0 Controller 0x1 InfoMask 0x10 CIPMask 0x0 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: Registered successful at CAPI
with ApplId 2
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: 1 controllers found
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: Capi driver: AVM Berlin,
version 2.0/1.16
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: Controller 1: AVM GmbH (2
B channels, DTMF, SuppServ, transparent, FaxG3, FaxG3ext), driver
version 2.0/49.18
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x1 Controller 0x1 InfoMask 0x10 CIPMask 0x10012 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x2 Controller 0x1 InfoMask 0x10 CIPMask 0x30012 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: PythonScript created.
Wed Feb 23 23:53:02 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: IdleScript created.
Wed Feb 23 23:53:33 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: executing idlescript...
Wed Feb 23 23:53:33 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: idlescript finished...
Wed Feb 23 23:54:03 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: executing idlescript...
Wed Feb 23 23:54:03 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: idlescript finished...

[Joern Nettingsmeier]

hi gernot, hi everyone!


first of all, thanks for a really cool tool!
it does not work for me yet, but the design and the docs are so nice
that i like it nonetheless :-D

i have a fritz pci card running on a dual-p3 machine with suse 9.2.

the card seems to be ok, capiinfo prints detailed information.
isdnlog logs all outgoing and incoming calls, so i assume the card is
running fine.

however, capisuite does not see any incoming calls... although i raised
the log level to 3, all i see is idlescript entries.

the card is connected to the s0 out of an eumex 306 (the docs say it's
wired directly to the external s0 bus).

i've tested the setup by dialling my own number (maybe that's the problem?)


my first assumption was that i must tell the isdn card which msns it
should respond to, but the yast configuration does not allow this,
neither does the capisuite main config file.
so i deduced that capisuite is probably listening to all numbers by
default and decides by the numbers in the fax and answerphone configs
whether to take or ignore a call - correct ?


this is probably a very simple isdn blunder on my part, but i'm really
clueless at this point. i'd welcome some generic test tools (i.e. make
the card dial a number etc.).
the suse setup is very complicated and breaks since my primary interface
is a dsl link....


best regards,


jörn


ps: please cc: me on replies, my subscription is not yet active, i'm
still waiting for the confirmation mail...



==> /var/log/capisuite.log <==
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: CapiSuite 0.4.4 started.
Wed Feb 23 23:53:02 2005 Capi 0x816b680: Capi object created
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x0 Controller 0x1 InfoMask 0x10 CIPMask 0x0 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: Registered successful at CAPI
with ApplId 2
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: 1 controllers found
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: Capi driver: AVM Berlin,
version 2.0/1.16
Wed Feb 23 23:53:02 2005 CapiSuite 0xbffff390: Controller 1: AVM GmbH (2
B channels, DTMF, SuppServ, transparent, FaxG3, FaxG3ext), driver
version 2.0/49.18
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x1 Controller 0x1 InfoMask 0x10 CIPMask 0x10012 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: >LISTEN_REQ ApplID 0x2 msgNum
0x2 Controller 0x1 InfoMask 0x10 CIPMask 0x30012 0x0 NULL NULL
Wed Feb 23 23:53:02 2005 Capi 0x816b680: info: 0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Capi 0x816b680: *
Wed Feb 23 23:53:02 2005 Capi 0x816b680: <LISTEN_CONF Controller 0x1
Info 0x0
Wed Feb 23 23:53:02 2005 Capi 0x816b680: **
Wed Feb 23 23:53:02 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: PythonScript created.
Wed Feb 23 23:53:02 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: IdleScript created.
Wed Feb 23 23:53:33 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: executing idlescript...
Wed Feb 23 23:53:33 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: idlescript finished...
Wed Feb 23 23:54:03 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: executing idlescript...
Wed Feb 23 23:54:03 2005 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x8180490: idlescript finished...

[Gernot Hillier]

Hi!

Post by Joern Nettingsmeier
first of all, thanks for a really cool tool!
it does not work for me yet, but the design and the docs are so nice
that i like it nonetheless :-D

:-)

Post by Joern Nettingsmeier
my first assumption was that i must tell the isdn card which msns it
should respond to, but the yast configuration does not allow this,
neither does the capisuite main config file.
so i deduced that capisuite is probably listening to all numbers by
default and decides by the numbers in the fax and answerphone configs
whether to take or ignore a call - correct ?

Yes, that's exactly how it's supposed to work.

Post by Joern Nettingsmeier
this is probably a very simple isdn blunder on my part, but i'm really
clueless at this point. i'd welcome some generic test tools (i.e. make
the card dial a number etc.).

Hmmm, this really looks like a low layer problem with the card or the driver.
Do you use the AVM CAPI driver? If yes, you could try activating its debug
feature via "avmcapictrl trace 0 on" and have a look in
your /var/log/messages when a call arrives.

If this doesn't help, you should try the suse-isdn mailing list - there are
people much more experienced with low level problems than me...

[Joern Nettingsmeier]

hello gernot!


thanks for your reply, and sorry for not getting back to you earlier...
i've been busy with work-related stuff.

Post by Gernot Hillier
Hi!

Post by Joern Nettingsmeier
first of all, thanks for a really cool tool!
it does not work for me yet, but the design and the docs are so nice
that i like it nonetheless :-D

:-)

Post by Joern Nettingsmeier
my first assumption was that i must tell the isdn card which msns it
should respond to, but the yast configuration does not allow this,
neither does the capisuite main config file.
so i deduced that capisuite is probably listening to all numbers by
default and decides by the numbers in the fax and answerphone configs
whether to take or ignore a call - correct ?

Yes, that's exactly how it's supposed to work.

good :)

Post by Gernot Hillier

Post by Joern Nettingsmeier
this is probably a very simple isdn blunder on my part, but i'm really
clueless at this point. i'd welcome some generic test tools (i.e. make
the card dial a number etc.).

Hmmm, this really looks like a low layer problem with the card or the driver.
Do you use the AVM CAPI driver? If yes, you could try activating its debug
feature via "avmcapictrl trace 0 on" and have a look in
your /var/log/messages when a call arrives.

i'll try.

Post by Gernot Hillier
If this doesn't help, you should try the suse-isdn mailing list - there are
people much more experienced with low level problems than me...

ok, thanks for the pointer.


best wishes,

jörn