Genesys Cloud (formerly PureCloud)

Discussion Thread View
Expand all | Collapse all

SIP trunk to external PBX in BYOC Cloud architecture

  • 1.  SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-05-2020 03:32
    Hi,

    theoretically its possible to stablish an external sip trunk to another PBX as long as it's SIP compliant. My Genesys Cloud org is BYOC Cloud based, no edges present. I have configured SIP trunk to IP Office (Avaya) and incoming calls work perfectly (I have configured extensions for that in Genesys Cloud side), but not outbound. Anyone faced something similar?
    #SIP/VolP

    ------------------------------
    Daniel Ondiviela
    LeadClic
    ------------------------------


  • 2.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-06-2020 04:27
    Hi Daniel

    How are you? How many time I do not know about yourself.

    Are you try create pattern and outbound route to IP Office using the trunk you created?
    In case you make Test Call, it recognize the pattern and indicate it use the SIP Trunk.

    Regards,

    ------------------------------
    Ricardo Macayo
    Telefonica Soluciones de Informatica
    ------------------------------



  • 3.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-06-2020 05:24
    Ey Ricardo, so good to "see" you again! Hope you are doing well

    The simulation of the call put it in the correct trunk. Besides, when I do the real test call to an extension of the external PBX (1206), I see within the trunk config 1 outbound call



    ------------------------------
    Daniel Ondiviela
    LeadClic
    ------------------------------



  • 4.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-06-2020 06:26
    Hi Daniel, everything well.
    Can you make trace over Trunk, on Diagnostics? I am not used BYOC and I do not know if you can take this trace.

    I have similar problem in other org, because org include prefix +34 on DNIS sended.
    If you have Simulation OK, maybe when dialing the system include prefix and it did not match with pattern.

    Review if you can take trace or try to modify Expression on pattern to do not include prefix when launch from agent.

    Regards

    ------------------------------
    Ricardo Macayo
    Telefonica Soluciones de Informatica
    ------------------------------



  • 5.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-06-2020 08:09
    Edited by Daniel Ondiviela 05-06-2020 08:09
    I have tried 3 types of number plan for matching these kind of external PBX calls:

    -Number list


    - Digit lenght

    - Regex

    Also tried more complicated regex than that in the screenshot. Nothing worked.

    I also tried dialing first "1206" (avaya extension) and then "sip:1206@xxxxxxx.zzz", and also, any of them didn't work

    PD: Extension and Network classifications are included in the outbound route pointing to the trunk




    ------------------------------
    Daniel Ondiviela
    LeadClic
    ------------------------------



  • 6.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    GENESYS
    Posted 05-06-2020 10:05
    Since you are using an External Trunk, I am guessing the Avaya views it as an inbound external call, like one coming from the telco?

    What format is the Avaya expecting for that type of call? I don't think it can just accept an extension. It may be expecting deflection info from Genesys Cloud, or a DID, or something like that...but not just an inbound call to the extension number.

    I guess I should ask, too...is the External Trunk set up as a PBX Trunk? I presume so, based on the first screenshot which has it as a Generic BYOC PBX type.

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



  • 7.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    Posted 05-07-2020 06:07
    Solved. It was a comms problem. One firewall before Avaya IP Office was blocking inbound SIP invites.

    Thanks everybody for the suggestions.

    ------------------------------
    Daniel Ondiviela
    LeadClic
    ------------------------------



  • 8.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    GENESYS
    Posted 05-07-2020 07:16
    That will do it. Glad to hear you got it fixed!

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



  • 9.  RE: SIP trunk to external PBX in BYOC Cloud architecture

    GCAP Member
    Posted 27 days ago
    PIggybacking on this thread, but it may merit it's own...

    @George Ganahl - what about inbound sip terminations that are in the form of a non e1.64 string like an extension? For example, if i get an invite into a byoc trunk at something like: +​123456@myorg.etc... Which site/number plan would I use to try to handle that? ​

    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------