[cisco-voip] Calling Name from PSTN over a Inter-Cluster H.323 (QSIG) Trunk

[Wes Sisk]

Matt,

I suspect this has to do with isdn cname feature and then propagation over 
the ict.

if you:
call from pstn into cm413 phone
answer cm413 phone
do you get calling name/number on cm413 phone?
if you then consult transfer that call over ict to cm612
do you get cm413 calling name/number on cm612 phone?
complete transfer (2nd transfer button)
do you get pstn calling name/number on cm612 phone?

/Wes

On Mon, 19 May 2008, Matthew Linsemier wrote:

> So a bit more on this.  It looks like calling name works from the outside
> (via MGCP) when the calls comes in via a IPCC Express CTI route
> point/trigger, but not via DID.
>
> Anyone that can offer any input on this would be great.  I¹m beating my head
> against the wall trying to get this to work.
>
>
> On 5/15/08 4:52 PM, "Matthew Linsemier" <MLinsemier at apcapital.com> wrote:
>
>> Hello all,
>>
>> We are currently working on migrating from an existing CallManager 4.1(3)
>> cluster to a fresh install of CallManager 6.1(2) in our environment.  In our
>> 4.1(3) environment, our gateways are configured with MGCP with both calling
>> name and number displayed from the PSTN.  I have configured a non-gateway
>> controlled Inter-Cluster H.323 (QSIG) trunk between the two clusters, set up a
>> few route patterns, and calls are working back and fourth.
>>
>> I have noticed that calling name is only working from subscribers on the
>> CallManager 4.1(3) cluster, and not incoming calls from the PSTN network which
>> enter that cluster, and then route to the new CallManager 6.1(2) cluster over
>> the Inter-cluster trunk.
>>
>> Caller [Matt/1234] --> MGCP GW [Matt/1234] --> CM4.1(3) [Matt/1234] --> Trunk
>> --> CM6.1(2) [1234] --> Phone only displays [1234] with no name.
>>
>> Is there a way to pass this PSTN caller ID information on or is this a
>> limitation?   Our hopes were to maintain the same functionality (outside
>> calling name) as we migrate users from one cluster to another.
>>
>> Any input would be greatly appreciated.
>>
>> Matt
>>
>
>
> 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.
>