Automatic hangup when starting meetme

Asterisk Asterisk General
1

Hi all,
I’m using asterisk 1.8.12.1 and I’m trying to start a meetme conference via AMI interface:
in my dialplan I’ve got this:
[normal]
exten => 10000,1,Answer()
exten => 10000,n,Meetme(300,1q)

After logging in via AMI, I write the command:

action:originate
Channel:SIP/ipl3
context:normal
Exten:10000
priority:1

which actually starts the conference, but before I can realize it’s hang up, showing this message:

Response: Success
Message: Originate successfully queued

Event: Newchannel
Privilege: call,all
Channel: SIP/ipl3-00000002
ChannelState: 0
ChannelStateDesc: Down
CallerIDNum: 006
CallerIDName: 
AccountCode: 
Exten: 
Context: pdef
Uniqueid: 1340349501.2

Event: NewAccountCode
Privilege: call,all
Channel: SIP/ipl3-00000002
Uniqueid: 1340349501.2
AccountCode: 
OldAccountCode: 

Event: NewCallerid
Privilege: call,all
Channel: SIP/ipl3-00000002
CallerIDNum: 006
CallerIDName: 
Uniqueid: 1340349501.2
CID-CallingPres: 0 (Presentation Allowed, Not Screened)

Event: Newstate
Privilege: call,all
Channel: SIP/ipl3-00000002
ChannelState: 5
ChannelStateDesc: Ringing
CallerIDNum: 006
CallerIDName: 
ConnectedLineNum: 
ConnectedLineName: 
Uniqueid: 1340349501.2

Event: Newstate
Privilege: call,all
Channel: SIP/ipl3-00000002
ChannelState: 6
ChannelStateDesc: Up
CallerIDNum: 006
CallerIDName: 
ConnectedLineNum: 
ConnectedLineName: 
Uniqueid: 1340349501.2

Event: Hangup
Privilege: call,all
Channel: SIP/ipl3-00000002
Uniqueid: 1340349501.2
CallerIDNum: 006
CallerIDName: <unknown>
ConnectedLineNum: <unknown>
ConnectedLineName: <unknown>
Cause: 16
Cause-txt: Normal Clearing

while at the CLI this messages are shown:

  == Using SIP RTP CoS mark 5
    -- Executing [10000@normal:1] Answer("SIP/ipl3-00000002", "") in new stack
    -- Executing [10000@normal:2] MeetMe("SIP/ipl3-00000002", "300,1xq") in new stack
  == Parsing '/etc/asterisk/meetme.conf':   == Found
  == Spawn extension (normal, 10000, 2) exited non-zero on 'SIP/ipl3-00000002'

I’ve been reading different discussions and I saw it could be a dahdi problem but if I “module show like dahdi”:

module show like dahdi
Module                         Description                              Use Count 
app_dahdiras.so                DAHDI ISDN Remote Access Server          0         
res_timing_dahdi.so            DAHDI Timing Interface                   2         
chan_dahdi.so                  DAHDI Telephony Driver                   0         
app_dahdibarge.so              Barge in on DAHDI channel application    0         
4 modules loaded

So I don’t know where to look for the problem now… :frowning:
Does somebody know where could the problem be?

Thank you!!

2

No one?
Could it be a matter of compatibility between the asterisk and dahdi versions?
I’m using asterisk 1.8.12.1 with dahdi 2.6.1+2.6.1… Are they compatible?

thanks!

ben.

3

When I try to start a conference with confbridge, it works, it’s not hang up, so it must be something to do with dahdi timing, right? I’ll try an older version just in case…

4

forget it, it’s just an stupid guy handling too many things at the same time… :blush: