[cisco-voip] Caller ID names and 4.x

[Mark Snow]

Peter,

Erick put it as best it can be put - I am confident this is exactly what is
happening to you with the Carrier's DB names being incorrect - and probably
the terminating carrier's DB.


-Mark Snow 
CCIE Voice # 14073

> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
> bounces at puck.nether.net] On Behalf Of Erick Bergquist
> Sent: Wednesday, December 14, 2005 10:17 AM
> To: Ruttman, Peter G.; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Caller ID names and 4.x
> 
> If you have display IE checked on the gateway, call
> manager will send the name out in setup message. Most
> all carriers ignore that though. The carriers look up
> the calling party number to a name in the database on
> the carriers network and thats where the name comes
> from passed to party being called. I would uncheck
> Display IE on links to the public network. I have also
> seen that confuse some carriers switches in a few
> cases resulting in the calling party # to name
> database lookup not being done right.
> 
> But the last carrier (where the call terminates) could
> use some other database then another carrier so thats
> why names may show up differently sometimes depending
> on where you call. No real easy way to fix this that I
> know of except to push your carrier to make sure the
> name is right for your numbers or call the carrier
> that the person you're calling is using and see if you
> can get them to update their records.
> 
> The other thing is, make sure if using ISDN , that the
> numbering plan and type is set correctly for calling
> party number and/or called party number. If you're in
> the US, setting the calling party number to ISDN and
> National is usually a good starting point. You may
> have to set different numbering plans and types for
> different numbers called though as some carriers like
> to see different settings , and other carriers down
> the line may want something else then another carrier
> to pass caller id right so it shows up. Setting the
> called party number type and plan to Unknown/Unknown
> is a good starting point also, but same thing applies
> -- it depends on carriers, types of switches used, and
> numbers called and what they want to see.
> 
> In most cases, the call will connect and work fine,
> but caller id and other stuff may not work as expected
> if there is a numbering plan/type not liked by someone
> along the way.
> 
> 
> --- "Ruttman, Peter G." <PRuttman at foley.com> wrote:
> 
> > We have two separate clusters (4.02 and 4.13) both
> > that have issues
> > where we mask our outbound caller id numbers with
> > our main number.  For
> > the name we would like it to be the name of our
> > company.  For these two
> > offices we get occasional reports that a person that
> > was once with our
> > company or is still with the company is showing up
> > on the caller ID for
> > people receiving calls from us.  In the case of the
> > retired person that
> > person is not even listed on our Callmanager.  He
> > also only seems to
> > show up when the call ends up at certain carriers
> > like Vonage.
> >
> > Does Callmanager control anything with caller ID
> > name?
> >
> > Pete
> >
> > The preceding email message may be confidential or
> > protected by the attorney-client privilege. It is
> > not intended for transmission to, or receipt by, any
> > unauthorized persons.  If you have received this
> > message in error, please (i) do not read it, (ii)
> > reply to the sender that you received the message in
> > error, and (iii) erase or destroy the message.
> > Legal advice contained in the preceding message is
> > solely for the benefit of the Foley & Lardner LLP
> > client(s) represented by the Firm in the particular
> > matter that is the subject of this message, and may
> > not be relied upon by any other party.
> >
> >
> > Internal Revenue Service regulations require that
> > certain types of written advice include a
> > disclaimer. To the extent the preceding message
> > contains advice relating to a Federal tax issue,
> > unless expressly stated otherwise the advice is not
> > intended or written to be used, and it cannot be
> > used by the recipient or any other taxpayer, for the
> > purpose of avoiding Federal tax penalties, and was
> > not written to support the promotion or marketing of
> > any transaction or matter discussed herein.
> >
> > > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip