Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  BYOC - SIP trunk to local SBC

    Posted 08-24-2022 11:05
    No replies, thread closed.
    Hi,

    I am pretty new to the topic Bring-Your-Own-Carrier-Cloud and I just want to ask what I can do to get the trunk up and running.

    Setup:
    - Genesys Cloud CX
    - local installation of an audiocodes SBC with a public IP address (and DNS).
    - PSTN/SIP Provider

    Current situation:
    The PSTN/SIP Provider is connected via SIP trunk to the audiocodes SBC via public IP address. The SBC at the private LAN side is connected to a Genesys Pure Connect with a range of 1.000 numbers. There are much more numbers routed to other destinations internally.

    Requested solution:
    The SBC should route a dedicated number range to Genesys Cloud for further processing by agents/AI/bots/...
    Therefore I need a SIP trunk between Genesys Cloud Edges and my SBC.

    Question:
    In Genesys Cloud I have 3 options for external trunks:
    • BYOC Carrier
    • BYOC PBX
    • External SIP
    1) I've setup a "Generic BYOC Carrier" trunk and configured "Inbound / Termination","outbound","SIP Servers or Proxies","Calling" and "SIP Access Control".
    This trunk get's to state "Operational".
    The problem is that I don't receive any SIP OPTIONS response to the requests of the SBC. Due to this it's not possible for the SBC to switch to another GC Edge destination in case an Edge is not reachable.

    2) So I've setup a "External SIP" trunk, but even I configure the same settings I could not get the trunk to an operation state. It's still "not configured".
    For this kind of trunk I can activate "Availability" (SIP OPTIONS ???) and "Registration" (SIP REGISTER ???) and even with this activation I don't receive any sip requests at the SBC.

    At the external trunk overview I can see both trunks with protocol "TLS", but trunk "Generic BYOC Carrier" has no Listen Port and trunk "External SIP" has Listen Port 5061.
    I expected that trunk "Generic BYOC Carrier" would also have any kind of Listen Port. It's strange that it's empty.

    Both trunks are configures at Sites -> "my site" -> Outbound Routes" as a dedicated route ("Outbound Route 1" and "Outbound Route 2") with different classifications.

    So my question are ....
    1) What's the correct type of trunk? "Generic BYOC Carrier" or "External SIP"?
    2) What else is my be missing?

    Would be very thankful if anyone could give me any kind of information that might be helpful.
    And yes ... I have read all related articles in the Ressource Center. But maybe I missed something that basically needed?

    BR, Robert




    #Integrations
    #SIP/VolP
    #SystemAdministration
    #Telephony

    ------------------------------
    Robert Herms
    arvato Systems GmbH
    ------------------------------


  • 2.  RE: BYOC - SIP trunk to local SBC

    Posted 08-25-2022 03:28
    No replies, thread closed.
    We have quite a few customer with this setup (using TLS). So I might be able to help if still needed.

    ------------------------------
    Tommy Braes
    CX Consultant
    Proximus PLC
    ------------------------------

    Original Message


  • 3.  RE: BYOC - SIP trunk to local SBC

    Posted 08-25-2022 23:45
    No replies, thread closed.

    I setup the same configuration recently using Pure Connect -  Audiocodes SBC  - Genesys Cloud using TLS.

    Generic BYOC Carrier is correct and the SBC does receive SIP option responses from the BYOC load balancers. 

    I found this document very useful.
    Genesys Cloud and Generic SIP Trunk using Mediant SBC Configuration Note (audiocodes.com)

    And this article in the resource centre. 
    TLS trunk transport protocol specification - Genesys Cloud Resource Center (mypurecloud.com)

    Hope that helps

    ------------------------------
    Nick Besestri
    ESSENTIAL ENERGY
    ------------------------------

    Original Message


  • 4.  RE: BYOC - SIP trunk to local SBC

    Posted 08-29-2022 09:36
    No replies, thread closed.

    Hi Nick,

    we have found the audiocodes docuemntation, too :-)

    We tried the DNS's mentioned in the second link but we still dont get any reply to our SIP OPTION ping.
    Due to this the trunks don't get "ONLINE" from audiocodes point of view.

    We will try to send the OPTONS ping with FQDN of the SBC instead of the IP. Maybe this will solve the general connectivity.

    BR, Robert



    ------------------------------
    Robert Herms
    arvato Systems GmbH
    ------------------------------

    Original Message


  • 5.  RE: BYOC - SIP trunk to local SBC

    Posted 08-30-2022 01:35
    No replies, thread closed.
    Hi Robert

    Not sure, the options message from our SBC is just the IP. 

    On the cloud trunk side I have the SIP Server or Proxies using the SBC DNS name and the SIP Access Control has the SBC External IP.

    Inbound SIP Termination identifier is set and the outbound is using TGRP attributes.

    I had issues with the network side of our environment and the firewall rules required as we are behind a NAT and needed to set the NAT translation on the SBC also.

    ------------------------------
    Nick
    ------------------------------

    Original Message


  • 6.  RE: BYOC - SIP trunk to local SBC

    Posted 08-30-2022 03:39
    No replies, thread closed.
    Hi Nick,

    "On the cloud trunk side I have the SIP Server or Proxies using the SBC DNS name":
    me too

    "SIP Access Control has the SBC External IP":
    me too

    "Inbound SIP Termination identifier is set":
    me too. I just set a name "TestRobert" as an identifier right now. But for OPTIONS ping it might not be necessary to set a good name.

    "the outbound is using TGRP attributes":
    we don't use TGRP attributes right now. For OPTIONS ping it might not be necessary, right?

    "we are behind a NAT":
    we have a public IP address at the SBC, so without NAT

    Today in the afternoon we have a meeting with Genesys Cloud support. Let's see what they can find out...

    BR, Robert

    ------------------------------
    Robert Herms
    arvato Systems GmbH
    ------------------------------

    Original Message


  • 7.  RE: BYOC - SIP trunk to local SBC

    Posted 08-31-2022 02:46
    No replies, thread closed.
    After some reviews we finally found the issue at the SBC interface configuration.
    Now it's working fine :-D

    BR, Robert

    ------------------------------
    Robert Herms
    arvato Systems GmbH
    ------------------------------

    Original Message


  • 8.  RE: BYOC - SIP trunk to local SBC

    Posted 04-29-2025 10:52
    Edited by Facundo Nowicky 04-29-2025 10:52
    No replies, thread closed.

    Hello Robert, 

    Could you tell me which options did you end up using on the SBC side to guarantee the SIP OPTIONS being answered? 
    Did you use a specific kind of External Trunk on Genesys Cloud?

    Regards,



    ------------------------------
    Facundo Nowicky
    Sr. Genesys Consultant - Sr. Software Developer
    ------------------------------

    Original Message


Related Content