cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1314
Views
0
Helpful
2
Replies
Highlighted
Beginner

B-ACD breaks when sip trunk is installed

B-ACD pilot number is 380 (I have tried setting up multiple B-ACD's on various pilot numbers to no avail).

Prior to SIP trunk being setup I can call the B-ACD fine, everything works as it should (I should mention this is ALL internal calling)

I then setup a "Generic SIP Trunk" using CCA 3.0(1) with only details for the proxy server and domain name.

The B-ACD now breaks and the error I get in the CLI is "%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"

Now I also had this issue earlier and Voicemail wasn't work either (399), but I updated the software to 8.2.0 and the voicemail stays up but the B-ACD doesnt.

I have tried debugging and gathering information etc etc and have tried chaning translation-rules etc no to avail.

This is what I think is happening:

Call to 380 is made

Correct Dial-peer is chosen (5002)

transalation rule is enforced.

number gets changed to ABCD380

next dial-peer is chosen (1003)

call falls over.

This is from debug voice ccapi error

   CALL_ERROR; Incoming Loop Call Is FoundIncoming Loop Call Is Found;

   Guid=AB833CB7-BE4F-11E0-8155-CB9A5DC23CE9; Calling Number=291;

   Called Number=ABCD380; Remote IP Address=10.12.115.41; Direction=XRULE_INCOMING;

   Incoming Dial-peer=1003; Return Code=-16

Below are the translation rules and the dial peers affected.

!

voice translation-rule 411

rule 1 /^0\(.*\)/ /ABCD0\1/

rule 5 /^\(...\)$/ /ABCD\1/

!

voice translation-rule 412

rule 1 /^ABCD\(.*\)/ /\1/

!

voice translation-rule 1000

rule 1 /.*/ //

!

!

voice translation-rule 1112

!

voice translation-rule 2001

!

voice translation-rule 2002

rule 1 /^6/ //

rule 2 /^A/ //

!

voice translation-rule 2222

!

!

voice translation-profile CALLER_ID_TRANSLATION_PROFILE

translate calling 1111

!

voice translation-profile CallBlocking

translate called 2222

!

voice translation-profile OUTGOING_TRANSLATION_PROFILE

translate called 1112

!

voice translation-profile PSTN_CallForwarding

translate redirect-target 410

translate redirect-called 410

!

voice translation-profile PSTN_Outgoing

translate calling 1111

translate called 1112

translate redirect-target 410

translate redirect-called 410

!

voice translation-profile SIP_Incoming

translate called 411

!

voice translation-profile SIP_Passthrough

translate called 412

!

voice translation-profile TestIncoming_Called_5

translate called 5

!

voice translation-profile XFER_TO_VM_PROFILE

translate redirect-called 2002

!

voice translation-profile incoming_Called_6

translate called 6

!

voice translation-profile nondialable

translate called 1000

!

!

dial-peer voice 5002 voip

description *** CCA BACD ***

service aaservice0

destination-pattern 380

session target ipv4:10.12.115.41

incoming called-number 380

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

!

!

dial-peer voice 1003 voip

description ** Passthrough Inbound Calls from CUE **

translation-profile incoming SIP_Passthrough

b2bua

session protocol sipv2

session target ipv4:10.1.10.1

incoming called-number ABCDT

dtmf-relay sip-notify

codec g711ulaw

no vad

!

Is anyone able to help please? I'm stuck!

2 REPLIES 2
Highlighted
Beginner

Issue was related to the CCA i was using, needed to upgrade to CCA 3.1, removed SIP trunk and re-added, all working ok.

There is also a work around.

Under dial-peer 5002, change the following

no incoming-called number 380

incoming called number ABCD380.

This apparently fixes it.

I  also found another work around which is related to the translation-rules,  specifically rule 411 rule 5, removing ABCD from there, but I think it's  a little too messy and would cause other issues relating to other calls.

Highlighted

Yes, this was a bug introduced by CCA 3.0.1 (CSCto34902) that was fixed in CCA 3.1.   The best workaround from the CLI was to change the "incoming called number" on the BACD dial-peer as you describe.

Glad you were able to use CCA 3.1 to get the fix!  

Laura