[cisco-voip] Call loop between CME and CUBE

[Nick Matthews]

>From these dial peers I cant tell what translations are going on.  This is
almost certainly a misconfiguration with your dial peers.  If your CUBE is
somehow sending the 999 back to your CME it will cause a call loop from what
you describe.

-nick

On Wed, Sep 29, 2010 at 8:22 AM, Marty van de Veerdonk <
marty at voiceidentity.nl> wrote:

> Hello,
> I want to test my CME-CUBE config by sending a call from CME extension 565
> to CME extension 0201234567 via the CUBE. I'm using a second dailpeer to
> test it.
> The CME uses the format 999T to send the call to CUBE. The dailpeers below
> are configured on the CUBE.
>
> The call gets forwared from the CME towards the CUBE, but in the CUBE it
> seems that is getting into a kind of loop.
>
> Is this a IOS bug or a design fault?
>
> ##PART OF ERROR LOG ##
> *Sep 29 12:13:14: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global
> identfier already present in the list of currently handled calls. It is
> being refused.
>
> ## PART OF CUBE CONFIG ##
> !
> voice translation-rule 99956
>  rule 1 /^999/ /0201234/
> !
> !
> voice translation-profile CME_99956X
>  translate calling 99956
>
> dial-peer voice 1012 voip
>  destination-pattern 02012345..
>  redirect ip2ip
>  session protocol sipv2
>  session target ipv4:192.168.1.12
>  incoming called-number 02012345..
>  voice-class codec 1
>  dtmf-relay rtp-nte
>  ip qos dscp cs5 media
>  ip qos dscp cs4 signaling
>  no vad
> !
> dial-peer voice 1013 voip
>  translation-profile outgoing CME_99956X
>  destination-pattern 999567
>  redirect ip2ip
>  session protocol sipv2
>  session target ipv4:192.168.1.12
>  incoming called-number 99956.
>  voice-class codec 1
>  dtmf-relay rtp-nte
>  ip qos dscp cs5 media
>  ip qos dscp cs4 signaling
>  no vad
> !
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100929/46b22f9b/attachment.html>