Solved Voiceflex Outgoing calls issue

Status
Not open for further replies.

OITMGR_Andy

Free User
Joined
Oct 26, 2021
Messages
7
Reaction score
2
Hello

I've recently signed up for the Free trial of the fully hosted 3CX system as my company are looking to move away from our current provider. We have SIP lines with Voiceflex which have been added to 3CX per the 3CX documentation on this and we can receive calls with no issues.

However we cannot make any outgoing calls at all. I've been in contact with Voiceflex who mentioned there's an issue with authentication between them and 3CX and they increased the timeout value accordingly to compensate but we're still unable to make calls. Voiceflex has said they cannot see any connection attempts for the outbound calls at their side.

I've created outbound rule as follows:

Calls to Numbers with length of: 10-13
Calls from Extension Group: Default
Make calls on: Route 1 - Voiceflex - Strip Digits: 0, Prepend: Blank, Outbound Caller ID: our primary Voiceflex number.

In the activity log we get:

27/10/2021 09:02:15 - [CM503003]: Call(C:20): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 93.95.124.50:5060

and

26/10/2021 16:22:00 - [Flow] Target endpoint for 0113xxxxxxx can not be built!

Does anyone have any suggestions as to what may be causing this, what we need to look at, etc?

Thanks for any help in advance,

Andy
 
Voiceflex has said they cannot see any connection attempts for the outbound calls at their side.
I have to say this is weird as the message below actually suggest they are and that they are actually replying:
27/10/2021 09:02:15 - [CM503003]: Call(C:20): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 93.95.124.50:5060
That said, I think this is not related to authentication issue you mentioned.

Also, regarding this message:
26/10/2021 16:22:00 - [Flow] Target endpoint for 0113xxxxxxx can not be built!
Bear in mind that this message denotes that the call did not match an Outbound Rule, however since this was on the 26th, I'm going to assume you made changes since then and now only receive the "404 Not found" Error . Please correct me if I'm wrong.


Now, based on what you are receiving from the provider, it would seem that something you are sending is not being accepted. What is the number you are dialing, is it a US number perhaps? Could you try dialing a UK number in this format: 0044##########

If that fails with the same error, please consider going over our guide and making sure that you've not missed anything: https://www.3cx.com/docs/uk-sip-trunk-voiceflex/
 
Hi Chris

I was dialing UK numbers (we're a UK based company). Have tried in international format but we're still getting the same issue. I've passed the info onto Voiceflex as well.

27/10/2021 10:12:05 - [CM503003]: Call(C:25): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 93.95.124.50:5060

27/10/2021 10:12:35 - Call to T:Line:10000>>0113xxxxxxx@[Dev:sip:[email protected]:5060] from L:27.1[Extn:301] failed, cause: Cause: 404 Not Found/INVITE from 93.95.124.50:5060

I've gone through the documentation in your link again but everything matches up with the setup.
 
Note that when you set up a SIP with Voiceflex you need to tell VF support to allow outbound calls as they're blocked by default.
 
  • Like
Reactions: Saqqara
Ok, so Voiceflex made another change to our SIP lines following the above information and we can now make outbound calls. Not sure what they did (no info given at their side).

Weird they block outbound by default but they were aware we wanted outbound a number of times so I'd hope they'd unblocked it long before we started going through all this.

Ah well, working now, I can continue to set it all up. Thanks guys.
 
  • Like
Reactions: ChrisC_3CX
Ok, so Voiceflex made another change to our SIP lines following the above information and we can now make outbound calls. Not sure what they did (no info given at their side).

Weird they block outbound by default but they were aware we wanted outbound a number of times so I'd hope they'd unblocked it long before we started going through all this.

Ah well, working now, I can continue to set it all up. Thanks guys.
They'd have allowed outbound calls. Yes, it is strange but we all learn this is needed the hard way :D
 
Ah well, working now, I can continue to set it all up. Thanks guys.
Glad to see this got sorted!

I'll be marking this thread as resolved for now so please feel free to post anew should anything else come up!
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,324
Messages
591,897
Members
165,476
Latest member
awan05