OBi1062 Speed Dial setup help needed

<< < (2/2)

Rhine:
Thanks for the interesting work-around. It's not a show stopper not having this automated but I don't think I am alone in wanting this functionality natively on the Obi10xx devices. It's not uncommon to have conf call meetings for business purposes. I currently have three different conf numbers I call on a regular basis with different clients scattered throughout the US.

I have the passcodes written down and enter them manually. Perhaps this feature will be added in a future release.

Would be nice.

I can't see myself going thru all that trouble getting an android phone for the work-around so I'll just continue to do it manually.

Thanks for the creative suggestion!

Jerry

drgeoff:
According to http://www.obitalk.com/forum/index.php?topic=8983.msg68384#msg68384, since 5.0.0.2895 this feature is supported. But it is not crystal clear how to use it.  :(

Quote:
New Feature: Expanded speed dial (using a soft key or feature key) to allow specifying a send parameter to transmit a sequence of DTMF digits to the call peer during a connected call.
End quote.

and for 5.0.0.2824:
"New Feature: Support ;send=... attribute in the Number field of a Speed Dial Feature Key . The value of this attribute specifies a number of digits to send to the remote party, with optional pauses and user input digits in-between."


I haven't found equivalents in the Release Notes for 1xx or 2xx/3xx devices.

oj_dkent:
Has anyone gotten this to work? I am trying to setup a conference number with a code for my Obi1022 and I got the following reply from support:

Quote

Number = {speed-dial-number};send={digits}

{digits} = one or more of the following codes (case-sensitive):

0-9,*,#,a,b,c,d = send corresponding dtmf (100 ms on+off)
S = Delay for 3s
s = Delay for 1s
A = Wait for Answer (or otherwise start sending on early media, if available,
                           or when call is answered, whichever first)
U = Prompt user on phone screen to dial any number of digits manually, then
      click "OK" to continue sending remaining DTMF's
"prompt" = (Only allowed right after a U) An optional prompt to
     show on screen to prompt user to enter digits; default is
     "Press OK to continue".

Here is an example:

{digits} = ASSss1234U"Enter Password"s4567U"sSEnter a code"123#

Means:
Wait for callee to answer, wait 8s, send 1234,
then prompt user to "Enter Password"
When user click OK, wait 1s, then send 4567.
Prompt user to "Enter a code", then send 123#

So I went to my SpeedDial options, added the following (wanting to call 123-555-1234 and enter the code 444-555-666#):

Quote

1235551234;send=AS444555666#

While it does dial the number, it never enters any DTMF tones. ???

Any help is appreciated.

drgeoff:
If you set the speed-dial to only dial the phone number and when answered you enter the code manually does it work?  If not, under Service Providers, ITSP Profile (whichever of A through F is applicable), General there is the parameter DTMF method.  Try all the options available there.

If/when you have it working manually, I would hope the extended speed-dial method will also work.

ianobi:
I tested this using my OBi1032
HardwareVersion 1.3
SoftwareVersion 5.0.0 (Build: 3223.1311)

For me it does work as Obihai Support describe. However, the speed dial number / digits have to be within the "Number" field of a Programmable Key set to "Speed Dial". I set it up like so:

Function: Speed Dial
Service: SP3
Number: 12345678901;send=ASS1234
Other fields not relevant.

Thanks go to oj_dkent for getting Support to release this information. I don't believe that this is documented anywhere within Obihai documentation that has been publicly released.

Edit: This also works with Line Keys when their function is set to "Speed Dial".

Navigation

[0] Message Index

[*] Previous page