sorry for the too late answer, but here we are now.
The not working call seems to have debugging enabled, so your temporary solution didn't last long hm :-) anyway, the other device answers with a RELEASE_COMPLETE with cause: 96 on our SETUP_ACKNOWLEGDE, which is very weird.. caue:96 means "Missing Information Element" .. I need to find out which Info Elements are mandatory on SetupAck and will check >Wed Aug 9 17:32:43 2006: P[ 1] I IND :RELEASE_COMPLETE oad: dad: pid:3 >state:WAITING4DIGS >Wed Aug 9 17:32:43 2006: P[ 1] --> channel:0 mode:NT cause:96 ocause:16 >rad: cad: >Wed Aug 9 17:32:43 2006: P[ 1] --> info_dad: onumplan:0 dnumplan:0 >rnumplan:0 cpnnumplan:0 >Wed Aug 9 17:32:43 2006: P[ 1] --> caps:Speech pi:0 keypad: >sending_complete:0 >Wed Aug 9 17:32:43 2006: P[ 1] --> screen:0 --> pres:0 >Wed Aug 9 17:32:43 2006: P[ 1] --> addr:50010102 l3id:10041 b_stid:0 >layer_id:50010180 >Wed Aug 9 17:32:43 2006: P[ 1] --> facility:FAC_NONE out_facility:FAC_NONE >Wed Aug 9 17:32:43 2006: P[ 1] --> bc_state:BCHAN_CLEANED >Wed Aug 9 17:32:43 2006: P[ 1] hangup_chan > You wrote before that the problem occurs at least since 0.3.1-rc18, didn't it occur before? I wonder why the other device sometimes like our SETUP_ACK and sometimes not.. what exact device is it? Regards, Christian _______________________________________________ Misdn-asterisk mailing list [email protected] http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk
