cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
715
Views
5
Helpful
2
Replies

CUBE %CALL_CONTROL-6-CALL_LOOP error, Is there a way to allow it?

PP75
Level 1
Level 1

Hi,

I have a CUBE that is sending an INVITE to a proxy, and in some cases the proxy just sends the call back the CUBE.

This causes the following error:

*Nov 29 22:20:37.652: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.



*Nov 29 22:20:37.653: //-1/69C3C8328124/CCAPI/cc_api_call_setup_ind_common:

   SPI Call Setup Request Is Failed

I think I understand why, as the Call-ID matches on the outgoing and incoming dial-peer as its just a proxy and not B2B

 

However, I need to allow this call. Is there a way to disable the check?

 

Many thanks

1 Accepted Solution

Accepted Solutions

PP75
Level 1
Level 1

I managed to allow the same call back by using a sip-profile to remove the Cisco-Guid header outbound to the proxy.

 

View solution in original post

2 Replies 2

Hi,

This can't be disabled. Its built in CUBE to avoid call loops that
exhaust the CPU. The proxy should be configured to stop hunting if the
destination dial-peers are down or can't complete the call.

**** please remember to rate useful posts

PP75
Level 1
Level 1

I managed to allow the same call back by using a sip-profile to remove the Cisco-Guid header outbound to the proxy.