Wondering if you are hitting this, check this out
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy39782
Symptom: cBarge delays by 4 seconds even when previous c-barge is successful within one second of initiation.
Conditions: 1. A calls B 2. B answers the call 3. Shared line users C and D try to cBarge in at the same time. Only one (let’s say, user C) will be successfully cBarge in. 4. CCM starts a timer (ConferenceTimer) for 4 seconds. 5. During these 4 seconds, any other attempts to cBarge in by other shared line users fail even though user C’s has successfully cBarged within a second. 6. Once the timer expires, other shared line user is able to cBarge in.
Workaround: NA
Further Problem Description: This applies to simultaneous cBarge attempts by shared line devices. This issue will be faced due to race condition in signals where ssDataInd for cBarge by the device reaches first, then ssInfoInd comes from the device, due to which ssDataInd, when rejected the signal already, after receiving ssInfoInd, does not reject again here. Due to this it starts a ConferenceTimer and which never gets stopped. After 4 seconds this timer is triggered and after which next successive cbarge will be considered. Ideally, the signal had to be rejected again after receiving ssInfoInd and never start ConferenceTimer for that C-Barge.
Hope this Helps
Cheers
Rath!
***Please rate helpful posts and if applicable mark "Accept as a Solution"***
