Updating CNAME...

OzarkEdge

A request for updating a DID CNAME requires submitting the following:
Phone number:
CNAM: (up to 15 alphanumeric characters, a-z and 0-9 allowed)
Name: (End user name, company name not allowed)
Address: (P.O. Box not allowed)
City:
State:
Zipcode:
Contact number:

So, not as simple as just DID and new CNAME. Presumably the additional data required ends up in a database somewhere? Can anyone comment on what the full affects might be from submitting this request? It's an old Verizon landline DID ported to the ITSP from an address that no longer exists... I'm wondering if I should just leave well enough alone.

px_eliezer_

OzarkEdge

You've been around long enough to know the chaotic situation of CNAME in the US.

Whoever your VoIP provider (ITSP) is, they can push out your desired CNAME to various different databases (LIDB) but there is no guarantee of success and no single database.

Again there are [multiple] LIDB, different (inbound) phone companies choose which LIDB they want to use. TransUnion has a huge one but there are several others.

Does the current CNAME say what you want it to say?

If so, why mess with it.

The service address is nor relevant at all for this situation (sure they want it as part of documentation, but it has no bearing at all on CNAME).

I've observed some CNAME for former Verizon customers who ported to some other carriers, yet the original CNAME seems to stick around even though not specifically requested.

TL/DR; Why mess with it unless there is an issue ???

OzarkEdge

px_eliezer_ TL/DR; Why mess with it unless there is an issue ???

The issue is I left the DID behind for family to use and it still pulls my name, so that's a bit sloppy. The DID usage will increase with rising toddlers (they like calling!) so I'm thinking about getting my name out of their way. Maybe a new DID would do it just as well.

The ITSP is VoIP.ms, of course.

px_eliezer_

OzarkEdge

Understood.

But CNAME is of decreasing value these days anyway.

At my office we see everyday some CNAME that are inaccurate because the caller is on a "family cellphone plan" with their [spouse]---or even with their [parent]---it gets very confusing because everyone on the family plan has the same CNAME.

But if you really want Voip.MS to push out a new CNAME---why not---it may work in some places but not in others, but you'll be no worse off overall.

Voip.MS charges $10 for that, as I recall.

OzarkEdge

px_eliezer_ But if you really want Voip.MS to push out a new CNAME---why not---it may work in some places but not in others, but you'll be no worse off overall.

Voip.MS charges $10 for that, as I recall.

Yeah, I was about to order it up... $10 is not a problem... but then had second thoughts, do I really want to update that other data that is no longer current. I may leave it as is. You make a good point about family plans and CNAME... I've never had a family plan! :-)

px_eliezer_

OzarkEdge

I did a CNAME request through Voip.MS.

It is $10 as you know.

The process was efficient.

On the recipient side, some of the various phone number databases (LIDB) were updated in a few days, while others took a few weeks, as they had told me in advance.

I did realize that I am sort of obligated to keep the number now—if I give it up and someone else gets it, it will still show my name.

But Voip.MS numbers are cheap enough…