search for: plci

...----------? -- Executing Dial("SIP/200-837b", "CAPI/010xxxxxx:b0478xxxxxx|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 IN...

...hing 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>XXX CallingPartyNumber = <00 a3> CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90...

...ing: 'contr2' 'NULL' '120' 'b' > capi: peerlink -1 allocated, peer is unlinked > CAPI devicestate requested for contr2#02/120 == contr2#02: Call CAPI/contr2#02/120-2 with B3 (pres=0x00, ton=0x00) CONNECT_REQ ID=002 #0x060c LEN=0048 Controller/PLCI/NCCI = 0x2 CIPValue = 0x1 CalledPartyNumber = <80>120 CallingPartyNumber = <00 80>22 CalledPartySubaddress = default CallingPartySubaddress = default BProtocol B1protocol =...

...exten => s,4,capiHOLD() 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...

...for interface 'capicard_primux_2_1' > parsed dialstring: 'capicard_primux_2_1' 'NULL' '017129478262' '' == capicard_primux_2_1: Call CAPI/capicard_primux_2_1/017129478262-2 (pres=0x00, ton=0x00) CONNECT_CONF ID=001 #0x0008 LEN=0014 Controller/PLCI/NCCI = 0x101 Info = 0x0 -- capicard_primux_2_1: received CONNECT_CONF PLCI = 0x101 CONNECT_REQ ID=001 #0x0008 LEN=0058 Controller/PLCI/NCCI = 0x1 CIPValue = 0x10 CalledPartyNumber = <80>01712947...

...et a busy. That is the 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 == S...

...t 25 seconds). I've posted various configs below. Any advice on how to debug would be appreciated. We are located in New Zealand. CLI showing capi debug (just before hangup) -- EICONISDN#02: DATA_B3_IND (len=160) fr.datalen=160 fr.subclass=8 DATA_B3_REQ ID=001 #0x04e1 LEN=0030 Controller/PLCI/NCCI = 0x10201 Data32 = 0x816d494 DataLength = 0xa0 DataHandle = 0x4d9 Flags = 0x0 Data64 = 0x0 DATA_B3_CONF ID=001 #0x04e1 LEN=0016 Controller/PLCI/NCCI...

...bled -- Accepting AUTHENTICATED call from 192.168.1.222, requested format = 2, actual format = 2 -- Executing Dial("IAX2/iax-olcs-brisbane at iax-olcs-brisbane/2", "CAPI/g1/4028") in new stack -- data = g1/4028 -- capi request group = 2 -- creating pipe for PLCI=0 == CAPI Call CAPI/contr1/4028-5 (pres=0x00) CONNECT_REQ ID=002 #0x3f55 LEN=0051 Controller/PLCI/NCCI = 0x1 CIPValue = 0x10 CalledPartyNumber = <80>4028 CallingPartyNumber = <00 80>4074 CalledPartySubaddress...

...recently I changed hardware 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...

...ncoming extensions.conf: [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_IN...

...debug", I see this: -- Executing Dial("SIP/hschurig-c63f", "CAPI/60039141:0170811xxxx|60|T") in new stack -- data = 60039141: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...

hi, I've been running a pure sip asterisk box for a while now with no problems, and i've recently added an isdn2e line from bt in the uk. everything is hooked up and i've got it ringing my sip extensions, but the logs don't quite look perfect and i can't see any description of what i should consider to be normal behaviour. would someone be able to look this over and tell me

...api debug output with verbosity 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 a...

...LI> capi info Contr1: 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...

...called number does not exists. i think that right response should be - line busy tone... right ? can anybody tell me what is wrong ? regards Marian this apear in log : Oct 22 09:22:36 NOTICE[49156]: File chan_capi.c, Line 1813 (capi_handle_msg): CONNECT_IND ID=001 #0x4f00 LEN=0053 Controller/PLCI/NCCI = 0x301 CIPValue = 0x1 CalledPartyNumber = <c1>5430754 CallingPartyNumber = <01 83>0903517715 CalledPartySubaddress = default CallingPartySubaddress = default BC...

...t;0") in new stack -- Executing Dial("SIP/xlite1-3b80", "CAPI/hfcpci/b17") in new stack > data = hfcpci/b17 > capi request for interface 'hfcpci' == hfcpci: Call CAPI/hfcpci/b17-1 (pres=0x00, ton=0x00) -- hfcpci: received CONNECT_CONF PLCI = 0x201 -- Called hfcpci/b17 == hfcpci: Interface cleanup PLCI=0x201 == No one is available to answer at this time (1:0/0/0) == Auto fallthrough, channel 'SIP/xlite1-3b80' status is 'NOANSWER' mISDNUser test tools show ISDN line working (testcon). capi info shows that 2...

...XXXX > parsed dialstring: 'g1' '43XXXXXX' '' > capi request group = 2 > parsed dialstring: 'g1' '43XXXXXX' '' == EICON: Call CAPI/EICON/43XXXXXX-6 (pres=0x00, ton=0x00) CONNECT_REQ ID=001 #0x000c LEN=0065 Controller/PLCI/NCCI = 0x1 CIPValue = 0x10 CalledPartyNumber = <80>43XXXXXX CallingPartyNumber = <00 80 22>EyeBeam<22> <3c>2004<3e> CalledPartySubaddress = default CallingPartySubaddress = defaul...

...added the following lines: [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#0...

...Call Forwarding In 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...

...=immediate isdnmode=ptp devices=30 extensions.conf: [demo] exten => 4132,6,Dial(SIP/test) so, I'm a bit confused now. what can I do??? thanks for helping me out! greetings, Sebastian Capi Debug output: CAPI Debugging Enabled -- CONNECT_IND ID=001 #0x0009 LEN=0050 Controller/PLCI/NCCI = 0x201 CIPValue = 0x10 CalledPartyNumber = <81>4132 CallingPartyNumber = <21 80>03621423132 CalledPartySubaddress = default CallingPartySubaddress = default BC...