Agent Transfers Failing

Voice & Telephony
1

For one of the call scenarios, the calls are failing for the customer.

The scenario is Agent 1 dials to Agent 2 , Agent 2 put him on hold and trying to do single step transfer to Agent 3.

the moment Agent 3 answers the call, its getting disconnected at both Agent 1 and Agent 3.

please find the error snap shot below.

12:32:54.842: Sending [0,UDP] 530 bytes to 56.207.75.92:19416 >>>>>
ACK sip:55586@56.207.75.92:19416;rinstance=adce9b7104499edc;transport=udp SIP/2.0
From: sip:8554118227@56.120.98.103:5060;tag=0097C8A4-A197-140A-ACAF-68627838AA77-60102
To: "55586"sip:55586@56.120.98.103:5060;tag=5168573f
Call-ID: 0097C89A-A197-140A-ACAF-68627838AA77-48426@56.120.98.103
CSeq: 8 ACK
Content-Length: 0
Via: SIP/2.0/UDP 56.120.98.103:5060;branch=z9hG4bK0097C8AE-A197-140A-ACAF-68627838AA77-264435
Allow: INVITE, ACK, PRACK, CANCEL, BYE, REFER, INFO, UPDATE, MESSAGE, NOTIFY, OPTIONS
Max-Forwards: 70

12:32:54.842: $:SIP:CTI:HA_SEND_SYNC_MESSAGE:683260
12:32:54.842: SipDialog: event CONNECTED_SEND_ACK, t=266123, s=7, r=8, m=2aaaac6d8c88
12:32:54.842 SIPCONN(55586): HandleSipDialogEvent(CONNECTED_SEND_ACK) - filtered
12:32:54.843: $:SIP:CTI:RTP_INFO:683261
12:32:54.843: SIPTR(227720): complete
12:32:54.843: SIPTR(227719): Step 0 - SipTransactionConnectCompleteAnswer(227720) complete
12:32:54.843: SIPTR(227719): complete
12:32:54.843: SIPCM: transaction SipScenario(227719) complete
12:32:54.843: PI: 10 S[CC]D[55586]C[*D[55586]]MP[C[*D[MSML]]C[*D[MSML]]]P[MSML!=-] - can’t recover
12:32:54.843: media peer: incorrect configuration 2
12:32:54.843: media peer: incorrect configuration 1
12:32:54.843: SD: none
12:32:54.843: call configuration error 4 detected
12:32:54.843 SIPCONN(MSML): ClrMediaPeer
12:32:54.843 SIPCONN(55586): set monitor 2aaaac6d8bb0, 0
12:32:54.843 SIPCONN(55586): state e:1,p:3,s:0,c:0,rc:0,m:0
12:32:54.843: SipDialog: ClearCall(phone=1,state=7)
12:32:54.843: SipDialog::Terminate(state=7,reason=0)
12:32:54.843: SIPDLG[51599]: register TRN[266124]
12:32:54.843: Sending [0,UDP] 443 bytes to 56.207.75.92:19416 >>>>>

Have anyone faced this scenario before?

2

Post full log please. That snippet doesn’t say much.
From SIP Server and the MS.

3

hey thanks.. Is there anyway I can send the log? The log is too big to copy here.

4

Not here, upload on some free service and post link here only. Try to make it on one that doesn’t request emails or something like that

5

Hey

thanks for your help. I got the fix for this issue.

When a single-step transfer is in progress, SIP Server now acknowledges the dynamic recording request for a transferred party, immediately, but starts recording only after a destination party answers the call. Previously in this scenario, SIP Server tried to start recording before the destination party answered the call that resulted in a failed recording attempt. (SIP-15693)

Genesys fixed this in latest hot fix. I will upgrade the SIp server