Flowroute outgoing calls

[nicedoggie]

V20 AWS hosted, Flowroute is the SIP trunk. Inbound calls work. Outbound not.

Level
Warning
Event ID
12294
Date & Time
03/02/2024 8:00 PM
Details
Call or Registration to 804xxxxxxx@(Ln.10001@Flowroute) has failed. sip:34.210.91.112:5060;lr replied: Forbidden (403)

I think I'm missing something. My outbound routes are the same as in v.18 but I see on the Flowroute's console if you are using ip authentication to format your outbound calls like;

If you want to use IP-based authentication for your outbound calls, define your outbound allowed IPs below and configure your phone system to prepend the tech prefix to the dialed number as shown in the examples below. Format should be {tech_prefix}*{country_code}{phone_number}@{sip_proxy} Is that supposed to be done in Trunk-Options- Reformat Incoming our Outgoing caller ID?
Thanks

 

[biggreyphone]

I am using a hosted version of 3CX with flowroute in V20 and have been receiving the same error messages for a few months. I can make and receive calls though. Wireshark on my WAN and LAN do not pick up anything with the IP addresses to Flowroute. I know packet capture is going to be available in V20, but it is not quite yet. Not sure what to do either.

 

[nicedoggie]

Great, did you use ip authentication and anything else with the trunk?

 

[biggreyphone]

I have been using IP authentication for at least a few years. When I updated from V18 to V20 in December I didn't change anything with the trunks in 3CX. I just logged into Flowroute and now see what you are referring to with prepending the tech prefix. I didn't change anything. I had called Flowroute a few months ago when I first noticed it and they didn't mention it to me but was saying I needed to see what was up on 3CX's end of things and do a packet capture, which wasnt seeing anything either.

 

[biggreyphone]

I am guessing you change this in your outbound rules. Edit outbound rules>select outbound rule name>edit and add prepend. I have not tried this yet.

 

[nicedoggie]

I had done an upgrade from v18 to v20 and this issue didn't occur. But this is a fresh v20 and I don't have enough information that is specific enough to fix this yet. I have a trouble ticket in with Flowroute and will see what they say on Monday.

 

[biggreyphone]

I had done an upgrade from v18 to v20 and this issue didn't occur. But this is a fresh v20 and I don't have enough information that is specific enough to fix this yet. I have a trouble ticket in with Flowroute and will see what they say on Monday.

please follow-up here as I'd like to know what is going on.

 

[biggreyphone]

Looking at my V20 SIP trunk details settings and I have Flowroute set to Register/Account based, not IP based. Not sure if Flowroute requires IP authentication now, ill have to go back and look

 

[biggreyphone]

I found this old thread from mid 2023. It appears that back then IP auth from Flowroute was not supported. I would assume it is now because it is an option from the pull down menu. However I am using register/account based authentication and I am still getting these errors.

https://www.3cx.com/community/threads/cannot-dial-out-via-flowroute.121795/

 

[nicedoggie]

The issue was mainly that I was using ip authentication, not sip registration... duh... I did get ip registration to work by prepending the tech id in the outgoing route.. like 123456*1NPA where 123456 is my tech id (for a 7 digit dialing route). After switching to sip registration, outbound routes were "normal".