[asterisk-r2] asterisk-r2 Digest, Vol 70, Issue 3

Tue Jun 10 07:25:17 CDT 2014

Thanks, you are correct, this problem was a context, I saw some problems like my problem and I post the solution in Forum.

On 9 de junho de 2014 21h36min09s BRT, asterisk-r2-request at lists.digium.com wrote:
>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.  Asterisk with Failure signaling R2D (solved) (natalia silva)
>   2. Re: Asterisk with Failure signaling R2D (solved) (Jose Rojas)
>  3. Re: Asterisk with Failure signaling R2D (solved) (Gerardo Barajas)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 9 Jun 2014 16:48:21 -0300
>From: natalia silva <natalianew at gmail.com>
>To: asterisk-r2 at lists.digium.com
>Subject: [asterisk-r2]  Asterisk with Failure signaling R2D (solved)
>Message-ID:
>	<CAG6RPm7v_wYU7iCk+7U+a72FJuE6To3KEZ3uATcGobVjSvVABg at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>First I would like to thank all the help found here on the forum
>Thank you to Mr. Gustavo Cremella and Mc Ricardo GRATH.
>
>The solution was found after some adjustments
>Remembering that they are functional in my environment and more:
>
>1 - My number is ported from another carrier.
>2 - Context of input and output
>3 - Setting the Dahdi-in virtual numbers provider to sync with its
>corresponding range ported in my real number.
>4 - Clock facing the operator, as in the case of Mundivox she needs to
>deliver the clock operator being called. Example I call a number from
>the
>operator OI, then Mundivox handle this connection and delivery to OI to
>complete the connection.
>
>
>chan_dahdi.conf
>[Channels]
>language = br
>context = default (default context for incoming calls)
>mfcr2_variant = en
>mfcr2_max_ani = 20
>mfcr2_max_dnis = 10
>mfcr2_category = national_subscriber
>mfcr2_logdir = span_ALL
>mfcr2_call_files = yes
>mfcr2_metering_pulse_timeout = 1000
>, Mfcr2_double_answer = yes (optional)
>group = 1
>context = dahdi-in (Uses the [internal] context in extensions.conf, as
>mentioned in point 3 above)
>signaling = mfcr2
>channel => 1-15
>context = default (Incoming calls go to [incoming] in extensions.conf)
>group = 63 (Gets, sets or clears the channel group, the limit is 63 so
>he
>was left for redundancy)
>
># Include dahdi-channels.conf
>
>system.conf
>span = 1,1,0, cas, hdb3
>cas = 1-15:1101
>echocanceller Mg2 = 0.1 to 31
>loadzone = br
>defaultzone = br
>
>
>[Dahdi-in]
>, Mundivox (range of virtual numbers, Mundivox)
>exten => _18 [2-7] X, 1, Answer ()
>exten => _18 [2-7] X, n, Queue (incoming_local, rn,,, 1)
>exten => _18 [2-7] X, n, Goto (Start Menu-, s, 1)
>exten => _18 [2-7] X, n, Hangup ()
>
>exten => _29 [4-7] X, 1, Answer ()
>exten => _29 [4-7] X, n, queu (incoming_local, rn,,, 1)
>exten => _29 [4-7] X, n, Goto (Start Menu-, s, 1)
>exten => _29 [4-7] X, n, Hangup ()
>
>Was required for the DDR's range that has this operator, it will make
>all
>connections to this range fall on the main trunk
>
>Already for a DDR'espec?cifico fall into a specific extension then you
>need
>to identify.
>This is simple just enter <cli and analyze logs, make a link to a
>particular DDR. In my case I started to see this error:
>
>new MFC/R2 call detected on chan 1.
>Offered MFC/R2 call on chan 1. = 21,980,823,777 ANI, DNIS = 1825,
>Category
>= National Subscriber
>[Jun 5 12:24:19] NOTICE [9466]: chan_dahdi.c: 4007
>dahdi_r2_on_call_offered: MFC/R2 call on channel 1 requested
>non-existent
>extension '1825 'in context' default '. Rejecting call.
>MFC/R2 call disconnected on channel 1
>MFC/R2 call end on channel 1
>
>
>So I needed to create this fix which then enter the call to your
>specific
>extension, in dahdi-in too.
>exten => _1825, 1, Answer ()
>exten => _1825, n, Macro (dialexten, 4105.20)
>exten => _1825, n, Hangup ()
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://lists.digium.com/pipermail/asterisk-r2/attachments/20140609/d4f811e5/attachment-0001.html>
>
>------------------------------
>
>Message: 2
>Date: Mon, 9 Jun 2014 19:29:17 -0430
>From: Jose Rojas <jygrrr at gmail.com>
>To: asterisk-r2 at lists.digium.com
>Subject: Re: [asterisk-r2] Asterisk with Failure signaling R2D
>	(solved)
>Message-ID:
>	<CADSYhC7YiiQxFD1eM42CU0q3qB_HjcnZ_HZZx1xKwMiWhW+iVQ at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>Hello Nataly, your problems is in the context. Change the context
>default
>for Dahdi-in in chan_dahdi.conf or include Dahdi-in in default in your
>dialplan.
>
>
>
>
>
>
>2014-06-09 15:18 GMT-04:30 natalia silva <natalianew at gmail.com>:
>
>> First I would like to thank all the help found here on the forum
>> Thank you to Mr. Gustavo Cremella and Mc Ricardo GRATH.
>>
>> The solution was found after some adjustments
>> Remembering that they are functional in my environment and more:
>>
>> 1 - My number is ported from another carrier.
>> 2 - Context of input and output
>> 3 - Setting the Dahdi-in virtual numbers provider to sync with its
>> corresponding range ported in my real number.
>> 4 - Clock facing the operator, as in the case of Mundivox she needs
>to
>> deliver the clock operator being called. Example I call a number from
>the
>> operator OI, then Mundivox handle this connection and delivery to OI
>to
>> complete the connection.
>>
>>
>> chan_dahdi.conf
>> [Channels]
>> language = br
>> context = default (default context for incoming calls)
>> mfcr2_variant = en
>> mfcr2_max_ani = 20
>> mfcr2_max_dnis = 10
>> mfcr2_category = national_subscriber
>> mfcr2_logdir = span_ALL
>> mfcr2_call_files = yes
>> mfcr2_metering_pulse_timeout = 1000
>> , Mfcr2_double_answer = yes (optional)
>> group = 1
>> context = dahdi-in (Uses the [internal] context in extensions.conf,
>as
>> mentioned in point 3 above)
>> signaling = mfcr2
>> channel => 1-15
>> context = default (Incoming calls go to [incoming] in
>extensions.conf)
>> group = 63 (Gets, sets or clears the channel group, the limit is 63
>so he
>> was left for redundancy)
>>
>> # Include dahdi-channels.conf
>>
>> system.conf
>> span = 1,1,0, cas, hdb3
>> cas = 1-15:1101
>> echocanceller Mg2 = 0.1 to 31
>> loadzone = br
>> defaultzone = br
>>
>>
>> [Dahdi-in]
>> , Mundivox (range of virtual numbers, Mundivox)
>> exten => _18 [2-7] X, 1, Answer ()
>> exten => _18 [2-7] X, n, Queue (incoming_local, rn,,, 1)
>> exten => _18 [2-7] X, n, Goto (Start Menu-, s, 1)
>> exten => _18 [2-7] X, n, Hangup ()
>>
>> exten => _29 [4-7] X, 1, Answer ()
>> exten => _29 [4-7] X, n, queu (incoming_local, rn,,, 1)
>> exten => _29 [4-7] X, n, Goto (Start Menu-, s, 1)
>> exten => _29 [4-7] X, n, Hangup ()
>>
>> Was required for the DDR's range that has this operator, it will make
>all
>> connections to this range fall on the main trunk
>>
>> Already for a DDR'espec?cifico fall into a specific extension then
>you
>> need to identify.
>> This is simple just enter <cli and analyze logs, make a link to a
>> particular DDR. In my case I started to see this error:
>>
>> new MFC/R2 call detected on chan 1.
>> Offered MFC/R2 call on chan 1. = 21,980,823,777 ANI, DNIS = 1825,
>Category
>> = National Subscriber
>> [Jun 5 12:24:19] NOTICE [9466]: chan_dahdi.c: 4007
>> dahdi_r2_on_call_offered: MFC/R2 call on channel 1 requested
>non-existent
>> extension '1825 'in context' default '. Rejecting call.
>> MFC/R2 call disconnected on channel 1
>> MFC/R2 call end on channel 1
>>
>>
>> So I needed to create this fix which then enter the call to your
>specific
>> extension, in dahdi-in too.
>> exten => _1825, 1, Answer ()
>> exten => _1825, n, Macro (dialexten, 4105.20)
>> exten => _1825, n, Hangup ()
>>
>> --
>> _____________________________________________________________________
>> -- 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
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://lists.digium.com/pipermail/asterisk-r2/attachments/20140609/24ff7cb0/attachment-0001.html>
>
>------------------------------
>
>Message: 3
>Date: Mon, 9 Jun 2014 19:36:56 -0500
>From: Gerardo Barajas <gerardo.barajas at gmail.com>
>To: asterisk-r2 at lists.digium.com
>Subject: Re: [asterisk-r2] Asterisk with Failure signaling R2D
>	(solved)
>Message-ID:
>	<CAOQhXxHu9z5WJZvr+rBjNet8JLN0pySQhXscJ9gReP8prx-K-A at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>Porting numbers sometimes is not so easy and plain.
>On Jun 9, 2014 2:48 PM, "natalia silva" <natalianew at gmail.com> wrote:
>
>> First I would like to thank all the help found here on the forum
>> Thank you to Mr. Gustavo Cremella and Mc Ricardo GRATH.
>>
>> The solution was found after some adjustments
>> Remembering that they are functional in my environment and more:
>>
>> 1 - My number is ported from another carrier.
>> 2 - Context of input and output
>> 3 - Setting the Dahdi-in virtual numbers provider to sync with its
>> corresponding range ported in my real number.
>> 4 - Clock facing the operator, as in the case of Mundivox she needs
>to
>> deliver the clock operator being called. Example I call a number from
>the
>> operator OI, then Mundivox handle this connection and delivery to OI
>to
>> complete the connection.
>>
>>
>> chan_dahdi.conf
>> [Channels]
>> language = br
>> context = default (default context for incoming calls)
>> mfcr2_variant = en
>> mfcr2_max_ani = 20
>> mfcr2_max_dnis = 10
>> mfcr2_category = national_subscriber
>> mfcr2_logdir = span_ALL
>> mfcr2_call_files = yes
>> mfcr2_metering_pulse_timeout = 1000
>> , Mfcr2_double_answer = yes (optional)
>> group = 1
>> context = dahdi-in (Uses the [internal] context in extensions.conf,
>as
>> mentioned in point 3 above)
>> signaling = mfcr2
>> channel => 1-15
>> context = default (Incoming calls go to [incoming] in
>extensions.conf)
>> group = 63 (Gets, sets or clears the channel group, the limit is 63
>so he
>> was left for redundancy)
>>
>> # Include dahdi-channels.conf
>>
>> system.conf
>> span = 1,1,0, cas, hdb3
>> cas = 1-15:1101
>> echocanceller Mg2 = 0.1 to 31
>> loadzone = br
>> defaultzone = br
>>
>>
>> [Dahdi-in]
>> , Mundivox (range of virtual numbers, Mundivox)
>> exten => _18 [2-7] X, 1, Answer ()
>> exten => _18 [2-7] X, n, Queue (incoming_local, rn,,, 1)
>> exten => _18 [2-7] X, n, Goto (Start Menu-, s, 1)
>> exten => _18 [2-7] X, n, Hangup ()
>>
>> exten => _29 [4-7] X, 1, Answer ()
>> exten => _29 [4-7] X, n, queu (incoming_local, rn,,, 1)
>> exten => _29 [4-7] X, n, Goto (Start Menu-, s, 1)
>> exten => _29 [4-7] X, n, Hangup ()
>>
>> Was required for the DDR's range that has this operator, it will make
>all
>> connections to this range fall on the main trunk
>>
>> Already for a DDR'espec?cifico fall into a specific extension then
>you
>> need to identify.
>> This is simple just enter <cli and analyze logs, make a link to a
>> particular DDR. In my case I started to see this error:
>>
>> new MFC/R2 call detected on chan 1.
>> Offered MFC/R2 call on chan 1. = 21,980,823,777 ANI, DNIS = 1825,
>Category
>> = National Subscriber
>> [Jun 5 12:24:19] NOTICE [9466]: chan_dahdi.c: 4007
>> dahdi_r2_on_call_offered: MFC/R2 call on channel 1 requested
>non-existent
>> extension '1825 'in context' default '. Rejecting call.
>> MFC/R2 call disconnected on channel 1
>> MFC/R2 call end on channel 1
>>
>>
>> So I needed to create this fix which then enter the call to your
>specific
>> extension, in dahdi-in too.
>> exten => _1825, 1, Answer ()
>> exten => _1825, n, Macro (dialexten, 4105.20)
>> exten => _1825, n, Hangup ()
>>
>> --
>> _____________________________________________________________________
>> -- 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
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://lists.digium.com/pipermail/asterisk-r2/attachments/20140609/b19f385c/attachment.html>
>
>------------------------------
>
>_______________________________________________
>--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
>
>End of asterisk-r2 Digest, Vol 70, Issue 3
>******************************************

-- 
E-mail enviado do meu celular Android usando K-9 Mail. Por favor, desculpe minha brevidade.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20140610/e1d83a28/attachment-0001.html>