Solved Flowroute : 407 Proxy Authentication/E164 format

[SFRAZ1]

Hello, Everyone I have a small problem, My client was using a 3cx with the management console and everything was fine as we used *480XXXXXX instead of +1480XXXXXXX in the DID section of the trunk.
now we are using an SMB for the client and in SMB we don't have the option to add * we have to use +1 in the field.

I called Flowroute and using a test environment we found out that if we use +1 in the 3cX with the management console it gives the error 407 Proxy auth error and the call never gets a tone.

 

[TheodorosG_3CX]

We did not had any other report so it might be related with the Flowroute account.

 

[SFRAZ1]

Ok makesense

 

[TheodorosG_3CX]

Let me know once you receive any feedback

 

[SnakeRiverWebDevelopment]

View attachment 37827
when i tried calling out it gave me this error.

That says it all, the +1 is US and Candia are you calling somewhere else? Are your DID's from outside US or Candia? I use Flowroute and as you see +1, and never have a issue

 

[SFRAZ1]

Let me know once you receive any feedback

We have found the call from yesterday and we are receiving a 480 Temporarily Unavailable back from your 3CX system which is causing the calls to fail. We recommend looking at the 3CX to see why it is giving back a 480.

This is the email from flowroute.

 

[SFRAZ1]

That says it all, the +1 is US and Candia are you calling somewhere else? Are your DID's from outside US or Candia? I use Flowroute and as you see +1, and never have a issue
View attachment 37835

No i am in US and call from and to a number in US (Tmobile number) for testing.

 

[Charles_3CX]

I suggest opening a ticket through your 3CX portal with us at 3CX technical support to request the data we require to check what may be happening.

 

[SFRAZ1]

I suggest opening a ticket through your 3CX portal with us at 3CX technical support to request the data we require to check what may be happening.

Okay opening a ticket.

 

[Charles_3CX]

Please ensure that the ticket is opened with the subscription for the SMB system in question.

 

[SFRAZ1]

Please ensure that the ticket is opened with the subscription for the SMB system in question.

Its the same across all 3cx licenses i have. The one I opened ticket with is set up with sip thats not working.

 

[Charles_3CX]

The ticket you opened was not for the SMB system that you are referring to. In any case, please see the guide related to the requirements for the format of the numbers: https://www.3cx.com/docs/sip-trunk/flowroute-usa/

 

[SFRAZ1]

The ticket you opened was not for the SMB system that you are referring to. In any case, please see the guide related to the requirements for the format of the numbers: https://www.3cx.com/docs/sip-trunk/flowroute-usa/

Please forget i ever mentioned a smb. Just fix the issue on the 3cx i opened the ticket with. I have looked at this document 100s of time it does not work when i use E164 format only works if i use it in this format *413*********

 

[Charles_3CX]

I have found the one SMB registered under your account and can not see a flowroute trunk under the system belonging to the subscription owner's details.

 

[SFRAZ1]

Please forget smb. The 3cx I opened the ticket with needs to be fixed. Thank you.

 

[Charles_3CX]

In this case, re-open a new ticket as the ticket you opened was closed and credited back to you as it was not opened with the subscription belonging to the SMB as all the communication thus far mentioned, and in the future, kindly post issues under the relevant sections of the forum to disperse any confusion.

 

[SFRAZ1]

If i have to reopen a ticket anyway. To not cause any confusion. I will register the sip in the smb account. And then open a ticket. That should clear things up.

 

[Charles_3CX]

Please open the ticket for the system you want assistance with. If it is for the SMB, then use the subscription for the SMB. For the other system, use that subscription key to open the ticket.

 

[SFRAZ1]

Please open the ticket for the system you want assistance with. If it is for the SMB, then use the subscription for the SMB. For the other system, use that subscription key to open the ticket.

new ticket has been opened.

 

[Charles_3CX]

I believe that you responded to close the ticket, as it is now working.

 

[SFRAZ1]

so I just created the new Sip with smb and set everything so I can create a ticket using that account and it worked. i am not sure what happened but i am testing it more. its still not working with 3cx with the management console but i thing it has to do with how the trunk gets created we have to create the trunk with E164 for this to work. sorry for bothering you so much. one last question regarding smb is do we always have to press 1 anyway to add an outbound rule that will add one to each call?