Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

%CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identfier already present in the list of currently handled calls.

000049: Oct 26 14:51:04.181: %VOICE_IEC-3-GW: H323: Internal Error (H323 Interwo

rking Error): IEC=1.1.127.5.21.0 on callID 261 GUID=80316352D0FE011E02002302A5CC

B8F9

000050: Oct 26 15:24:50.315: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a

global identfier already present in the list of currently handled calls. It is b

eing refused.

000051: Oct 26 15:24:50.315: %VOICE_IEC-3-GW: CCAPI: Internal Error (Incoming lo

op): IEC=1.1.180.1.28.0 on callID 0

000052: Oct 26 15:24:50.315: %VOICE_IEC-3-GW: H323: Internal Error (H323 Interwo

rking Error): IEC=1.1.127.5.21.0 on callID 363

According to Cisco it says:

It means that the voice gateway has detected a loop in the call route

What debugs can I do to track this problem down.

All dial peers are like this. They are all voip dial peers with different  destination-patterns and different session target IP addresses. No PSTN dial peers at all.

dial-peer voice 30000 voip
huntstop
destination-pattern 3[01]...
session target ipv4:192.168.99.4
dtmf-relay h245-signal
ip qos dscp cs5 media

  • IP Telephony
18 REPLIES
Silver

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

Hi,

Assuming that there is no CUCM in this mix I would do a debug voip dialpeer and see what dialpeers the call is looping through.

HTH,

Art

Cisco Employee

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

This is a call loop prevention mechanism so that

we do not crash the box by running the CPU too high.

Most likley a config issue, very possible a dialplan

or digit manipulation mis config causing the call to

be looped back to the GW itself.

Also, u should not  configure allow connection

commands (under voice service voip) if this box is

not a CUBE/IPIPGW.

Can u share you config as well?

New Member

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

Show tech attached.

This is an IP to IP Gateway

Silver

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

How often are you seeing this occur?

Is there anything in the logs at approximately the same time that might give a clue?

Please set up the debug voip dialpeer if at all possible as it may give a clue...

HTH,

Art

New Member

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

show logging - part of it is

in my original post

Silver

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

Ok, bear with me,

How long has this system been in place - is it a new system, or is this something that just started on a system that has been in place for awhile?  If so were ther any changes to the infrastructure, or the dialplan in particular?

Have you seen this occur in the past in the logs?  If so how often do you see it?

Have you tried to establish what is causing these: H323: Internal Error (H323 Interworking Error)  ?

Art

New Member

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

Q: How long has this system been in place - is it a new system, or is this something that just started on a system that has been in place for awhile? 

A: My customer says to me that this system has been in place for nearly a year and the problem started only a couple of days ago.

Q: If so were there any changes to the infrastructure, or the dialplan in particular?

A: Again this is the first question I asked and he said “NO CHANGES”. But that is what most customer say – right?

Q: Have you seen this occur in the past in the logs?  If so how often do you see it?

A: Started on 26th Oct 2010. Since the problem started the router has been reloaded and the problem is still there. It is very intermittent and I have to do the debug when I get the problem.

Q: Have you tried to establish what is causing these: H323: Internal Error (H323 Interworking Error)  ?

A: Not sure how to troubleshoot this. The explanation of this message on CCO is not that great.

Silver

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

have to say, laughed out loud at this:

A: Again this is the first question I asked and he said “NO CHANGES”. But that is what most customer say – right?

Thanks!  I needed that!

I'll drag you back to the debug voip dialpeer - I'm still hoping that will identify the call that starts the loop and we can trace from there.

Cheers!

Art

New Member

Re: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global id

Thanks You.

It is going to be hard to catch the problem to do the debug voip dialpeer at the same time.

Can I leave this debug running all the time, so that when the problem occurs we can see what happened in the debug or will that drain CPU cycles.

Also does the   debug voip dialpeer       have any more parameters or just       debug voip dialpeer?

14225
Views
40
Helpful
18
Replies
This widget could not be displayed.