Conference Call disconnect with Cause=124

[SgHancock]

I have a unique disconnect issue. User X receives a call from outside party K. Outside party initiates a conference call to add others to the call. User X is dropped from the call with silence on their end. K still sees X as connected but not on call. The logs show the call connected and released with the following:

CMReleaseComp
Line: type=IPLine 350 Call: lid=367 id=8525 in=0
Called[5915] Type=Default (100) Reason=CMDRdirect Calling[2142432927@1.1.2.1] Type=Unknown Plan=Default
Cause=124, Answered By Other(IPO)


This issue can only be re-created when the calling party is on the same service provider network.

System is Avaya IPO Server Edition

Any thoughts would be greatly appreciated.

 

[amriddle01]

The other system is doing a "Refer" and the trunk is dropping the call I'd wager, not much you can do about it, they are controlling the call/actions at that point. They would have the same issue if someone else was on the same platform and they did the same to them.

But X and K, what's that all about?

 

[SgHancock]

Thank you fort he response.
Referring to X as receiving the call and K as the caller. Trying to give some hard evidence to the service provider

 

[amriddle01]

lol I know, but normal people would say A and B or X and Y