Displaying 19 results from an estimated 19 matches for "disconnect_resp".
Did you mean:
disconnect_req
2007 Jul 26
2
ISDN: Problems starting off
...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 PLCI=0x101 in state 4
== ISDN1#02: Interface cleanup PLCI=0...
2007 Jul 27
1
ISDN: Problems starting off [another attempt]
...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 PLCI=0x101 in state 4
== ISDN1#02: Interface cleanup PLCI=0...
2006 Jan 16
1
chan_capi-cm and DID
...XXXXX
CONNECT_CONF ID=001 #0x000c LEN=0014
Controller/PLCI/NCCI = 0x201
Info = 0x0
-- EICON: received CONNECT_CONF PLCI = 0x201
DISCONNECT_IND ID=001 #0x0011 LEN=0014
Controller/PLCI/NCCI = 0x201
Reason = 0x3302
DISCONNECT_RESP ID=001 #0x0011 LEN=0012
Controller/PLCI/NCCI = 0x201
> CAPI INFO 0x3302: Protocol error layer 2
== EICON: CAPI Hangingup
== EICON: Interface cleanup PLCI=0x201
== No one is available to answer at this time
my capi.conf looks like:
[DID]
controller=1,2,3,4
isdnmode=did...
2004 Jun 07
6
chan_capi and DDI (Anlagenanschluss)
.../PLCI/NCCI = 0x101
Info = 0x0
== received CONNECT_CONF PLCI = 0x101 INFO = 0
-- DISCONNECT_IND ID=001 #0x0019 LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3302
== DISCONNECT_IND PLCI=0x101 REASON=0x3302
> sent DISCONNECT_RESP PLCI=0x101
-- CAPI Hangingup
-- removed pipe for PLCI = 0x101
== No one is available to answer at this time
Is there any source where I can lookup what "REASON=0x3302" means?
--
M&N Solutions GmbH http://www.mn-solutions.de
Holger Schurig
Dieselstr. 18
61191 Rosbach v.d....
2005 Jul 15
2
Strange problem with SIP and CAPI
...D=003 #0x0863 LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
-- DISCONNECT_IND ID=003 #0x8146 LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3400
== DISCONNECT_IND PLCI=0x101 REASON=0x3400
> sent DISCONNECT_RESP PLCI=0x101
-- removed pipe for PLCI = 0x101
== Spawn extension (intern, 00478xxxxxx, 1) exited non-zero on
'SIP/200-837b'
----------------------------------------------------------------------------
---------------------------------------------------
International :
----------------...
2005 Oct 06
0
chan_capi configuration with AVM C2 card
...FO = 0
Oct 6 20:04:23 VERBOSE[12454]: -- DISCONNECT_IND ID=001 #0x0003
LEN=0014
Controller/PLCI/NCCI = 0x202
Reason = 0x3302
Oct 6 20:04:23 VERBOSE[12454]: == DISCONNECT_IND PLCI=0x202 REASON=0x3302
Oct 6 20:04:23 VERBOSE[12454]: > sent DISCONNECT_RESP PLCI=0x202
Oct 6 20:04:23 VERBOSE[12454]: -- CAPI Hangingup
TIA
jd
--
John Daragon john@argv.co.uk
argv[0] limited
Lambs Lawn Cottage, Staple Fitzpaine, Taunton, TA3 5SL, UK
v +44 (0) 1460 234068 f +44 (0) 1460 234069 m +44 (0) 7836 576127
2005 Aug 24
2
Error when answering CAPI
...= 0x18
InfoElement = <89>
> sent INFO_RESP (PLCI=0x101)
-- DISCONNECT_IND ID=001 #0x0003 LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x0
== DISCONNECT_IND PLCI=0x101 REASON=0
> sent DISCONNECT_RESP PLCI=0x101
-- CAPI Hangingup
> activehangingup
-- removed pipe for PLCI = 0x101
capi.conf
=======
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
[interfaces]
; mode: ptmp (point-to-multipoint) or ptp (point-to-point)
isdnmode=ptp
;...
2006 Jun 04
5
chan_capi-cm-0.6 and incoming calls problem
...BChannelinformation = default
Keypadfacility = default
Useruserdata = default
Facilitydataarray = default
DISCONNECT_IND ID=001 #0x03aa LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x0
DISCONNECT_RESP ID=001 #0x03aa LEN=0012
Controller/PLCI/NCCI = 0x101
== ISDN1: CAPI Hangingup
== ISDN1: Interface cleanup PLCI=0x101
I will apreciate your assistance
Esteban
_________________________________________________________________
New year, new job – there's more than 100,00 jobs...
2004 Jan 20
4
CAPI: Early-B3 working with AVM-B1?
...ND NCCI=0x10101
> sent DISCONNECT_B3_RESP NCCI=0x10101
> sent DISCONNECT_REQ PLCI=0x101
-- DISCONNECT_CONF ID=001 #0x001b LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
== DISCONNECT_IND PLCI=0x101 REASON=0x3495
> sent DISCONNECT_RESP PLCI=0x101
-- removed pipe for PLCI = 0x101
-------
Hardware is a AVM-B1 (active BRI card)
What am I doing wrong, or where can I start debugging?
Thanks,
Karsten
2005 Sep 19
0
Call dropped 100% of time when incoming IAX routed to outgoing CAPI
...02 89 d2 02 01 22>0<0a a1
05>0<03 02 01 00 82 01 01>
INFO_RESP ID=002 #0x575b LEN=0012
Controller/PLCI/NCCI = 0x101
== info element FACILITY
DISCONNECT_IND ID=002 #0x575c LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3490
DISCONNECT_RESP ID=002 #0x575c LEN=0012
Controller/PLCI/NCCI = 0x101
-- removed pipe for PLCI = 0x101
If you would like some additional info, email me direct
(christopher.mylonas at olcs.com.au) and I'll send whatever you need to the
mailing list and/or to your own email.
Kind Regards,
Ch...
2006 Feb 23
2
chan_capi-cm-0.6.4
...ER=0x1)
> ISDN1: msn='*' DNID='11' DID
== ISDN1: Incoming call '0650621XXXX' -> '11'
-- Remote UNIX connection disconnected
DISCONNECT_IND ID=001 #0x074a LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3301
DISCONNECT_RESP ID=001 #0x074a LEN=0012
Controller/PLCI/NCCI = 0x101
> CAPI INFO 0x3301: Protocol error layer 1 (broken line or B-channel removed by signalling protocol)
-- ISDN1: DISCONNECT_IND on incoming without pbx, doing hangup.
== ISDN1: CAPI Hangingup
== ISDN1: Interface clea...
2007 Jul 24
0
Diva Server BRI hangs up after about 25 seconds
...a
InfoElement = default
INFO_RESP ID=001 #0x04f2 LEN=0012
Controller/PLCI/NCCI = 0x201
-- EICONISDN#02: info element RELEASE COMPLETE
DISCONNECT_IND ID=001 #0x04f4 LEN=0014
Controller/PLCI/NCCI = 0x201
Reason = 0x3490
DISCONNECT_RESP ID=001 #0x04f4 LEN=0012
Controller/PLCI/NCCI = 0x201
> EICONISDN#02: CAPI INFO 0x3490: Normal call
clearing
== EICONISDN#02: Interface cleanup PLCI=0x201
/usr/lib/divas/Config
Interface mode: TE (verified)
D Channel: ETSI-DSS1 (verified)
NT-2 mode: No
D-Channel Layer act...
2006 Jan 13
2
PrimuX Cards with chan_capi-cm
...CIP=0x1,CONTROLLER=0x1)
> capicard_primux_2_1: msn='309874' DNID='309874' MSN
== capicard_primux_2_1: Incoming call '' -> '309874'
DISCONNECT_IND ID=001 #0x8001 LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x0
DISCONNECT_RESP ID=001 #0x8001 LEN=0012
Controller/PLCI/NCCI = 0x101
-- capicard_primux_2_1: DISCONNECT_IND on incoming without pbx, doing hangup.
== capicard_primux_2_1: CAPI Hangingup
== capicard_primux_2_1: Interface cleanup PLCI=0x101
-------------- next part --------------
CONNECT_IND I...
2007 Sep 13
1
fax machine detection for outgoing call on DIVA card
...= 0x804d
InfoElement = default
INFO_RESP ID=002 #0x094d LEN=0012
Controller/PLCI/NCCI = 0x302
-- contr2#02: info element RELEASE
DISCONNECT_IND ID=002 #0x094f LEN=0014
Controller/PLCI/NCCI = 0x302
Reason = 0x3490
DISCONNECT_RESP ID=002 #0x094f LEN=0012
Controller/PLCI/NCCI = 0x302
> contr2#02: CAPI INFO 0x3490: Normal call clearing
== contr2#02: Interface cleanup PLCI=0x302
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
2005 Sep 02
2
chan_capi hfcpci mISDN linux 2.6.12 not working
Hello,
These are error messages I get when I try to call a number over CAPI channel.
-- Executing SetCallerID("SIP/xlite1-3b80", "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,
2005 Dec 30
3
using a Gigaset SX440isdn on a Diva 4BRI ?
Hello,
I just received a couple SX440isdn phones and was wondering if they can
be plugged into a Diva 4BRI port in NT mode and work with
asterisk+chan_capi?
I know they probably work fine with mutliHFC cards with either bristuff
of chan_misdn but since I have some spare Divas, I was curious about
their potential as phone ports.
The Diva's 3 and 4 ports are already set to NT mode at boot
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 Mar 18
1
Choppy sound with chan_capi + Fritz Card USB
...efault
SendingComplete = default
DISCONNECT_CONF ID=002 #0x0194 LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
DISCONNECT_IND ID=002 #0x0197 LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3490
DISCONNECT_RESP ID=002 #0x0197 LEN=0012
Controller/PLCI/NCCI = 0x101
> ISDN1#02: CAPI INFO 0x3490: Normal call clearing
== ISDN1#02: Interface cleanup PLCI=0x101