" /> Call gets busy signal - can't tell why - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Call gets busy signal - can't tell why  (Read 4709 times)

Offline Belle90

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Call gets busy signal - can't tell why
« on: May 18, 2017, 01:45:29 PM »
Advertisement
our customer calls a number which routes internally to another group- it rings for about a minute and then they get a busy signal. Below is a snippet from the sipserver log that shows the busy - any idea why?:

07:44:10.330: Sending  [0,UDP] 405 bytes to 10.30.243.242:5060 >>>>>
ACK sip:88599774892@10.92.243.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.94.159.45:5060;branch=z9hG4bK96F215F5-4695-4921-97CE-24079C79D085-179694
From: <sip:2105079557@10.94.159.45:5060>;tag=386ADA4B-D516-4399-B159-7ED3DA8AA348-72752
To: <sip:88599774892@10.94.159.45:5060>;tag=gK088487c3
Call-ID: 1CA5EF58-FD43-4816-A2C8-11BF7AD35DB4-43347@10.94.159.45
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0


07:44:10.330: SipDialog: event CALLING_RESREJECT, t=1266336, s=9, r=5, m=0000000012e5fc28
07:44:10.330 SIPCONN(282608599774892): HandleSipDialogEvent(CALLING_RESREJECT)
07:44:10.330 SIPCONN(282608599774892): 1pcc event CALLING_RESREJECT
07:44:10.330 SIPCONN(282608599774892): ConvertResponse: 403
07:44:10.330 SIPCONN(282608599774892): ConvertResponse: no conversion configured for 403
07:44:10.330 SIPCONN(282608599774892): Failed to obtain Media Server ID
07:44:10.330 SIPCONN(282608599774892): Failed to obtain Media Server ID
07:44:10.330: ExtSvc: Script parse failed, cannot find priority 102 to execute
07:44:10.330: ERROR: 10000004, GetInstruction(priority, instruction), SipExtendedServicesResult.cpp,901
07:44:10.330: ERROR: 10000004, SetNextInstruction(priority), SipExtendedServicesResult.cpp,990
07:44:10.330 SIPCONN(282608599774892): state e:4,p:2,s:6,c:8,rc:403,m:1
07:44:10.330 SIPCONN(6530): CheckUpdateTransferStatus: no original dialog
07:44:10.330 SIPPARTY(282608599774892): 16789829 verify update of party-connection state A-F
07:44:10.330 +++ CIFace::Event +++
  +++ Pre-event +++
    Type EventDestinationBusy
    Devices: <6530/6530> <-/282608599774892> <-/->
    Calls: 16782278/019102a0d93e5fd2/16782278.1125d420/c:2/r:0 0/none
    Parties: D6530/6530.11608700-1125d420:1/l:1/r:0/Dialing,Active,Origination
    X282608599774892/282608599774892.11606e40-1125d420:1/l:2/r:0/Alerting,Destination
    none
    Cause: Blocked/35, Info: 0
    Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
  --- Pre-event ---
  +++ DestBusy +++
    -- target state not compatible at line 1170
    SetFailed: party 6530.11608700-1125d420:1, cause Blocked
@07:44:10.3300 [0] 8.1.102.09 distribute_event: message EventDestinationBusy
AttributeEventSequenceNumber 0000000000069989
AttributeTimeinuSecs 330000
AttributeTimeinSecs 1494513850 (07:44:10)
AttributeExtensions [23] 00 01 01 00..
'BusinessCall' 0
AttributeOtherDNRole 2
AttributeOtherDN '282608599774892'
AttributeThisDNRole 1
AttributeAgentID '38560'
AttributeThisDN '6530'
AttributeDNIS '88599774892'
AttributeUserData [160] 00 04 00 00..
'IW_CaseUid' '47cb2bc6-d164-451b-976c-7b307e193c53'
'IW_BundleUid' '4d52c48e-e136-4b55-b453-3562d178b835'
'CustomerSegment' 'SHSV'
'ContactId' '0008GaBRP4EVBS7D'
AttributeCallUUID '39EDAO5G9L41DFO39TP55JK7EC0003UU'
AttributeConnID 019102a0d93e5fd2
AttributeCallID 16782278
AttributePropagatedCallType 3
AttributeCallType 3
AttributeCallState 5
07:44:10.330 Int 04544 Interaction message "EventDestinationBusy" generated


Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Call gets busy signal - can't tell why
« Reply #1 on: May 18, 2017, 01:52:31 PM »
As you can see on SIP level there is a SIP 403 message. Unfortunately, from the fragment is not clear from what site the message coming.
Logged

Offline Belle90

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: Call gets busy signal - can't tell why
« Reply #2 on: May 18, 2017, 05:00:04 PM »
i have the full sip logs - what should i look for before this to find the cause for the busy? Thank you!
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Call gets busy signal - can't tell why
« Reply #3 on: May 18, 2017, 05:41:31 PM »
¬¬ Search for 403 error and follow WHOLE call flow...you need to understand what you are doing. There is no magic answer. That is why logs exists.
Logged

Offline Belle90

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: Call gets busy signal - can't tell why
« Reply #4 on: May 19, 2017, 01:30:02 PM »
the 403 happens just prior to that when it is applying a treatment. That announcement exists and plays except for the occasional busy that happens here.: I appreciate any assistance -

07:44:10.330 Trc 04541 RequestApplyTreatment received from [1328] (000000b8 URS_P 10.21.154.16:58013)
message RequestApplyTreatment
AttributeThisDN '000005000'
AttributeConnID 019102a0d93e5fed
AttributeTreatmentType 7 (TreatmentPlayAnnouncement)
AttributeTreatmentParms [84] 00 02 00 00..
'LANGUAGE' 'English(US)'
'PROMPT'(list) '1'(list) 'INTERRUPTABLE' 0
                        'ID' 19999
AttributeExtensions [39] 00 01 00 00..
'NO_ANSWER_OVERFLOW' '33333000005000'
AttributeReferenceID 425825
07:44:10.330 Int 04543 Interaction message "RequestApplyTreatment" received from 1328 ("URS_P")
07:44:10.330  -- created: CRequest@8c66030 RequestApplyTreatment-URS_P[1328]/425825
07:44:10.330: $+TLIB:CTI:Unknown:0:13773
07:44:10.330 +++ CIFace::Request +++
  -- new invoke
  -- thisCall by party
  Parsed: RequestApplyTreatment
  From: URS_P[1328]/425825
  Numbers: +<000005000> -<none>
  Calls: 1125a890:1 none
  Parties: 000005000.ccc05c0-1125a890:1
          none
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
  -- validate
  -- state check: ok
  CIFace: Sent CRequest@8c66030 RequestApplyTreatment-URS_P[1328]/425825
  FinishRequest CRequest@8c66030 RequestApplyTreatment-URS_P[1328]/425825
  IFace stats: q=0 s=0
  -- complete
07:44:10.330: free_dcr 0000000010cd9db0
07:44:10.330: SIPTR(94497): Begin step 0 - SipTransactionProcessMsml(94498)
07:44:10.330: free_dcr 0000000012357fb0
07:44:10.330 SIPCONN(PHX_GVP_8): CtiRequest(3)
07:44:10.330: SIPDLG[45500]: register TRN[1271596]
07:44:10.330: Sending  [0,UDP] 913 bytes to 10.94.159.44:5090 >>>>>
INFO sip:Genesys@10.94.148.45:5170 SIP/2.0
From: sip:8043533260@10.92.243.242;tag=386ADA4B-D516-4399-B159-7ED3DA8AA348-72962
To: <sip:PHX_GVP_8@10.94.159.45:5060>;tag=D07FD391-9CB1-40AF-EEB5-D725DC154008
Call-ID: 1CA5EF58-FD43-4816-A2C8-11BF7AD35DB4-43495@10.94.159.45
CSeq: 7 INFO
Content-Length: 308
Content-Type: application/vnd.radisys.msml+xml
Via: SIP/2.0/UDP 10.94.159.45:5060;branch=z9hG4bK96F215F5-4695-4921-97CE-24079C79D085-181964
Contact: <sip:8043533260@10.94.159.45:5060>
Max-Forwards: 69
Route: <sip:000000000D40DD20@10.94.159.44:5090;lr;gvp.rm.datanodes=1%7C2;idtag=0000131C>

<?xml version="1.0" encoding="UTF-8"?>
<msml version="1.1">
<dialogstart target="conn:D07FD391-9CB1-40AF-EEB5-D725DC154008" name="announcement425825" type="application/moml+xml">
<play barge="false" cleardb="true" gvp:precheck="true">
<video uri="announcement/19999"/>
</play>
</dialogstart>
</msml>

07:44:10.330: SipDialog: event CONNECTED_SEND_REQUEST, t=1271596, s=7, r=6, m=0000000012e615d8
07:44:10.330 SIPCONN(PHX_GVP_8): HandleSipDialogEvent(CONNECTED_SEND_REQUEST) - filtered
  -- deleted: CRequest@13003320 RequestApplyTreatment-URS_P[1328]/425474
07:44:10.330 --- CIFace::Request ---
07:44:10.330: $-TLIB:CTI:Unknown:0:566

07:44:10.330: $+NET:SIP::0:0
07:44:10.330: SIPTR: Received [0,UDP] 387 bytes from 10.30.243.242:5060 <<<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.94.159.45:5060;branch=z9hG4bK96F215F5-4695-4921-97CE-24079C79D085-179694;received=10.94.148.24
From: <sip:2105079557@10.94.159.45:5060>;tag=386ADA4B-D516-4399-B159-7ED3DA8AA348-72752
To: <sip:88599774892@10.94.159.45:5060>;tag=gK088487c3
Call-ID: 1CA5EF58-FD43-4816-A2C8-11BF7AD35DB4-43347@10.94.159.45
CSeq: 1 INVITE
Content-Length: 0


07:44:10.330: Sending  [0,UDP] 405 bytes to 10.30.243.242:5060 >>>>>
ACK sip:88599774892@10.92.243.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.94.159.45:5060;branch=z9hG4bK96F215F5-4695-4921-97CE-24079C79D085-179694
From: <sip:2105079557@10.94.159.45:5060>;tag=386ADA4B-D516-4399-B159-7ED3DA8AA348-72752
To: <sip:88599774892@10.94.159.45:5060>;tag=gK088487c3
Call-ID: 1CA5EF58-FD43-4816-A2C8-11BF7AD35DB4-43347@10.94.159.45
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0


07:44:10.330: SipDialog: event CALLING_RESREJECT, t=1266336, s=9, r=5, m=0000000012e5fc28
07:44:10.330 SIPCONN(282608599774892): HandleSipDialogEvent(CALLING_RESREJECT)
07:44:10.330 SIPCONN(282608599774892): 1pcc event CALLING_RESREJECT
07:44:10.330 SIPCONN(282608599774892): ConvertResponse: 403
07:44:10.330 SIPCONN(282608599774892): ConvertResponse: no conversion configured for 403
07:44:10.330 SIPCONN(282608599774892): Failed to obtain Media Server ID
07:44:10.330 SIPCONN(282608599774892): Failed to obtain Media Server ID
07:44:10.330: ExtSvc: Script parse failed, cannot find priority 102 to execute
07:44:10.330: ERROR: 10000004, GetInstruction(priority, instruction), SipExtendedServicesResult.cpp,901
07:44:10.330: ERROR: 10000004, SetNextInstruction(priority), SipExtendedServicesResult.cpp,990
07:44:10.330 SIPCONN(282608599774892): state e:4,p:2,s:6,c:8,rc:403,m:1
07:44:10.330 SIPCONN(6530): CheckUpdateTransferStatus: no original dialog
07:44:10.330 SIPPARTY(282608599774892): 16789829 verify update of party-connection state A-F
07:44:10.330 +++ CIFace::Event +++
  +++ Pre-event +++
    Type EventDestinationBusy
    Devices: <6530/6530> <-/282608599774892> <-/->
    Calls: 16782278/019102a0d93e5fd2/16782278.1125d420/c:2/r:0 0/none
    Parties: D6530/6530.11608700-1125d420:1/l:1/r:0/Dialing,Active,Origination
    X282608599774892/282608599774892.11606e40-1125d420:1/l:2/r:0/Alerting,Destination
    none
    Cause: Blocked/35, Info: 0
    Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
  --- Pre-event ---
  +++ DestBusy +++
    -- target state not compatible at line 1170
    SetFailed: party 6530.11608700-1125d420:1, cause Blocked
@07:44:10.3300 [0] 8.1.102.09 distribute_event: message EventDestinationBusy
AttributeEventSequenceNumber 0000000000069989
AttributeTimeinuSecs 330000
AttributeTimeinSecs 1494513850 (07:44:10)
AttributeExtensions [23] 00 01 01 00..
'BusinessCall' 0
AttributeOtherDNRole 2
AttributeOtherDN '282608599774892'
AttributeThisDNRole 1
AttributeAgentID '38560'
AttributeThisDN '6530'
AttributeDNIS '88599774892'
AttributeUserData [160] 00 04 00 00..
'IW_CaseUid' '47cb2bc6-d164-451b-976c-7b307e193c53'
'IW_BundleUid' '4d52c48e-e136-4b55-b453-3562d178b835'
'CustomerSegment' 'SHSV'
'ContactId' '0008GaBRP4EVBS7D'
AttributeCallUUID '39EDAO5G9L41DFO39TP55JK7EC0003UU'
AttributeConnID 019102a0d93e5fd2
AttributeCallID 16782278
AttributePropagatedCallType 3
AttributeCallType 3
AttributeCallState 5
07:44:10.330 Int 04544 Interaction message "EventDestinationBusy" generated
07:44:10.330 Trc 04542 EventDestinationBusy sent to [1772]
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Call gets busy signal - can't tell why
« Reply #5 on: May 19, 2017, 03:35:51 PM »
Forbidden, so it is trying to access something it doesn't has permission to read at. Check your security and permissions on you WAS.
Logged
Pages: [1]   Go Up
« previous next »