Call Status

for any call that gets routed via exotel, the status is tabulated based on the direction of the call initiation viz incoming and outgoing, which in turn results in inferring the leg1 status (status of the 1st party on the call i e from number) and leg2 status (status of the 2nd party on the call i e to number) dashboard inbox & reports completed the caller & the callee were successfully connected over a call call attempt the caller hung up before the call could be routed to any of the agents missed call no answer the call was not answered by any of the agents after it rang for the specified duration busy none of the agents were available to answer the call failed calls could not either reach or connect to the agents voicemail based on the call flow, if a voicemail applet is configured, then any calls that end up here would have a final status indicating that it is a ‘voicemail’ dashboard call stats (beta) this feature is available only on demand and might be chargeable please contact your account manager or write to hello\@exotel com what does the status bucket mean on the page? completed the destination number answered the call no answer exotel dialed the number but no one answered before the timeout elapsed canceled the caller disconnected the call during a dial attempt or ringing the destination number busy exotel dialed the number but received a busy response from the destination number inbound calls leg1status will always be 'completed' if the call is picked up by exotel i e , if the caller is connecting to a call flow that has a menu prompt such as greeting, ivr, gather, and voicemail as the first applet leg1status leg2status (dialcallstatus) status description completed completed completed this indicates that a connection was established and audio was exchanged between the caller and the callee completed no answer completed exotel dialed the number but we did not get an answered event back before the timeout value elapsed completed busy completed exotel dialed the number but received a busy response completed failed completed exotel's carriers could not connect the call possible reasons include the number is switched off or not reachable, the number being invalid, transient connection error, etc completed canceled completed exotel dialed the number (leg2) but leg1 disconnected the call before we received the completed / busy / failed / no answer signal (i e before the timeout period elapsed) this can occur if a user disconnects when the call is queued / ringing or as he begins to hear the operator tone suggesting the phone number is invalid or switched off completed n/a (empty) completed the incoming call didn't have a second leg or the user disconnected before exotel reached the connect applet to begin dialing completed n/a missed call this status comes up when all of your agents were busy on other calls or all of them had toggled off leg1status can vary in case the caller is connecting to a call flow that does not have a menu prompt in the beginning as exotel will directly patch the user to the 2nd leg without picking up the call leg1status leg2status (dialcallstatus) status description busy no answer / busy completed exotel dialed the number but we did not get answered event back before the timeout value elapsed or leg2 disconnected in such cases, exotel will send a busy signal back to leg1 no answer no answer completed exotel dialed the number but we did not get answered event back before the timeout value elapsed in such cases, exotel will send a no answer signal back to leg1 busy canceled completed exotel dialed the number but leg1 disconnected the call before the timeout value elapsed in such cases, exotel will receive a busy signal from leg1 note in case of an incoming call, for all purposes, leg2status will determine all scenarios to find out what happened with a call 'status' and 'leg1status' are not really relevant to be used for practical purposes and are present due to archaic (backward compatibility) reasons explanation the overall ‘status’ will always be 'completed' in case of an incoming call as it has successfully arrived at exotel from the caller leg2status (also passed as 'dialcallstatus' in pass thru) will refer to the call status of the callee (to whom the caller wanted to get connected to) of the last attempted number via the connect applet (if it attempts to multiple numbers) outbound calls connecting two numbers (api link) leg1status leg2status (dialcallstatus) status description completed completed completed this indicates that a connection was established and audio was exchanged between the caller and the callee completed no answer no answer this indicates leg1 picked up the call and exotel dialed the leg2 number but we did not get an answered event back before the timeout value elapsed completed busy busy this indicates leg1 picked up the call and exotel dialed the leg2 number but received a busy response completed failed failed this indicates leg1 picked up the call and exotel dialed the leg2 number but exotel's carriers could not connect the call possible reasons include the number is switched off or not reachable, the number being invalid, transient connection error, etc completed canceled failed exotel dialed the number (leg2) but leg1 disconnected the call before we received the completed / busy / failed / no answer signal (i e before the timeout period elapsed) this can occur if a user disconnects before the ringing is completed or as soon as he begins to hear the operator tone suggesting the phone number is invalid / switched off completed n/a (empty) failed this indicates leg1 picked up the call but the call didn't have a second leg or the user disconnected before exotel began to dial no answer n/a (empty) no answer this indicates exotel dialed the leg1 number but we did not get an answered event back before the timeout value elapsed busy n/a (empty) busy exotel dialed the leg1 number but received a busy response failed n/a (empty) failed exotel's carriers could not connect leg1 of the call possible reasons include the number is switched off or not reachable, the number being invalid, transient connection error, etc note in case of an outgoing call, for all purposes, leg1status and leg2status will determine all scenarios to find out what happened with a call 'status' is not really relevant to be used for practical purposes and is present due to archaic (backward compatibility) reasons connecting a number to a call flow (api link) leg1 status leg2 status (dialcallstatus) status description completed completed completed this indicates that a connection was established and audio was exchanged between the caller and the callee completed no answer completed this indicates leg1 picked up the call and exotel dialed the leg2 number but we did not get an answered event back before the timeout value elapsed completed busy completed this indicates leg1 picked up the call and exotel dialed the leg2 number but received a busy response completed failed completed this indicates leg1 picked up the call and exotel dialed the leg2 number but exotel's carriers could not connect the call possible reasons include the number is switched off or not reachable, the number is invalid, transient connection error, etc completed canceled completed exotel dialed the number (leg2) but leg1 disconnected the call before we received the completed / busy / failed / no answer signal (i e before the timeout period elapsed) this can occur if a user disconnects before the ringing is completed or as soon as he begins to hear the operator tone suggesting the phone number is invalid / switched off completed n/a (empty) completed this indicates leg1 picked up the call but the call didn't have a second leg or the user disconnected before exotel began to dial no answer n/a (empty) no answer this indicates exotel dialed the leg1 number but we did not get an answered event back before the timeout value elapsed busy n/a (empty) busy exotel dialed the leg1 number but received a busy response failed n/a (empty) failed exotel's carriers could not connect leg1 of the call possible reasons include the number is switched off or not reachable, the number being invalid, transient connection error, etc note in case of an outgoing call, for all purposes, leg1status and leg2status will determine all scenarios to find out what happened with a call 'status' is not really relevant to be used for practical purposes and is present due to archaic (backward compatibility) reasons points to remember in the call details api, we have the leg1status and leg2status that denote the statuses of those specific legs, in a particular call here, you would also find an additional parameter called ‘canceled’, which would essentially indicate that ‘the call was canceled while queued or ringing’ i e during the call run similarly, in the pass thru applet, we have a ‘dialcallstatus’ that corresponds to leg2status irrespective of the status, a call is charged based on the leg1 or leg2 (or both) having answered a call from an exotel number (exophone), at any given point in time below are the reasons for leg2 which can be n/a (empty/null) no number is returned to dial out the 2nd leg of the call the number is returned but before even exotel starts dialing out, the 1st leg caller dropped the call if there is no leg2 in the call flow glossary leg1status status of the first leg of the call can be one of completed the call was answered and has ended normally busy the caller received a busy signal failed the call could not be completed as dialed, most likely because the phone number was non existent no answer the call ended without being answered canceled the call was canceled while queued or ringing leg2status status of the second leg of the call can be one of completed the call was answered and has ended normally busy the caller received a busy signal no answer the call ended without being answered failed the call could not be completed as dialed, most likely because the phone number was non existent canceled the call was canceled while queued or ringing