Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CallLost(cause=124)

Status
Not open for further replies.

Rene Heuven

Programmer
May 20, 2017
7
NL
Hi,

I am getting CallLost(cause=124) when the IPO500 is put into a mode where all calls from a hunt group are unconditionally forwarded to a different hunt group (containing a single user). Basically the idea is that all incoming calls are diverted to the mobile phone number of this user. Here is part of the Monitor logs:

16:20:39 676953472mS CMARS: LINE ep Received: CMConnect - child->state = CMCSRinging - ARS Call State = CMCSRinging
16:20:39 676953472mS CMCallEvt: 0.1498.0 24 TargetingEP: RequestEnd 17.1501.0 24 SIPTrunk Endpoint
16:20:39 676953473mS CMTARGET: 17.1497.1 24 SIPTrunk Endpoint: Removed HG from Callinfo
16:20:39 676953473mS CMCallEvt: 0.1499.0 24 ACDTep(Nacht): StateChange: END=??? CMCSIdle->CMCSDelete
16:20:39 676953473mS CMCallEvt: 0.1499.0 -1 BaseEP: DELETE CMEndpoint f52897b8 TOTAL NOW=4 CALL_LIST=1
16:20:39 676953473mS CMTARGET: 17.1497.1 24 SIPTrunk Endpoint: CancelTimer CMTCNoAnswerTimeout
16:20:39 676953474mS CMCallEvt: 0.1498.0 -1 BaseEP: DELETE CMEndpoint f52d3ec8 TOTAL NOW=3 CALL_LIST=1
16:20:39 676953474mS CMARS: CMARSEndpoint::CallLost(cause=124) - Address: 0.1500.0 24 ARS for Main - Call State: CMCSRinging
16:20:39 676953474mS CMCallEvt: 0.1500.0 -1 ARS for Main: StateChange: END=X CMCSRinging->CMCSDelete
16:20:39 676953474mS CMCallEvt: 17.1501.0 24 SIPTrunk Endpoint: StateChange: END=B CMCSRinging->CMCSConnReq
16:20:39 676953475mS CMCallEvt: 17.1497.1 24 SIPTrunk Endpoint: StateChange: END=A CMCSRingBack->CMCSOGConnReq

Any idea how I can resolve the "CallLost(cause=124)"? And where can I find an explaination for the cause number?

This PBX has 1 outgoing SIP Trunk (Line 17). The incoming call uses the same line. Is that or can that be a problem? This has worked before (unknow when this was working the last time, but it has been working before) - and there have been no relevant changes in the configuration.

Best regards,
Rene
 
A cause 124 means the call is answered/redirected to another destination as the targetted destination.
E.g. the call is answered by a call pickup action or send to a divert destination.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top