Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Architect transfert with another/different trunk

    Posted 12-11-2023 09:46
    No replies, thread closed.

    Hello everyone,

    As stated in the documentation  Add a Transfer action to a flow - Genesys Cloud Resource Center

    , outgoing calls are currently routed through the same trunk used for incoming calls.

    I am currently looking for a solution to be able to use a different outbound trunk. Is this feasible, and if so, how can I achieve this? I have already assigned my specific trunk to the site/division of the flow, but it doesn't seem to be working.

    Thank you very much for your assistance.

    Arnaud


    #ArchitectureandDesign
    #Implementation
    #PlatformAdministration
    #Telephony

    ------------------------------
    Arnaud
    ------------------------------


  • 2.  RE: Architect transfert with another/different trunk

    Posted 12-11-2023 10:54
    No replies, thread closed.

    Unfortunately, only the same inbound trunk or the default site.  We only had default site for many years.  You can vote up this one:  Define Site for Transfer to External | Genesys Cloud Ideas Portal (aha.io)



    ------------------------------
    Robert Wakefield-Carl
    ttec Digital
    Sr. Director - Innovation Architects
    Robert.WC@ttecdigital.com
    https://www.ttecDigital.com
    https://RobertWC.Blogspot.com
    ------------------------------



  • 3.  RE: Architect transfert with another/different trunk

    Posted 12-12-2023 01:37
    No replies, thread closed.

    I recently came across the same issue. I researched on this community forum and got the solution.  Thanks to all the people who shared the knowledge here.

    In Genesys Cloud CX, the Architect flow uses the default site and its number plans and Outbound Routes based on the classification defined in the Number plan section. There is no other way. I have tested this solution and it works. Here are the steps.

    1) Identify the default site.

    2) Create a new number plan with a new or existing classification(s) in the default site

    3) Create a new Outbound Route using the new trunk you have created.

    4) Use the Architect flow and transfer the call with the number format adhering to the new Number Plan created.

    5) While the flow is being executed, watch the Trunk graph! you see the call being routed through the new trunk.

    Hope this helps.



    ------------------------------
    Ajay Reddy
    VoiceXnet
    ------------------------------



  • 4.  RE: Architect transfert with another/different trunk

    Posted 12-13-2023 08:33
    No replies, thread closed.

    Yes, you need to create a new new Outbound Route en the default site.

    Take a look in the new combo box for select the default site in the trunk.



    ------------------------------
    Max Hernandez
    ------------------------------



  • 5.  RE: Architect transfert with another/different trunk

    Posted 12-15-2023 11:33
    No replies, thread closed.

    Thank you for your answers, which have guided me well. I can now use the desired route with a prefix. However, it works directly via the dialpad/softphone, but I have a failure when using it on my flow architect. There is a good chance that my problem is with the regex.

    Can you help me ? or how can I obtain routing logs with the call ID intercation on the flow?



    ------------------------------
    Arnaud
    ------------------------------

    Original Message


  • 6.  RE: Architect transfert with another/different trunk

    Posted 12-15-2023 11:42
    Edited by Ajay Reddy 12-15-2023 12:28
    No replies, thread closed.

    Hi,

    What would be the prefixed number you are planning to dial from the Architect flow?

    Maybe RegEx - ^(999)(\d{10})$  is what you are looking for.

    Normalized Number Expression $2  or +1$2  ( Depends if you simply want the 10-digit or E.164 formatted number)

    Based on what I learned each () constitutes $n  where "n" stands for the N th parenthesis. Again, that is what I observed and I could be wrong.

    I followed the link below to understand the RegEx. very simplified instructions.

    https://github.com/ziishaned/learn-regex/blob/master/README.md

    NOTE: You can simulate a call and see if your RegEx is working and taking the path of your new trunk created.
    ------------------------------
    Ajay Reddy
    VoiceXnet
    ------------------------------

    Original Message


Related Content