[asterisk-r2] asterisk-r2 Digest, Vol 5, Issue 12

Thu Jan 15 08:43:34 CST 2009

Please enable call files and pastebin the resulting call files for the
outgoing and incoming legs. The sample configuration at google code
includes information about how to enable call files.

On Thu, Jan 15, 2009 at 8:04 AM, Gabriel Monsalvo <gabriel at arlab.com.ar> wrote:
> Hi list!
> I'm tryng to implement an E1 from Telecom Argentina, everything looks
> fine, I don't have any alarms but when i dial from any extension nothing
> happens
> this is the log when i dial:
>
> Executing [s at macro-dialout-trunk:20] Dial("SIP/999-093b4088"
> , "ZAP/g0/156402080|300|") in new stack
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: no MFC/R2 category specified for
> chan Zap/1-1, using default Nati
> onal Subscriber
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - Attempting to make call
> (ANI=999, DNIS=156402080, catego
> ry=National Subscriber)
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - CAS Tx >> [SEIZE] 0x00
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x01
> [Jan 15 01:41:57] VERBOSE[6645] logger.c:     -- Called g0/156402080
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: bits changed in chan 1
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - Bits changed from 0x08 to
> 0x0C
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - CAS Rx << [SEIZE ACK] 0x0C
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - Sending DNIS digit 1
> [Jan 15 01:41:57] DEBUG[6645] chan_dahdi.c: Chan 1 - MF Tx >> 1 [ON]
> [Jan 15 01:43:25] DEBUG[6645] chan_dahdi.c: disconnecting MFC/R2 call on chan 1
> [Jan 15 01:43:25] DEBUG[6645] chan_dahdi.c: Chan 1 - CAS Tx >> [CLEAR FORWARD]
> 0x08
> [Jan 15 01:43:25] DEBUG[6645] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x09
> [Jan 15 01:43:25] VERBOSE[6645] logger.c:     -- Hungup 'Zap/1-1'
>
>
> if i call to the main number of the DDE, i don't see anything in the asterist console, but this is the log:
>
> NOTICE[6618] chan_dahdi.c: New MFC/R2 call detected on chan 3.
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Rx << 6 [ON]
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - Getting DNIS digit 6
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - DNIS so far: 6, expected
> length: 4
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - Requesting next DNIS with
> signal 0x31.
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Tx >> 1 [ON]
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Rx << 6 [OFF]
> [Jan 15 01:44:26] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Tx >> 1 [OFF]
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Rx << 6 [ON]
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - Getting DNIS digit 6
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - DNIS so far: 66, expected
> length: 4
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - Requesting next DNIS with
> signal 0x31.
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Tx >> 1 [ON]
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Rx << 6 [OFF]
> [Jan 15 01:44:27] DEBUG[6618] chan_dahdi.c: Chan 3 - MF Tx >> 1 [OFF]
>
> I have elastix 1.3 with the patched chan_dadhi the mfcr2 show status
> command tell me thats everything ok (all the 30 channels are up and the
> status is idle).
>
> i would be appreciate any helps,
>
> Gabriel Monsalvo.
>
>
>> Send asterisk-r2 mailing list submissions to
>>       asterisk-r2 at lists.digium.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>       http://lists.digium.com/mailman/listinfo/asterisk-r2
>> or, via email, send a message with subject or body 'help' to
>>       asterisk-r2-request at lists.digium.com
>>
>> You can reach the person managing the list at
>>       asterisk-r2-owner at lists.digium.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of asterisk-r2 digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Problem using patch for 1.4.18 (Carlos Chavez)
>>    2. Re: Problem using patch for 1.4.18 (Moises Silva)
>>    3. Re: Problem using patch for 1.4.18 (Carlos Chavez)
>>    4. Re: Problem using patch for 1.4.18 (Moises Silva)
>>    5. Re: Problem using patch for 1.4.18 (Carlos Chavez)
>>    6. Re: Problem using patch for 1.4.18 (Moises Silva)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 14 Jan 2009 11:22:31 -0600
>> From: Carlos Chavez <cursor at telecomabmex.com>
>> Subject: [asterisk-r2] Problem using patch for 1.4.18
>> To: asterisk-r2 at lists.digium.com
>> Message-ID: <1231953751.3371.8.camel at cursor.telecomabmex.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>>       I am trying to use the patch for Asterisk 1.4.18, it applies with now
>> errors or warnings.  I do get several warnings when running bootstrap.sh
>> but no errors.  When running ./configure I get the following error:
>>
>> checking for a sed that does not truncate output... ./configure: line
>> 6379: syntax error near unexpected token `SED,'
>> ./configure: line 6379: `     _AC_PATH_PROG_FEATURE_CHECK(SED, sed
>> gsed,'
>>
>>       I do not know if this has something to do that I applied the patch on a
>> Fedora 10 system because I do not have autoconf 2.60 on the machine I am
>> trying to compile asterisk (Fedora Core 5).
>>
>>
>>
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>

-- 
"I do not agree with what you have to say, but I'll defend to the
death your right to say it." Voltaire