Solved Problem With Outbound Calls With Anveo Direct

[HelloPBX]

I setup 3cx using the "Self-host in your Cloud" option with Digital Ocean.

I also created an Anveo Direct Outbound Trunk and added the Digital Ocean ip address to the "Authorized IP Addresses" for the trunk.

And I added a 3CX Trunk following the tips here: https://www.3cx.com/community/threads/does-3cx-work-with-anveo-direct.74061/post-332922
To summarize: Hostname: sbc.anveo.com, Auto Discovery, Supports Re-Invite.

But then when I try to make a call in the Chrome Desktop App on Mac, I enter the Number +1xxxxxxxxxx, press the green button to make the call and the dial pad disappears and no call is made.

On the 3CX call log I see the call attempt appear with the "Talking" column value of "Not Answered"

On the Anveo Direct side, I'm not seeing anything in the call logs.

What am I missing here?

Thanks in advance for your help!

 

[leejor]

Do you have any other devices, to try making outside calls on? Are you able to dial another extension successfully?

 

[YiannisH_3CX]

Did you add an outbound rule to allow the call to be sent out?

 

[HelloPBX]

Do you have any other devices, to try making outside calls on? Are you able to dial another extension successfully?

I don't have any other devices or extensions setup.

 

[HelloPBX]

Did you add an outbound rule to allow the call to be sent out?

Yes

 

[YiannisH_3CX]

Check your Activity log and look for any errors that could indicate what the issue is. You will need to increase the logging level to verbose to get the maximum details.

 

[HelloPBX]

I added a 2nd sip trunk from a different voip provider. The 2nd trunk uses "Register/Account based" Authentication and I see values in the "Register Sent and Register OK" columns and the calls work when I used the 2nd trunk. So it must be an authentication issue with Anveo Direct because when I just switch the call routing between the two trunks it doesn't work with Anveo Direct but it does work with the 2nd carrier.

 

[HelloPBX]

Check your Activity log and look for any errors that could indicate what the issue is. You will need to increase the logging level to verbose to get the maximum details.

I'm seeing this error in the logs `[Extn:100] failed, cause: Cause: 503 destination is invalid/INVITE from ip_address_redacted`

 

[YiannisH_3CX]

If the redacted IP is the IP of your provider then you should speak with them and ask why the call is rejected.

 

[HelloPBX]

If the redacted IP is the IP of your provider then you should speak with them and ask why the call is rejected.

Yes it is the ip address of the provider. Do you think I need to edit the 3cx firewall to allow that ip address to make it through? Or is the problem on the provider's side?

 

[YiannisH_3CX]

It looks like the request is reaching the provider so is the error that is sent back. So I am guessing the error is due to something else but your provider should be able to easily answer why you are receiving this error and if you need to change something on your side. It might be a number format or an outbound parameter or something entirely different.

 

[leejor]

Cause: 503 destination is invalid

Suggests you may be sending the number in an incorrect format.

 

[HelloPBX]

Suggests you may be sending the number in an incorrect format.

Yes thanks you are correct. I didn't have any special rules setup to format the number so I have to make sure I was entering it exactly like 1xxxxxxxxxx.

But what also complicated things is that I was seeing errors like `503 Transport failure: no transports left to try/INVITE from local` and `503 Service Unavailable/INVITE from ip_address_redacted`.

I think the 'transport failure' error is caused because I am only using 1 carrier for testing purposes and sometimes that carrier doesn't want to deliver the call so anveo is telling me there aren't any more carriers to try because I only selected 1 carrier.

And I think the 'service unavailable` error is because the 1 carrier I selected to use with the trunk isn't routing the call properly internally.

Does my assessment of those two different 503 errors sound correct?

 

[leejor]

If the call makes it to your provider, you will see a response from their IP address in the Activity log (Verbose). Providers will reject a call for a number of reasons...incorrect format of the dialed number, unacceptable caller ID, no credit on your account, trunks setting issue, etc. Sometimes the rejection message is more explicit. Otherwise, assume that something in 3CX prevents the call from making it to a trunk, be that an outbound rule not matching, or some other reason.

 

[YiannisH_3CX]

Is it safe to assume that the issue has been resolved? Can we set the thread to resolved?

 

[HelloPBX]

Is it safe to assume that the issue has been resolved? Can we set the thread to resolved?

Yes thanks!