Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Site and Edge

    Posted 07-14-2020 14:18
    No replies, thread closed.
    Hi all,

    I have the following setup on sites and edges

    Site A: EdgeA1, EdgeA2 and EdgeA3
    Site B: EdgeB1, EdgeB2 and EdgeB3

    We have hundred of WebRTC phones in either Site A and Site B.

    First of all, our goal was to move everyone off of Site B.  So here is what I did:

    1. Change Site A Phone Edge Assignments to "Use this site"
    2. Change Site B Phone Edge Assignments to "Use these site" and Site A in both Primary and Secondary Sites.

    After the above changes, I verified all WebRTC had one of the 3, EdgeA1, EdgeA2 and EdgeA3 as Primary and Secondary Edge.  However I still saw outgoing calls thru EdgeB1, EdgeB2 and EdgeB3 so I created a support ticket.  They responded back saying because some of the WebRTC phones were still in Site B so they would use Site B edges for outgoing calls.  I then posted the following questions that I haven't gotten certain answers:

    1. Does it mean the primary and secondary edges in the WebRTC phones are only for incoming calls?  I assume if an agent phone was registered to EdgeA1 and EdgeA2, a call coming into EdgeB1 would still be able to route to the agent.  Is it correct?
    2. In terms of outgoing calls, I can go thru all hundred WebRTC phones and change the site to SiteA.  However during DR situation when let's say SiteA is down, does it mean I have to go thru all hundred WebRTC phones and change the site to SiteB so that the agents can make outgoing calls?

    Thanks in advance.



    #Telephony

    ------------------------------
    Edward Wu
    BANK OF HAWAII
    ------------------------------


  • 2.  RE: Site and Edge

    Posted 11-09-2020 02:25
    No replies, thread closed.
    Hi Edward,

    I have the same question with you, have you found any answers?

    ------------------------------
    Charis Sideridis
    Intracom S.A. Telecom Solutions
    ------------------------------



  • 3.  RE: Site and Edge

    Posted 11-09-2020 16:51
    No replies, thread closed.
    That's a good one.

    1. In this scenario, the call is routed to the Edge with the Primary registration(Intra Edge communication) and delivered to the user.
    2. If you have all the trunks on the same Edge group you don't have to do anything.

    ------------------------------
    Paulo Mesquita
    Spark NZ Trading
    ------------------------------

    Original Message


  • 4.  RE: Site and Edge

    Posted 11-11-2020 09:06
    No replies, thread closed.
    The station's phone assignment is the Edge that is responsible for contacting the station.  When an outbound call is placed from the UI, two call legs actually are made which are tied together.  The first is a call leg is to the user's station - this will be a call from one of the Edges assigned to that station to the user's selected station.  The second call is the dialed outbound call leg- this will follow the dial plan setup for the site in which the station exists.  You can use the "Simulate Call" function on the site to see what will happen.  In your scenario, if you have a number plan tied to a classification, and that classification is tied to an outbound route, and the selected trunk for the outbound route is assigned to Edges in both sites A & B, then in order to balance load it may be determined to use an Edge in site B for the dialed call leg even though the station is in site A.  If you want to prevent this, then you will need to build trunks unique for each site.  However, be careful and test your redundancy because if you have removed Site B from station assignments completely your stations will likely not be available if all the Edges in Site A become unavailable.  You may prefer for Site B to be the secondary Edge assignment for each station.  However, as I mentioned before, always test your redundancy capabilities so you know it is working as intended before a real situation arises.

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

    Original Message


Related Content