Inbound caller ID number is my own?

R_Acuti · ‎08-02-2012

Hi folks,

I'm the new CUCM SME at my workplace. The job was dumped in my lap with no training and I won't be getting any. I'm doing my best with online resources available.

Question:

We have a system running CUCM 4.3, and we have established an H.225 trunk for communicating with Tandberg VTC units. When a Tandberg unit dials a Voip phone (7965 or 7970), the incoming phone number is presenting as the number being called. The actual "Who" information is showing correctly. I have tried modifying settings in the trunk configuration page under "Inbound" and "Outbound" calls with no effect.

Specifically:

Calling Party Selection

Calling Line ID Presentation

and Calling Search Space

Any advice?

Thanks.

Rob Huffman · ‎08-02-2012

Hi Richard,

It looks like you are hitting this bug (check the fixed-in versions)

CSCsu02192 - CUCM 5.x - Calling ID is changed to Called Number

Description

Symptom:

IP Phones display the caller ID as the called number rather than the calling number when call comes from Tandberg endpoint.

Conditions:

CUCM 5.1.3

Tandberg calls via H323 GK Controlled Trunk to IP Phone.

Workaround:

None.

Details

First Found in: (1)

5.1

Status:

Fixed

Last Modified:

Dec 23,2011

Fixed in: (15)

7.1(2.10000.16),7.1(0.98999.7),7.1(0.39000.48)

7.0(2.10000.18),7.0(1.11101.1),6.1(3.9999.1)

6.1(3.1000.16),6.1(2.9901.156),6.1(2.1115.2)

6.0(1.3110.1),5.1(3.4111.1),4.3(2.81),4.3(2)ES13

4.2(3)ES77,4.1(3)ES155

Less

Product:

Cisco Unified Communications Manager (CallManager)

Platform:

Dependent

Severity:

3 - moderate

Cheers!

Rob

"Always movin' ahead and never lookin' back" - Springsteen

R_Acuti · ‎08-02-2012

I was pretty excited when I saw this, so I jumped on the other network I maintain, that is running CUCM 8.5. Turns out that it's happening on that system as well. It should definitely be fixed in CUCM 8.5, right? Or am I missing something?

Rob Huffman · ‎08-02-2012

Hi Richard,

You would think that this type of Bug fix would be rolled up into

all future releases of CUCM,......but that is not necessarily the case.

I've made that assumption before and been bitten badly Generally

speaking you have to go with the fixed-in versions. In our example here

we see that the last fixed-in version is 7.1(2) which came out about the

same time that Cisco purchased Tandberg and started pushing towards

Telepresence. One might think that the bug fix development may have ceased

at that point.

Just sayin'

Cheers!

Rob

"Always movin' ahead and never lookin' back" - Springsteen

R_Acuti · ‎08-02-2012

Hm. Perhaps at this point, I should open a trouble ticket and ask Cisco to replicate the problem?

Rob Huffman · ‎08-02-2012

Hi Richard,

A TAC case sounds like an excellent place to go with this Please

let us know your results.

Cheers!

Rob

"Always movin' ahead and never lookin' back" - Springsteen