[cisco-voip] Inbound Caller ID NAME

[Linsemier, Matthew]

Does anyone know when features like this transfer out of a specialized
XW release and are added to the general or T train of code?

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Justin
Steinberg
Sent: Thursday, September 27, 2007 9:03 AM
To: CarlosOrtiz at bayviewfinancial.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Inbound Caller ID NAME

 

H.323 NAME Display feature in 12.4(11) XW

http://www.cisco.com/en/US/products/ps6706/prod_release_note09186a008083
7f1a.html#wp329995

 

On 9/20/07, CarlosOrtiz at bayviewfinancial.com <
CarlosOrtiz at bayviewfinancial.com
<mailto:CarlosOrtiz at bayviewfinancial.com> > wrote:


Can anyone verify Robert's suggested IOS version for inbound Caller ID
to work on H.323?  What additional commands on the gateway and Call Mgr
config are needed? 

Carlos 




Robert Kulagowski <rkulagow at gmail.com> 

09/14/2007 11:30 AM 

To

CarlosOrtiz at bayviewfinancial.com 

cc

cisco-voip at puck.nether.net 

Subject

Re: [cisco-voip] Inbound Caller ID NAME

 

		




> I was looking through the archives and it seems that to get inbound 
> caller ID NAME to work you MUST:
> 
> 1) Use MGCP
> 2) Enable NI2 protocol
> 
> Is this still the case?  Did I miss anything else?

Check the archives a little more! :)

We just discussed this not too long ago.

You can use H.323: either use the cname tcl script that was written by 
David Zilk or the IOS that has this built-in.  12.4.11XU?


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip

 


CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070927/ee67e829/attachment.html