Displaying 20 results from an estimated 61 matches for "hangingup".
Did you mean:
hanging
2006 May 01
1
/var/spool/asterisk/outgoing/ prematurely hangingup
...cAllister
-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Tom
Engleward
Sent: Monday, May 01, 2006 11:43 PM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] /var/spool/asterisk/outgoing/ prematurely
hangingup
I have a PSTN termination provider "foo" which will
accept standard U.S. calls in the form 1<10 digit
ph#>.
I have an outbound route named "foo", with dial
pattern "5|.", with the only entry in trunk sequence
being "IAX2/foo".
I have an X-lite local e...
2005 Jun 04
2
Zap channel not hangingup
Hi,
I am setting up a test call center using *. I am using one Zap channel
(Wildcard TDM400P REV E/F -- 4 FXO modules) for incoming call and sip
phones (SjPhone) for call agents. I have setup queues and agents. While
testing I found that if the agent presses * key in soft phone while
attending calls Zap channel gets hung up, and another customer can call.
But if the caller hangs up (for example
2005 Oct 08
2
No incoming calls from chan_capi 0.6
...39;9100'
Urgent handler
-- numeris1: info element PI 84 83
Urgent handler
-- numeris1: info element CALLED PARTY NUMBER
Urgent handler
-- numeris1: info element CHANNEL IDENTIFICATION 89
Urgent handler
-- numeris1: info element Sending Complete
Urgent handler
== numeris1: CAPI Hangingup
Urgent handler
== numeris1: Interface cleanup PLCI=0x101
Urgent handler
-- 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...
2007 Jul 26
2
ISDN: Problems starting off
...= 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=0x101
> CAPI devicestate requested for ISDN1/9876543
Seems that the MSN or even `capi-in' cannot be found at all.
Could anyone give me a hint what is going wrong here or at
least what I have to diagnose next?
Than...
2006 Oct 23
4
Problems with chan-capi and Eicon Diva 4BRI
...channel
name: CAPI/ISDN4/1-8ab9
Oct 20 17:18:19 VERBOSE[2663] logger.c: -- ISDN4#02: Updated channel
name: CAPI/ISDN4/11-8aba
Oct 20 17:18:26 VERBOSE[19772] logger.c: > ISDN4#02: CAPI INFO
0x34e6: Recovery on timer expiry
Oct 20 17:18:26 VERBOSE[2663] logger.c: == ISDN4#02: CAPI Hangingup
for PLCI=0x104 in state 4
Oct 20 17:18:26 VERBOSE[2663] logger.c: == Everyone is busy/congested
at this time (1:0/0/1)
Oct 20 17:18:26 VERBOSE[2663] logger.c: -- Executing
Hangup("CAPI/ISDN2/32xx11-8ab8", "") in new stack
Oct 20 17:18:26 VERBOSE[2663] logger.c: == Spa...
2003 Apr 09
0
can't use both controllers...
...I=-1
== sent CONNECT_REQ MN =0xc53d
== received CONNECT_CONF PLCI = 0x302 INFO = 0
-- Called 22545066:b90044875
== DISCONNECT_IND PLCI=0x302 REASON=0x34a2
STATE = 0x5
-- CAPI[contr2/] is busy
== Everyone is busy at this time
NOTICE[7061521]: File chan_capi.c, Line 414 (capi_hangup): hangingup
-- removed pipe for PLCI = 0x302
-- Executing Dial("SIP/torgeir-b476",
"CAPI/22545060:bBYEXTENSION|120|Ttr") in new stack
== data = 22545060:b90044875
== capi request omsn = 22545060
NOTICE[7061521]: File chan_capi.c, Line 884 (capi_request): didn't find capi
d...
2006 Dec 13
1
Diva Server V-BRI-2 and internal numbers
...ternal phone, heres the logs from asterisk:
-- Executing Dial("SIP/Greg-081f5a10", "CAPI/ISDN1/b:107||rtT") in new
stack
-- Called ISDN1/b:107
-- CAPI/ISDN1/107-1a is proceeding passing it to SIP/Greg-081f5a10
-- CAPI/ISDN1/107-1a is busy
== ISDN1: CAPI Hangingup
== Everyone is busy/congested at this time (1:1/0/0)
-- Executing Hangup("SIP/Greg-081f5a10", "") in new stack
== Spawn extension (macro-appel_sortant, s, 2) exited non-zero on
'SIP/Greg-081f5a10' in macro 'appel_sortant'
== Spawn extension (macro-a...
2007 Jul 12
0
No subject
1. If the other end picks up the phone the conversation is successful and when
the conversation ends, the channel is properly released:
-- CAPI/ISDN1#02/2104988888-0 answered SIP/1000-081d91b0
== ISDN1#02: CAPI Hangingup for PLCI=0x101 in state 2
== Spawn extension (internal, 2104988888, 1) exited non-zero on
'SIP/1000-081d91b0'
> ISDN1#02: CAPI INFO 0x3490: Normal call clearing
2. BUT: If I hangup the softphone before someone answers, I get:
== ISDN1#02: CAPI Hangingup for PLCI=0x101 in sta...
2007 Sep 13
1
SMS in France - allways get "NAK"
...> Channel CAPI/ISDN4#02/0809101000-1 was answered.
> Launching SMS(0) on CAPI/ISDN4#02/0809101000-1
-- SMS RX 93 00 6D
-- SMS TX 91 0D 01 01 0A 81 60 70 93 66 66 00 F1 01 58 5C
-- SMS RX 96 0A 01 A0 00 70 90 31 51 54 45 80 24
-- SMS TX 94 00 6C
== ISDN4#02: CAPI Hangingup for PLCI=0x104 in state 2
[Sep 13 15:45:58] NOTICE[23584]: pbx_spool.c:371 attempt_thread: Call completed to CAPI/g1/0809101000
> ISDN4#02: CAPI INFO 0x3495: Call rejected
As I understand it the "RX 96" is FT NAK'ing my "TX 91" "DELIVER".
Any idea what...
2005 Sep 29
1
chan_cap-cm-0.6 is not working for incomming calls
...9903xxxx' -> '97'
-- reventix: info element CALLED PARTY NUMBER
-- reventix: info element CHANNEL IDENTIFICATION 89
Urgent handler
-- reventix: info element CALLED PARTY NUMBER
-- reventix: info element CHANNEL IDENTIFICATION 89
Urgent handler
== reventix: CAPI Hangingup
== reventix: Interface cleanup PLCI=0x101
Urgent handler
--- snap ---
--- snip: capi.conf ---
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
;ulaw=yes
[reventix]
;ntmode=yes
isdnmode=msn
incomingmsn=*
controller=1
group=1
;prefix=0
softdtmf=on
relaxdtmf=on
accountcode=...
2003 Sep 03
1
SIP to CAPI problem
...up I don't get any
communication and the SIP client stay in its
"trying..." state.
Here is what the * consol shows:
-- Executing Dial("SIP/1000-ce58",
"CAPI/32:076XXXXXX|tr") in new stack
-- creating pipe for PLCI=-1
-- Called 32:076XXXXXX
-- CAPI Hangingup
-- Setting up echo canceller (PLCI=0x101,
function=1, options=2, tail=64)
-- Echo canceller successfully set up (PLCI=0x101)
-- removed pipe for PLCI = 0x201
nothing more. What is happening? Ideas?
Can anybody help?`
=Ben=
___________________________________________________________
D...
2007 Jul 27
1
ISDN: Problems starting off [another attempt]
...= 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=0x101
> CAPI devicestate requested for ISDN1/9876543
Seems that the MSN or even `capi-in' cannot be found at all.
Could anyone give me a hint what is missing here or at
least what I have to diagnose next?
Thanks i...
2004 May 24
1
SetVar - bellcode and cisco phone
...;)
in new stack
-- Executing Dial("CAPI[contr1/s]/0", "SIP/22|35|t") in new stack
-- Called 22
-- started pbx on channel (callgroup=2)!
-- SIP/22-e97c is ringing
== Spawn extension (incoming, s, 2) exited non-zero on
'CAPI[contr1/s]/0'
-- CAPI Hangingup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040524/d74529a3/attachment.htm
2004 Jun 28
2
sip to isdn-capi call problem
...channel 'SIP/102-767c' failed
Jun 28 10:51:21 NOTICE[278545]: channel.c:1621 ast_set_write_format:
Unable to find a path from SLINR to G723
Jun 28 10:51:21 WARNING[278545]: indications.c:76 playtones_alloc:
Unable to set 'SIP/102-767c' to signed linear format (write)
-- CAPI Hangingup
== Spawn extension (from-sip, 9, 1) exited non-zero on 'SIP/102-767c'
2006 Jan 16
1
chan_capi-cm and DID
...ECT_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
incomingmsn=*
softdtmf=on
relaxdtmf=on
accountcode=
context=DID
echocancel=yes
;echocancelold=yes
devices=2
group=1
___________________________...
2006 Jan 27
1
No IN and OUT on ISDN line at the same time?
...xxx' -> '83086921'
-- Executing Dial("CAPI/ISDN1/83086921-0", "CAPI/ISDN1/zzzzzzzz|20|tr") in new stack
-- Called ISDN1/zzzzzzzzzz
> CAPI INFO 0x34a2: No circuit / channel available
-- CAPI/ISDN1/zzzzzzzzzzz-1 is circuit-busy
== ISDN1: CAPI Hangingup
== Everyone is busy/congested at this time
;/etc/asterisk/capi.conf
; chan_capi_cm with EICON 2BRI
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
language=de
[ISDN1]
incomingmsn=83086920,83086921
isdnmode=msn
group=1
controller=1
softdtmf=1
context=demo
echosquelch=1
e...
2006 Feb 11
4
Problem with Wait() and chan_capi-cm?
...in new stack
== ISDN1: Answering for 12345
-- Executing Milliwatt("CAPI/ISDN1/12345-19", "") in new stack
> CAPI INFO 0x34d1: Invalid call reference value
== Spawn extension (capi-in, 12345, 3) exited non-zero on
'CAPI/ISDN1/12345-19'
== ISDN1: CAPI Hangingup
If I try that in a pure sip-context, it works as I thought it would.
Now: do I do something wrong? Is there a problem with the Wait()
application? Or is that more likely a bug in chan_capi-cm?
Regards, Florian.
2005 Aug 26
1
bridging sip to capi, no playtones back to caller
...ro on
'SIP/2.7.184.61-08152880'
asterisk-pri-1:/etc/asterisk # cat extensions.conf
[general]
static=yes
writeprotect=yes
[globals]
[default]
exten => _X.,1,Playtones(ring)
exten => _X.,2,Dial,CAPI/0226265583:${EXTEN}
exten => _X.,3,HangupSIP/2.7.184.61-08152880
-- CAPI Hangingup
> sent DISCONNECT_B3_REQ NCCI=0x10101
> sent DISCONNECT_REQ PLCI=0x101
-- removed pipe for PLCI = 0x101
asterisk-pri-1:/etc/asterisk # cat sip.conf
[general]
context=default
port=5060
bindaddr=192.168.1.101
srvlookup=no
canreinvite=no
disallow=all...
2005 Mar 13
5
possible bug in chan_capi concerning context handling
...CAPI[contr1/2810111694]/3 at ,s,1 still failed so falling
back to context 'default'
Mar 13 11:52:41 WARNING[10744]: pbx.c:1893 ast_pbx_run: Channel
'CAPI[contr1/2810111694]/3' sent into invalid extension 's' in context
'default', but no invalid handler
-- CAPI Hangingup
-----------------------------------------------------------------------------
When I move the "exten => s,1,Dial(${DNID:4},60,tr)" in the context
"[default]" of the /etc/asterisk/extensions.conf, I get the following
debug info and the sip phone rings ok:
-----------------...
2004 Jun 24
5
chan_capi problem - hangup???
...IND
(PLCI=0x101,DID=**some_number**,CID=**some_number**,CIP=0x10,CONTROLLER=0x1)
Jun 24 22:19:49 WARNING[1086696368]: pbx.c:1819 ast_pbx_run: Channel
'CAPI[contr1/**some_number**]/0' sent into invalid extension '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 archiv...