<HTML>
<HEAD>
<TITLE>Re: [cisco-voip] Calling Name from PSTN over a Inter-Cluster H.323 (QSIG) Trunk</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Wes,<BR>
<BR>
Thanks for the input... I have still yet to try this, however after looking at this in detail today, I am wondering about scalability. If I have 100 phones on one cluster and 100 on another, will this mean that every call will sit for 6 seconds before its forward to the other cluster with calling name? I also don’t know how this will scale with numerous incoming calls simultaneously.<BR>
<BR>
Would the results be the same using a SIP trunk?<BR>
<BR>
Matt<BR>
<BR>
<BR>
On 5/19/08 1:00 PM, "Wes Sisk" <<a href="wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>try this:<BR>
create a line on a registered phone with wildcards<BR>
612XXXX<BR>
<BR>
stick the phone in the corner and turn off the ringer.<BR>
set the inbound gateway css to hit this dn for incoming calls to 612XXXX<BR>
<BR>
set CFNA timer to something over ~6 seconds and use XXXXXXX<BR>
(literally X's) as the forward no answer destination. This is a mask and will automatically propagate the digits from the current called number.<BR>
Give it a forwarding css that allows it to hit your actual route pattern 612XXXX that points to the cm612 ICT.<BR>
<BR>
you can either play the above games with CSS or you can use different number prefixes, but the result should be the same. so long as the cm413 cluster receives the cname info from pstn before it extends the call the info should be presented to the next hop destination.<BR>
<BR>
/wes<BR>
<BR>
Matthew Linsemier wrote: <BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
I Suspect that you are right in regards to the ICT trunk.<BR>
<BR>
If you call in from the PSTN to the CM 4.1(3) Cluster and answer a CM 4.1(3)<BR>
phone, you get calling name and number (we have had this working via MGCP<BR>
for the last 5 years).<BR>
<BR>
If you then transfer this CM 4.1(3) call (with name and number) over to the<BR>
CM 6.1(2) cluster, you get the name and number of both calling parties<BR>
throughout the transfer.<BR>
<BR>
They both hit the same route pattern which forwards the call over the ICT,<BR>
yet if you direct dial the same number into the CM 4.1(3) cluster, which<BR>
then hits the route pattern and forwards the call over to the CM 6.1(2)<BR>
cluster via the ICT, calling name is dropped.<BR>
<BR>
Thoughts? Ideas?<BR>
<BR>
<BR>
On 5/19/08 11:12 AM, "Wes Sisk" <<a href="wsisk@cisco.com">wsisk@cisco.com</a>> <<a href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>> wrote:<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
Matt,<BR>
<BR>
I suspect this has to do with isdn cname feature and then propagation over<BR>
the ict.<BR>
<BR>
if you:<BR>
call from pstn into cm413 phone<BR>
answer cm413 phone<BR>
do you get calling name/number on cm413 phone?<BR>
if you then consult transfer that call over ict to cm612<BR>
do you get cm413 calling name/number on cm612 phone?<BR>
complete transfer (2nd transfer button)<BR>
do you get pstn calling name/number on cm612 phone?<BR>
<BR>
/Wes<BR>
<BR>
On Mon, 19 May 2008, Matthew Linsemier wrote:<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
So a bit more on this. It looks like calling name works from the outside<BR>
(via MGCP) when the calls comes in via a IPCC Express CTI route<BR>
point/trigger, but not via DID.<BR>
<BR>
Anyone that can offer any input on this would be great. I¹m beating my head<BR>
against the wall trying to get this to work.<BR>
<BR>
<BR>
On 5/15/08 4:52 PM, "Matthew Linsemier" <<a href="MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>> <<a href="mailto:MLinsemier@apcapital.com">mailto:MLinsemier@apcapital.com</a>> wrote:<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
Hello all,<BR>
<BR>
We are currently working on migrating from an existing CallManager 4.1(3)<BR>
cluster to a fresh install of CallManager 6.1(2) in our environment. In our<BR>
4.1(3) environment, our gateways are configured with MGCP with both calling<BR>
name and number displayed from the PSTN. I have configured a non-gateway<BR>
controlled Inter-Cluster H.323 (QSIG) trunk between the two clusters, set up<BR>
a<BR>
few route patterns, and calls are working back and fourth.<BR>
<BR>
I have noticed that calling name is only working from subscribers on the<BR>
CallManager 4.1(3) cluster, and not incoming calls from the PSTN network<BR>
which<BR>
enter that cluster, and then route to the new CallManager 6.1(2) cluster<BR>
over<BR>
the Inter-cluster trunk.<BR>
<BR>
Caller [Matt/1234] --> MGCP GW [Matt/1234] --> CM4.1(3) [Matt/1234] --><BR>
Trunk<BR>
--> CM6.1(2) [1234] --> Phone only displays [1234] with no name.<BR>
<BR>
Is there a way to pass this PSTN caller ID information on or is this a<BR>
limitation? Our hopes were to maintain the same functionality (outside<BR>
calling name) as we migrate users from one cluster to another.<BR>
<BR>
Any input would be greatly appreciated.<BR>
<BR>
Matt<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
CONFIDENTIALITY STATEMENT<BR>
This communication and any attachments are CONFIDENTIAL and may<BR>
be protected by one or more legal privileges. It is intended<BR>
solely for the use of the addressee identified above. If you<BR>
are not the intended recipient, any use, disclosure, copying<BR>
or distribution of this communication is UNAUTHORIZED. Neither<BR>
this information block, the typed name of the sender, nor<BR>
anything else in this message is intended to constitute an<BR>
electronic signature unless a specific statement to the<BR>
contrary is included in this message. If you have received this<BR>
communication in error, please immediately contact me and delete<BR>
this communication from your computer. Thank you.<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
CONFIDENTIALITY STATEMENT<BR>
This communication and any attachments are CONFIDENTIAL and may<BR>
be protected by one or more legal privileges. It is intended<BR>
solely for the use of the addressee identified above. If you<BR>
are not the intended recipient, any use, disclosure, copying<BR>
or distribution of this communication is UNAUTHORIZED. Neither<BR>
this information block, the typed name of the sender, nor<BR>
anything else in this message is intended to constitute an<BR>
electronic signature unless a specific statement to the<BR>
contrary is included in this message. If you have received this<BR>
communication in error, please immediately contact me and delete<BR>
this communication from your computer. Thank you.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
<P><FONT face=Arial color=#808080 size=1>
<HR>
</FONT></P>
<P><FONT color=#808080><FONT face=Arial size=1>CONFIDENTIALITY STATEMENT<BR>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.</FONT> </FONT></P>
<P><FONT color=#808080>
<HR>
</FONT></P>
</BODY>
</HTML>