sorry for the delay. for any destination number (say
"2123334444,43333;444"), it would be:
destNum = destNum.replaceAll("#", ENCODE_POUND);
if (destNum.endsWith(ENCODE_POUND)) //calls ending with "#" will fail
{
destNum= destNum.substring(0, destNum.length()-ENCODE_POUND.length
());
}
Intent mIntent = new Intent(Intent.ACTION_CALL, Uri.parse("tel:" +
destNum));
where:
private static final String ENCODE_POUND = "%23";
On Feb 10, 9:22 am, "shimo...@gmail.com" <shimo...@gmail.com> wrote:
> Hi,
>
> Can you share the code snippet you use to call, for example -
> "2123334444,43333;444" ?
>
> (the comma should yield a "timed" pause, the ';' - a "hard" pause -
> waiting for the user to acknowledge before dialing)
>
> Thanks !
>
> On Feb 9, 1:19 pm, legerb <drim...@gmail.com> wrote:
>
> > I had problems with the '#', but when encoded, it works fine. With
> > other symbols i didn't have any problems. And i remember that when '#'
> > was the last char (even encoded), it was always stripped.
>
> > On Feb 9, 9:25 am, "shimo...@gmail.com" <shimo...@gmail.com> wrote:
>
> > > Hi,
>
> > > Using a DEV phone, seems I can not make calls to numbers containing
> > > extra digits (i.e. pauses - either 'hard' or 'timed'). They are
> > > stripped.
>
> > > If I start the call from the built-in contacts app using the
> > > ACTION_VIEW
> > > intent and then tapping a phone field with, say - *151,5555#,1 it is
> > > dialed
> > > ok.
>
> > > Is there any intent other than ACTION_CALL I need to use to start a
> > > call
> > > to a number like *151,5555#,1 to have the device call then send those
> > > extra digits ?
>
> > > Or is there any specific intent data ? type ? extra ?
> > > Or maybe a formatting ?
>
> > > TIA
>
> > > On Feb 8, 6:09 am, Dianne Hackborn <hack...@android.com> wrote:
>
> > > > Not any time soon. Most of the classes there will only work when
> > > > running
> > > > code in the phone process, and making them work in other process would
> > > > be
> > > > significant work.
>
> > > > Also on the G1 I don't believe that anything in the application
> > > > processor
> > > > even has access the voice data stream, so it just wouldn't be able to do
> > > > what you want even if you were modifying the platform itself.
>
> > > > On Sat, Feb 7, 2009 at 11:04 AM, Gero Mudersbach <ger...@web.de> wrote:
> > > > > Hello,
>
> > > > > are there plans to make com.android.internal.telephony available
> > > > > public? As
> > > > > far as I understand it is currently not possible to write e.g. an
> > > > > answering
> > > > > machine "within" the current framework (standard sdk), because direct
> > > > > access
> > > > > to "acceptCall" and hangup methods is missing.
>
> > > > > Best
> > > > > G. Mudersbach
>
> > > > --
> > > > Dianne Hackborn
> > > > Android framework engineer
> > > > hack...@android.com
>
> > > > Note: please don't send private questions to me, as I don't have time to
> > > > provide private support. All such questions should be posted on public
> > > > forums, where I and others can see and answer them.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
