problema con las conferencias al ingresar el PIN

Estoy trabajando con asterisk 1.6 y freepbx 2.5 y he tenido problemas al crear una conferencia pues cuando se marca el número de la conferencia ésta pide el PIN para ingresar pero al digitarlo se corta la conferencia o la llamada... anexo el log que genera asterisk para que alguien me pueda decir cual es el posible error:

[1;35;40mUsing CallerID "Servidor VoIP" <300>[0;37;40m") in new stack
[Mar 17 03:57:16] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:2] [1;36;40mSet[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mMEETME_ROOMNUM=1234[0;37;40m") in new stack
[Mar 17 03:57:16] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:3] [1;36;40mSet[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mMEETME_RECORDINGFILE=/var/spool/asterisk/monitor/meetme-conf-rec-1234-1268816236.1[0;37;40m") in new stack
[Mar 17 03:57:16] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:4] [1;36;40mGotoIf[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m0?READPIN[0;37;40m") in new stack
[Mar 17 03:57:16] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:5] [1;36;40mAnswer[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m[0;37;40m") in new stack
[Mar 17 03:57:16] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:6] [1;36;40mWait[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1[0;37;40m") in new stack
[Mar 17 03:57:17] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:7] [1;36;40mSet[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mPINCOUNT=0[0;37;40m") in new stack
[Mar 17 03:57:17] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:8] [1;36;40mRead[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mPIN,enter-conf-pin-number,,,,[0;37;40m") in new stack
[Mar 17 03:57:17] VERBOSE[29115] file.c: -- <SIP/300-00000001> Playing 'enter-conf-pin-number.gsm' (language 'es')
[Mar 17 03:57:33] VERBOSE[29115] app_read.c: -- User entered '12345'
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:9] [1;36;40mGotoIf[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1?USER[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Goto (from-internal,1234,17)
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:17] [1;36;40mSet[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mMEETME_OPTS=cIMsr[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [1234@from-internal:18] [1;36;40mGoto[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mSTARTMEETME,1[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Goto (from-internal,STARTMEETME,1)
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [STARTMEETME@from-internal:1] [1;36;40mMeetMe[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1234,cIMsr,12345[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] config.c: == Parsing '/etc/asterisk/meetme.conf': [Mar 17 03:57:33] VERBOSE[29115] config.c: == Found
[Mar 17 03:57:33] VERBOSE[29115] config.c: == Parsing '/etc/asterisk/meetme_additional.conf': [Mar 17 03:57:33] VERBOSE[29115] config.c: == Found
[Mar 17 03:57:33] WARNING[29115] app_meetme.c: Unable to open pseudo device
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: == Spawn extension (from-internal, STARTMEETME, 1) exited non-zero on 'SIP/300-00000001'
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [h@from-internal:1] [1;36;40mMacro[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40mhangupcall[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [s@macro-hangupcall:1] [1;36;40mGotoIf[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1?skiprg[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Goto (macro-hangupcall,s,4)
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [s@macro-hangupcall:4] [1;36;40mGotoIf[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1?skipblkvm[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Goto (macro-hangupcall,s,7)
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [s@macro-hangupcall:7] [1;36;40mGotoIf[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m1?theend[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Goto (macro-hangupcall,s,9)
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: -- Executing [s@macro-hangupcall:9] [1;36;40mHangup[0;37;40m("[1;35;40mSIP/300-00000001[0;37;40m", "[1;35;40m[0;37;40m") in new stack
[Mar 17 03:57:33] VERBOSE[29115] app_macro.c: == Spawn extension (macro-hangupcall, s, 9) exited non-zero on 'SIP/300-00000001' in macro 'hangupcall'
[Mar 17 03:57:33] VERBOSE[29115] pbx.c: == Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/300-00000001'

VozToVoice: 

Re: problema con las conferencias al ingresar el PIN

[Mar 17 03:57:33] WARNING[29115] app_meetme.c: Unable to open pseudo device

Pareciera que no tienen instalado DAHDI o no está funcionando bien.

Revisa con:

CLI> dahdi show status

que aparezca algo parecido a esta linea:

DAHDI_DUMMY/1 (source: Linux26) 1        UNCONFI 0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)

Saludos

Suscribirse a Comentarios de "problema con las conferencias al ingresar el PIN" Suscribirse a VozToVoice - Todos los comentarios