Ringing Tone instead busy Tone for non existing number

[mar1us_CS]

Hello Everyone,

I had recently an UC Cluster upgrade from v.11.5 to v.14 and something changed regarding the calls.

When I receive an inbound call to a number which is not configured in Call Manager, I get a ringing tone, instead of a busy or non existent number tone.

Nothing has been changed in the Call Manager, just as I said, an upgrade has been done.

The inbound Call path is:

Provider->H 323 Gateway->Call Manager

Call Manager Version before upgrade: 11.5 SU8

Call Manager version after upgrade: 14.0.1.10000-20

Please, does anyone have an idea where should I look into?

Many thanks.

[Leonardo Santana]

Hi,

Did you check at your voice gateway if these calls are incoming to you?

[mar1us_CS]

Hello,

Yes, I checked on the gateway and the call is coming in, as you can see below:

Dec 10 13:36:35.593: ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x383B
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA18395
Preferred, Channel 21
Calling Party Number i = 0x2180, '137466477'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '3215'
Plan:ISDN, Type:Subscriber(local)
Sending Complete
Dec 10 13:36:35.594: ISDN Se0/1/0:15 Q931: Received SETUP callref = 0xB83B callID = 0x1875 switch = primary-net5 interface = User
Dec 10 13:36:35.601: ISDN Se0/1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xB83B
Channel ID i = 0xA98395
Exclusive, Channel 21
Dec 10 13:36:35.618: ISDN Se0/1/0:15 Q931: TX -> ALERTING pd = 8 callref = 0xB83B
Progress Ind i = 0x8188 - In-band info or appropriate now available
Dec 10 13:36:42.331: ISDN Se0/1/0:15 Q931: TX -> CONNECT pd = 8 callref = 0xB63B
Dec 10 13:36:42.390: ISDN Se0/1/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x363B
Dec 10 13:36:42.391: %ISDN-6-CONNECT: Interface Serial0/1/0:18 is now connected to 1071 N/A
Dec 10 13:36:49.668: ISDN Se0/1/0:15 Q931: TX -> PROGRESS pd = 8 callref = 0xB83B
Cause i = 0x8181 - Unallocated/unassigned number
Dec 10 13:36:54.750: ISDN Se0/1/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x383B
Cause i = 0x8090 - Normal call clearing
Dec 10 13:36:54.751: ISDN Se0/1/0:15 Q931: TX -> RELEASE pd = 8 callref = 0xB83B
Dec 10 13:36:54.810: ISDN Se0/1/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x383B

Interesting is that I can see in the Logs a Disconnect Message with a cause code of 0x8181, which is Unallocated/unassigned number, but the ringing tone can be heard, till i drop the call by myself at the time: 13:36:54.750

Thank you.

[Maren Mahoney]

We're seeing the ISDN side, but not how CUCM is interacting with the H323 gateway. Can you post a trace file that includes this kind of call? (Privately, if you are concerned about security.) That will show us if (and if so, why) CUCM is sending a ringing message.

Maren

[mar1us_CS]

Hello Maren,

Just sent you a private message.

Thank you.