Anveo + custom callerID configuration

(1/2) > >>

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:
Quote from: AlanB on March 19, 2014, 04:09:54 pm

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:
Quote from: Marty.ba.calif.usa on March 19, 2014, 04:39:46 pm


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.

Navigation

[0] Message Index

[#] Next page