search for: infoelement

Displaying 20 results from an estimated 22 matches for "infoelement".

2005 Jul 15
2
Strange problem with SIP and CAPI
...= 0x101 Info = 0x0 == received CONNECT_CONF PLCI = 0x101 INFO = 0 > sent CONNECT_REQ MN =0x844 -- Called 010xxxxxx:b0478xxxxxx -- INFO_IND ID=003 #0x811c LEN=0015 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x8002 InfoElement = default -- INFO_IND ID=003 #0x811c LEN=0015 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x8002 InfoElement = default > sent INFO_RESP (PLCI=0x101) -- INFO_IND ID=003 #0x811d LEN=0016 Controller/PLCI/...
2007 Sep 13
1
fax machine detection for outgoing call on DIVA card
...r2/120/b CONNECT_CONF ID=002 #0x060c LEN=0014 Controller/PLCI/NCCI = 0x302 Info = 0x0 -- contr2#02: received CONNECT_CONF PLCI = 0x302 INFO_IND ID=002 #0x0687 LEN=0017 Controller/PLCI/NCCI = 0x302 InfoNumber = 0x1e InfoElement = <81 88> INFO_RESP ID=002 #0x0687 LEN=0012 Controller/PLCI/NCCI = 0x302 -- contr2#02: info element PI 81 88 > contr2#02: In-band information available CONNECT_B3_REQ ID=002 #0x060d LEN=0013 Controller/PLCI/NCCI = 0x302 NCPI...
2004 Jan 20
0
chan_capi capiECT
...ND (PLCI=0x101,DID=30,CID=01722950xxx,CIP=0x10,CONTROLLER=0x1) -- Executing Wait("CAPI[contr1/30]/0", "1") in new stack -- started pbx on channel! -- INFO_IND ID=004 #0x0315 LEN=0018 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <81>30 -- INFO_IND ID=004 #0x0316 LEN=0016 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x18 InfoElement = <89> -- ALERT_CONF ID=004 #0x0314 LEN=0014 Controller/PLCI/NCCI = 0x101 Info...
2004 Nov 27
2
capi question
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
2005 Sep 19
0
Call dropped 100% of time when incoming IAX routed to outgoing CAPI
...ed 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/PLCI/NCCI = 0x101 == info element SETUP ACK INFO_IND ID=002 #0x5756 LEN=0017 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x1e InfoElement = <81 88&g...
2005 Jan 05
0
Problems with msn's, did not find device for msn
...efault Useruserdata = default Facilitydataarray = default == CONNECT_IND (PLCI=0x201,DID=4132,CID=03621423132,CIP=0x10,CONTROLLER=0x1) -- INFO_IND ID=001 #0x000a LEN=0020 Controller/PLCI/NCCI = 0x201 InfoNumber = 0x70 InfoElement = <81>4132 2005-01-05 15:41:32 ERROR[31716]: chan_capi.c:1696 pipe_msg: did not find device for msn = 4132 -- INFO_IND ID=001 #0x000b LEN=0018 Controller/PLCI/NCCI = 0x201 InfoNumber = 0x18 InfoElement = <a9...
2005 Aug 24
2
Error when answering CAPI
...t AdditionalInfo = default == CONNECT_IND (PLCI=0x101,DID=1138121122,CID=1181114000,CIP=0x1,CONTROLLER=0x1) -- creating pipe for PLCI=0x101 msn = * -- INFO_IND ID=001 #0x0001 LEN=0026 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <a1>1138121122 -- INFO_IND ID=001 #0x0001 LEN=0026 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <a1>1138121122 > sent INFO_RESP (PLCI=0x101) > sent CONNECT_RESP for...
2003 Oct 22
0
capi incoming call
...2:36 ERROR[49156]: File chan_capi.c, Line 1111 (find_pipe): unable to find a pipe for PLCI = 0x301 MN = 0x4f01 Oct 22 09:22:36 NOTICE[49156]: File chan_capi.c, Line 1211 (pipe_msg): INFO_IND ID=001 #0x4f01 LEN=0023 Controller/PLCI/NCCI = 0x301 InfoNumber = 0x70 InfoElement = <c1>5430754 Oct 22 09:22:36 ERROR[49156]: File chan_capi.c, Line 1111 (find_pipe): unable to find a pipe for PLCI = 0x301 MN = 0x4f02 Oct 22 09:22:36 NOTICE[49156]: File chan_capi.c, Line 1211 (pipe_msg): INFO_IND ID=001 #0x4f02 LEN=0016 Controller/PLCI/NCCI...
2005 Feb 21
1
Problem with ISDN Dialin via CAPI
...CONNECT_IND (PLCI=0x101,DID=523065,CID=6101806124,CIP=0x10,CONTROLLER=0x1) Feb 21 11:32:30 ERROR[384]: chan_capi.c:2051 capi_handle_msg: did not find device for msn = 523065 -- INFO_IND ID=001 #0x0021 LEN=0022 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <c1>523065 Feb 21 11:32:30 ERROR[384]: chan_capi.c:1198 find_pipe: unable to find a pipe for PLCI = 0x101 MN = 0x21 Feb 21 11:32:30 NOTICE[384]: chan_capi.c:1302 pipe_msg: INFO_IND ID=001 #0x0021 LEN=0022 Controller/PLCI/NCCI = 0x101 InfoNumber...
2005 Oct 10
2
AVM Fritz! + chan_capi + mISDN + PTP
...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]: chan_capi.c:1184 find_pipe: PLCI doesnt match last pipe (P...
2006 Jan 26
3
Chan_capi on builds 7955>8320 strangeness
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
2006 Jun 04
5
chan_capi-cm-0.6 and incoming calls problem
...I=0x101,DID=99546476,CID=(null),CIP=0x10,CONTROLLER=0x1) > ISDN1: msn='*' DNID='99546476' MSN == ISDN1: Incoming call '' -> '99546476' INFO_IND ID=001 #0x03a7 LEN=0024 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <c1>99546476 INFO_RESP ID=001 #0x03a7 LEN=0012 Controller/PLCI/NCCI = 0x101 -- ISDN1: info element CALLED PARTY NUMBER > ISDN1: INFO_IND DID digits not used in this state. INFO_IND ID=001 #0x03a8 LEN=0016 Controller/PLCI/NCCI = 0...
2005 Sep 05
6
asterisk CAPI dial-in issues
...uttotry) 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=0016 Controller/PLCI/NCCI = 0x101 InfoNumbe...
2010 Mar 09
0
Asterisk 1.6.2.5 crash with chan_capi upon calling to PSTN
...-- 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 InfoNumber = 0x8002 InfoElement = default INFO_RESP ID=002 #0x03e7 LEN=0012 Controller/PLCI/NCCI = 0x101 -- ISDN1#02: info element CALL PROCEEDING -- chan_capi queue frame: TYPE: Control (4) SUBCLASS: Unknown control '15' (15) ] [ISDN1#02] CAPI: ApplId=0x0002 Com...
2007 Mar 18
1
Choppy sound with chan_capi + Fritz Card USB
...TROLLER=0x1) > ISDN1#02: msn='*' DNID='XXX' MSN == ISDN1#02: setting format alaw - 0x8 (alaw) == ISDN1#02: Incoming call '' -> 'XXX' INFO_IND ID=002 #0x016f LEN=0017 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x1e InfoElement = <80 83> INFO_RESP ID=002 #0x016f LEN=0012 Controller/PLCI/NCCI = 0x101 -- ISDN1#02: info element PI 80 83 > ISDN1#02: Origination is non ISDN INFO_IND ID=002 #0x0170 LEN=0022 Controller/PLCI/NCCI = 0x101 InfoNumber...
2004 Feb 17
5
chan_capi problem
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
2007 Jul 24
0
Diva Server BRI hangs up after about 25 seconds
...= 0x0 DATA_B3_CONF ID=001 #0x04e2 LEN=0016 Controller/PLCI/NCCI = 0x10201 DataHandle = 0x4da Info = 0x0 INFO_IND ID=001 #0x04ee LEN=0017 Controller/PLCI/NCCI = 0x201 InfoNumber = 0x8 InfoElement = <82 90> INFO_RESP ID=001 #0x04ee LEN=0012 Controller/PLCI/NCCI = 0x201 -- EICONISDN#02: info element CAUSE 82 90 INFO_IND ID=001 #0x04ef LEN=0015 Controller/PLCI/NCCI = 0x201 InfoNumber = 0x8045 InfoElement...
2004 Jun 24
5
chan_capi problem - hangup???
...ension 's' in context 'default', but no invalid handler -- CAPI Hangingup > activehangingup -- started pbx on channel (callgroup=0)! -- INFO_IND ID=002 #0x011e LEN=0023 Controller/PLCI/NCCI = 0x101 InfoNumber = 0x70 InfoElement = <c1>**some_number** I read in the mailing list archives of commenting out line 2615 in chan_capi.c, but that did not change anything. Has anybody got an idea what the error: "Channel 'CAPI[contr1/**some_number**]/0' sent into invalid extension 's...
2005 Mar 07
2
SIP and ISDN
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
2005 Feb 21
0
[SOLVED] Problem with ISDN Dialin via CAPI
...23065,CID=6101806124,CIP=0x10,CONTROLLER=0x1) > Feb 21 11:32:30 ERROR[384]: chan_capi.c:2051 capi_handle_msg: did not find > device for msn = 523065 > -- INFO_IND ID=001 #0x0021 LEN=0022 > Controller/PLCI/NCCI = 0x101 > InfoNumber = 0x70 > InfoElement = <c1>523065 I think the outgoingmsn is missing / the one you are looking for > > > Here are my entries of /etc/asterisk/capi.conf: > ================================= > ; CAPI config > ; > [general] > nationalprefix=0 > internationalprefix=00...