Beta Feature: Star Codes

Quote:

---

Originally Posted by fisamo

Bummer on the code interception. Is this the "Special Feature" setting on the HT502? I looked at the options that dropdown and see that you can choose 'standard' 'CBCOM' 'RNK' or 'Huawei'. But there's no option for 'disabled' or 'none'... Do you think Grandstream would be willing to allow their vertical service code interceptions to be completely disabled?

---

About a third down on the FXS Port pages..

Enable Call Features: No Yes (if Yes, call features using star codes will be supported locally)

Is this what you mean?

GS will let you disable it, but it also disables call waiting :)

We finally opted to just not fight with it anymore and go with the new numbering and also use some of the local ones on the device (like disabling call waiting) anyway.

Quote:

---

Originally Posted by VOIPoTim

GS will let you disable it, but it also disables call waiting :)

We finally opted to just not fight with it anymore and go with the new numbering and also use some of the local ones on the device (like disabling call waiting) anyway.

---

Disappointing, IMO, but completely understandable. That is one area where the PAP2 has an advantage--you can competely customize feature codes, etc. (No--I'm not advocating/wishing for a different choice in ATAs--just lamenting the inability to easily follow the standard star codes. :(

I must be going nuts..

For me, the *67 only works when calling from one cloned line to the other.

Yesterday the code worked fine. Today, as I look at my call logs, every outbound call has my home number listed as anonymous, yet all the calls went through and when I checked with the receiving ends, they all see my complete CID.

I wonder if there isn't some interaction within the *code database that might cause a scenario like this.

Just tried *67 from my home VOIPo to my cell and 'private' is the only thing that shows. I'm still on sip, by the way..

I accidentally dialed *123 instead of 123 for voicemail and received the confirmation "Thank You" from the system. Any idea what feature I may have enabled or disabled by dialing *123?

* Just received a response from Tim that *12 isn't mapped to any feature in the system so nothing would happen.

Quote:

---

Originally Posted by rcboats24

I accidentally dialed *123 instead of 123 for voicemail and received the confirmation "Thank You" from the system. Any idea what feature I may have enabled or disabled by dialing *123?

* Just received a response from Tim that *12 isn't mapped to any feature in the system so nothing would happen.

---

lol thank goodness the audio response didn't say:
"Thank you for using Voipo. Your account has now been closed", and with that - the unit goes silent.
Could have been worse I guess....:rolleyes:

Thats what I was worried about. Thought there might have been a 'feature' programmed in for those of us trying to use Viatalk's voicemail code on Voipo. :)

Quote:

---

Originally Posted by rcboats24

Thats what I was worried about. Thought there might have been a 'feature' programmed in for those of us trying to use Viatalk's voicemail code on Voipo. :)

---

Now that you mention that, it may not be a bad add to add an alias for that to go to VM since it's unused anyway. I'll add this to our list.

It could prevent some confusion.

Thanks, it would be a help for customers coming from Vonage and Viatalk which both use the *123 for voicemail.

Quote:

---

Originally Posted by orum

Yes, it's a HT502. And I am dialing all the digits at once.

I will try again tomorrow in case this is caused by the recent changes to my account on Friday.

Dan

---

I tried *67 yesterday, and it came up "unknown" on my cell phone. Looks like whatever wasn't working is working now.

Thanks!
Dan