Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-09 Thread Armin Schindler
On Mon, 9 Apr 2007, Peer Oliver Schmidt wrote:
 Hello Armin (and happy easter),
 
 thanks for you continuing support.
 
  Can you please try HEAD version of SVN trunk (443)?
 
 Did checkout the 443.
 
 It works without any verbosity.
 
 THANK YOU! I'll buy you a beer, if you ever happen to come to the
 northern part of Germany.

Thank you, but real thanks should go to the bug reporter of PR#28
on bugs.melware.net.

Armin

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-08 Thread Armin Schindler
On Tue, 3 Apr 2007, Armin Schindler wrote:
 On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote:
  Hello Armin,
  
  thanks a lot for your help.
  
   Can you please do the same with 'showcapimsgs=2'?
   It may give more info on the commands itself, maybe some parameters are
   wrong here.
  
  Here you go. 17:23:17 is the magic time.
 
 This log below shows no error in parameters, but the problem is still the 
 same: the fcpci driver doesn't respond and I cannot tell why.

Can you please try HEAD version of SVN trunk (443)?
It seems that the Fritz driver has a bug when registering at its CAPI
interface.

Armin

  Apr  3 17:23:09 server42 kernel: [263323.308388] fcpci: AVM FRITZ!Card PCI
  driver, revision 0.7.2
  Apr  3 17:23:09 server42 kernel: [263323.308411] fcpci: (fcpci built on Feb 
  27
  2007 at 21:22:25)
  Apr  3 17:23:09 server42 kernel: [263323.308421] fcpci: -- 32 bit CAPI 
  driver
  --
  Apr  3 17:23:10 server42 kernel: [263323.311559] PCI: Found IRQ 10 for 
  device
  :00:0e.0
  Apr  3 17:23:10 server42 kernel: [263323.311602] fcpci: AVM FRITZ!Card PCI
  found: port 0xdcc0, irq 10
  Apr  3 17:23:10 server42 kernel: [263323.311613] fcpci: Loading...
  Apr  3 17:23:10 server42 kernel: [263323.311625] fcpci: Driver 'fcpci'
  attached to fcpci-stack. (152)
  Apr  3 17:23:10 server42 kernel: [263323.539987] fcpci: Stack version 
  3.11-07
  Apr  3 17:23:10 server42 kernel: [263323.541140] kcapi: Controller 1:
  fcpci-dcc0-10 attached
  Apr  3 17:23:10 server42 kernel: [263323.541154] kcapi: card 1 
  fcpci-dcc0-10
  ready.
  Apr  3 17:23:10 server42 kernel: [263323.541833] fcpci: Loaded.
  Apr  3 17:23:12 server42 kernel: [263325.975634] capi20: Rev 1.1.2.7: 
  started
  up with major 68 (middleware+capifs)
  Apr  3 17:23:17 server42 kernel: [263330.892916] kcapi: put [0x1] 
  FACILITY_REQ
  ID=001 #0x0001 LEN=0018
  Apr  3 17:23:17 server42 kernel: [263330.892926]   Controller/PLCI/NCCI
  = 0x1
  Apr  3 17:23:17 server42 kernel: [263330.892933]   FacilitySelector
  = 0x3
  Apr  3 17:23:17 server42 kernel: [263330.892939] FacilityRequestParameter
  = 00 00 00
  Apr  3 17:23:17 server42 kernel: [263330.892946]
  Apr  3 17:23:17 server42 kernel: [263330.893153] kcapi: got [0x1]
  FACILITY_CONF  ID=001 #0x0001 LEN=0026
  Apr  3 17:23:17 server42 kernel: [263330.893163]   Controller/PLCI/NCCI
  = 0x1
  Apr  3 17:23:17 server42 kernel: [263330.893169]   Info= 0x0
  Apr  3 17:23:17 server42 kernel: [263330.893176]   FacilitySelector
  = 0x3
  Apr  3 17:23:17 server42 kernel: [263330.893182] 
  FacilityConfirmationParameter
  = 00 00 06 00 00\37703 00 00
  Apr  3 17:23:17 server42 kernel: [263330.893190]
  Apr  3 17:23:17 server42 kernel: [263330.900689] kcapi: put [0x1] LISTEN_REQ
  ID=001 #0x0002 LEN=0026
  Apr  3 17:23:17 server42 kernel: [263330.900699]   Controller/PLCI/NCCI
  = 0x1
  Apr  3 17:23:17 server42 kernel: [263330.900706]   InfoMask=
  0x
  Apr  3 17:23:17 server42 kernel: [263330.900713]   CIPmask=
  0x1fff03ff
  Apr  3 17:23:17 server42 kernel: [263330.900720]   CIPmask2= 0x0
  Apr  3 17:23:17 server42 kernel: [263330.900726]   CallingPartyNumber
  = default
  Apr  3 17:23:17 server42 kernel: [263330.900733] CallingPartySubaddress
  = default
  Apr  3 17:23:17 server42 kernel: [263330.900739]
  
  -- 
  Best regards
  
  Peer Oliver Schmidt
  PGP Key ID: 0x83E1C2EA
  
  ___
  --Bandwidth and Colocation provided by Easynews.com --
  
  asterisk-users mailing list
  To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users
  
  
 ___
 --Bandwidth and Colocation provided by Easynews.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
 
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-08 Thread Peer Oliver Schmidt
Hello Armin (and happy easter),

thanks for you continuing support.

 Can you please try HEAD version of SVN trunk (443)?

Did checkout the 443.

It works without any verbosity.

THANK YOU! I'll buy you a beer, if you ever happen to come to the
northern part of Germany.
-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Armin Schindler
On Mon, 2 Apr 2007, Peer Oliver Schmidt wrote:
 Hello Armin,
 
  [EMAIL PROTECTED]:~# grep capi /var/log/asterisk/messages
 
  [Mar 31 16:17:03] ERROR[3850] chan_capi.c: Unable to listen on contr1
  (error=0x100f)
 
  Is this helpful, or do you need more information?
  
  Yes, at this state it might be possible that less CPU power causes
  problems. The 'listen' command expects an answer and maybe it is coming too 
  late. Can you please try the patch below?
  
   Index: chan_capi.c
  ===
  --- chan_capi.c (revision 436)
  +++ chan_capi.c (working copy)
  @@ -631,7 +631,7 @@
  error = LISTEN_CONF_INFO(CMSG);
  break;
  }
  -   usleep(2);
  +   usleep(10);
 
 tried the patch, but it did not work. It waits quite a long time
 before the chan-capi error message comes up, according to the time
 stamp it is about 12 seconds. It is kind of strange, that the whole
 startup process for asterisk usually takes only about 4-5 seconds.

That's too long, normaly the confirmation message arrives within a few 
msecs. So it seems that the driver isn't responding.

 Do you need additional information?

Which card/driver do you use? 
A debug log (capi trace) from the driver or kernelcapi helps to see
what messages are wrong/missing.

Armin

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Peer Oliver Schmidt
Good Morning Armin,

 tried the patch, but it did not work. It waits quite a long time
 before the chan-capi error message comes up, according to the time
 stamp it is about 12 seconds. It is kind of strange, that the whole
 startup process for asterisk usually takes only about 4-5 seconds.

 That's too long, normaly the confirmation message arrives within a few 
 msecs. So it seems that the driver isn't responding.
 
 Do you need additional information?
 
 Which card/driver do you use? 

[EMAIL PROTECTED]:~# lspci -s 0:0e -v
00:0e.0 Network controller: AVM Audiovisuelles MKTG  Computer System
GmbH A1 ISDN [Fritz] (rev 02)
Subsystem: AVM Audiovisuelles MKTG  Computer System GmbH
FRITZ!Card ISDN Controller
Flags: medium devsel, IRQ 10
Memory at ff001400 (32-bit, non-prefetchable) [size=32]
I/O ports at dcc0 [size=32]

[EMAIL PROTECTED]:~# capiinit status
1 fcpci  running  fcpci-dcc0-10A1 3.11-07 0xdcc0 10

Driver from ubuntu edgy

 A debug log (capi trace) from the driver or kernelcapi helps to see
 what messages are wrong/missing.

What is the best way to produce this?
-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Armin Schindler
On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote:
 Good Morning Armin,
 
  tried the patch, but it did not work. It waits quite a long time
  before the chan-capi error message comes up, according to the time
  stamp it is about 12 seconds. It is kind of strange, that the whole
  startup process for asterisk usually takes only about 4-5 seconds.
 
  That's too long, normaly the confirmation message arrives within a few 
  msecs. So it seems that the driver isn't responding.
  
  Do you need additional information?
  
  Which card/driver do you use? 
 
 [EMAIL PROTECTED]:~# lspci -s 0:0e -v
 00:0e.0 Network controller: AVM Audiovisuelles MKTG  Computer System
 GmbH A1 ISDN [Fritz] (rev 02)
 Subsystem: AVM Audiovisuelles MKTG  Computer System GmbH
 FRITZ!Card ISDN Controller
 Flags: medium devsel, IRQ 10
 Memory at ff001400 (32-bit, non-prefetchable) [size=32]
 I/O ports at dcc0 [size=32]
 
 [EMAIL PROTECTED]:~# capiinit status
 1 fcpci  running  fcpci-dcc0-10A1 3.11-07 0xdcc0 10
 
 Driver from ubuntu edgy

I cannot tell anything about the AVM drivers.
 
  A debug log (capi trace) from the driver or kernelcapi helps to see
  what messages are wrong/missing.
 
 What is the best way to produce this?

If the AVM driver can do that, I don't know.
But on load of the module 'kernelcapi', you can specify the
module parameter
  showcapimsgs=X
where X is the verbose level.
By default it is 0, which means no messges. You should set it
to 3 to get the CAPI control messages on the kernel-console (logfile).
Or even to 7 to have all CAPI messages (including data messages) which 
might be too much.

Armin

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Peer Oliver Schmidt

Hello Armin,

here are the results, after modprobe kernelcapi showcapimsgs=3

/var/log/kern.log

Apr  3 15:06:14 server42 kernel: [255113.053170] CAPI Subsystem Rev 1.1.2.8
Apr  3 15:06:18 server42 kernel: [255116.814334] fcpci: AVM FRITZ!Card 
PCI driver, revision 0.7.2
Apr  3 15:06:18 server42 kernel: [255116.814356] fcpci: (fcpci built on 
Feb 27 2007 at 21:22:25)
Apr  3 15:06:18 server42 kernel: [255116.814367] fcpci: -- 32 bit CAPI 
driver --
Apr  3 15:06:18 server42 kernel: [255116.817598] PCI: Found IRQ 10 for 
device :00:0e.0
Apr  3 15:06:18 server42 kernel: [255116.817642] fcpci: AVM FRITZ!Card 
PCI found: port 0xdcc0, irq 10

Apr  3 15:06:18 server42 kernel: [255116.817653] fcpci: Loading...
Apr  3 15:06:18 server42 kernel: [255116.817665] fcpci: Driver 'fcpci' 
attached to fcpci-stack. (152)
Apr  3 15:06:18 server42 kernel: [255117.049308] fcpci: Stack version 
3.11-07
Apr  3 15:06:18 server42 kernel: [255117.050442] kcapi: Controller 1: 
fcpci-dcc0-10 attached
Apr  3 15:06:18 server42 kernel: [255117.050456] kcapi: card 1 
fcpci-dcc0-10 ready.

Apr  3 15:06:18 server42 kernel: [255117.050480] kcapi: notify up contr 1
Apr  3 15:06:19 server42 kernel: [255117.051283] fcpci: Loaded.
Apr  3 15:06:22 server42 kernel: [255120.102281] capi20: Rev 1.1.2.7: 
started up with major 68 (middleware+capifs)

Apr  3 15:06:35 server42 kernel: [255133.725987] kcapi: appl 1 up
Apr  3 15:06:35 server42 kernel: [255133.727235] kcapi: put [0x1] id#1 
FACILITY_REQ len=18
Apr  3 15:06:35 server42 kernel: [255133.727712] kcapi: got [0x1] id#1 
FACILITY_CONF len=26

Apr  3 15:06:35 server42 kernel: [255133.729933] kcapi: appl 1 down
Apr  3 15:06:35 server42 kernel: [255133.730585] kcapi: appl 1 up
Apr  3 15:06:35 server42 kernel: [255133.731478] kcapi: put [0x1] id#1 
LISTEN_REQ len=26

Apr  3 15:06:52 server42 kernel: [255150.690252] kcapi: appl 1 down



At 15:06:35 the loading stopped.

Is this helpful, or do you need a higher verbosity?
--
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Armin Schindler
On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote:
 Hello Armin,
 
 here are the results, after modprobe kernelcapi showcapimsgs=3
 
 /var/log/kern.log
... 
 Apr  3 15:06:22 server42 kernel: [255120.102281] capi20: Rev 1.1.2.7: started 
 up with major 68 (middleware+capifs)
 Apr  3 15:06:35 server42 kernel: [255133.725987] kcapi: appl 1 up
 Apr  3 15:06:35 server42 kernel: [255133.727235] kcapi: put [0x1] id#1 
 FACILITY_REQ len=18
 Apr  3 15:06:35 server42 kernel: [255133.727712] kcapi: got [0x1] id#1 
 FACILITY_CONF len=26
 Apr  3 15:06:35 server42 kernel: [255133.729933] kcapi: appl 1 down
 Apr  3 15:06:35 server42 kernel: [255133.730585] kcapi: appl 1 up
 Apr  3 15:06:35 server42 kernel: [255133.731478] kcapi: put [0x1] id#1 
 LISTEN_REQ len=26
 Apr  3 15:06:52 server42 kernel: [255150.690252] kcapi: appl 1 down
 
 
 
 At 15:06:35 the loading stopped.
 
 Is this helpful, or do you need a higher verbosity?

Well, it confirmes what I have expected, but I cannot tell why it happens.
The driver doesn't respond to the LISTEN_REQ command, that's why chan-capi 
shows an error.
So with this info, the driver is the problem.
Can you please do the same with 'showcapimsgs=2'?
It may give more info on the commands itself, maybe some parameters are 
wrong here.

Armin

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Peer Oliver Schmidt

Hello Armin,

thanks a lot for your help.


Can you please do the same with 'showcapimsgs=2'?
It may give more info on the commands itself, maybe some parameters are 
wrong here.


Here you go. 17:23:17 is the magic time.

Apr  3 17:23:09 server42 kernel: [263323.308388] fcpci: AVM FRITZ!Card 
PCI driver, revision 0.7.2
Apr  3 17:23:09 server42 kernel: [263323.308411] fcpci: (fcpci built on 
Feb 27 2007 at 21:22:25)
Apr  3 17:23:09 server42 kernel: [263323.308421] fcpci: -- 32 bit CAPI 
driver --
Apr  3 17:23:10 server42 kernel: [263323.311559] PCI: Found IRQ 10 for 
device :00:0e.0
Apr  3 17:23:10 server42 kernel: [263323.311602] fcpci: AVM FRITZ!Card 
PCI found: port 0xdcc0, irq 10

Apr  3 17:23:10 server42 kernel: [263323.311613] fcpci: Loading...
Apr  3 17:23:10 server42 kernel: [263323.311625] fcpci: Driver 'fcpci' 
attached to fcpci-stack. (152)
Apr  3 17:23:10 server42 kernel: [263323.539987] fcpci: Stack version 
3.11-07
Apr  3 17:23:10 server42 kernel: [263323.541140] kcapi: Controller 1: 
fcpci-dcc0-10 attached
Apr  3 17:23:10 server42 kernel: [263323.541154] kcapi: card 1 
fcpci-dcc0-10 ready.

Apr  3 17:23:10 server42 kernel: [263323.541833] fcpci: Loaded.
Apr  3 17:23:12 server42 kernel: [263325.975634] capi20: Rev 1.1.2.7: 
started up with major 68 (middleware+capifs)
Apr  3 17:23:17 server42 kernel: [263330.892916] kcapi: put [0x1] 
FACILITY_REQ   ID=001 #0x0001 LEN=0018
Apr  3 17:23:17 server42 kernel: [263330.892926]   Controller/PLCI/NCCI 
   = 0x1
Apr  3 17:23:17 server42 kernel: [263330.892933]   FacilitySelector 
   = 0x3
Apr  3 17:23:17 server42 kernel: [263330.892939] 
FacilityRequestParameter= 00 00 00

Apr  3 17:23:17 server42 kernel: [263330.892946]
Apr  3 17:23:17 server42 kernel: [263330.893153] kcapi: got [0x1] 
FACILITY_CONF  ID=001 #0x0001 LEN=0026
Apr  3 17:23:17 server42 kernel: [263330.893163]   Controller/PLCI/NCCI 
   = 0x1
Apr  3 17:23:17 server42 kernel: [263330.893169]   Info 
   = 0x0
Apr  3 17:23:17 server42 kernel: [263330.893176]   FacilitySelector 
   = 0x3
Apr  3 17:23:17 server42 kernel: [263330.893182] 
FacilityConfirmationParameter   = 00 00 06 00 00\37703 00 00

Apr  3 17:23:17 server42 kernel: [263330.893190]
Apr  3 17:23:17 server42 kernel: [263330.900689] kcapi: put [0x1] 
LISTEN_REQ ID=001 #0x0002 LEN=0026
Apr  3 17:23:17 server42 kernel: [263330.900699]   Controller/PLCI/NCCI 
   = 0x1
Apr  3 17:23:17 server42 kernel: [263330.900706]   InfoMask 
   = 0x
Apr  3 17:23:17 server42 kernel: [263330.900713]   CIPmask 
   = 0x1fff03ff
Apr  3 17:23:17 server42 kernel: [263330.900720]   CIPmask2 
   = 0x0
Apr  3 17:23:17 server42 kernel: [263330.900726]   CallingPartyNumber 
   = default
Apr  3 17:23:17 server42 kernel: [263330.900733] 
CallingPartySubaddress  = default

Apr  3 17:23:17 server42 kernel: [263330.900739]

--
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Armin Schindler
On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote:
 Hello Armin,
 
 thanks a lot for your help.
 
  Can you please do the same with 'showcapimsgs=2'?
  It may give more info on the commands itself, maybe some parameters are
  wrong here.
 
 Here you go. 17:23:17 is the magic time.

This log below shows no error in parameters, but the problem is still the 
same: the fcpci driver doesn't respond and I cannot tell why.

Armin
 
 Apr  3 17:23:09 server42 kernel: [263323.308388] fcpci: AVM FRITZ!Card PCI
 driver, revision 0.7.2
 Apr  3 17:23:09 server42 kernel: [263323.308411] fcpci: (fcpci built on Feb 27
 2007 at 21:22:25)
 Apr  3 17:23:09 server42 kernel: [263323.308421] fcpci: -- 32 bit CAPI driver
 --
 Apr  3 17:23:10 server42 kernel: [263323.311559] PCI: Found IRQ 10 for device
 :00:0e.0
 Apr  3 17:23:10 server42 kernel: [263323.311602] fcpci: AVM FRITZ!Card PCI
 found: port 0xdcc0, irq 10
 Apr  3 17:23:10 server42 kernel: [263323.311613] fcpci: Loading...
 Apr  3 17:23:10 server42 kernel: [263323.311625] fcpci: Driver 'fcpci'
 attached to fcpci-stack. (152)
 Apr  3 17:23:10 server42 kernel: [263323.539987] fcpci: Stack version 3.11-07
 Apr  3 17:23:10 server42 kernel: [263323.541140] kcapi: Controller 1:
 fcpci-dcc0-10 attached
 Apr  3 17:23:10 server42 kernel: [263323.541154] kcapi: card 1 fcpci-dcc0-10
 ready.
 Apr  3 17:23:10 server42 kernel: [263323.541833] fcpci: Loaded.
 Apr  3 17:23:12 server42 kernel: [263325.975634] capi20: Rev 1.1.2.7: started
 up with major 68 (middleware+capifs)
 Apr  3 17:23:17 server42 kernel: [263330.892916] kcapi: put [0x1] FACILITY_REQ
 ID=001 #0x0001 LEN=0018
 Apr  3 17:23:17 server42 kernel: [263330.892926]   Controller/PLCI/NCCI
 = 0x1
 Apr  3 17:23:17 server42 kernel: [263330.892933]   FacilitySelector
 = 0x3
 Apr  3 17:23:17 server42 kernel: [263330.892939] FacilityRequestParameter
 = 00 00 00
 Apr  3 17:23:17 server42 kernel: [263330.892946]
 Apr  3 17:23:17 server42 kernel: [263330.893153] kcapi: got [0x1]
 FACILITY_CONF  ID=001 #0x0001 LEN=0026
 Apr  3 17:23:17 server42 kernel: [263330.893163]   Controller/PLCI/NCCI
 = 0x1
 Apr  3 17:23:17 server42 kernel: [263330.893169]   Info= 0x0
 Apr  3 17:23:17 server42 kernel: [263330.893176]   FacilitySelector
 = 0x3
 Apr  3 17:23:17 server42 kernel: [263330.893182] FacilityConfirmationParameter
 = 00 00 06 00 00\37703 00 00
 Apr  3 17:23:17 server42 kernel: [263330.893190]
 Apr  3 17:23:17 server42 kernel: [263330.900689] kcapi: put [0x1] LISTEN_REQ
 ID=001 #0x0002 LEN=0026
 Apr  3 17:23:17 server42 kernel: [263330.900699]   Controller/PLCI/NCCI
 = 0x1
 Apr  3 17:23:17 server42 kernel: [263330.900706]   InfoMask=
 0x
 Apr  3 17:23:17 server42 kernel: [263330.900713]   CIPmask=
 0x1fff03ff
 Apr  3 17:23:17 server42 kernel: [263330.900720]   CIPmask2= 0x0
 Apr  3 17:23:17 server42 kernel: [263330.900726]   CallingPartyNumber
 = default
 Apr  3 17:23:17 server42 kernel: [263330.900733] CallingPartySubaddress
 = default
 Apr  3 17:23:17 server42 kernel: [263330.900739]
 
 -- 
 Best regards
 
 Peer Oliver Schmidt
 PGP Key ID: 0x83E1C2EA
 
 ___
 --Bandwidth and Colocation provided by Easynews.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
 http://lists.digium.com/mailman/listinfo/asterisk-users
 
 
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-03 Thread Peer Oliver Schmidt

Good evening Armin,

This log below shows no error in parameters, but the problem is still the 
same: the fcpci driver doesn't respond and I cannot tell why.


Ok. Thanks for your assistants anyhow. What strikes me as strange ist 
the fact, that turning on verbose helps to circumvent the problem.


Thanks again, and have a good night.
--
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-02 Thread Peer Oliver Schmidt
Hi,

I have installed the above two, and have two questions:

* Is there a reason (or better=a fix), why the chan-capi-1.0.0 does
not compile together with Asterisk 1.4.2?

* Anyone else experiencing problems with chan-capi-HEAD not seeing
the controller? If I run asterisk with verbose setting to 0, i.e.
just asterisk -c chan-capi does not find the controller. Starting
asterisk with verbosity turned up, most of the time the controller is
found.

Might this be a problem of missing CPU power (PII-400)?

Any and all help is greatly appreciated.
-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-02 Thread Armin Schindler
On Mon, 2 Apr 2007, Peer Oliver Schmidt wrote:
 Hi,
 
 I have installed the above two, and have two questions:
 
 * Is there a reason (or better=a fix), why the chan-capi-1.0.0 does
 not compile together with Asterisk 1.4.2?

Actually chan-capi-1.0.0 does compile with Asterisk 1.4.2. The problem is 
that after Asterisk 1.4.1 the asterisk version file was changed and the
chan-capi script to detect the asterisk version does not recognize it.
This problem is fixed in HEAD version of chan-capi, but you can also just
change the line
  if grep -q ASTERISK_VERSION_NUM 0104 $INCLUDEDIR/version.h; then
to
  if grep -q ASTERISK_VERSION_NUM .*104 $INCLUDEDIR/version.h; then
in create_config.sh
 
 * Anyone else experiencing problems with chan-capi-HEAD not seeing
 the controller? If I run asterisk with verbose setting to 0, i.e.
 just asterisk -c chan-capi does not find the controller. Starting
 asterisk with verbosity turned up, most of the time the controller is
 found.
 
 Might this be a problem of missing CPU power (PII-400)?

I don't know where this could happen. Do you have more info on what exactly 
is happening and when?

Armin

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-02 Thread Peer Oliver Schmidt
Hello Armin,

 Actually chan-capi-1.0.0 does compile with Asterisk 1.4.2. [..]but you [..] 
 just
 change the line
   if grep -q ASTERISK_VERSION_NUM 0104 $INCLUDEDIR/version.h; then
 to
   if grep -q ASTERISK_VERSION_NUM .*104 $INCLUDEDIR/version.h; then
 in create_config.sh

thanks, will try.

 * Anyone else experiencing problems with chan-capi-HEAD not seeing
 the controller? If I run asterisk with verbose setting to 0, i.e.
 just asterisk -c chan-capi does not find the controller. Starting
 asterisk with verbosity turned up, most of the time the controller is
 found.

 Might this be a problem of missing CPU power (PII-400)?
 
 I don't know where this could happen. Do you have more info on what exactly 
 is happening and when?


[EMAIL PROTECTED]:~# grep capi /var/log/asterisk/messages

[Mar 31 16:17:03] ERROR[3850] chan_capi.c: Unable to listen on contr1
(error=0x100f)

Is this helpful, or do you need more information?
-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-02 Thread Armin Schindler
On Mon, 2 Apr 2007, Peer Oliver Schmidt wrote:
 Hello Armin,
 
  Actually chan-capi-1.0.0 does compile with Asterisk 1.4.2. [..]but you [..] 
  just
  change the line
if grep -q ASTERISK_VERSION_NUM 0104 $INCLUDEDIR/version.h; then
  to
if grep -q ASTERISK_VERSION_NUM .*104 $INCLUDEDIR/version.h; then
  in create_config.sh
 
 thanks, will try.
 
  * Anyone else experiencing problems with chan-capi-HEAD not seeing
  the controller? If I run asterisk with verbose setting to 0, i.e.
  just asterisk -c chan-capi does not find the controller. Starting
  asterisk with verbosity turned up, most of the time the controller is
  found.
 
  Might this be a problem of missing CPU power (PII-400)?
  
  I don't know where this could happen. Do you have more info on what exactly 
  is happening and when?
 
 
 [EMAIL PROTECTED]:~# grep capi /var/log/asterisk/messages
 
 [Mar 31 16:17:03] ERROR[3850] chan_capi.c: Unable to listen on contr1
 (error=0x100f)
 
 Is this helpful, or do you need more information?

Yes, at this state it might be possible that less CPU power causes
problems. The 'listen' command expects an answer and maybe it is coming too 
late. Can you please try the patch below?

Armin
--

Index: chan_capi.c
===
--- chan_capi.c (revision 436)
+++ chan_capi.c (working copy)
@@ -631,7 +631,7 @@
error = LISTEN_CONF_INFO(CMSG);
break;
}
-   usleep(2);
+   usleep(10);
waitcount--;
}
if (!waitcount)
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] chan-capi-HEAD and Asterisk 1.4.2

2007-04-02 Thread Peer Oliver Schmidt
Hello Armin,

 [EMAIL PROTECTED]:~# grep capi /var/log/asterisk/messages

 [Mar 31 16:17:03] ERROR[3850] chan_capi.c: Unable to listen on contr1
 (error=0x100f)

 Is this helpful, or do you need more information?
 
 Yes, at this state it might be possible that less CPU power causes
 problems. The 'listen' command expects an answer and maybe it is coming too 
 late. Can you please try the patch below?
 
  Index: chan_capi.c
 ===
 --- chan_capi.c   (revision 436)
 +++ chan_capi.c   (working copy)
 @@ -631,7 +631,7 @@
   error = LISTEN_CONF_INFO(CMSG);
   break;
   }
 - usleep(2);
 + usleep(10);

tried the patch, but it did not work. It waits quite a long time
before the chan-capi error message comes up, according to the time
stamp it is about 12 seconds. It is kind of strange, that the whole
startup process for asterisk usually takes only about 4-5 seconds.

Do you need additional information?
-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users