Logs for a successful agent-based progressive outbound call

From DocWiki

Jump to: navigation, search
Logs for a successful agent-based progressive outbound call

Check for the below logs to track a successful call:

The following logs shows that the CSQs that are associated with the particular Campaign and the details 
about number of agents logged in and how many agents that are ready  

30262: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:getNumOfWorkingObAgentForCSQ: csqID: 2numOfWorkingObAgents:0 
30263: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  Processing CSQ :2
30264: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # Ready Agents : 1
30265: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # Logged in Agents : 1
The Following logs shows % CSQ allocation for the campaign. The Ready OB agents which are available for the campaign. 

30266: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # CSQ Allocation (Percantage of OB agents ) : 
100numWorkingObAgent : 0
30267: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # Logged in OB Agents : 1
30268: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # Ready OB Agents (Cumulative) : 1
30269: Jun 10 16:28:19.722 IST %MIVR-SS_RM-7-UNK:RsrsMgr:getNumOfReadyAgentForGivenCSQs  # Ready OB Agents (Cumulative) : 1 
#Ready OB Agents (Unique) : 1 # Ready OB Agents (Final) : 1
30270: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:DailerUtil:getNumberOfReadyAgents  # Ready OB Agents after removing 
duplicates : 1
30271: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration numOfReadyAgents: 1
The LPA value considered for dialing out the contacts for current Iteration. For progressive campaign, this value is nothing but the value
configured in Outbound campaign Page. For predictive campaign, LPA will be calculated for each iteration based on the CPA analysis.

30275: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration linesPerAgent: 1.0
The number of Ready agent(s) is 1 here and LPA is configured as 1 , so number of contacts to dial-out is 1 .  

30277: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration maxContactsToDial: 1
30278: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration contactsToDial: 1
30279: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration numAgentsToReserve: 1
30280: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:totalNumOfAgentsInCurrentIteration() - 1
30281: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:numOfAgentsReservedInCurrentIteration() - 0
30282: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:AgentDialer:beginNewDialOutIteration.. END
The number of contacts dialed out will be set in RunningCampaignInfo data structure. 

30283: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:SIPCampaignRunningInfo::setTotalNumContactsInCurrentIteration : 1
30284: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:SIPCampaignRunningInfo::setNumContactsDialedInCurrentIteration : 0
Fetching contacts from memory for Dialing out and checking the whether the contact is within valid time zone to dial-out 

30287: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: campaignID=3;#of DLC=1
30288: Jun 10 16:28:19.722 IST %MIVR-SS_OB-7-UNK:CMgrUtil.getTimeZoneId - phoneNum=1000
30289: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:CMgrUtil: getGmtOffset: DST observed=false
30290: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:CMgrUtil.getTimeZoneId - phoneNum=1000
30291: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime:
timezone=sun.util.calendar.ZoneInfo[id="Asia/Kolkata",offset=19800000,dstSavings=0,useDaylight=false,transitions=6,lastRule=null]
30292: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=false
30293: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true
The number of Agents to be reserved for the campaign. 

30307: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:AgentDialer:getNumOfAgentsToReserve(): numAgentsCanbeReserved : 1
30308: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:AgentDialer:getNumOfAgentsToReserve(): numAgentsToReserve : 1
30309: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:AgentDialer:dialOutContacts(): numAgentsToReserve : 1
Posting the ReserveAndDialAgentOutboundContactsMsg to dial out the contacts. The dlc ids which is picked for dial out will 
be displayed in this message. The DLC id can be used for tracing out the contacts.

30310: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:AgentDialer:dialOutContacts(): posting
ReserveAndDialAgentOutboundContactsMsgReserveAndDialAgentOutboundContactsMsg for campaign id 3 # Agents to Reserve: 1 # Contacts to Dial: 1 dlc
ids: 83 , 
Outbound Subsystem sends the Agent reservation message to RMCM with number of Agents to be reserved.

30319: Jun 10 16:28:19.723 IST %MIVR-SS_OB-7-UNK:AgentDialer:reserveAgents(): Sending ReserveOutboundRsrcsSyncMsg to RmCM to reserve 1 agents.
30320: Jun 10 16:28:19.723 IST %MIVR-SS_RM-7-UNK:Processing msg: ReserveOutboundRsrcsMsg   CSQs:2, numToRequest: 1 dialerType:AGENT_DIALER
30321: Jun 10 16:28:19.723 IST %MIVR-SS_RM-7-UNK:RsrcMgrMsgProcessor: process ReserveOutboundRsrcsSyncMsg. 
30322: Jun 10 16:28:19.723 IST %MIVR-SS_RM-7-UNK:RsrcMgrMsgProcessor.processReserveOutboundRsrcsSyncMsg : Checking Agents in CSQ: 2 # Agents
already reserved : 0
The number of Outbound Agent Licenses that are already consumed.

30325: Jun 10 16:28:19.723 IST %MIVR-SS_RM-7-UNK:RsrsMgr:isFreeLicenseAvailableForAgentProgPred():number Of Total Agents Consumed= 0
maxProgPredAgentCount= 150
The Agent state will be changed to RESERVED and also old state will be also be printed.

30327: Jun 10 16:28:19.724 IST %MIVR-SS_RM-7-UNK:Rsrc: 6904 New State:RESERVED Old State:AVAILABLE Reason code:32747
The number of reserved Agents from RMCM.

30331: Jun 10 16:28:19.724 IST %MIVR-SS_RM-7-UNK:RsrcMgrMsgProcessor.processReserveOutboundRsrcsSyncMsg : Reserved  1 agents.
30333: Jun 10 16:28:19.724 IST %MIVR-SS_OB-7-UNK:AgentDialer:reserveAgents(): Received response for ReserveOutboundRsrcsSyncMsg from  RmCM. #
Agents reserved now: 1
Adding Agent info to AgentReservationTimeOutKeeper.

30339: Jun 10 16:28:19.724 IST %MIVR-SS_OB-7-UNK:AgentReservationTimeOutKeeper:addAgentCampaignInfo . Adding agent 6904 for campaign 3. Current 
Time :1402397899724 , To be timed out at : 140239791472
The Agent Id 6904 is mapped with Dialing List Id 83 . 
30343: Jun 10 16:28:19.724 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:addAgentContactMapping: agentID: 6904 DialingListID : 83
Once Agent is reserved, Dialer will place the call to Gateway .

30347: Jun 10 16:28:19.725 IST %MIVR-SS_OB-7-UNK:SIPAdapter.placeCall GWCall:  dlcID: 83, csqID: -1, contactNumToDial:1000null,
dialerType:AGENT_DIALER, DialerSipCall-5, null, fromDN=, toDN=, callId=14023978997255@10.78.95.190, from=DN1800112233, toDN=1000, map.size=1
30362: Jun 10 16:28:19.727 IST %MIVR-SS_OB-7-UNK:buildInvite DialerSipCall-5, State=CONTACTING, fromDN=1800112233, toDN=1000,   
callId=14023978997255@10.78.95.190 try to send

30363: Jun 10 16:28:19.728 IST %MIVR-SS_OB-7-UNK:
SIP-1000  INVITE sip:1000@10.78.91.14:5060;transport=udp SIP/2.0
SIP-1000  Max-Forwards: 70
SIP-1000  To: <sip:1000@10.78.91.14>
SIP-1000  From: <sip:1800112233@10.78.95.190>;tag=dsdf744283
Once the outbound call starts ringing on Customer phone , the gateway sends the 183 Session Progress response

SIP-1000  SIP/2.0 183 Session Progress
SIP-1000  Via: SIP/2.0/UDP 10.78.95.190:5065;branch=z9hG4bKqzVD2Wfu.yhnFQ0iU3bcPg~~12
SIP-1000  To: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  From: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 100 INVITE
The dialer will process the 183 Session Progress response message from Gateway

30373: Jun 10 16:28:19.762 IST %MIVR-SS_OB-7-UNK:SIPDialer:processOutboundPlaceGWCallRespMsg: OutboundPlaceGWCallRespMsg: GWCall:  
dlcID: 83, csqID: -1, contactNumToDial:1000null, dialerType:AGENT_DIALER, DialerSipCall-5, State=CONTACTING, fromDN=1800112233, toDN=1000,
callId=14023978997255@10.78.95.190, status=RINGING
Once Call is answered by the customer, the CCX receives the 200 OK from the SIP gateway. 

30451: Jun 10 16:28:24.758 IST %MIVR-SS_OB-7-UNK:
SIP-1000  SIP/2.0 200 OK
SIP-1000  Via: SIP/2.0/UDP 10.78.95.190:5065;branch=z9hG4bKqzVD2Wfu.yhnFQ0iU3bcPg~~12
SIP-1000  To: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  From: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 100 INVITE
The 200 OK will be processed by CCX and update the CampaignStatistics info .

30458: Jun 10 16:28:24.767 IST %MIVR-SS_OB-7-UNK:SIPDialer:preProcessGWCallRespMsg()- call status = OK for outbound contact number =1000dlcID:83
30459: Jun 10 16:28:24.767 IST %MIVR-SS_OB-7-UNK:CampaignStatistics:incrementAttemptedCalls() for phoneNumber=1000 to 1
30460: Jun 10 16:28:24.767 IST %MIVR-SS_OB-7-UNK:HalfHourCampaignData:incrementAttemptedCalls() by 1. Total attempted calls = 1
The SIP Gateway sends the UPDATE message with CPA status . For this particular call the dialed out call is detected as Live Voice call

30513: Jun 10 16:28:26.994 IST %MIVR-SS_OB-7-UNK:
SIP-1000  UPDATE sip:1800112233@10.78.95.190:5065;transport=udp SIP/2.0
SIP-1000  Via: SIP/2.0/UDP 10.78.91.14:5060;branch=z9hG4bKF4410B7
SIP-1000  Max-Forwards: 69
SIP-1000  To: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  From: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 102 UPDATE
SIP-1000  Content-Length: 167
SIP-1000  Date: Tue, 10 Jun 2014 10:46:20 GMT
SIP-1000  User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
SIP-1000  Supported: timer,resource-priority,replaces,sdp-anat
SIP-1000  Timestamp: 1402397183
SIP-1000  Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
SIP-1000  Contact: <sip:1000@10.78.91.14:5060>
SIP-1000  Min-SE: 1800
SIP-1000  Content-Type: application/x-cisco-cpa
SIP-1000  Content-Disposition: signal;handling=optional
SIP-1000  
SIP-1000  event=detected
SIP-1000  status=LS
SIP-1000  pickupT=1490
SIP-1000  maxActGlitchT=0
SIP-1000  numActGlitch=0
SIP-1000  valSpeechT=260
SIP-1000  maxPSSGlitchT=0
SIP-1000  numPSSGlitch=0
SIP-1000  silenceP=380
SIP-1000  termToneDetT=0
SIP-1000  noiseTH=1000
SIP-1000  actTh=32000
The CPA status received as Live Voice for the dialed out contact
30518: Jun 10 16:28:26.997 IST %MIVR-SS_OB-7-UNK:onCPAStatus DialerSipCall-5, State=ACTIVE, fromDN=1800112233, toDN=1000,
callId=14023978997255@10.78.95.190 notify com.cisco.wf.subsystems.outbound.SIPAdapterCallListenerImpl@1135623.onCPAStatus(status=LiveHumanSpeech)
30519: Jun 10 16:28:26.997 IST %MIVR-SS_OB-7-UNK:SIPAdapterCallListenerImpl.onCPAStatus post OutboundUpdateGWCallStatusMsg: GWCall:  dlcID: 83,
csqID: -1, contactNumToDial:1000null, dialerType:AGENT_DIALER, DialerSipCall-5, State=ACTIVE, fromDN=1800112233, toDN=1000,
callId=14023978997255@10.78.95.190, status=LiveHumanSpeech

30523: Jun 10 16:28:26.997 IST %MIVR-SS_OB-7-UNK:AgentDialer:handleLiveSpeachCPAResultEvent(): Live Human Speech detected
Updating the Dialing List table 

30527: Jun 10 16:28:26.998 IST %MIVR-SS_OB-7-UNK:UpdateContactsMsgProcessor:Processing msg: OutboundSIPUpdateContactMsg 
(dlc:DialingListConfig[schema=DialingListConfig#3,time=2014-06-10  
16:28:07.0,recordId=83,desc=,recordID=0,dialingListID=83,campaignID=3,accountNumber=,firstName=,lastName=,phone01=1000,phone02=,
phone03=,gmtZonePhone01=253,dstPhone01=false,gmtZonePhone02=-1,dstPhone02=true,gmtZonePhone03=-1,dstPhone03=true,callbackNumber=,
callbackDateTime=2014-06-10 
10:58:07.0,callStatus=2,callResult=0,callResult01=0,callResult02=0,callResult03=0,lastNumberDialed=0,callsMadeToPhone01=0,
callsMadeToPhone02=0,callsMadeToPhone03=0,numMissedCallback=0,retry=false])  (bACampaign:null)  (bAAccountNumber:null)  
(bAResponse:null)  (bAStatus:null)  (bADialedListID:null)  (bATimeZone:null)  (bABuddyName:null)  (phoneNumDialed:1000)  
(dialerCallStatus:3)  (dialerCallResult:1)
Once Live voice detected the call should be transferred to reserved Agent.

30535: Jun 10 16:28:26.998 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:getAgentForContact:  DialingListID : 83  agentID: 6904
30537: Jun 10 16:28:26.998 IST %MIVR-SS_OB-7-UNK:AgentDialer:getAgentIDToTransfer campID: 3 agentID:6904, dlcID: 83
30538: Jun 10 16:28:26.998 IST %MIVR-SS_OB-7-UNK:AgentCampaignRunningInfo:getCsqIdForAgent: agent: 6904 csq id:  2

The OutboundContactKey is added . 
30542: Jun 10 16:28:26.999 IST %MIVR-SS_RM-7-UNK:RIMgr:addToOutboundSIPCallDetail Adding Key = AgentOutboundContactKey [agentPhoneNumber=6904,
contactPhoneNumber=1000] Value : SIPOutboundDialingListData [dlcID=83, callResult=1, campaignType=1, agentID=6904, campaignName=Agent Progressive,
csqID=2, campaignID=3, phoneNumber=1000, firstName=, lastName=, accountNumber=, timeZone=330, transferedOrConferenced=false]

The call will be transferred to reserved Agent.

30545: Jun 10 16:28:26.999 IST %MIVR-SS_OB-7-UNK:SipDialer:sendTransferReqToGateway(): after posting OutboundTransferGWCallReqMsg
30547: Jun 10 16:28:26.999 IST %MIVR-SS_OB-7-UNK:SIPAdapter.transfer GWCall:  dlcID: 83, csqID: -1, contactNumToDial:1000TRANSFER_TO_AGENT,
cpaStatus:LiveHumanSpeech, dialerType:AGENT_DIALER, DialerSipCall-5, State=ACTIVE, fromDN=1800112233, toDN=1000,  
callId=14023978997255@10.78.95.190, transferDN=6904

30551: Jun 10 16:28:26.999 IST %MIVR-SS_OB-7-UNK:
SIP-1000  REFER sip:1000@10.78.91.14:5060 SIP/2.0
SIP-1000  Max-Forwards: 70
SIP-1000  To: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  From: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 101 REFER
SIP-1000  Content-Length: 0
SIP-1000  Contact: <sip:1800112233@10.78.95.190:5065;transport=udp>
SIP-1000  Referred-By: <sip:1800112233@10.78.95.190>
SIP-1000  Refer-To: <sip:6904@10.78.91.14>
SIP-1000  Allow: INVITE, BYE, CANCEL, ACK, UPDATE, NOTIFY
SIP-1000  Cisco-Guid: 695512487-1832175530-402950154-1254009031
SIP-1000  User-Agent: Cisco-UCCX/8.5
Once transferred call starts ringing on Agent's desktop , RM revives ringing event.

30580: Jun 10 16:28:27.023 IST %MIVR-SS_RM-7-UNK:RIMgrAddressCallObserver.callChangedEvent():
Unknown event. eventID:104:2004/1
Unknown event. eventID:203:2004/1
Unknown event. eventID:116:2004/1
Unknown event. eventID:119:2004/1
CallCtlTermConnRingingEv 2004/1
30581: Jun 10 16:28:27.023 IST %MIVR-SS_RM-7-UNK:RIMgrAddressCallObserver: TermConnRingingEv received for call 16779220 [2004/1] and agent 6904 
The handleAgentOutboundCall log message indicates that Agent is identified as Outbound resource. The Call is ringing on Agent Desktop.

30589: Jun 10 16:28:27.023 IST %MIVR-SS_RM-7-UNK:handleAgentOutboundCall AgentOutboundResourceRingingMsg-- AgentOutboundResourceRingingMsg (Call  
Id: 2004/1OutboundContactKey: AgentOutboundContactKey [agentPhoneNumber=6904, contactPhoneNumber=1000]) 
30590: Jun 10 16:28:27.023 IST %MIVR-SS_OB-7-UNK:OutboundMgrMsgProcessor:Processing msg: AgentOutboundResourceRingingMsg (Call Id:
2004/1OutboundContactKey: AgentOutboundContactKey [agentPhoneNumber=6904, contactPhoneNumber=1000])
Once transferred call starts ringing on Agent Desktop , the Gateway sends NOTIFY request with 180 ringing . If there is an issue in 
transferring the call to Agent , the Gateway sends back NOTIFY request with error response. For example if there is an issue with Dial peer 
in SIP gateway then the SIP gateway sends back NOTIFY request with 503 Service Unavailable. 

30602: Jun 10 16:28:27.026 IST %MIVR-SS_OB-7-UNK:
SIP-1000  NOTIFY sip:1800112233@10.78.95.190:5065;transport=udp SIP/2.0
SIP-1000  Via: SIP/2.0/UDP 10.78.91.14:5060;branch=z9hG4bKF46100E
SIP-1000  Max-Forwards: 69
SIP-1000  To: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  From: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 104 NOTIFY
SIP-1000  Content-Length: 23
SIP-1000  Date: Tue, 10 Jun 2014 10:46:23 GMT
SIP-1000  User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
SIP-1000  Event: refer
SIP-1000  Subscription-State: active
SIP-1000  Contact: <sip:1000@10.78.91.14:5060>
SIP-1000  Content-Type: message/sipfrag
SIP-1000  
SIP-1000  SIP/2.0 180 Ringing
SIP-1000   
Once Call is answered by an Agent . 

30652: Jun 10 16:28:27.034 IST %MIVR-SS_RM-7-UNK:Exiting callChangedEvent
30653: Jun 10 16:28:27.034 IST %MIVR-SS_RM-7-UNK:RIMgr:removeFromOutboundSIPCallDetail Removing Key = AgentOutboundContactKey
[agentPhoneNumber=6904, contactPhoneNumber=1000]
30654: Jun 10 16:28:27.034 IST %MIVR-SS_RM-7-UNK:RIMgrAddressCallObserver.callChangedEvent():
Unknown event. eventID:105:2004/1
CallCtlConnEstablishedEv 2004/1
TermConnActiveEv 2004/1
CallCtlTermConnTalkingEv 2004/1
The SIP agteway sends the NOTIFY request with 200 OK once call is answered by the Agent.
  
30910: Jun 10 16:28:27.108 IST %MIVR-SS_OB-7-UNK:
SIP-1000  NOTIFY sip:1800112233@10.78.95.190:5065;transport=udp SIP/2.0
SIP-1000  Via: SIP/2.0/UDP 10.78.91.14:5060;branch=z9hG4bKF479D4
SIP-1000  Max-Forwards: 69
SIP-1000  To: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  From: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 105 NOTIFY
SIP-1000  Content-Length: 18
SIP-1000  Date: Tue, 10 Jun 2014 10:46:23 GMT
SIP-1000  User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
SIP-1000  Event: refer
SIP-1000  Subscription-State: terminated;reason=noresource
SIP-1000  Contact: <sip:1000@10.78.91.14:5060>
SIP-1000  Content-Type: message/sipfrag
SIP-1000  
SIP-1000  SIP/2.0 200 OK
SIP-1000  
Processing the transfer success message.

30915: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:SIPDialer:processOutboundTransferGWCallRespMsg: OutboundTransferGWCallRespMsg: GWCall:  
dlcID: 83, csqID: -1, contactNumToDial:1000TRANSFER_TO_AGENT, cpaStatus:LiveHumanSpeech, dialerType:AGENT_DIALER, DialerSipCall-5,
 State=TRANSFERRING, fromDN=1800112233, toDN=1000, callId=14023978997255@10.78.95.190, status=OK
30916: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:SIPDialer:processOutboundTransferGWCallRespMsg()- call status OK for contact number = 1000

30918: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:HalfHourCampaignData:incrementLiveVoiceCalls() by 1. Total live voice calls = 1
30919: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:AgentDialer:processTransferSuccess(): Removing agent from timeout keeper
30920: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:AgentReservationTimeOutKeeper:removeAgentCampaignInfo . Removing agent 6904
30921: Jun 10 16:28:27.110 IST %MIVR-SS_OB-7-UNK:AgentReservationTimeOutKeeper:removeAgentCampaignInfo . Removed agent?: true


Once call transferred successfully and Agent answers the call, the Gateway disconnect the call with CCX by sending BYE request.

30923: Jun 10 16:28:27.114 IST %MIVR-SS_OB-7-UNK:
SIP-1000  BYE sip:1800112233@10.78.95.190:5065;transport=udp SIP/2.0
SIP-1000  Via: SIP/2.0/UDP 10.78.91.14:5060;branch=z9hG4bKF484B7
SIP-1000  Max-Forwards: 69
SIP-1000  To: <sip:1800112233@10.78.95.190>;tag=dsdf744283
SIP-1000  From: <sip:1000@10.78.91.14>;tag=6BBF199A-16FB
SIP-1000  Call-ID: 14023978997255@10.78.95.190
SIP-1000  CSeq: 106 BYE
SIP-1000  Content-Length: 0
SIP-1000  Date: Tue, 10 Jun 2014 10:46:23 GMT
SIP-1000  User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
SIP-1000  Timestamp: 1402397183
SIP-1000  Reason: Q.850;cause=16
SIP-1000  P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=2
SIP-1000

Rating: 0.0/5 (0 votes cast)

Personal tools