Genesys Cloud (formerly PureCloud)

Discussion Thread View
Expand all | Collapse all

Can't RLT transfer (Edge responds with SIP 488)

  • 1.  Can't RLT transfer (Edge responds with SIP 488)

    Posted 08-19-2020 06:33
    Hi, we tried to do RLT transfer from the Architect and have Enabled RLT transfer in External trunk settings.
    However, when we initiate the transfer, from SIP trunking provider we get 202 Accepted and then NOTIFY (as showed on the image), but Edge responds with 488.
    Right side of the ladder diagram is Genesys Media Edge. Left side is SIP trunking provider.


    Is there any additional Setting we are missing here?

    Also we have find on community information indicating that RLT can be accomplished only from Architect (agent can not initiate transfer using REFER) and we find this information to be right.

    Thank you,
    Regards,


    #SIP/VolP
    #Telephony

    ------------------------------
    Nebojsa Radovanovic
    Star Telecom
    ------------------------------


  • 2.  RE: Can't RLT transfer (Edge responds with SIP 488)

    GENESYS
    Posted 09-02-2020 11:42
    I have a BYOC-Premises model with a tie-line to a PureConnect server. Here is an example of the NOTIFY the IC Server sends on a RLT from the IVR that works:

    NOTIFY sip:13172111000@10.19.87.19:5060 SIP/2.0 To: "Community Support And Referral Services IN" <sip:13172111000@10.19.87.19>;tag=Yk1gk5w From: <sip:3172011000@geo.edu.inin.com>;tag=jlybnjA CSeq: 2 NOTIFY Call-ID: 7c1ecabcd33d5b8acb762ad3d4244866@10.19.87.17 Via: SIP/2.0/UDP 10.19.87.17;branch=z9hG4bKbIIf4f72gh2d67vfwkg6 Contact: <sip:3172011000@10.19.87.17> Max-Forwards: 70 x-inin-crn: 3001840129 Supported: join, replaces User-Agent: ININ-TsServer/20.1.4.22 Event: refer Subscription-State: terminated;reason=noresource Content-Type: message/sipfrag;version=2.0 Content-Length: 18 SIP/2.0 200 OK ​
    The main difference I see is that this one which works has "join" in the Supported: element, and the one from your SBC does not. I don't know if that is significant, but it's the only real difference that jumps out at me.

    The agent transfer functionality was never built due to complexity in getting it right, and the Resource Center should be updated soon. There is an Idea you can vote for to try and get it implemented:

    https://genesyscloud.ideas.aha.io/ideas/TEL-I-252

    Have you opened a case with Care regarding the 488?

    ------------------------------
    George Ganahl GCP (Genesys Cloud), ICCE
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 3.  RE: Can't RLT transfer (Edge responds with SIP 488)

    GENESYS
    Posted 27 days ago
    Was this resolved?  The issue from the screen shot appears to be that the new destination is attempting to use RFC3420 (message/sipfrag).  I expect the SIP/488 response is in regards to that.  Can sipfrag be disabled on the new target?

    ------------------------------
    Phil Whitener
    Genesys - Employees
    ------------------------------



  • 4.  RE: Can't RLT transfer (Edge responds with SIP 488)

    Posted 24 days ago
    Hi,
    Yes, this was resolved, thank you.
    Regards,

    ------------------------------
    Nebojsa Radovanovic
    Star Telecom
    ------------------------------