search for: cipvalue

...annels 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> LLC...

...NOTICE[5948]: chan_capi.c:1301 pipe_msg: INFO_IND ID=001 #0x0001 LEN=0016 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x18 InfoElement = <89> -- CONNECT_IND ID=001 #0x0002 LEN=0044 Controller/PLCI/NCCI = 0x101 CIPValue = 0x1 CalledPartyNumber = <81>20 CallingPartyNumber = <01 83>0123456789 CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

...=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 = <80 90 a3> LLC...

...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>017129478262 CallingPartyNumber = <00 80>309874 CalledPartySubaddress = default CallingPartySubaddress = default BProtocol B1protocol = 0x1 B2protocol...

...gt; *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...

...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 = <80 90 a3> LLC...

...tring: '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 = default BProtocol B1protocol...

...rything works fine while starting Asterisk, but when a call comes in Asterisk hangsup the call after two times of ringing. The output is like: Jun 24 22:19:49 NOTICE[1082178480]: chan_capi.c:1931 capi_handle_msg: CONNECT_IND ID=002 #0x011d LEN=0048 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <c1>**some_number** CallingPartyNumber = <21 83>**some_number** CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3&...

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

...lement = <89> > CAPI: no interface for PLCI = 0x101 MN = 0x40b INFO_RESP ID=001 #0x040b LEN=0012 Controller/PLCI/NCCI = 0x101 CAPI: INFO_IND no interface for PLCI=0x101 CONNECT_IND ID=001 #0x040c LEN=0038 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <81>61 CallingPartyNumber = <09 80>17 CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/bmp Size: 2918 bytes Desc: Picture (Metafile) Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050307/cb404791/attachment.bmp

...en => 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...

...fos I need to know about chan_sip.c >> (because I suppose it's it that I need to play with)? > >Some stuff is already there. This is a "capi debug" trace where i SEND >UUS1 from a normal ISDN Phone TO an asterisk: > > Controller/PLCI/NCCI = 0x101 > CIPValue = 0x10 > CalledPartyNumber = <c1>5559999 > CallingPartyNumber = <01 81>5551234 > CalledPartySubaddress = default > CallingPartySubaddress = default > BC = <80 90 a3&g...

...app_dial.c:674 dial_exec: Unable to create channel of type 'CAPI' == Everyone is busy at this time -------------------------------- ISDN to * May 25 19:18:59 NOTICE[81926]: chan_capi.c:1895 capi_handle_msg: CONNECT_IND ID=003 #0x0038 LEN=0035 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <81>41 CallingPartyNumber = A<80>30 CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

...d 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> LLC...

...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...

...X2/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 = default CallingPartySubaddress = default BProtocol B1protocol = 0x1 B2protocol...

...= <89> INFO_RESP ID=001 #0x0748 LEN=0012 Controller/PLCI/NCCI = 0x101 CAPI: INFO_IND no interface for PLCI=0x101 > CAPI: Command=INFO_IND,0x8492: no interface for PLCI=0x101, MSGNUM=0x748! CONNECT_IND ID=001 #0x0749 LEN=0046 Controller/PLCI/NCCI = 0x101 CIPValue = 0x10 CalledPartyNumber = <81>11 CallingPartyNumber = <21 83>650621XXXX CalledPartySubaddress = default CallingPartySubaddress = default BC = <80 90 a3> LLC...

...LL' '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 = 0x1 B2protocol...

Hello All, I am having an odd problem with Armin's chan-capi_cm on builds higher than 7955. It would seem that this happens on anything higher than 7955. What is happening is the isdn is ringing, then asterisk does a goto-if and just hangs. Asterisk itself is ok, but the isdn then rings out or busys out on the other side. Outgoing works fine, this only seems to effect incoming. I