Genesys Cloud - Main

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Sam, thanks for this.

I did, here's a snippet of configs:

Thank you.

Tiago

------------------------------
Tiago Silva
Senior Sales Engineer

Original Message:
Sent: 02-05-2026 12:20
From: Samuel Jillard
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

------------------------------
Sam Jillard
Online Community Manager/Moderator
Genesys - Employees

Original Message:
Sent: 02-05-2026 11:42
From: Tiago Silva
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

@Tiago - We also needed to accomplish this in order to keep calls made to another Genesys Cloud org from going out the PSTN.

Apologies if this was already presumed, but in our case because we don't have any Sites defined on the Trunks, Architect uses the Default Site for our outbound calls. Just for grins/giggles, can you open your Default Site and go to the Number Plan tab. Can you confirm your "RTT" Number Plan is at the top of that list?

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology | Colossians 3:23-24

Original Message:
Sent: 02-05-2026 12:43
From: Tiago Silva
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi Sam, thanks for this.

I did, here's a snippet of configs:

Thank you.

Tiago

------------------------------
Tiago Silva
Senior Sales Engineer

Original Message:
Sent: 02-05-2026 12:20
From: Samuel Jillard
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

------------------------------
Sam Jillard
Online Community Manager/Moderator
Genesys - Employees

Original Message:
Sent: 02-05-2026 11:42
From: Tiago Silva
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Sam, thanks for this.

I did, here's a snippet of configs:

Thank you.

Tiago

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi,
this is important because...
- agent initiated outbound calls and consult transfers use the site to which the agent's phone is associated.
- transfers in architect and blind transfers by agents use the site which was used when the call arrived in Genesys Cloud. The Number Plan Site feature on the trunk  to control which site is used for these transfers.  

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Christian, indeed makes sense. Thank you, but even with the number plans and Outbound routes in place (I test them and they work OK) the call is not going out that new trunk because it's using the "default OB route". Now if I use the newly created Ext trunk in the Default OB route, it works - so the trunk itself seems to work fine, but the rules don't seem to be applied to the Architect transferred call.

Result of the simulate call from the SITE where calls land into:

thanks

Hi,
this is important because...
- agent initiated outbound calls and consult transfers use the site to which the agent's phone is associated.
- transfers in architect and blind transfers by agents use the site which was used when the call arrived in Genesys Cloud. The Number Plan Site feature on the trunk  to control which site is used for these transfers.  

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi,
did you configure this site as Number Plan Site on the new trunk?

Kind regards,
Christian

Hi Christian, indeed makes sense. Thank you, but even with the number plans and Outbound routes in place (I test them and they work OK) the call is not going out that new trunk because it's using the "default OB route". Now if I use the newly created Ext trunk in the Default OB route, it works - so the trunk itself seems to work fine, but the rules don't seem to be applied to the Architect transferred call.

Result of the simulate call from the SITE where calls land into:

thanks

Hi,
this is important because...
- agent initiated outbound calls and consult transfers use the site to which the agent's phone is associated.
- transfers in architect and blind transfers by agents use the site which was used when the call arrived in Genesys Cloud. The Number Plan Site feature on the trunk  to control which site is used for these transfers.  

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Christian,

I did indeed, and I'm assuming that the Current Trunk (Genesys Voice that I am not able to amend configs on) should have the same site(?). I've configured the following on this new Trunk?

Thanks again.

Tiago

Hi,
did you configure this site as Number Plan Site on the new trunk?

Kind regards,
Christian

Hi Christian, indeed makes sense. Thank you, but even with the number plans and Outbound routes in place (I test them and they work OK) the call is not going out that new trunk because it's using the "default OB route". Now if I use the newly created Ext trunk in the Default OB route, it works - so the trunk itself seems to work fine, but the rules don't seem to be applied to the Architect transferred call.

Result of the simulate call from the SITE where calls land into:

thanks

Hi,
this is important because...
- agent initiated outbound calls and consult transfers use the site to which the agent's phone is associated.
- transfers in architect and blind transfers by agents use the site which was used when the call arrived in Genesys Cloud. The Number Plan Site feature on the trunk  to control which site is used for these transfers.  

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi, 
sorry, is the new trunk the one where the inbound calls come in? If not and it's the GCV, I'm out of ideas - probably best to open a ticket.

Hi Christian,

I did indeed, and I'm assuming that the Current Trunk (Genesys Voice that I am not able to amend configs on) should have the same site(?). I've configured the following on this new Trunk?

Thanks again.

Tiago

Hi,
did you configure this site as Number Plan Site on the new trunk?

Kind regards,
Christian

Hi Christian, indeed makes sense. Thank you, but even with the number plans and Outbound routes in place (I test them and they work OK) the call is not going out that new trunk because it's using the "default OB route". Now if I use the newly created Ext trunk in the Default OB route, it works - so the trunk itself seems to work fine, but the rules don't seem to be applied to the Architect transferred call.

Result of the simulate call from the SITE where calls land into:

thanks

Hi,
this is important because...
- agent initiated outbound calls and consult transfers use the site to which the agent's phone is associated.
- transfers in architect and blind transfers by agents use the site which was used when the call arrived in Genesys Cloud. The Number Plan Site feature on the trunk  to control which site is used for these transfers.  

Hi Tiago,

Have you set the site with the number plan that you want to use?  Number Plan Site feature 

If this isn't set, it may just use your default outbound route

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi Tiago,

You are falling in to the same 'bug' that I found, that Architect number transfer does not respect the same rules as agent/simulated call on the number plans.
I had to submit an idea, which has gained zero traction, so must be a very low used solution design.
https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-231

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

hi Kevin,

it indeed makes sense, but I am wondering if this is some sort of config/bug as the rules seem to be working when we simulate, but not when we route calls from Architect?

I thought the rules should apply to any call from the site, so we could select a different trunk to send the calls out from? (or transfer them). I'll review the idea and vote, but as you said there was not traction on it... hmmm

A Support case maybe is a better idea?

Cheers

Tiago

Hi Tiago,

You are falling in to the same 'bug' that I found, that Architect number transfer does not respect the same rules as agent/simulated call on the number plans.
I had to submit an idea, which has gained zero traction, so must be a very low used solution design.
https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-231

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

hi Kevin,

it indeed makes sense, but I am wondering if this is some sort of config/bug as the rules seem to be working when we simulate, but not when we route calls from Architect?

I thought the rules should apply to any call from the site, so we could select a different trunk to send the calls out from? (or transfer them). I'll review the idea and vote, but as you said there was not traction on it... hmmm

A Support case maybe is a better idea?

Cheers

Tiago

Hi Tiago,

You are falling in to the same 'bug' that I found, that Architect number transfer does not respect the same rules as agent/simulated call on the number plans.
I had to submit an idea, which has gained zero traction, so must be a very low used solution design.
https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-231

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Have you looked at the Execution Data in the Architect flow doing the transfer to see exactly what number and format is being used for the outbound call on the transfer?

------------------------------
George Ganahl GCCX-AI, GCP, GCD
Technical Adoption Champion
Genesys

Original Message:
Sent: 02-06-2026 09:08
From: Tiago Silva
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

hi Kevin,

it indeed makes sense, but I am wondering if this is some sort of config/bug as the rules seem to be working when we simulate, but not when we route calls from Architect?

I thought the rules should apply to any call from the site, so we could select a different trunk to send the calls out from? (or transfer them). I'll review the idea and vote, but as you said there was not traction on it... hmmm

A Support case maybe is a better idea?

Cheers

Tiago

------------------------------
Tiago Silva
Senior Sales Engineer

Original Message:
Sent: 02-06-2026 04:47
From: Kevin Young
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi Tiago,

You are falling in to the same 'bug' that I found, that Architect number transfer does not respect the same rules as agent/simulated call on the number plans.
I had to submit an idea, which has gained zero traction, so must be a very low used solution design.
https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-231

------------------------------
Kevin Young
TTEC Digital, LLC
kevin.young@ttecdigital.com

Original Message:
Sent: 02-05-2026 11:42
From: Tiago Silva
Subject: Transfer to an external number not going via the correct trunk even that rules are set to do so

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------

Hi all, 

need some help please. In a nutshell:

• Call lands in Genesys using a Genesys Voice Trunk
• Routing transfers to "external number" that i've collected from a Data Table (33123456789@rtt.voip.parloa.com) via an Architect flow (listened to it and is doing the right thing)
• There is a site number plan set :^([^@\:]+@)(rtt\.voip\.parloa\.com)$
• there is an Outbound route set with the new trunk configured (and also the Main trunk as default)
• Simulated call as per the format shared, it works as it seems to target the new trunk
• But the Inbound call via my mobile don't, listening to it the format seems exactly as the above (second point)
• Call continues to be routed via "default route" (if i change the respective trunk there, the new one works so it does not seem that Trunk is the issue)

How can I enforce the correct trunk to be used?

any help please?

Thank you

#Telephony

#BYOC

#ExternalTrunk

------------------------------
Tiago Silva
Senior Sales Engineer
------------------------------