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
------------------------------
Original Message:
Sent: 05-06-2020 08:08
From: Daniel Ondiviela
Subject: SIP trunk to external PBX in BYOC Cloud architecture
I have tried 3 types of number plan for matching these kind of external PBX calls:
-Number list
------------------------------
Daniel Ondiviela
LeadClic
Original Message:
Sent: 05-06-2020 04:27
From: Ricardo Macayo
Subject: SIP trunk to external PBX in BYOC Cloud architecture
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
Original Message:
Sent: 05-05-2020 03:31
From: Daniel Ondiviela
Subject: SIP trunk to external PBX in BYOC Cloud architecture
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
------------------------------