Flowroute DIDs Proxy Authentication Required Error

Status
Not open for further replies.

DrSAHenry

Trainee Partner
Intermediate Cert.
Joined
Dec 13, 2022
Messages
1
Reaction score
0
Alright, so I have been working on this issue for the past 42 hours, and have kind of hit a roadblock, 3CX tells me this is a provider issue and Flowroute (the provider) is telling me this is a hardware issue. I have been going through the 3CX and Flowroute forums, Blogs, and Knowledgebases, and have found literally hundreds of posts that I have tried implementing the changes and non of them seem to do anything. The issue is I have 14 DID's with Flowroute,
my main DID is 0877, and the secondary DID's (used for Ad tracking) that redirect to the main number 0903 and 2199, as well as a toll free number 3104. I also have 10 Additional DID's for the various extensions ranging from 0020 - 0029.

The issue is the 0877 Number connects fine to the phone system (thankfully), all of the additional numbers do not, they return a proxy authentication required, I have already spoken with 3CX, who told me to add the + onto the front of the number (DID NOT WORK), spoke to flowroute that told me to only use a 1 at the front of a number as they only support 11 Digit redirection (DID NOT WORK), I have even found several posts speaking about adding the * instead of the + at the beginning of the number (DID NOT WORK). The authentication is setup as Register/Account Based, with my SIP User ID and Password, I have already changed my Transport protocol (per 3CX and Flowroutes recommendations) to UDP, I have enabled Supports Re-Invite and Supports Replaces (Per 3CX Recommendation). I have disabled Call Source Identification (Per Flowroute Tech Support) and changed all of the Caller Number/Name Field Mappings to "Leave Default Value" (Per Flowroute Tech).

Now I have run a Capture, and this is what I see:

Code:
INVITE sip:*******@*******:5060 SIP/2.0
call-id: *******@*******
contact: <sip:+*******@*******5:5060>
content-length: 228
content-type: application/sdp
cseq: 111663 INVITE
from: "[V]SCOTT HENRY" <sip:+*******@fl.gg>;tag=gK0c6348b4
max-forwards: 66
min-se: 90
p-asserted-identity: "[V]SCOTT HENRY" <sip:+*******;[email protected]>
p-attestation-indicator: A
record-route: <sip:*******;lr>
session-expires: 21600
supported: timer
to: <sip:+*******@fl.gg>
via: SIP/2.0/UDP *******:5060;branch=z9hG4bKcfdb.46dcbde50a5ef045738cf85f05f3786b.0

v=0
o=- 975205 542535 IN IP4 *******
s=-
c=IN IP4 *******
t=0 0
m=audio 20462 RTP/AVP 0 8 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20

INVITE SIP/2.0
call-id: *******@*******
content-length: 0
cseq: 111663 INVITE
from: "[V]SCOTT HENRY" <sip:+*******@fl.gg>;tag=gK0c6348b4
proxy-authenticate: Digest nonce="414d53596398b7f162:31f776428fd8447b4e7691c989e4e2f1",algorithm=MD5,realm="3CXPhoneSystem"
to: <sip:+*******@fl.gg>;tag=5a6acd5a
via: SIP/2.0/UDP *******:5060;branch=z9hG4bKcfdb.46dcbde50a5ef045738cf85f05f3786b.0

ACK sip:*******@*******:5060 SIP/2.0
call-id: *******@*******
content-length: 0
cseq: 111663 ACK
from: "[V]SCOTT HENRY" <sip:+*******@fl.gg>;tag=gK0c6348b4
max-forwards: 66
to: <sip:+*******@fl.gg>;tag=5a6acd5a
via: SIP/2.0/UDP *******:5060;branch=z9hG4bKcfdb.46dcbde50a5ef045738cf85f05f3786b.0


So the kicker is that I have SMS on the Flowroute account as well, and that is working with 3CX, so I know that it is delivering to the server, but the server is kicking back the Proxy Authentication required, only on incoming phone calls.

I have even gone a step further and changed on of the secondary DID's to the Main Trunk number and voila, magically that number works and nothing else. Flowroute is adamant that this is a 3CX issue and 3CX seems to be saying the same thing. Some help would be greatly appreciated.
 
As per the ticket opened with support, please ensure that the sip trunk settings are as per the default template, with no modifications, particularly to the Source identification section.
 
As per the ticket opened with support, please ensure that the sip trunk settings are as per the default template, with no modifications, particularly to the Source identification section.
Did this resolve the issue for the reporting user?
 
Did this resolve the issue for the reporting user?
Once we have any information regarding this, we will update the customer. Do you have a similar issue to report?
 
I had this same issue on 3cx systems when using flowroute as a provider. I usually can resolve this by going into the 3cx and enable call source identification, save , then disable it again and save. Works every time.
 
I would suggest leaving the settings as per default template, with SID enabled and ensure the the DiDs are entered in trunk settings using the correct E164 format.

If I doubt what these settings should be then delete the trunk and create a new one.
 
I also had this issue. Here are the setting changes that worked for me.
Screen Shot 2023-02-02 at 6.33.49 PM.pngScreen Shot 2023-02-02 at 6.33.35 PM.png
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet