[cisco-voip] Calling Name lost inbound from PSTN over Intercluster Trunk with QSIG

[Jason Aarons (AM)]

Depending on switch/telco could also be a Facility IE vs Display IE issue, I would pull debug q931/debug ccm-manager backhaul packets/ CCM traces and look.  Do 7900 phones on both sides show name on incoming call from PSTN? It's just the ICT that isn't passing name across. Does the ICT work 7900 Phone to 7900 phone with name delivery?

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Monday, October 29, 2012 10:30 AM
To: Linsemier, Matthew
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Calling Name lost inbound from PSTN over Intercluster Trunk with QSIG



What was the answer you got in 2008?   In order for calling name to be delivered to the remote cluster the originating cluster is going to have to send it, and the remote is going to have to honor it.

How is the name delivered on the 6.1 side and what do ccm traces show for what it sends on to the 8.6 cluster?

-Ryan

On Oct 28, 2012, at 4:26 PM, "Linsemier, Matthew" <MLinsemier at thedoctors.com<mailto:MLinsemier at thedoctors.com>> wrote:


All,

I asked this question back in 2008 and I am wondering if anything has changed since then.

I have two Unified Communication clusters, one on 6.1 (existing) and a new one on 8.6 (new greenfield cluster).  They are currently connected via a Intercluster Trunk using QSIG.  Everything is working well across the trunk from internal calling name and number as well as MWI.

The issue we are having is as we move users from the old cluster to the new cluster, inbound calls from the PSTN on the old cluster (via MGCP gateways that are still registered there) destined for users on the new cluster will lose calling name.  This means that during the migration (which will be going on for 3-4 weeks), users on the new cluster will lose Calling Name from outside PSTN users.

PSTN GW - MGCP --> UC6.1 <--- ICT ---> UC8.6 --- Phone

Is there any way to fix this?

Sincerely,

<image001.gif>




Matthew M. Linsemier, CCNP / CCDP
Senior Network Engineer
The Doctors Company


* 517.324.6695
* mlinsemier at thedoctors.com<mailto:mlinsemier at thedoctors.com>





Confidentiality Notice: This message and any attachments hereto may contain confidential and privileged communications or information and/or attorney client communications or work-product protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this e-mail in error, please notify the sender immediately and permanently delete this e-mail.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121029/bbd37c4c/attachment.html>