calls being sent out wrong trunk

[needafix]

Hi, seeing calls which are overseas calls that have 011 in front and A2B configured to remove the 011 using the wrong trunk.

In the simulator putting either the number with 011 or without, shows the correct trunk. When dialing these overseas numbers its using a trunk that is for North America instead.

Have tried removing the rate cards from the rate plan and add them back but that did not change anything.
Any ideas on how to fix this?

Thanks.

[moretalk]

Have you looked at using the simulator and are you seeing the wrong trunk selection there? Also check the database as I have seen spaces in prefixes before that cause issues. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: needafix <notifications@github.com> Sent: Tuesday, April 23, 2019 5:11:43 PM To: Star2Billing/a2billing Cc: Subscribed Subject: [Star2Billing/a2billing] calls being sent out wrong trunk (#162) Hi, seeing calls which are overseas calls that have 011 in front and A2B configured to remove the 011 using the wrong trunk. In the simulator putting either the number with 011 or without, shows the correct trunk. When dialing these overseas numbers its using a trunk that is for North America instead. Have tried removing the rate cards from the rate plan and add them back but that did not change anything. Any ideas on how to fix this? Thanks. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#162>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABRY2BJXM73RU37N45T7EO3PR4YL7ANCNFSM4HH2AQEQ>.

[needafix]

Hi Moretalk, yeah ran the simulator several times, The trunk used when dialing the TN, is NOT a trunk listed in the rates/trunks displayed.

[needafix]

I have small FreePBX installed along with A2Billing. What I am also noticing is although all the info in the trunk setting for both A2Billing and FreePBX are correct, A2Billing doesn't want to use it. However, if i put the FQDN instead of a trunk name in A2Billing it does dial out. I have had this A2B working well for > 6 years, It must be in the last month I started noticing issues when calling someone overseas that I know would use the trunk.

[needafix]

Oh by the way, the reason its using the other trunk not listed in the simulator for the TN, is due to the setting in A2Billing for failover trunk. So we know that part is working. It seems that its not talking to FreePBX since the FreePBX trunk has the FQDN of the carrier. We have always just had one name like 'overseasprovider' in the trunk settings in A2Billing and of course in FreePBX in SIP part of trunk the name would be same 'overseasprovider'. I wonder where the problem lies.

I just changed the name in A2Billing to the FQDN, make a call overseas and in cli saw it was using the correct trunk 'overseasprovider'.

[needafix]

The whole issue was all DNS. It's fixed.