Anveo + custom callerID configuration

[Marty.ba.calif.usa]

I'm testing an Anveo account with my obi110.  On their page for custom callerID numbers, it says

"To use custom CallerID phone numbers you need to enter a phone number(s), click save/update button and then verify it via an automated call. Also, when making calls from SIP device a CallerID prefix can be used before the phone number to use a specific callerid number."

So, I thought maybe I could enter my name and my wife's name (same number, though), which I did, and verified.  So, I have my name on a line starting with "*01" in the column with a heading "SIP Dial Prefix".

I thought I would be able to dial *01xxx-xxx-xxxx" from my phone to choose the first one, and "*02..." for the 2nd.  But when I dial the "*01", I immediately get a busy signal.  In fact, I have found no way to configure this name to be used as my outgoing callerID name.  I can choose it in the DID setup page, and it uses the number, but the name is always one I don't want, which is in the form "Last, First, MI", and there's nowhere I can change this.

With voip.ms, it will take the name from the obi setup itself, but Anveo won't, even if I tell it to.  In that case, it uses a totally different state than even the DID number.

Before I use up a limited support ticket, I'm wondering if there could be a problem with the obi110 setup that gives me the busy signal after *01.  The outgoing digimap seems like it has something to allow for this, although I haven't really learned how they work yet.  It's currently set to (area code 925): 
(*xx|1xxxxxxxxxx|<1925>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)

Any Anveo users have a clue?

[AlanB]

I'm no expert on these at all, but I think you need to set up a "Star Code".  You can find these under the Expert Configuration.

I recently added this one to be able to type *123 from Anveo: *123(<sp2(*123)>), Record Greeting, call($Code)

Looking at the preset star codes, the one I posted, and the documentation (http://www.obihai.com/OBiDeviceAdminGuide#_Toc367543114) might help.  I'm sure others could tell you exactly how to do it.

[AlanB]

One additional comment.  I don't think Anveo can pass two different names for the same phone number.  I don't think they generate the names.  I think the name is registered with a CNAM service.  The RECEIVING party looks up the name in the CNAM service based on the incoming Caller ID phone number.    I'm sure someone will step in to correct me if I'm wrong.

[Marty.ba.calif.usa]

I'm no expert on these at all, but I think you need to set up a "Star Code".  You can find these under the Expert Configuration.

I recently added this one to be able to type *123 from Anveo: *123(<sp2(*123)>), Record Greeting, call($Code)

Looking at the preset star codes, the one I posted, and the documentation (http://www.obihai.com/OBiDeviceAdminGuide#_Toc367543114) might help.  I'm sure others could tell you exactly how to do it.

I thought the star codes were for codes that the obi interpreted, although I think I see what you did.  I actually tried something that worked in a different way;  I added an extra code to the beginning of the digiMap for the ITSP profile for Anveo, to make it look like this:
(*xxx|*xx|1xxxxxxxxxx|<1925>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)
--------  I added the *xxx| to the beginning.

I really don't quite understand what's going on with their outgoing CNAM.  I have a voip.ms account that I'm also experimenting with, and it sends out the name from the obi100. 

Still, Anveo makes it look like I can enter a list of names and callerIDs, as long as the callerID gets verified by them. 

[AlanB]

Still, Anveo makes it look like I can enter a list of names and callerIDs, as long as the callerID gets verified by them. 

I think that's just a list of Caller ID numbers, with the Name being just for your reference.

[Marty.ba.calif.usa]

Still, Anveo makes it look like I can enter a list of names and callerIDs, as long as the callerID gets verified by them. 

I think that's just a list of Caller ID numbers, with the Name being just for your reference.

You might be right about that; it actually might make sense, although it would be nice if it used ther name. 

Or, lacking that, it would be nice if the outgoing name was configurable at all.  I'm also trying out voip.ms, and they use the name from my OBi device, making it easy to change without even going to their website.

[AlanB]

You might be right about that; it actually might make sense, although it would be nice if it used ther name. 

Or, lacking that, it would be nice if the outgoing name was configurable at all. 

Marty,

I thought I read in another post that you have the Personal Unlimited plan. You can configure your outgoing caller ID name on that plan I thought.

It's under "Manage Phone Numbers"..."Edit" desired phone number..."Caller ID" tab. 

[Marty.ba.calif.usa]

Yes, thanks.  I had actually forgotten about that, but I had originally set up a name there, but it has not been used, so far.  It seems like CallerID Name is so confusing that I don't even know if it matters.  For one thing, I just learned today that cell phones don't show the name at all if it's not in the contacts, only the name in the contacts for the phone is shown.

As far as the custom callerIDs, that only chooses the number, not the name.  The name is apparently just an identifier for the entry.

[Marty.ba.calif.usa]

Well, if anyone is interested, I've learned a lot about Anveo, and how this feature works in particular.

First of all, my problems were due to the OBi DigitMap for for "Service Providers ITSP profile for Anveo.  The original setting (don't know where it came from) which I posted in my first post blocked a lot of required information.  Evidently, OBi needs to know when a number is complete to send it, so it was sending it early, and telling Anveo to use CallerID 01, quickdial entry 1 if I sent *011, or quickdial entry 2 for *012, etc. With no quickdial entries, it gave a busy signal.  This feature might be useful to some, but not really to me.

Changing the DigitMap to "(*xx.|1xxxxxxxxxx|<1925>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)" fixed all the problems, although if I wanted to dial something like just *012, there will be a 10 second delay before OBi decides I'm done.

This custom callerID page only chooses the outgoing number, not the name.  In fact, possibly in response to my confustion, they changed the "Name" column to "Title", to emphasize that the name entered is not a callerID name (CNAM), but just a label for the entry to identify it for future use.

The custom callerID is mostly useful for setting up address book entries, I think.  For each person in the address book, you can enter a custom callerID number, and this is where the "Title" is useful.  I have not confirmed whether this is automatically used when you dial out, but I would like to assume it is.

So, it was frustrating, but useful in that I learned a lot about the OBi configuration and the Anveo website and configuration.  It's not so bad once you learn your way around, and their incoming IVR is very good.  I was able to quickly set up a call flow where people not on my contact list need to press 1 to continue, or 2 to leave a message (actually any other key for now), and get disconnected if they don't do anything.

If they are on a blocked list, they get sent immediately to voicemail, or a different blacklist can give them a number disconnected message (or hang up/give busy signal).  This is all really easy to do graphically once you get the hang of it.