Post new topic Reply to topic  [ 5 posts ] 

Board index : TeleFlow Forums : NMS Communication Boards

Author Message
 Post subject: Errors generated when attempting to place an outbound call
PostPosted: Thu Jun 05, 2008 3:42 pm 
Offline

Joined: Wed Mar 12, 2008 1:14 pm
Posts: 59
Location: Atlanta, GA
Hello - We are getting errors whenever we try to place an outbound call. I've searched the NMS docs and didn't see the highlighted errors, so maybe I can get some insight from the TeleFlow side. We've tried changing the format of the phone number itself (ie with a '1' or without). Please advise at your earliest - thanks!!! Susan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2008/06/05 18:31:06.265: [2] FINISH
2008/06/05 18:31:06.265: OutboundReq_Check<==DbSet
2008/06/05 18:31:06.265: [25] Set Local Variable
2008/06/05 18:31:06.265: Setting local variable '@MSGID' to '0'
2008/06/05 18:31:06.265: [5] SQL Statement
2008/06/05 18:31:06.265: Handle is '1'
2008/06/05 18:31:06.265: Warning time threshold is ''
2008/06/05 18:31:06.265: Empty Warning time threshold defaults to '2000'
2008/06/05 18:31:06.265: <----- BEGIN ----->
SELECT Top 1
CallID,
MessageID AS MsgID,
PhoneNo AS OUTCALLNUM

FROM
CallMain
WHERE
(DATEDIFF(minute,CallDueDate,GETDATE()) between -10 and 10)
and CallStatus = 1
Order By CallID ASC

<----- END ----->
2008/06/05 18:31:06.265: Elapsed Time: 0.000
2008/06/05 18:31:06.265: [7] SQL Fetch
2008/06/05 18:31:06.265: Handle is '1'
2008/06/05 18:31:06.265: Setting global variable '@CALLID' to '74'
2008/06/05 18:31:06.265: Setting local variable '@MSGID' to '17'
2008/06/05 18:31:06.265: Setting global variable '@OUTCALLNUM' to '16784781963'
2008/06/05 18:31:06.265: [10] SQL End
2008/06/05 18:31:06.265: Handle is '1'
2008/06/05 18:31:06.265: [26] Set Global Variable
2008/06/05 18:31:06.265: Setting global variable '@PLAYWAV' to 'C:\InnovationRXWavs\17.wav'
2008/06/05 18:31:06.265: [19] SQL Statement
2008/06/05 18:31:06.265: Handle is '2'
2008/06/05 18:31:06.265: Warning time threshold is ''
2008/06/05 18:31:06.265: Empty Warning time threshold defaults to '2000'
2008/06/05 18:31:06.265: <----- BEGIN ----->
Update
callmain
set callstatus = 2
Where CallId = 74

<----- END ----->
2008/06/05 18:31:06.281: Elapsed Time: 0.016
2008/06/05 18:31:06.281: [22] SQL End
2008/06/05 18:31:06.281: Handle is '2'
2008/06/05 18:31:06.281: [27] SQL Statement
2008/06/05 18:31:06.281: Handle is '3'
2008/06/05 18:31:06.281: Warning time threshold is ''
2008/06/05 18:31:06.281: Empty Warning time threshold defaults to '2000'
2008/06/05 18:31:06.281: <----- BEGIN ----->
exec WriteWavToFile 74

<----- END ----->
2008/06/05 18:31:06.281: Elapsed Time: 0.000
2008/06/05 18:31:06.281: [29] SQL End
2008/06/05 18:31:06.281: Handle is '3'
2008/06/05 18:31:06.281: [32] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@LOGTYPE' to '1'
2008/06/05 18:31:06.281: [31] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@LOGMESSAGE' to 'Phonecall process started'
2008/06/05 18:31:06.281: [30] Run Flowchart
2008/06/05 18:31:06.281: Flowchart is 'UpdateDbLog'
2008/06/05 18:31:06.281: OutboundReq_Check==>UpdateDbLog
2008/06/05 18:31:06.281: [1] START
2008/06/05 18:31:06.281: [3] Run Flowchart
2008/06/05 18:31:06.281: Flowchart is 'dbset'
2008/06/05 18:31:06.281: UpdateDbLog==>DbSet
2008/06/05 18:31:06.281: [1] START
2008/06/05 18:31:06.281: [3] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@DB_COUNTER' to '1'
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: UpdateDbLog<==DbSet
2008/06/05 18:31:06.281: [4] SQL Statement
2008/06/05 18:31:06.281: Handle is '1'
2008/06/05 18:31:06.281: Warning time threshold is ''
2008/06/05 18:31:06.281: Empty Warning time threshold defaults to '2000'
2008/06/05 18:31:06.281: <----- BEGIN ----->
Insert Into CallLog
(CallID,Description,ActionType)
Values(74,'Phonecall process started',1)

<----- END ----->
2008/06/05 18:31:06.281: Elapsed Time: 0.000
2008/06/05 18:31:06.281: [6] SQL End
2008/06/05 18:31:06.281: Handle is '1'
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: OutboundReq_Check<==UpdateDbLog
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: Outbound_Main<==OutboundReq_Check
2008/06/05 18:31:06.281: [93] Compare
2008/06/05 18:31:06.281: First Value '@OUTCALLNUM' evaluates to '16784781963'
2008/06/05 18:31:06.281: Second Value is '0'
2008/06/05 18:31:06.281: @OUTCALLNUM = 0?
2008/06/05 18:31:06.281: (integer):16784781963 = (integer):0?
2008/06/05 18:31:06.281: FALSE
2008/06/05 18:31:06.281: [122] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@RETRYCALL' to '0'
2008/06/05 18:31:06.281: [101] Run Flowchart
2008/06/05 18:31:06.281: Flowchart is 'outbound_call'
2008/06/05 18:31:06.281: Outbound_Main==>Outbound_Call
2008/06/05 18:31:06.281: [1] START
2008/06/05 18:31:06.281: [8] Connect Point
2008/06/05 18:31:06.281: [4] Place Call
2008/06/05 18:31:06.281: Telephone Number '@OUTCALLNUM' evaluates to '16784781963'
2008/06/05 18:31:06.281: Rings before TIMEOUT '@RINGCOUNT' evaluates to '5'
2008/06/05 18:31:06.281: Do not capture answering voice length to TeleFlow variable
2008/06/05 18:31:06.281: Silence timeout is ''
2008/06/05 18:31:06.281: Empty Silence timeout defaults to none
2008/06/05 18:31:06.281: Maximum voice length timeout is ''
2008/06/05 18:31:06.281: Empty Maximum voice length timeout defaults to none
2008/06/05 18:31:06.281: Place call to 16784781963
and wait for up to 5 rings
2008/06/05 18:31:06.281: Do not connect on CED
2008/06/05 18:31:06.281: Do not connect on SIT
2008/06/05 18:31:06.281: Do not perform initial voice length detection.
2008/06/05 18:31:06.281: Open port 1
2008/06/05 18:31:06.281: Board: 0 stream: 0 slot: 0
2008/06/05 18:31:06.281: NMS Services:
2008/06/05 18:31:06.281: 0. NCC, ADIMGR, 0, 0:0, 15
2008/06/05 18:31:06.281: 1. ADI, ADIMGR, 0, 0:0, 15
2008/06/05 18:31:06.281: 2. SWI, SWIMGR, 0, 0:0, 15
2008/06/05 18:31:06.281: 3. VCE, VCEMGR, 0, 0:0, 15
2008/06/05 18:31:06.281: Event: CTAEVN_OPEN_SERVICES_DONE, Finished
2008/06/05 18:31:06.281: Using 'isd0' protocol...
2008/06/05 18:31:06.281: Echo canceller not started
2008/06/05 18:31:06.281: Event: NCCEVN_START_PROTOCOL_DONE, CTA_REASON_FINISHED
2008/06/05 18:31:06.281: Event: NCCEVN_CALL_DISCONNECTED, NCC_DIS_DIAL_FAILURE
2008/06/05 18:31:06.281: Setting system variable '@CALLOUT_RESULT' to 'FAILURE'
2008/06/05 18:31:06.281: Setting system variable '@CALLOUT_REASON' to 'DIAL_FAILURE'
2008/06/05 18:31:06.281: Event: NCCEVN_CALL_RELEASED
2008/06/05 18:31:06.281: u-Event: NCCEVN_CALL_RELEASED
2008/06/05 18:31:06.281: Event: NCCEVN_STOP_PROTOCOL_DONE, CTA_REASON_FINISHED
2008/06/05 18:31:06.281: Event: CTAEVN_DESTROY_CONTEXT_DONE, Finished
2008/06/05 18:31:06.281: FAILURE

2008/06/05 18:31:06.281: [17] Set Local Variable
2008/06/05 18:31:06.281: Setting local variable '@CALL_RESULT' to 'Call_Failed - unable to acquire the specified port '
2008/06/05 18:31:06.281: [23] Connect Point
2008/06/05 18:31:06.281: [55] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@CALLSTATUS' to '2'
2008/06/05 18:31:06.281: [58] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@LOGTYPE' to '2'
2008/06/05 18:31:06.281: [61] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@LOGMESSAGE' to 'Call_Failed - unable to acquire the specified port '
2008/06/05 18:31:06.281: [60] Run Flowchart
2008/06/05 18:31:06.281: Flowchart is 'UpdateDbLog'
2008/06/05 18:31:06.281: Outbound_Call==>UpdateDbLog
2008/06/05 18:31:06.281: [1] START
2008/06/05 18:31:06.281: [3] Run Flowchart
2008/06/05 18:31:06.281: Flowchart is 'dbset'
2008/06/05 18:31:06.281: UpdateDbLog==>DbSet
2008/06/05 18:31:06.281: [1] START
2008/06/05 18:31:06.281: [3] Set Global Variable
2008/06/05 18:31:06.281: Setting global variable '@DB_COUNTER' to '1'
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: UpdateDbLog<==DbSet
2008/06/05 18:31:06.281: [4] SQL Statement
2008/06/05 18:31:06.281: Handle is '1'
2008/06/05 18:31:06.281: Warning time threshold is ''
2008/06/05 18:31:06.281: Empty Warning time threshold defaults to '2000'
2008/06/05 18:31:06.281: <----- BEGIN ----->
Insert Into CallLog
(CallID,Description,ActionType)
Values(74,'Call_Failed - unable to acquire the specified port ',2)

<----- END ----->
2008/06/05 18:31:06.281: Elapsed Time: 0.000
2008/06/05 18:31:06.281: [6] SQL End
2008/06/05 18:31:06.281: Handle is '1'
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: Outbound_Call<==UpdateDbLog
2008/06/05 18:31:06.281: [45] Global Event
2008/06/05 18:31:06.281: Label is 'CALLER_GONE'
2008/06/05 18:31:06.281: Setting system variable '@HANGUP' to 'CALLER_GONE'
2008/06/05 18:31:06.281: [2] FINISH
2008/06/05 18:31:06.281: Outbound_Main<==Outbound_Call
2008/06/05 18:31:06.281: [118] Compare
2008/06/05 18:31:06.281: First Value '@CallStatus' evaluates to '2'
2008/06/05 18:31:06.281: Second Value is '2'
2008/06/05 18:31:06.281: @CallStatus = 2?
2008/06/05 18:31:06.281: (integer):2 = (integer):2?
2008/06/05 18:31:06.281: TRUE
2008/06/05 18:31:06.281: [137] Math
2008/06/05 18:31:06.281: Base value '@RetryCall' evaluates to '0'
2008/06/05 18:31:06.281: Modifying value is '1'
2008/06/05 18:31:06.281: @RetryCall = @RetryCall + 1
2008/06/05 18:31:06.281: @RetryCall = (integer):0 + (integer):1
2008/06/05 18:31:06.281: Setting global variable '@RETRYCALL' to '1'
2008/06/05 18:31:06.281: [124] Compare
2008/06/05 18:31:06.296: First Value '@RetryCall' evaluates to '1'
2008/06/05 18:31:06.296: Second Value is '2'
2008/06/05 18:31:06.296: @RetryCall = 2?
2008/06/05 18:31:06.296: (integer):1 = (integer):2?
2008/06/05 18:31:06.296: FALSE
2008/06/05 18:31:06.296: [121] Wait
2008/06/05 18:31:06.296: Delay is '30000'
2008/06/05 18:31:06.296: Waiting 30000 milliseconds
2008/06/05 18:31:18.750: Reload normal request
2008/06/05 18:31:18.750: Shutdown not permitted

_________________
Susan Burkley
Input Technologies
Atlanta, GA ~ GMT -4, Eastern Daylight Time

Those who believe in telekinetics, raise my hand.
- Kurt Vonnegut


Back to top
 Profile YIM 
 
 Post subject: Re: Errors generated when attempting to place an outbound call
PostPosted: Thu Jun 05, 2008 4:30 pm 
Offline

Joined: Wed Mar 19, 2003 4:28 pm
Posts: 510
Location: Canada
Has any channel/port on this circuit EVER successfully placed so much as a single call out? If so, try adding a hang up step between calls. This is "generally" handled by TeleFlow, but with the FAIL path in particular, it might need to be specifically in the path between calls.

If not, has this circuit ever received so much as a single call? (just to verify that the phone service is all configured properly, I mean) If possible, it is always a good idea to start with something very rudimentary(Eg. Answer a call, play an audio file) on a new circuit, such as the AnswerTest TeleFlow application.


Back to top
 Profile WWW 
 
 Post subject: Re: Errors generated when attempting to place an outbound call
PostPosted: Thu Jun 05, 2008 4:46 pm 
Offline

Joined: Wed Mar 12, 2008 1:14 pm
Posts: 59
Location: Atlanta, GA
We are still in the implementation setup phase, so no, we've not been able to place a call yet. This is an outbound call, so the call has never been made and the flow doesn't get processed beyond that. Our call flow is the default outbound, and we have have added very little. Literally, this thing just queries a DB for a number, and it plays a wav then hangs up and goes to the next record. We will try the AnswerTest Tap tomorrow morning, but since our flow is also pretty basic, I'm not seeing the huge benefit in doing that, and the call rolls over and dies when it comes to the point of engaging the line for transmission. Do the errors below correlate to anything specific?

_________________
Susan Burkley
Input Technologies
Atlanta, GA ~ GMT -4, Eastern Daylight Time

Those who believe in telekinetics, raise my hand.
- Kurt Vonnegut


Back to top
 Profile YIM 
 
 Post subject: Re: Errors generated when attempting to place an outbound call
PostPosted: Thu Jun 05, 2008 6:00 pm 
Offline

Joined: Wed Mar 19, 2003 4:28 pm
Posts: 510
Location: Canada
Generally speaking, there is less to go wrong with inbound, which is why it is always your best bet for testing that your circuit is up and everything is running properly. For this reason, we always start there ourselves.

I believe the error you have below is a pretty "generic" error for a failure to place a call.

Since you haven't had any calls at all on this circuit yet, in or out:
- Does the circuit provider believe there is currently clean communication with the IVR?
- Does the NMS command-line utility "trunkmon" currently show clean communication?
- The last post in the following thread has information about a possible issue. It also indicates the NMS document to refer to for the ctatest utility. (A utility for testing your circuit with the NMS card only.) If ctatest doesn't work, then there is something incorrect with either the NMS configuration or the circuit itself. viewtopic.php?f=3&t=528&p=1915&hilit=ctatest#p1915
NOTE: You should stop the TeleFlow service before trying to use ctatest.


Back to top
 Profile WWW 
 
 Post subject: Re: Errors generated when attempting to place an outbound call
PostPosted: Thu Jun 05, 2008 6:21 pm 
Offline

Joined: Wed Mar 12, 2008 1:14 pm
Posts: 59
Location: Atlanta, GA
Trunkmon seems OK. But I'll try your other recommended NMS tools first thing in the morning and see what happens.

Thanks,

_________________
Susan Burkley
Input Technologies
Atlanta, GA ~ GMT -4, Eastern Daylight Time

Those who believe in telekinetics, raise my hand.
- Kurt Vonnegut


Back to top
 Profile YIM 
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

Board index : TeleFlow Forums : NMS Communication Boards


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Style by Midnight Phoenix & N.Design Studio
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.