Call Failure Reason Notifications

the agents should be notified about the reason in case a call fails due to any problem by the user or customer channel ameyo appserver features the toast messages and browser notifications at ameyo user console that shows the reason why the call is failed to connect refer to the following screenshots this feature is available only in ameyo 4 8 ga and later versions the common error messages that will be displayed at the customer end, agent console, and phone are listed in the following table nodes scenarios messages dial node originatecrt party did not answer customer did not answer there was no answer from the customer you may want to try again later user did not answer there was no answer on the user leg you may want to check your extension phone there was no answer from the number you dialled you may want to try again later " party could not be connected reason party could not be connected (action node timed out) generic message the call could not be completed at this time you may want to try again later customer already hung up generic message the call could not be completed at this time you may want to try again later originate timed out generic message the call could not be completed at this time you may want to try again later while adding a call leg failure some entity already hung up generic message the call could not be completed at this time you may want to try again later can not make call, timed out if originatecrtandmakecallnode timeout " unable to make call" generic message the call could not be completed at this time you may want to try again later originatecrtnode determinecallcontextfromusercalllegdetails agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor possible failure reasons callcontextstatemanager null crt object found while determining call context agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor callcontextstatemanager null call leg details found while determining call context agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor callcontextstatemanager determination context map found null while determining and transforming call leg details agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor callcontextstatemanager determination context map doesnt contain key campaign id to get outboundcallcontextdeterminationpolicy agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor callcontextstatemanager failed to determine no outbound policy returned by policy manager agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor callcontextstatemanager outboundcallcontextdeterminationpolicymanager precheck task failed before determination total calls in campaign might have exceeded the max calls alloted in campaign agent channel your extension might not be valid you may have to register your extension again customer channel your extension might not be valid please contact your supervisor phone/third party your extension might not be valid please contact your supervisor amdnode answering machine detected your call reached the answering machine you may want to try again later customer hungup amd failed the call could not be completed at this time you may want to try again later other failure reason coming from asterisk dnc node "customer excluded disposed" call could not be completed as the number is registered for dnc callback scheduled for customer call could not be completed as there is a callback already scheduled for this number contact of customer is registered for do not call (if customer is available in ameyo) call could not be completed as the number is registered for dnc contact is registered for do not call (customer not available in ameyo) call could not be completed as the number is registered for dnc do not call check failed for number due to internal error temporary dnc failure please contact your supervisor do not call check failed due to internal error for number temporary dnc failure please contact your supervisor put on hold node can not be 'put on hold' already hung up call your call cannot be put on hold at this time generic message the call could not be completed at this time you may want to try again later resume node can not resume talk as already hung up your call could not be resumed at this time schedule callback node callbackmanager failed to persist info to db callbackmanager mandator column callback time missing callback could not be scheduled as the time was missing callbackmanager specify futuretime for callback callback could not be scheduled as the time preceded the current time callbackmanager specify agent for selfcallback (if selfcallback is true and userid is not available) self callback could not be scheduled as the user was not available call back manager invalid phone number (if phone is null and customerid is less than 0) callback could not be scheduled the phone number was not valid call back manager record already exist callback could be scheduled as another callback already exists no license for callback if nodeflow stopped in between execution and this event can only be received if the request is placed from the user interface, which means in case of inbound, auto dial, and callback(enqueue by a server) does not receive any event or message generic message the call could not be completed at this time you may want to try again later event → cancel received reasons that are thrown by application directly from different modules like avr (asterisk voice resource), call manager, voice campaign, and others, we send a direct message from the exception so if messages like (messages like no answer, provider temporary failure, and others) have to be thrown as an exception in the application, then this can be possibly sent to user interface