search for: 0x101

...xxxx|30") in new stack -- data = 010xxxxxx:b0478xxxxxx -- capi request omsn = 010xxxxxx == found capi with omsn = 010xxxxxx == CAPI Call CAPI[contr1/010xxxxxx]/80 with B3 -- creating pipe for PLCI=-1 -- CONNECT_CONF ID=003 #0x0844 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 -- CONNECT_CONF ID=003 #0x0844 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 == received CONNECT_CONF PLCI = 0x101 INFO = 0 > sent CONNECT_REQ MN =0x844 -- Called 010xxxxxx:b0478xxxxxx --...

...= <00 00> Keypadfacility = default Useruserdata = default Facilitydataarray = default SendingComplete = default -- Called g1/4028 CONNECT_CONF ID=002 #0x3f55 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 == received CONNECT_CONF PLCI = 0x101 INFO = 0 INFO_IND ID=002 #0x5755 LEN=0015 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x800d InfoElement = default INFO_RESP ID=002 #0x5755 LEN=0012 Controller...

...e try from inside to outside: stern01*CLI> -- data = @89930:0107901723168212 -- capi request omsn = @89930 == found capi with omsn = 89930 == CAPI Call CAPI[contr1/89930]/2 == CAPI Call CAPI[contr1/89930]/2 -- CONNECT_CONF ID=003 #0x000d LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 == received CONNECT_CONF PLCI = 0x101 INFO = 0 -- DISCONNECT_IND ID=003 #0x0002 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason = 0x3302 == DISCONNECT_IND PLCI=0x101 REASON=0x3302 == Spawn extension (OutDial-...

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

...dware and my nightmare started. Now when I call someone through the chan_capi (0.3.5 or 0.4.0) it works fine but when I receive calls I always get hungup. Can someone please give some help? Here are the logs: *CLI> -- CONNECT_IND ID=001 #0x0000 LEN=0049 Controller/PLCI/NCCI = 0x101 CIPValue = 0x1 CalledPartyNumber = <a1>1138121122 CallingPartyNumber = A<83>1181114000 CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> L...

...f: [incoming] exten => _XX,1,Playback(demo-abouttotry) exten => _XX,n,Dial,SIP/xlite1 exten => _XX,n,HangUp When call is placed, the following debug info is shown, after the last line, it stalls until caller gives up: INFO_IND ID=001 #0x040a LEN=0016 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x7e InfoElement = <04> > CAPI: no interface for PLCI = 0x101 MN = 0x40a INFO_RESP ID=001 #0x040a LEN=0012 Controller/PLCI/NCCI = 0x101 CAPI: INFO_IND no interface for PLCI=0x101 INFO_IND ID=001 #0x040b LEN=001...

..._von_ntba_primux_immediate_no.txt". This seems to be the same behaviour as someone on this list had this week. So I tried with immediate=yes "eingehend_von_ntba_primux.txt". There is no ringing on my sip phone and chan-capi-cm says capicard_primux_2_1: too much voice to send for NCCI=0x10101 Any hints? Thanks in advance Christian Peter -------------- next part -------------- -- Executing SetCallerID("SIP/10-dec7", "10 <10>") in new stack -- Executing Goto("SIP/10-dec7", "pbx_incoming_ip_telefon_1_autocontext_2|BYEXTENSION|1") i...

...erbosity 15, is shown below. I can see that after the channel identification message and then the sending complete message, a DISCONNECT_IND comes straight after and it does not provide any reasons... CAPI Debugging Enabled CONNECT_IND ID=001 #0x03a6 LEN=0037 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <c1>99546476 CallingPartyNumber = default CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

...: 2 B channels total, 2 B channels free. (looks good) *CLI> capi debug CAPI Debugging Enabled When i call my msn with a normal phone i see the following content: ================================================= -- CONNECT_IND ID=001 #0x0020 LEN=0047 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <c1>523065 CallingPartyNumber = <21 81>6101806124 CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LL...

...9141:01708112001 -- capi request omsn = 60039141 == found capi with omsn = 60039141 == CAPI Call CAPI[contr1/60039141]/1 -- creating pipe for PLCI=-1 > sent CONNECT_REQ MN =0x5 -- Called 60039141:01708112001 -- CONNECT_CONF ID=001 #0x0005 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 -- CONNECT_CONF ID=001 #0x0005 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 == received CONNECT_CONF PLCI = 0x101 INFO = 0 -- DISCONNECT_IND ID=001 #0x0019 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason...

...es: [capi-in] exten => 9876543,1,Goto(demo,1000,1) where 9876543 is my MSN without the area prefix. `demo' is the context that plays `demo-congrats'. The debug output I yield ends with (after a pause) DISCONNECT_IND ID=001 #0x0027 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason = 0x0 DISCONNECT_RESP ID=001 #0x0027 LEN=0012 Controller/PLCI/NCCI = 0x101 -- ISDN1#02: DISCONNECT_IND on incoming without pbx, doing hangup. > CAPI/ISDN1/9876543-2: set channel task to 1 == ISDN1#02: CAPI Hangingup for PL...

...and the following directive in /etc/asterisk/extensions.conf in the context [isdn] [isdn] exten => s,1,Dial(SIP/${DNID:4},60,tr) Here follows the debug info I get when an incoming call starts: ---------------------------------------------------------------------------- == CONNECT_IND (PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1) -- creating pipe for PLCI=0x101 msn = 2810111694 > sent ALERT_REQ PLCI = 0x101 == Starting CAPI[contr1/2810111694]/3 at ,2810111694,1 failed so falling back to exten 's' == Starting CAPI[contr1/2810111694]/3 at ,s,1 st...

...n Asterisk, when an incoming call arrives, it shows me the following: Asterisk Ready. *CLI> capi info Contr1: 2 B channels total, 2 B channels free. *CLI> capi debug CAPI Debugging Enabled *CLI> *CLI> *CLI> -- INFO_IND ID=001 #0x0001 LEN=0016 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x18 InfoElement = <89> -- INFO_IND ID=001 #0x0001 LEN=0016 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x18 InfoElement = <89> Oct 10 09:17:16 NOTICE[5948]: cha...

Hi to all I've mada up my mind and i tried to change from i4l to chan_capi, following some councelling from the gurus. I compiled it up, and when i try to load it in modules.conf, i get that wonderful message and Asterisk does not start: [chan_capi.so]Feb 17 09:21:40 WARNING[16384]: loader.c:239 ast_load_resource: /usr/lib/asterisk/modules/chan_capi.so: undefined symbol: ast_get_group Feb

...eruserdata = default Facilitydataarray = default SendingComplete = <01 00> CAPI: ApplId=0x0002 Command=0x02 SubCommand=0x81 MsgNum=0x0004 NCCI=0x00000101 CONNECT_CONF ID=002 #0x0004 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 -- ISDN1#02: received CONNECT_CONF PLCI = 0x101 -- Called ISDN1/012341234567 CAPI: ApplId=0x0002 Command=0x08 SubCommand=0x82 MsgNum=0x03e7 NCCI=0x00000101 INFO_IND ID=002 #0x03e7 LEN=0015 Controller/PLCI/NCCI = 0x101...

...tried an older version). When using the Capi-Channel, everything works fine except from the sound it sounds extremely choppy and is unusable :-( When e.g. capisuite is used for fax, everything sounds fine... I found the following when using capi debug: ISDN1#02: too much voice to send for NCCI=0x10101 Google finds nothing relevant for this error message :-( Has anybody any idea ? Christoph P.S.: Here is the output of capi debug CONNECT_IND ID=002 #0x016e LEN=0037 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <c1&g...

...es: [capi-in] exten => 9876543,1,Goto(demo,1000,1) where 9876543 is my MSN without the area prefix. `demo' is the context that plays `demo-congrats'. The debug output I yield ends with (after a pause) DISCONNECT_IND ID=001 #0x0027 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason = 0x0 DISCONNECT_RESP ID=001 #0x0027 LEN=0012 Controller/PLCI/NCCI = 0x101 -- ISDN1#02: DISCONNECT_IND on incoming without pbx, doing hangup. > CAPI/ISDN1/9876543-2: set channel task to 1 == ISDN1#02: CAPI Hangingup for PL...

...LD() exten => s,5,capiECT(30:31) #### #### Here's what "capi debug" on the CLI returns: #### *CLI> capi debug CAPI Debugging Enabled *CLI> Jan 20 10:06:31 NOTICE[2051]: chan_capi.c:1870 capi_handle_msg: CONNECT_IND ID=004 #0x0314 LEN=0044 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 C30dPartyNumber = <81>30 CallingPartyNumber = A<80>01722950xxx C30dPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

...0.6 of chan_capi-cm for outgoing calls it works perfectly but for incoming calls it doesn't work. I tried to set an extension to dial my from-pstn context and it works. So I think there's a problem with my capi.conf or something... Here's a debug when calling -- CONNECT_IND (PLCI=0x101,DID=9100,CID=46720XXXX,CIP=0x4,CONTROLLER=0x1) Urgent handler == numeris1: Incoming call '046720XXXX' -> '9100' Urgent handler -- numeris1: info element PI 84 83 Urgent handler -- numeris1: info element CALLED PARTY NUMBER Urgent handler -- numeris1: info element CH...

...e first output of echo-test when I call extension 29 and the call is properly put on "hold". Then phone number 12 rings as expected. However when I pick up phone number 12, the connections are hung up. I derive this from the following output of asterisk -r -vvv: -- CONNECT_IND (PLCI=0x101,DID=29,CID=14,CIP=0x4,CONTROLLER=0x1) == Started pbx on channel CAPI/ISDN1/29-20 -- Executing Answer("CAPI/ISDN1/29-20", "") in new stack -- Executing Wait("CAPI/ISDN1/29-20", "3") in new stack Apr 2 00:16:41 WARNING[11926]: channel.c:1591 ast_wait...