Re: One-Way Audio

On Fri, Mar 16, 2012 at 11:59:38AM +0100, Ralf Schlatterbeck wrote:
> I'm observing one-way audio here with the following configuration:
> 
> - Asterisk 1.8.4.4 on ubuntu
> - Kernel 3.2.0-18 from ubuntu
> - mISDN, mISDNuser, LCR from yesterday (GIT mISDN.eu)
> - made sure to remove old mISDN from installed kernel in /lib/modules,
>   installed new modules and ran depmod, so I'm quite sure we're running
>   correct version
> - HFCmulti card (I can dig out the info which card if needed)

I can now provide some more details:
- I've reproduced this on a debian stable kernel:
  Linux version 2.6.32-5-686 (Debian 2.6.32-41) (ben-/[email protected])
  (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:04:25 UTC
  2012
- asterisk 1.8 installed from source
- also all mISDN and lcr packages from GIT mISDN.eu
- deinstalled /lib/modules2.6.32-5-686/kernel/drivers/isdn/mISDN and
  /lib/modules2.6.32-5-686/kernel/drivers/isdn/hardware and ran depmod
- HFCmulti card: 00:09.0 ISDN controller [0204]: Cologne Chip Designs
  GmbH ISDN network Controller [HFC-4S] [1397:08b4] (rev 01)

Concerning the versions:
- for mISDN I'm on the "socket" branch (this is the default HEAD)
- for mISDNuser I'm on the "pending" branch (default HEAD)
- for lcr I'm on the "master" branch

Maybe the branches don't fit together? What branch should be used for which
package??


A call *out* from this system will send out audio but won't receive any
audio (now I'm running this with a local digium phone card, so I'm sure
there are no sip-related one-way audio issues, no SIP is involved now)
When using monitoring with asterisk the audio-file for the received side is
zero length (just the .wav header)

DTMF *is* received, so it seem mISDN_dsp is doing dtmf recognition.
After receiving the first DTMF from the remote, we no longer send any
audio out :-(

Log from lcr:
17.03.12 17:07:38.207 EP(4): CHANNEL SELECTION (found given interface)  interface Int
17.03.12 17:07:38.207 EP(4): CHANNEL SELECTION (found given interface)  interface Int
17.03.12 17:07:38.207 EP(4): CHANNEL SELECTION (selecting free channel)  port 2  position 0  channel 1
17.03.12 17:07:38.207 EP(4): SETUP  to CH(4)  caller id number=4 present=allowed  caller id2 number=4 present=allowed  dialing 99
17.03.12 17:07:38.208 CH(4): MT_NEW_L3ID REQUEST  port 2  callref new=0xff008004
17.03.12 17:07:38.208 CH(4): MT_SETUP REQUEST N->U  port 2  channel_id exclusive=0 channel=1  calling_pn type=0 plan=1 present=0 screen=0 number=4  call_pn 2 type=0 plan=1 present=0 screen=0 number=4  called_pn type=0 plan=1 number=99  bearer coding=0 capability=0 mode=0 rate=16 multi=-1 user=3
17.03.12 17:07:38.258 CH(4): MT_SETUP_ACK INDICATION N<-U  port 2  channel_id exclusive=1 channel=1
17.03.12 17:07:38.258 CH(4): CHANNEL SELECTION (first reply to setup)  port 2  channel request='1 (suggest)' reply=1  conclusion 'channel was accepted as given'  connect channel=1
17.03.12 17:07:38.258 CH(4): BCHANNEL create socket  port 2  channel 1  socket 17
17.03.12 17:07:38.258 CH(4): BCHANNEL activate  port 2  channel 1
17.03.12 17:07:38.258 EP(4): SETUP ACKNOWLEDGE  from CH(4)
17.03.12 17:07:38.259 CH(4): BCHANNEL control  port 2  DSP-DTMF 1
17.03.12 17:07:38.379 CH(4): MT_CONNECT INDICATION N<-U  port 2
17.03.12 17:07:38.380 CH(4): MT_CONNECT RESPONSE N->U  port 2
17.03.12 17:07:38.380 CH(4): MT_NEW_L3ID INDICATION  port 2  callref old=0xff008004 new=0x18004
17.03.12 17:07:38.380 EP(4): CONNECT  from CH(4)  connect id number= present=allowed
17.03.12 17:07:38.380 CH(4): MESSAGE_BCHANNEL (from remote application)  port 2  type 'export request'
17.03.12 17:07:38.380 CH(4): BCHANNEL deactivate  port 2  channel 1
17.03.12 17:07:38.380 CH(4): BCHANNEL remove socket  port 2  channel 1  socket 17
17.03.12 17:07:38.380 CH(4): MESSAGE_BCHANNEL (to remote application)  port 2  type assign  channel 2.1
17.03.12 17:07:38.381 CH(4): MESSAGE_BCHANNEL (from remote application)  port 2  type assign_ack
17.03.12 17:07:43.279 CH(4): MESSAGE_BCHANNEL (from remote application)  port 2  type 'import request'
17.03.12 17:07:43.279 CH(4): MESSAGE_BCHANNEL (to remote application)  port 2  type remove  channel 2.1
17.03.12 17:07:43.279 EP(4): TONE  to CH(4)  directory default  name cause_10
17.03.12 17:07:43.279 EP(4): DISCONNECT  to CH(4)  cause value=16 location=1-Local-PBX
17.03.12 17:07:43.279 CH(4): MT_DISCONNECT REQUEST N->U  port 2  progress codeing=0 location=1 indicator=8  cause location=5 value=16
17.03.12 17:07:43.290 CH(4): MESSAGE_BCHANNEL (from remote application)  port 2  type remove_ack
17.03.12 17:07:43.290 CH(4): BCHANNEL create socket  port 2  channel 1  socket 17
17.03.12 17:07:43.290 CH(4): BCHANNEL activate  port 2  channel 1
17.03.12 17:07:43.290 CH(4): BCHANNEL control  port 2  DSP-DTMF 1
17.03.12 17:07:43.331 CH(4): MT_RELEASE INDICATION N<-U  port 2  cause location=1 value=16
17.03.12 17:07:43.331 CH(4): MT_RELEASE_L3ID INDICATION  port 2  callref 0x18004
17.03.12 17:07:43.331 EP(4): RELEASE  from CH(4)  cause value=16 location=5-Remote-PBX
17.03.12 17:07:43.331 CH(4): BCHANNEL deactivate  port 2  channel 1
17.03.12 17:07:43.331 CH: BCHANNEL remove socket  port 2  channel 1  socket 17


Any ideas?
Ralf
-- 
Ralf Schlatterbeck             email: [email protected]