Too many the same calls in "show isdn active"

[michal_madejowski]

I have a problem, on one of my gateway i have too much calls in command "show isdn active", please see there are doubled calls:

I have no idea why this is happening.

Number 227785XXX is a company number and numbers 695 66X XXX are custumers numbers. This situation repeats practically every few moments. My IOS version: ROM: System Bootstrap, Version 15.0(1r)M6, RELEASE SOFTWARE (fc1). In attachment I upload "show call active voice brief" command from this case.

[Jitender Bhandari]

Hi

Sounds like a process leak, What do get fro "show voice call status".

JB

[michal_madejowski]

I have something like this:

[Jitender Bhandari]

Hi,

As i said earlier, sounds like process leak, first recommendation would be to upgrade the IOS to see if that clears the issue as it seems like there are hung session on router. which as you informed are cleared by reboot and then piles up slowly.

Troubleshooting the issue would require reboot and getting the gateway to clear all zombie process. Then run schedule  debug from the time there are no session to the time you see the first hung session to get to root cause.

Above process is time\resource consuming, if you are after the resolution try upgrading to see if that clears the issue.

(Rate if it helps)

JB

[Manish Gogna]

A router reload should help clear these stale/duplicate entries. if the issue persists then it needs to be investigated via debugs for a few test calls to see if the IOS is being affected by a bug. try to find if calls to any specific phone type or calls invoking any specific mid call features are being shown as duplicate to narrow down the issue.

HTH

Manish

[michal_madejowski]

I have new cases in every minutes, for ex. situation from now:

Types of phones you means model of phones?

[Mohamed Amine Jaafar]

Also, you may have a call loop in your configuration.

Double-check this with "debug isdn q931", if the duplicate entries appear at the same time when the debug shows multiple instances similar to this :

Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9838E

                Exclusive, Channel 14

        Calling Party Number i = 0x0081, '227785XXX'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '69566XXXX'

                Plan:Unknown, Type:Unknown

Then it means you have a call loop in your configuration (assuming the problem is not from telco side).

[michal_madejowski]

maybe it's doubled, I do isdn 931 debug when we have this type of call:

RTR-VG-02#show isdn active
--------------------------------------------------------------------------------
ISDN ACTIVE CALLS
--------------------------------------------------------------------------------
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle Units/Currency
--------------------------------------------------------------------------------
In 697281XXX 227785XXX 906 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
In 227785XXX 225637XXX 15 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
In 227785XXX 225637XXX 15 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
In 227785XXX 225637XXX 15 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
In 227785XXX 225637XXX 15 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
In 227785XXX 225637XXX 15 0 0
Out 227785XXX 225637XXX 15 0 0 0.29 ZL
Out 227785XXX 883159XXX 2 0 0 0.29 ZL
Out 2277854XXX 606320XXX 1 0 0 0.29 ZL
--------------------------------------------------------------------------------

and the log from debug:

Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA18387
Preferred, Channel 7
Calling Party Number i = 0x0181, '227785XXX'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '225637XXX'
Plan:ISDN, Type:Unknown
701301: Apr 7 07:43:24.213: ISDN Se0/0/1:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8915
Channel ID i = 0xA98387
Exclusive, Channel 7
701302: Apr 7 07:43:24.221: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref = 0x39A1
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98388
Exclusive, Channel 8
Calling Party Number i = 0x0181, '227785XXX'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '225637XXX'
Plan:ISDN, Type:Unknown
701303: Apr 7 07:43:24.221: ISDN Se0/0/1:15 Q931: Received SETUP callref = 0xB9A1 callID = 0x69B5 switch = primary-net5 interface = User
701304: Apr 7 07:43:24.229: ISDN Se0/0/1:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 227785XXX
701305: Apr 7 07:43:24.229: ISDN Se0/0/1:15 Q931: Sending SETUP callref = 0x0916 callID = 0x8009 switch = primary-net5 interface = User
701306: Apr 7 07:43:24.229: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xB9A1
Channel ID i = 0xA98388
Exclusive, Channel 8
701307: Apr 7 07:43:24.229: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8 callref = 0x0916
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA18389
Preferred, Channel 9
Calling Party Number i = 0x0181, '227785XXX'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '225637XXX'
Plan:ISDN, Type:Unknown
701308: Apr 7 07:43:24.237: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x8909
Date/Time i = 0x110407092B18
Date (dd-mm-yr) = 17-04-07
Time (hr:mnt:sec) = 09:43:24
701309: Apr 7 07:43:24.237: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0909
701310: Apr 7 07:43:24.249: ISDN Se0/0/1:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8916
Channel ID i = 0xA98389
Exclusive, Channel 9
701311: Apr 7 07:43:24.249: ISDN Se0/0/0:15 Q931: RX <- FACILITY pd = 8 callref = 0x8909
Facility i = 0x91A11D020280570201213014A10C81025A4CA20681011D820101820100830100
Protocol Profile = Remote Operations Protocol
0xA11D020280570201213014A10C81025A4CA20681011D820101820100830100
Component = Invoke component
Invoke Id = 32855
Operation = AOCDCurrency
Currency = ZL
Currency amount = 29, Multiplier = 1/100
Type of charging : Subtotal
701312: Apr 7 07:43:24.253: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref = 0x39A2
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838A
Exclusive, Channel 10
Calling Party Number i = 0x0181, '227785XXX'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '225637XXX'
Plan:ISDN, Type:Unknown
701313: Apr 7 07:43:24.253: ISDN Se0/0/1:15 Q931: Received SETUP callref = 0xB9A2 callID = 0x69B6 switch = primary-net5 interface = User
701314: Apr 7 07:43:24.265: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 227785XXX
701315: Apr 7 07:43:24.265: ISDN Se0/0/0:15 Q931: Sending SETUP callref = 0x0917 callID = 0x800A switch = primary-net5 interface = User
701316: Apr 7 07:43:24.265: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xB9A2
Channel ID i = 0xA9838A
Exclusive, Channel 10
701317: Apr 7 07:43:24.265: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0917

[Mohamed Amine Jaafar]

Thanks.

Yes channels 7, 8, 9 and then 10 are progressively allocated to the same call. It's a clear symptom of a call loop in the VG configuration.

Can you attach your show-run in order to investigate it and found out why there's a loop ?

[michal_madejowski]

I cant send you all of show run config. I deleted some information from this but leave any something that may be helped in this case. Please write what of section do you want to check. A few minute ago I encountered a similar situation with number:227785375

[Mohamed Amine Jaafar]

Thanks Michal,

I've seen the show run and surely it's a complex dial-plan to be *theorically* analyzed.

But I'm sure the call is looping since it enters then returns back in/from the same E1 link (one time is Setup TX, then afterwards it's Setup RX, then again Setup TX etc.)

You may troubleshoot further the dial-peer selection when it happens with "debug voip dialpeer detail" to see what outgoing dial-peers are matched.

Can you post the debug voip dialpeer detail as it happens ?

Sorry but the configuration is complex to be only interpreted by reading it.

[michal_madejowski]

I know it'a complex configuration. No problem with debug, here in attachment I upload 5 minutes logs from "debug voip dialpeer detail" when I catched this looped call. Show isdn active is there too so You can find a numbers that relate to this call