Mailing List Archive

The outgoing *name* is not generated by your equipment -- it's done by a
reverse-lookup that is done on the far-end (called party's) switch.

I did some research a while ago when calls made from one of our PRI's
would appear on CID displays with a number but no name. As it turned
out, there was some misconfiguration between our PRI provider and the
company that maintained the master database. Who maintained the
database? Verisign. Surprise. Turns out that Verisign bought up the
company that maintains the database a couple years ago.

As far as the displayed *number* goes, it's up to your PRI provider to
determine what you're allowed to put there. On our AT&T PRI, we can put
anything we want. On our Verizon PRI, they won't let us put anything --
they force the DID number that was used to place the call.

-----Original Message-----
From: Oliver Rebollido [mailto:ORebollido@fenwick.com]
Sent: Tuesday, December 16, 2003 11:28 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Outgoing Caller ID


We're in the process of changing our outgoing caller ID from
"Unavailable" to showing something (we have yet to decide what will
appear). We have CallManager 3.2(2), and I've looked all over, but is
it actually possible to configure the name of the outgoing caller ID?
I'm assuming that is something that is controlled by the local phone
company. I was thinking of showing the company name and main number or
user name and direct number. What outgoing caller ID setup do most of
you have?

Thanks,
Oliver

ATTENTION

The information contained in this message may be legally privileged

and confidential. It is intended to be read only by the individual

or entity to whom it is addressed or by their designee. If the reader

of this message is not the intended recipient, you are on notice that

any distribution of this message, in any form, is strictly prohibited.



If you have received this message in error, please immediately notify

the sender and/or Fenwick & West LLP by telephone at (650) 988-8500



and delete or destroy any copy of this message.




#####################################################################################
CONFIDENTIAL: This e-mail, including its contents and attachments, if any, are confidential. It is neither an offer to buy or sell, nor a solicitation of an offer to buy or sell, any securities or any related financial instruments mentioned in it. If you are not the named recipient please notify the sender and immediately delete it. You may not disseminate, distribute, or forward this e-mail message or disclose its contents to anybody else. Unless otherwise indicated, copyright and any other intellectual property rights in its contents are the sole property of Mizuho Securities USA Inc.
E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Although we routinely screen for viruses, addressees should check this e-mail and any attachments for viruses. We make no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that to ensure regulatory compliance and for the protection of our customers and business, we may monitor and read e-mails sent to and from our server(s).
#####################################################################################

it depends.

it depends on how your PSTN circuits are provisioned. The carrier can send
CNAME as sent by the originating equipment or it can do a database lookup
and send the name the number is registered to.

Callmanager has supported sending calling party name in a display IE back to
the 3.0 days.
Most CO's have moved to switches using NI-3 protocol (national protocol,
revision 3) which sends and expects to receive calling name in a ROSE
encoded Facility IE. Callmanger 3.3(3) and later supports this.

Usually telco's expect to receive the calling party number with
calling party IE number type = national
calling number plan = isdn

some telco's require different settings here, just depends how they are
configured. most cannot tell you, so there are only 4 or so values for each
so try permutations until you find the one that works for you. If your
telco requires name in the facility IE, set the "send calling number in
faciliity IE" on the MGCP gateway config page in CCMAdmin and reset the
gateway. use q931translator.exe to look at detailed CCM traces to see if
your CCM is sending the calling party name on outbound setup messages to
your carrier.

frequently carriers will drop calling party name when the call passes to
another carrier, keep this in mind when doing your testing. they will drop
it 99% of the time if the plan/type as discussed above is incorrect.

As for how to specify the name, you have to configure it on the line
configuration page of the phone.

/Wes
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Grabowski, David
Sent: Tuesday, December 16, 2003 12:41 PM
To: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Outgoing Caller ID


The outgoing *name* is not generated by your equipment -- it's done by a
reverse-lookup that is done on the far-end (called party's) switch.

I did some research a while ago when calls made from one of our PRI's
would appear on CID displays with a number but no name. As it turned out,
there was some misconfiguration between our PRI provider and the company
that maintained the master database. Who maintained the database? Verisign.
Surprise. Turns out that Verisign bought up the company that maintains the
database a couple years ago.

As far as the displayed *number* goes, it's up to your PRI provider to
determine what you're allowed to put there. On our AT&T PRI, we can put
anything we want. On our Verizon PRI, they won't let us put anything -- they
force the DID number that was used to place the call.
-----Original Message-----
From: Oliver Rebollido [mailto:ORebollido@fenwick.com]
Sent: Tuesday, December 16, 2003 11:28 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Outgoing Caller ID


We're in the process of changing our outgoing caller ID from
"Unavailable" to showing something (we have yet to decide what will appear).
We have CallManager 3.2(2), and I've looked all over, but is it actually
possible to configure the name of the outgoing caller ID? I'm assuming that
is something that is controlled by the local phone company. I was thinking
of showing the company name and main number or user name and direct number.
What outgoing caller ID setup do most of you have?

Thanks,
Oliver
ATTENTION
The information contained in this message may be legally privileged
and confidential. It is intended to be read only by the individual
or entity to whom it is addressed or by their designee. If the reader
of this message is not the intended recipient, you are on notice that
any distribution of this message, in any form, is strictly prohibited.

If you have received this message in error, please immediately notify
the sender and/or Fenwick & West LLP by telephone at (650) 988-8500

and delete or destroy any copy of this message.



----------------------------------------------------------------------------
--

CONFIDENTIAL: This e-mail, including its contents and attachments, if any,
are confidential. It is neither an offer to buy or sell, nor a solicitation
of an offer to buy or sell, any securities or any related financial
instruments mentioned in it. If you are not the named recipient please
notify the sender and immediately delete it. You may not disseminate,
distribute, or forward this e-mail message or disclose its contents to
anybody else. Unless otherwise indicated, copyright and any other
intellectual property rights in its contents are the sole property of Mizuho
Securities USA Inc.

E-mail transmission cannot be guaranteed to be secure or error-free. The
sender therefore does not accept liability for any errors or omissions in
the contents of this message which arise as a result of e-mail transmission.
If verification is required please request a hard-copy version.

Although we routinely screen for viruses, addressees should check this
e-mail and any attachments for viruses. We make no representation or
warranty as to the absence of viruses in this e-mail or any attachments.
Please note that to ensure regulatory compliance and for the protection of
our customers and business, we may monitor and read e-mails sent to and from
our server(s).