Alpha Feature: Remote Access - Control Features/Dial Out

**frankd1** · 06-30-2009 11:34 AM

+1, tried outcall, CID was not my VOIPo #, but a 714 #.

**VOIPoTim** · 08-17-2009 12:46 PM

Is it recognizing the VOIPo numbers now for you guys?

**tj008** · 08-17-2009 01:30 PM

Not sure. Somehow she doesnt hear my DTMF tones now.

On hold now waiting for support. have the Grandstream 486 with "in audio" checked. Does it require alternate setting?

Will try this alpha feature again when....

Terry

**Xponder1** · 08-17-2009 04:13 PM

Originally Posted by VOIPoTim

Is it recognizing the VOIPo numbers now for you guys?

If you mean when you first connect to it and then dial a VOIPo number then yes I just tested and that worked fine (for my number anyway). Caller id returned was Brivia Comm LLC 1-714-209-7280. That did not work before.

As for feature codes I logged in *MyNumber PASS and tried *67 twice and both times it immediately ended the call. I thought maybe it was because I was not dialing fast enough but the second time I was dialing none stop and it ended the call right after I hit the 7.

Used it to call my home voipo number and caller id info returned was that for the cell phone I was calling from. Is this how its supposed to work? I thought it was supposed to display your VOIPo number?

EDIT- Did some more testing and found that *26 (fail over to voicemail) does work but then tried *25number and it ended the call before I could finish dialing the fail over number.

I also wanted to mention that it seems there is no time out so once you login you can sit there forever with it saying "Please enter the number you wish to call or the feature code to access now" over and over. I would strongly recommend a time out.

Hope this helps.

**voipoh** · 06-30-2009 10:29 PM

Doesn't recognize my number (10 & 11 digit) as a VOIPo number.

Can't login in as account holder. (Note I do have a password in my account but my voicemail is not currently active)

**usa2k** · 08-18-2009 02:12 PM

*30 does not block a call to my VOIPo number from my cell.
(I like that it tells you what you did.)
Calling the cell back from VOIPo said "Unavailable"

*31 did unblock the VOIPo CID feature and the interactive response said so.

Another thought on the HELP subject
** for the long list of * codes would be helpful
"**30" for example for a one code description because you think you know its "Permanently Block Caller ID".

"**code" is a great idea.
"**3" could give you all the "*3_" features ...
Just thinking user-friendly

**VOIPoTim** · 08-17-2009 01:34 PM

Support is a little busy right now so hold times are a little higher than usual due to another large increase in orders hitting homes today due to a HostGator newsletter mailing last week. Lots of initial setup questions.

Ticket may be best if not urgent so you don't have to wait.

**tj008** · 08-17-2009 02:03 PM

played with some settings and tones are working now.

After calling 714 number, SHE asks for your destination number. I enter it. She says not recognized. (shouldnt she recognize your caller ID, know it, then when she asks for the destination number, she should dial it?)

I call again. This time I enter *. She asks for my number and password. then number to call. It worked that way. Woo hoo!

BUT, the caller ID was the 714 number not my voipo number.

It's getting closer.

Terry

**VOIPoTim** · 08-17-2009 02:05 PM

When it first asks for it, it's asking for a VOIPo number to connect you to. The idea is someone could call a local access number and connect to any VOIPo number from it.

To dial non-voipo numbers, you would hit * like you did.

The Caller ID we're working on fixing. It should show your account's CID.

**tj008** · 08-17-2009 02:11 PM

Could she say "Enter your Voipo destination number. For all other numbers, press * "? That would help.

So it must be working in general, except for showing my caller ID. Calls to the 714 number show in my call logs too.

Very nice

Terry