[asterisk-users] AMI Queue information about incoming call's channel before link

2010-06-09 Thread Alexandr Krylovskiy 
Hi,
I'm developing an application using AMI and I need to get information
about incoming call _before_ queue member answers it.
I'm using static members (queue is pretty simple) and don't want to use
chan_agent (I think AgentCalled event will do what I'm looking for).

Here is what I'm getting now:
1. Newchannel event for incoming call followed by Newstate and Join. All these
events can be identified with uniqueid 001
2. Newchannel event for outgoing channel to queue member followed by Newstate
State: Ringing = that's what I need. But this channel (of course) has another
uniquied 002.
3. Link. That's the place where channels are get bridged and I can find out
which member (by channel) answered the call (002 answered 001 in this example).

The problem is that I need to get information about call 001 at stage 2 that
is currently possible only at stage 3, when channels get bridged.
Any ideas?

-- 
Alexandr Krylovskiy

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] DAHDI User-User information Message longer than it should be??

2010-04-22 Thread Alexandr Krylovskiy 
 Hi.
 My configuration is Elastix 1.5.2-2 (asterisk 1.4.24, libpri-1.4.3-5,
dahdi-2.1.0.4-7 ) and OpenVox d210e connected to telco provider (Euro ISDN).

Here is my /etc/dahdi/system.conf:
# Span 1: TE2/0/1 T2XXP (PCI) Card 0 Span 1 (MASTER) HDB3/CCS ClockSource 
span=1,1,0,ccs,hdb3
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=oslec,1-15,17-31

# Span 2: TE2/0/2 T2XXP (PCI) Card 0 Span 2 HDB3/CCS/CRC4 RED
span=2,2,0,ccs,hdb3
# termtype: te
bchan=32-46,48-62
dchan=47
echocanceller=oslec,32-46,48-62

# Global data
loadzone= ru
defaultzone = ru


... and /etc/asterisk/chan_dahdi.conf:
[trunkgroups]
[channels]
context=from-pstn
signalling=fxs_ks
rxwink=300  ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
;Uncomment these lines if you have problems with the disconection of your 
analog lines
;busydetect=yes
;busycount=3
immediate=no

; Span 1: TE2/0/1 T2XXP (PCI) Card 0 Span 1 (MASTER) HDB3/CCS ClockSource 
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel = 1-15,17-31
context = default
group = 63

; Span 2: TE2/0/2 T2XXP (PCI) Card 0 Span 2 HDB3/CCS/CRC4 RED
group=0,12
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel = 32-46,48-62
context = default
group = 63



 On incoming call from telco I'm getting this (pri debug, full log attached):

 Protocol Discriminator: Q.931 (8)  len=39
 Call Ref: len= 2 (reference 538/0x21A) (Originator)
 Message type: SETUP (5)
 [a1]
 Sending Complete (len= 1)
 [04 03 80 90 a3]
 Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer capability: 
Speech (0)
  Ext: 1  Trans mode/rate: 64kbps, circuit-mode 
(16)
  Ext: 1  User information layer 1: A-Law (35)
 [18 03 a9 83 9a]
 Channel ID (len= 5) [ Ext: 1  IntID: Implicit  PRI  Spare: 0  Exclusive  
Dchan: 0
ChanSel: Reserved
   Ext: 1  Coding: 0  Number Specified  Channel Type: 3
   Ext: 1  Channel: 26 ]
 [6c 09 41 81 32 37 39 39 30 39 39]
 Calling Number (len=11) [ Ext: 0  TON: Subscriber Number (4)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
   Presentation: Presentation permitted, user number 
passed network screening (1)  '3800100' ]
 [70 06 c1 36 39 34 31 31]
 Called Number (len= 8) [ Ext: 1  TON: Subscriber Number (4)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1)  '70522' ]
 [7e 04 00 09 f3 63]
 User-User Information (len= 6) [ 00 09 73 63 ]
[Apr 22 11:25:15] ERROR[29838]: chan_dahdi.c:9482 dahdi_pri_error: XXX Message 
longer than it should be?? XXX
-- Processing Q.931 Call Setup
-- Processing IE 161 (cs0, Sending Complete)
-- Processing IE 4 (cs0, Bearer Capability)
-- Processing IE 24 (cs0, Channel Identification)
-- Processing IE 108 (cs0, Calling Party Number)
-- Processing IE 112 (cs0, Called Party Number)
[Apr 22 11:25:15] ERROR[29838]: chan_dahdi.c:9482 dahdi_pri_error: XXX Message 
longer than it should be?? XXX
Sending Receiver Ready (86)



After many attempts it gives up and sending me DISCONNECT:

 Protocol Discriminator: Q.931 (8)  len=9
 Call Ref: len= 2 (reference 539/0x21B) (Originator)
 Message type: DISCONNECT (69)
 [08 02 80 e6]
 Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  
Location: User (0)
  Ext: 1  Cause: Recover on timer expiry (102), class = 
Protocol Error (e.g. unknown message) (6) ]



On this message DAHDI replies with RELEASE COMPLETE:

 Protocol Discriminator: Q.931 (8)  len=9
 Call Ref: len= 2 (reference 539/0x21B) (Terminator)
 Message type: RELEASE COMPLETE (90)
 [08 02 81 d1]
 Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  
 Location: Private network serving the local user (1)
  Ext: 1  Cause: Invalid call reference value (81), class = 
 Invalid message (e.g. parameter out of range) (5) ]
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate 

==

I have another asterisk box which works with this telco. My configuration there 
is rather
different in both hardware and software (no PCI-E and no Elastix there, plain 
asterisk 1.4.21.2 
built from source, libpri 1.4.4 and zaptel 1.4.11).
That fact causes me to think that smth wrong with my DAHDI configuration.

Any ideas? 
-- 
Alexandr Krylovskiy

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users