No "sound", no messages, ...

[Alexander Wimmer]

Hi,

I just installed CapiSuite 0.4.4 on my Debian-server. Installation of the
binary-packages went fine, calls are identified, but no messages are played
and no recording od messages is possible.

The call is "answered", so i get a connection, but i hear nothing. the
user-dirs are read- and writeable to the user. I even tried to copy a
prerecorded (default) message to the user-dir, renaming it to
announcement.la", but still no "sound".

Although record-length is set to 120 (seconds) even after 300 senconds the
line is still "active", no recordings are made.

I have a PCI-AVM B1-card, v.2.0, which is connected to the S0-plug in my
ntba (not sure if i got the terms right here) with a ethernet-cable.

I browed all mail on this list until back in 2002 (i think), but I found no
solution. So please, if anyone has a hint for me, please tell me so.

Alex

This is what happens when I call:
(log-level 2)

Sat Jan 8 20:10:33 2005 CapiSuite 0xbffffd90: CapiSuite 0.4.4 started.
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: Capi object created
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: >LISTEN_REQ ApplID 0x1 msgNum 0x0
Controller 0x1 InfoMask 0x10 CIPMask 0x0 0x0 NULL NULL
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: Registered successful at CAPI with
ApplId 1
Sat Jan 8 20:10:33 2005 CapiSuite 0xbffffd90: 1 controllers found
Sat Jan 8 20:10:33 2005 CapiSuite 0xbffffd90: Capi driver: AVM Berlin,
version 2.0/1.16^@
Sat Jan 8 20:10:33 2005 CapiSuite 0xbffffd90: Controller 1: AVM GmbH (2 B
channels, DTMF, SuppServ, transparent, FaxG3, FaxG3ext), driver version
2.0/48.113
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: >LISTEN_REQ ApplID 0x1 msgNum 0x1
Controller 0x1 InfoMask 0x10 CIPMask 0x10012 0x0 NULL NULL
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: >LISTEN_REQ ApplID 0x1 msgNum 0x2
Controller 0x1 InfoMask 0x10 CIPMask 0x30012 0x0 NULL NULL
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: <LISTEN_CONF Controller 0x1 Info
0x0
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: <LISTEN_CONF Controller 0x1 Info
0x0
Sat Jan 8 20:10:33 2005 Capi 0x80a3298: <LISTEN_CONF Controller 0x1 Info
0x0
Sat Jan 8 20:10:51 2005 Capi 0x80a3298: <CONNECT_IND PLCI 0x101 CIP 0x10
Sat Jan 8 20:10:51 2005 Connection 0x80c1c08: Connection object created for
incoming call PLCI 101 from XXXXXXXXXXX to XXXXXXXXXXX CIP 0x10
Sat Jan 8 20:10:51 2005 Pythonscript
/usr/lib/capisuite/incoming.py,callIncoming,0x80b9b38: Connection 0x80c1c08
created IncomingScript
Sat Jan 8 20:10:51 2005 Connection 0x80c1c08: call from XXXXXXXXXXX to
XXXXXXXXXXX for MYNAME connecting with voice
Sat Jan 8 20:10:51 2005 Capi 0x80a3298: >ALERT_REQ: ApplId 0x1, MsgNr 0x3,
PLCI0x101
Sat Jan 8 20:10:51 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:10:51 2005 Capi 0x80a3298: <ALERT_CONF, PLCI: 0x101, Info 0x0
Sat Jan 8 20:11:01 2005 Connection 0x80c1c08: accepting with service 0
Sat Jan 8 20:11:01 2005 Connection 0x80c1c08: using faxStationID
faxHeadline
Sat Jan 8 20:11:01 2005 Capi 0x80a3298: >CONNECT_RESP ApplId 0x1, msgNum
0xc, PLCI 0x101, Reject 0x0, B1proto 0x1, B2proto 0x1, B3proto 0x0
Sat Jan 8 20:11:01 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:11:01 2005 Capi 0x80a3298: <CONNECT_ACTIVE_IND PLCI 0x101
Sat Jan 8 20:11:01 2005 Capi 0x80a3298: >CONNECT_ACTIVE_RESP ApplId 0x1
MsgNum 0xd PLCI 0x101
Sat Jan 8 20:11:01 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: <INFO_IND: Controller/PLCI 0x101,
InfoNumber 1e (ignoring)
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: >INFO_RESP ApplId 0x1, MsgNr 0xe,
Address 0x101
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: <DISCONNECT_IND PLCI 0x101 Reason
0x3490
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: >DISCONNECT_RESP ApplId 0x1 MsgNum
0xf PLCI 0x101
Sat Jan 8 20:11:47 2005 Capi 0x80a3298: info: 0
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: connection lost with cause
0x3490, 0x0
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: Python: deleting connection
object
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: stop_file_transmission
initiated
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: stop_file_transmission
finished
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: stop_file_reception finished
Sat Jan 8 20:11:47 2005 Connection 0x80c1c08: Connection object deleted
Sat Jan 8 20:11:47 2005 Pythonscript
/usr/lib/capisuite/incoming.py,callIncoming ,0x80b9b38: IncomingScript
deleted

My answering_machine.conf is:
[MYNAME]
voice_numbers="XXXXXXXX"
voice_action="MailAndSave"
voice_delay="10"
record_length="120"
voice_email="MAIL-+***@public.gmane.org"
pin="ZZZZ"


My fax.conf is:
[MYNME]
fax_numbers="XXXXXXXXY"
fax_stationID="[phone]"
fax_headline="MYNAME - sent by CapiSuite"
fax_email="MAIL-+***@public.gmane.org"
fax_action="MailAndSave"

[Gernot Hillier]

Hi!

Post by Alexander Wimmer
I browed all mail on this list until back in 2002 (i think), but I found no
solution. So please, if anyone has a hint for me, please tell me so.
Alex
(log-level 2)

[...]


Any helpful entries in capisuite.error?

[Alexander Wimmer]

Post by Gernot Hillier
Hi!

Post by Alexander Wimmer
I browed all mail on this list until back in 2002 (i think), but I found

no

Post by Gernot Hillier

Post by Alexander Wimmer
solution. So please, if anyone has a hint for me, please tell me so.
Alex
(log-level 2)

[...]
Any helpful entries in capisuite.error?
-- Ciao, Gernot

Hi Gernot,

thanks for the quick reply. Unfortunately there are no entries in the
capisuite.error-file, apart from the starts and stops of capisuite
(capisuite does not stop/terminate when a call is "received", btw. But I
think you already guessed that from the other log i posted ;-) )

Thanks again for your time and any hints,

Alex

[Gernot Hillier]

Hi!

Post by Alexander Wimmer

Post by Gernot Hillier

Post by Alexander Wimmer
(log-level 2)

[...]
Any helpful entries in capisuite.error?

thanks for the quick reply. Unfortunately there are no entries in the
capisuite.error-file, apart from the starts and stops of capisuite
(capisuite does not stop/terminate when a call is "received", btw. But I
think you already guessed that from the other log i posted ;-) )

Hmmm... Could you please try to raise the logging level to 3, call the
machine, keep connected for about 10 seconds or so (to assure that if
CapiSuite plays something it gets ready with it) and hang up. Then please
send the log to this list or if it's too long to me personally - or even
better put it somewhere on the web.

Could your CAPI driver perhaps have a problem? (I.e. bug in driver -> try to
update, Interrupt problems -> try another PCI slot, ...)