DRD Report post Posted 06/22/2017 03:14 PM I have been going through my vgEngine call logs and have seen some OutDial Results such as NOANSWER and NOTCONTACTED that seem to be redundant? DISCONNECTED and BUSY, from what I can tell in these forums, can also both happen if a Busy signal is detected by the Dialogic card. What, if any, distinction is there between these Dispositions? I apologize if I missed this in the Help File but I am very new to VoiceGuide and Dialogic cards. More specifically, I am trying to replicate a problem I have been having that is related to Disconnected calls. However, when I answer and immediately disconnect the call, the Disposition returned is either ANSWERED_LIVE (if I respond) or ANSWERED_UNDETERMINED (if I hang up immediately). What would I need to do differently to force a DISCONNECTED Disposition? Share this post Link to post
SupportTeam Report post Posted 06/22/2017 09:57 PM DISCONNECTED disposition occurs if the call was disconnected without being answered. This can occur if number does not exist (is "out of service"). Can also happen if the call is declined by recipient and call is just dropped without being transferred to voicemail etc. NOANSWER means that call timed out without being answered. BUSY means that the dialed number was busy. The NOTCONTACTED is only set at beginning of call (which you can see in vgEngine log) but you should not see this in the CDR logs. That disposition should be updated with other outcome before being saved in CDR log. If you have any CDR entries that have NOTCONTACTED disposition please post the vgEngine logs that capture those calls (please .ZIP traces before posting them). Or if you can post vgEngine traces for entire day we can scan though them and advise what call outcomes we can see in them and if we can see anything unusual. Share this post Link to post
DRD Report post Posted 06/23/2017 12:57 PM I have quite a lot of NOTCONTACTED Dispositions in my cdrout table... This is one of the calls, as far as I can tell I got all of it. If more are necessary I can provide them, but I have to edit out any personal information so I doubt I can do an entire day's vgEngine trace. 6-17 notcontacted.zip Share this post Link to post
SupportTeam Report post Posted 06/23/2017 08:46 PM Trace shows the outbound call was made but then no signalling of any type was received to advise how this call was progressing. VoiceGuide waited for 2 minutes, and after not being sent any information about that call for 2 minutes it ended the call. This looks to be a T1 ISDN system, correct? (looks like system is using two T1 ISDN trunks, allowing for 46 simultaneous calls to be handled by system) What company is providing those T1 ISDN trunks to you? You need to contact them and advise them that they are not sending any call progress information on some of the outgoing calls that you make. Look at the calls that were connected. On calls that are completed properly you would be seeing "Proceeding" and/or "Alerting" messages (which mean that destination number started ringing) and then either a "Connected" or "Disconnected" or "Busy" etc. None of those messages are being received here. The call that was made just went dead, with no messages about the call received by VoiceGuide system at all... Do you know exactly how these ISDN links that are plugged into your card are provisioned? Are these ISDN lines connected directly from Telco's switch or is there some other equipment in-between Telco's switch and your system ? You should not be seeing calls just go dead like this on properly provisioned ISDN systems. This is a behavior that one may sometimes see on a poorly set up VoIP system - where bandwidth or other similar problems may intermittently stop the VoIP signalling from being properly passed on. You should find out exactly what equipment is being used between the VoiceGuide system and the main Telco switching fabric. And particularity see if at any stage your calls are going though any media gateways that send the calls over VoIP for any leg between your system and the main Telco switching fabric. It looks like there is a unreliable connection somewhere along that path. . Line 4207: 080013.339 7 104 35 state Dialing (auto) 1########## Line 4208: 080013.339 7 104 35 t timer set 90 sec : EV_TIMEOUT_MAKECALL_NORESPONSE Line 4209: 080013.339 7 104 35 Issue_MakeCall begin Line 4210: 080013.339 7 104 35 L1_set Dialing (iState=LS_WAITAFTERDIALINGOUT) Line 4211: 080013.339 7 104 35 L2_set Running_Dialing (called from Issue_MakeCall) Line 4212: 080013.339 7 104 35 rvns add OutDial_Result|NOTCONTACTED Line 4213: 080013.340 7 104 35 ktTel_MakeCall_Enqueue([1##########],DX_PAMDOPTEN, 90,0,0,1##########,<CallerId>1##########</CallerId>) call Line 4214: 080013.340 7 104 35 q_tel + cmd_MakeCall 0 [0,0,90,0,0][1##########|<CallerId>1##########</CallerId>|1##########|DX_PAMDOPTEN|] Line 4218: 080013.342 7 104 35 q_scr run evktTelCompletion sCode=[Completion_MakeCall] iActionID=0, crn=0 [41943094|0|0|0|0][1##########|1##########|<result>ok</result><crn>41943094</crn><crnx>2800036</crnx>|||] 00:00:00 max:1|00:00:00 Line 4219: 080013.342 7 104 35 OnCompletion_ktTel_MakeCall sRet=[<result>ok</result><crn>41943094</crn><crnx>2800036</crnx>] sCidSentThisCall=[1##########] Line 4220: 080013.343 7 104 35 clear the EV_TIMEOUT_MAKECALL_NORESPONSE timer in OnCompletion_ktTel_MakeCall Line 4221: 080013.343 7 104 35 t timer clear (force=False) Line 4222: 080013.343 7 104 35 state Dialing (auto) 1########## . Line 4225: 080013.355 7 104 35 q_scr run evCallState sCode=[GCEV_DIALING] iActionID=0, crn=2800036 [16|0|16|0|0][|||||] 00:00:00 max:1|00:00:00 Line 4226: 080013.355 7 104 35 callstate crn_event=2800036 0|GCEV_DIALING state=16|Dialing calldirection=0 gcCallState=16 [||], ScriptState=LS_WAITAFTERDIALINGOUT Line 4227: 080013.355 7 104 35 LineEvCallState L1_current=Dialing crn_event=2800036,ev=0,GCEV_DIALING,0, sParam1= Line 4228: 080013.355 7 104 35 LineEvCallState LINECALLSTATE_DIALING begin Line 4229: 080013.355 7 104 35 state Dialing (auto) 1########## .. Line 4230: 080013.355 7 104 35 t timer set 120 sec : EV_TIMEOUT_AFTERDIALING_AWAIT Line 6497: 080212.703 7 104 35 q_scr run evScriptEvent sCode=[EV_TIMEOUT_AFTERDIALING_AWAIT] iActionID=0, crn=0 [0|0|0|0|0][|||||] 00:00:00 max:2|00:00:00.0140000 Line 6498: 080212.703 7 104 35 se EV_TIMEOUT_AFTERDIALING_AWAIT 9016 0|0|0 || LineState=LS_WAITAFTERDIALINGOUT Line 6499: 080212.703 7 104 35 LsWaitAfterDialingOut : 9016,0,EV_TIMEOUT_AFTERDIALING_AWAIT,0,0,0,,, Line 6500: 080212.703 7 104 35 t timer clear (force=False) Line 6501: 080212.703 7 104 35 dial OnOutboundCallNotAnswered begin, RetriesLeft=0 Line 6502: 080212.703 7 104 35 dial DeleteFromOutDialQue ID=7195969 Line 6503: 080212.703 7 104 35 dial no escalation calls Line 6504: 080212.703 7 104 35 LsWaitAfterDialingOut EV_TIMEOUT_AFTERDIALING_AWAIT Line 6505: 080212.703 7 104 35 HangupCall (EV_TIMEOUT_AFTERDIALING_AWAIT) crn_in=0, L1=Dialing, L2=Running_Dialing, lPlayId=0, lRecId=0 Line 6506: 080212.704 7 104 35 ccrn_connected=0, crn_NewCallArriving=0, crn_CurrentMakeCall=2800036, crn_InProcessOfReleasing=0 Line 6507: 080212.704 7 104 35 rv add Hangup Source|EV_TIMEOUT_AFTERDIALING_AWAIT Line 6508: 080212.704 7 104 35 HangupCall sScriptToRunOnHangup=[] Line 6509: 080212.704 7 104 35 no script running on this line. AfterHangup script will not be ran. Line 6510: 080212.704 7 104 35 rv add DropCall_Source| Line 6511: 080212.704 7 104 35 crn 0 set to crn_makecall 2800036 Line 6512: 080212.704 7 104 35 HangupCall for an outgoing call that was disconnected before connecting to destination. no new call arriving Line 6513: 080212.704 7 104 35 L1_set Disconnect_Pending (iState=LS_WAITAFTERDIALINGOUT) Line 6514: 080212.704 7 104 35 state Hanging up... [EV_TIMEOUT_AFTERDIALING_AWAIT] Share this post Link to post