Solved: Outside caller ID wrong

jasonhilt69 · ‎07-21-2015

CUCM 10.5.2.11900-3, recently upgraded from 6.xx

Calling to an outside number from a remote building, caller ID shows the wrong building on some phone carriers, but is correct on AT&T which provides our PRI lines.

Example: Call to my AT&T cell, caller ID shows correct number. Call to a Verizon phone and some other carriers from same phone and line, caller ID shows the main line number for the high school where all calls go out the PRIs. Remote school calls another remote school by dialing outside, caller ID shows the high school number.

As far as I know we didn't have this issue before the upgrade.

I have checked in the Route Patterns and the "Calling Party Transform Mask" is set correctly for each building.

Calling Line ID Presentation - Default
Calling Name Presentation - Default
Calling Party Number Type - Cisco Callmanager
Calling Party Numbering Plan - Cisco Callmanager

Gateway config on one of the trouble remote schools:

Called Party IE number type unknown* - Cisco CallManager
Calling party IE number type unknown* - Cisco CallManager
Called Numbering Plan* - Cisco CallManager
Calling Numbering Plan - Cisco CallManager

On the PRI config it's:

National
National
ISDN
ISDN

respectively for each one.

Am I missing some other place that would cause Caller ID to be wrong but only on some carriers? I am going to put in a ticket with AT&T, but we all know how that will probably go.

Wilson Samuel · ‎07-21-2015

Hi,

ISDN PRIs can be bit tricky at times, could you please post the debug outputs from debug isdn q931 for both types of calls?

Also, could you please change both Plan and Type as Unknown and see if it makes any difference whatsover?

Regards

View solution in original post

Wilson Samuel · ‎07-21-2015

Hi,

ISDN PRIs can be bit tricky at times, could you please post the debug outputs from debug isdn q931 for both types of calls?

Also, could you please change both Plan and Type as Unknown and see if it makes any difference whatsover?

Regards

jasonhilt69 · ‎07-21-2015

Jul 21 13:04:20: ISDN Se0/3/0:23 Q931: TX -> SETUP pd = 8 callref = 0x2548

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98395

Exclusive, Channel 21

Display i = 'test'

Calling Party Number i = 0x2181, 'xxx7824274'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, 'xxxxxx2222'

Plan:ISDN, Type:National

Jul 21 13:04:20: ISDN Se0/3/0:23 Q931: RX <- STATUS pd = 8 callref = 0xA548

Cause i = 0x82E328 - Information element not implemented

Call State i = 0x01

Jul 21 13:04:20: ISDN Se0/3/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xA548

Channel ID i = 0xA98395

Exclusive, Channel 21

Jul 21 13:04:22: ISDN Se0/3/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0xA548

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jul 21 13:04:24: ISDN Se0/3/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0xA547

Cause i = 0x8090 - Normal call clearing

Cause i = 0x8490 - Normal call clearing

Jul 21 13:04:24: ISDN Se0/3/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x2547

Jul 21 13:04:24: ISDN Se0/3/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xA547

Jul 21 13:04:25: ISDN Se0/3/0:23 Q931: RX <- ALERTING pd = 8 callref = 0xA548

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jul 21 13:04:31: ISDN Se0/3/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x2548

Cause i = 0x8090 - Normal call clearing

Jul 21 13:04:31: ISDN Se0/3/0:23 Q931: RX <- RELEASE pd = 8 callref = 0xA548

Jul 21 13:04:31: ISDN Se0/3/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x2548

Above is a call to my AT&T cell which shows the correct caller ID - xxx7824274

Below is a call to a Verizon phone which shows the incorrect call ID of xxx8626646 on the cell phone.

As you can see the Calling Party Number is correct.

Jul 21 13:10:56: ISDN Se0/3/0:23 Q931: TX -> SETUP pd = 8 callref = 0x2553

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98392

Exclusive, Channel 18

Display i = 'test'

Calling Party Number i = 0x2181, 'xxx7824274'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '1xxxxx1499'

Plan:ISDN, Type:National

Jul 21 13:10:56: ISDN Se0/3/0:23 Q931: RX <- STATUS pd = 8 callref = 0xA553

Cause i = 0x82E328 - Information element not implemented

Call State i = 0x01

Jul 21 13:10:56: ISDN Se0/3/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xA553

Channel ID i = 0xA98392

Exclusive, Channel 18

Jul 21 13:10:57: ISDN Se0/3/0:23 Q931: TX -> CONNECT pd = 8 callref = 0xB615

Display i = 'CT-Main line'

Jul 21 13:10:57: ISDN Se0/3/0:23 Q931: RX <- STATUS pd = 8 callref = 0x3615

Cause i = 0x82E328 - Information element not implemented

Call State i = 0x08

Jul 21 13:10:57: ISDN Se0/3/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x3615

Jul 21 13:10:57: ISDN Se0/3/0:23 Q931: RX <- ALERTING pd = 8 callref = 0xA553

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jul 21 13:10:59: ISDN Se0/3/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x3614

Cause i = 0x8490 - Normal call clearing

Jul 21 13:10:59: ISDN Se0/3/0:23 Q931: TX -> RELEASE pd = 8 callref = 0xB614

Jul 21 13:10:59: ISDN Se0/3/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x3614

Jul 21 13:11:02: ISDN Se0/3/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x2553

Cause i = 0x8090 - Normal call clearing

Jul 21 13:11:02: ISDN Se0/3/0:23 Q931: RX <- RELEASE pd = 8 callref = 0xA553

Jul 21 13:11:02: ISDN Se0/3/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x2553

jasonhilt69 · ‎07-21-2015

Changed the plan and type to unknown and also Cisco Callmanager and no change in ID. AT&T was fine. Sprint and Verizon still show wrong number.

What gets me is if one school calls another school by dialing an outside line, call ID is wrong. I wouldn't think that call would have left AT&Ts network, but I could be wrong.

And what is with the cisco forum site? I keep getting this:

502 Bad Gateway

EdgePrismSSL

shyam2014 · ‎07-21-2015

Hi Jason,

Verizon generally block caller IDs and sends main billing number if you are not requesting otherwise. They will have a calling party number screening removal form which you need to request and after that removal only it will show whatever number you are calling from.

Wilson Samuel · ‎07-21-2015

Hi,

It looks like something in the ATT is doing something different, it may be coincidental with your system upgrade time line. So, I would want to raise a Support Ticket with ATnT explaining the issue.

At the same time, I would want to test the outgoing calls with changing the ISDN = Unknown Plan=Unknown and see if it makes any difference whatsoever.

HTH

jasonhilt69 · ‎07-21-2015

Thank you Wilson Samuel!

Your unknown, unknown, did work. I just missed the "must apply config" for it to take affect.

Test calls are showing correct caller ID now.

jasonhilt69 · ‎07-21-2015

scratch that.

Calls are once again showing wrong ID.

ISDN config still set to Unknown on the main gateway.

UGH!

jasonhilt69 · ‎07-21-2015

So if I click "Apply Config" on the Gateway config page in Cucm I see the gateway reset. Calls then show correct caller ID for about 3 test calls then revert back to showing incorrect number again.

jasonhilt69 · ‎07-21-2015

Problem isn't fixed after all.

Should I start a new discussion or continue on this one?

Mohammed al Baqari · ‎07-21-2015

Sorry but I am not fully clear about the scenario? Are all the schools part of the same UCM cluster. Can you clarify the call routing?

jasonhilt69 · ‎07-21-2015

One Callmanager cluster at our high school. All outside calls go in and out the PRIs at the high school.

Each school has a gateway to handle fax/analog, 911, and in case the link back to the high school goes down.