[asterisk-r2] asterisk-r2 Digest, Vol 68, Issue 4

Thu May 1 00:13:59 CDT 2014

Hi,
Sometimes the '*'  must be replaced with a sequence of digits. For 
example, our office PBX is connected to Cellcom (Israel) via E1 PRI 
line. We have to send 1222 instead of *. For example, in order to send  
*3462 it is necessary to send 12223462 instead.
Probably your telco allows (or requires?) the '*' replacement with a 
digits sequence?
Best regards,
Leonid Fainshtein
Xorcom Ltd.

On 05/01/2014 12:40 AM, 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. Re: How to dial a '*' digit? (Moises Silva)
>     2. Calls ended (Rafael Montante)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Apr 2014 17:01:50 -0400
> From: Moises Silva <moises.silva at gmail.com>
> To: "asterisk-r2 at lists.digium.com" <asterisk-r2 at lists.digium.com>
> Subject: Re: [asterisk-r2] How to dial a '*' digit?
> Message-ID:
> 	<CAA4nhyBTmBpewAvi5Ridjh92ALFETFUzLpyHE-WoDrTrgrUF_g at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> It's just matter of removing the isdigit() validation in src/r2proto.c
>
> On Wed, Apr 30, 2014 at 4:28 PM, servtelar <servtelar at gmail.com> wrote:
>
>> Hi Moi
>>
>> Mine does. I don?t remember where, but out there is a patch to allow this.
>> Perhaps I applied in the past. I?ll try to get it.
>>
>>
>> On Apr 30, 2014, at 3:52 PM, Moises Silva <moises.silva at gmail.com> wrote:
>>
>> openr2 only sends digits (0-9), so not even letters will work. I could
>> allow sending ABCDEF but not sure if that will help you.
>>
>>
>> *Moises Silva **Manager, Software Engineering*
>> msilva at sangoma.com
>> Sangoma Technologies
>> 100 Renfrew Drive, Suite 100, Markham, ON L3R 9R6 Canada
>>
>> t.   +1 800 388 2475 (N. America)
>> t.   +1 905 474 1990 x128
>> f.   +1 905 474 9223
>>
>>
>> <http://www.sangoma.com/contact?utm_source=signature&utm_medium=email&utm_campaign=email+signatures>
>> Products<http://sangoma.com/products?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Solutions<http://sangoma.com/solutions?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Events<http://sangoma.com/about_us/events?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Contact<http://www.sangoma.com/contact?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Wiki<http://wiki.sangoma.com/?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Facebook<http://www.facebook.com/pages/Sangoma-VoIP-Cards/43578453335?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>   | Twitter<http://www.twitter.com/sangoma?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>`|
>> | YouTube<http://www.youtube.com/sangomatechnologies?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
>>
>>
>>
>> On Wed, Apr 30, 2014 at 1:39 PM, servtelar <servtelar at gmail.com> wrote:
>>
>>> * is not a digit. The numbers coded are hexadecimal. Try using B (or C,
>>> don?t remember now) instead of *.
>>>
>>>
>>> On Apr 30, 2014, at 2:21 PM, Rafael Montante <rafamontante at yahoo.com.mx>
>>> wrote:
>>>
>>> Hi,
>>>
>>> I'm trying to dial a string which contains the '*' char (*86) but it
>>> seems the char is not sent and the following message is displayed:
>>>
>>> [Apr 23 17:42:44] VERBOSE[64318][C-0000806a] chan_dahdi.c: Chan 186 -
>>> Char '*' is not a digit, DNIS will not be sent
>>>
>>> the complete log is:
>>>
>>> [Apr 23 17:42:44] VERBOSE[64318][C-0000806a] pbx.c:     -- Executing
>>> [688 at abc:3] Dial("IAX2/5344-14485", "DAHDI/G0/*86,30,tT") in new stack
>>> [Apr 23 17:42:44] VERBOSE[64318][C-0000806a] chan_dahdi.c: Chan 186 -
>>> Char '*' is not a digit, DNIS will not be sent.
>>> [Apr 23 17:42:44] VERBOSE[64318][C-0000806a] app_dial.c:     -- Called
>>> DAHDI/G0/*86
>>> [Apr 23 17:43:14] VERBOSE[64318][C-0000806a] app_dial.c:     -- Nobody
>>> picked up in 30000 ms
>>> [Apr 23 17:43:14] VERBOSE[64318][C-0000806a] chan_dahdi.c:     -- Hungup
>>> 'DAHDI/186-1'
>>>
>>> Do you know is there any way to force dial these char?
>>>
>>> This is the log of mfcr2:
>>>
>>> [17:42:44:287] [Thread: 140064829769472] [Chan 186] - Call started at Wed
>>> Apr 23 17:42:44 2014 on chan 186 [openr2 version 1.3.3, revision (release)]
>>> [17:42:44:287] [Thread: 140064829769472] [Chan 186] - Outgoing call
>>> proceeding: ANI=5344, DNIS=*86, Category=National Subscriber
>>> [17:42:44:287] [Thread: 140064829769472] [Chan 186] - CAS Tx >> [SEIZE]
>>> 0x00
>>> [17:42:44:287] [Thread: 140064829769472] [Chan 186] - CAS Raw Tx >> 0x01
>>> [17:42:44:287] [Thread: 140064829769472] [Chan 186] - scheduled timer id
>>> 2 (r2_seize)
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - Bits changed from
>>> 0x08 to 0x0C
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - CAS Rx << [SEIZE
>>> ACK] 0x0C
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - Attempting to
>>> cancel timer timer 2
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - timer id 2 found,
>>> cancelling it now
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - MFC/R2 call
>>> acknowledge!
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - No more DNIS. Doing
>>> nothing, waiting for timeout.
>>> [17:42:44:341] [Thread: 140064829769472] [Chan 186] - scheduled timer id
>>> 3 (mf_fwd_safety)
>>> [17:43:14:288] [Thread: 140064829769472] [Chan 186] - Attempting to
>>> cancel timer timer 0
>>> [17:43:14:288] [Thread: 140064829769472] [Chan 186] - Cannot cancel timer
>>> 0
>>> [17:43:14:288] [Thread: 140064829769472] [Chan 186] - CAS Tx >> [CLEAR
>>> FORWARD] 0x08
>>> [17:43:14:288] [Thread: 140064829769472] [Chan 186] - CAS Raw Tx >> 0x09
>>> [17:43:14:326] [Thread: 140077689812736] [Chan 186] - Bits changed from
>>> 0x0C to 0x08
>>> [17:43:14:326] [Thread: 140077689812736] [Chan 186] - CAS Rx << [IDLE]
>>> 0x08
>>> [17:43:14:326] [Thread: 140077689812736] [Chan 186] - Call ended
>>> [17:43:14:326] [Thread: 140077689812736] [Chan 186] - Attempting to
>>> cancel timer timer 0
>>> [17:43:14:326] [Thread: 140077689812736] [Chan 186] - Cannot cancel timer
>>> 0
>>>
>>> Here in Mexico the carrier has a service that require dial *86 or *88.
>>>
>>> Any help would be appreciate it.
>>>
>>> Best regards
>>> --
>>> _____________________________________________________________________
>>> -- 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
>>>
>>>
>>>
>>> --
>>> _____________________________________________________________________
>>> -- 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
>>>
>> --
>> _____________________________________________________________________
>> -- 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
>>
>>
>>
>> --
>> _____________________________________________________________________
>> -- 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/20140430/de1ad584/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 30 Apr 2014 14:50:04 -0700 (PDT)
> From: Rafael Montante <rafamontante at yahoo.com.mx>
> To: "asterisk-r2 at lists.digium.com" <asterisk-r2 at lists.digium.com>
> Subject: [asterisk-r2] Calls ended
> Message-ID:
> 	<1398894604.39579.YahooMailNeo at web140302.mail.bf1.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> how we can know if any call was finished from called party side or the calling party?.?
>
> In the logs from /var/log/asterisk/mfcr2/span1 I can see the message:
>
> Far end disconnected. Reason: Normal Clearing
>
>
> when the calling party hangup the call (considering the calling party as a customer making calls to an inbound campaign in the asterisk). That message is not displayed when the call was hangup from the called party side (an agent behind asterisk).
>
> Can I consider as a rule that if that message is displayed in the log, then the call was finished from the calling party side? Any time the message is not displayed the call was finished from the Asterisk side?
>
> Regards,?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20140430/392ed2a8/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 68, Issue 4
> ******************************************