 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
|
09-14-07 06:11 PM
> 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?
[ Post a follow-up to this message ]
|
|
|
 |
|
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
|
 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
|
09-27-07 06:12 PM
H.323 NAME Display feature in 12.4(11) XW
http://www.cisco.com/en/US/products...br />
wp329995
On 9/20/07, CarlosOrtiz@bayviewfinancial.com <
CarlosOrtiz@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@gmail.com>*
>
> 09/14/2007 11:30 AM
> To
> CarlosOrtiz@bayviewfinancial.com cc
> cisco-voip@puck.nether.net Subject
> Re: [cisco-voip] Inbound Caller ID NAME
>
>
>
>
>
>
>
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
|
09-27-07 06:12 PM
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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Justin
Steinberg
Sent: Thursday, September 27, 2007 9:03 AM
To: CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@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...ote09186a008083
7f1a.html#wp329995
On 9/20/07, CarlosOrtiz@bayviewfinancial.com <
CarlosOrtiz@bayviewfinancial.com
<mailto:CarlosOrtiz@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@gmail.com>
09/14/2007 11:30 AM
To
CarlosOrtiz@bayviewfinancial.com
cc
cisco-voip@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@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.
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
|
09-27-07 06:12 PM
This may indicate a fix in IOS for H323, but will CallManager 4.1 show
the incoming Calling Party Name on a 79XX just like MGCP ? I've seen
things fixed in IOS, only to have CallManager still not work.
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Linsemier,
Matthew
Sent: Thursday, September 27, 2007 10:46 AM
To: Justin Steinberg; CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Inbound Caller ID NAME
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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Justin
Steinberg
Sent: Thursday, September 27, 2007 9:03 AM
To: CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@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...ote09186a008083
7f1a.html#wp329995
On 9/20/07, CarlosOrtiz@bayviewfinancial.com <
CarlosOrtiz@bayviewfinancial.com
<mailto:CarlosOrtiz@bayviewfinancial.com> > wrote:
Can anyone verify Robert's suggested IOS version for inbound Caller ID
to work on H.323? What additionalcommands on the gateway and Call Mgr
config are needed?
Carlos
Robert Kulagowski <rkulagow@gmail.com>
09/14/2007 11:30 AM
To
CarlosOrtiz@bayviewfinancial.com
cc
cisco-voip@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 scriptthat was written by
David Zilk or the IOS that has this built-in. 12.4.11XU?
________________________________________
_______
cisco-voip mailing list
cisco-voip@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 tothe
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.
________________________________
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
 |  |  |  |  |
 |
 |
|
CarlosOrtiz@bayviewfinancial.com |
|
|
 |
 |


 |
 |
 |
|  |  |  |  |
|
09-27-07 06:12 PM
Not in general but for this particular feature my SE sent an email stating
the following:
"Carlos,
H.323 calling name is a feature that was released in IOS 12.4.11XW and
will be integrated into the mainline release 12.15(1)T. This particular
release has not been "officially" recommended in the "golden bridge" IP
telephony matrix for IOS gateways. Your best option to deliver this
feature to the business would be to go with the latest revision of the XW
train available on CCO currently XW3. The fact that this release is not
included in the IP telephony matrix as a recommended release for gateways
does not mean is a bad release; it should not create any problems for you
but realistically it could as the introduction of new features some times
introduce new issues. I would recommend that you test it on a single site
for a couple of weeks and if all goes well then deploy it to additional
sites."
"Linsemier, Matthew" <MLinsemier@apcapital.com>
Sent by: cisco-voip-bounces@puck.nether.net
09/27/2007 10:45 AM
To
"Justin Steinberg" <jsteinberg@gmail.com>,
<CarlosOrtiz@bayviewfinancial.com>
cc
cisco-voip@puck.nether.net
Subject
Re: [cisco-voip] Inbound Caller ID NAME
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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Justin Steinber
g
Sent: Thursday, September 27, 2007 9:03 AM
To: CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@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...br />
wp329995
On 9/20/07, CarlosOrtiz@bayviewfinancial.com <
CarlosOrtiz@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@gmail.com>
09/14/2007 11:30 AM
To
CarlosOrtiz@bayviewfinancial.com
cc
cisco-voip@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@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.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: Inbound Caller ID NAME |
 |
 |
|
 |  |  |  |  |
 |
 |
|
CarlosOrtiz@bayviewfinancial.com |
|
|
 |
 |


 |
 |
 |
|  |  |  |  |
|
09-27-07 06:12 PM
I will hopefully be testing this out in the coming weeks. If anyone else
does please post your results. I'll send mine when I test it out.
"Jason Aarons \(US\)" <jason.aarons@us.didata.com>
09/27/2007 10:53 AM
To
"Linsemier, Matthew" <MLinsemier@apcapital.com>, "Justin Steinberg"
<jsteinberg@gmail.com>, <CarlosOrtiz@bayviewfinancial.com>
cc
<cisco-voip@puck.nether.net>
Subject
RE: [cisco-voip] Inbound Caller ID NAME
This may indicate a fix in IOS for H323, but will CallManager 4.1 show the
incoming Calling Party Name on a 79XX just like MGCP ? I’ve seen things
fixed in IOS, only to have CallManager still not work.
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Linsemier,
Matthew
Sent: Thursday, September 27, 2007 10:46 AM
To: Justin Steinberg; CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Inbound Caller ID NAME
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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Justin Steinber
g
Sent: Thursday, September 27, 2007 9:03 AM
To: CarlosOrtiz@bayviewfinancial.com
Cc: cisco-voip@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...br />
wp329995
On 9/20/07, CarlosOrtiz@bayviewfinancial.com <
CarlosOrtiz@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@gmail.com>
09/14/2007 11:30 AM
To
CarlosOrtiz@bayviewfinancial.com
cc
cisco-voip@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@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.
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and
deleting it from your computer. Thank you.
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
|
Sponsored Links |
 |
 |
|
|
 |
All times are GMT. The time now is 08:49 PM. |
 |
|
|
 |
|
 |
|
|
 |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
|
|
|
|
Medical and Health forum | Computer Games Reviews | Graphics design forum
|
 |
|
 |
|