401 Unauthorized for inbound calls

FreePBX Providers
1

I’m getting 401 Unauthorized for inbound calls, can someone tell me why?

PJSIP Logging enabled
<— Received SIP request (1043 bytes) from UDP:18.27.187.249:5060 —>
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+d14c6622+33008bb5
To: sip:****1757009@vncluster.******.it
CSeq: 535253210 INVITE
Expires: 180
Content-Length: 195
Call-Info: sip:18.27.187.249:5060;method=“NOTIFY;Event=telephone-event;Duration=2000”
Supported: resource-priority,siprec, 100rel
Contact: sip:[email protected]
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
Organization: MSW
Max-Forwards: 44
Accept: application/sdp, application/dtmf-relay

v=0
o=- 39471695329630 39471695329630 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50180 RTP/AVP 18 8 96
a=rtpmap:96 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<— Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+d14c6622+33008bb5
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
CSeq: 535253210 INVITE
WWW-Authenticate: Digest realm=“asterisk”,nonce=“1680884006/9396c7f61b34ffab233f0a2fb6b73aeb”,opaque=“1eb9b772568cc05f”,algorithm=MD5,qop=“auth”
Server: FPBX-16.0.40(19.8.0)
Content-Length: 0

<— Received SIP request (476 bytes) from UDP:18.27.187.249:5060 —>
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+d14c6622+33008bb5
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
CSeq: 535253210 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
Max-Forwards: 44

<— Received SIP request (1043 bytes) from UDP:18.27.187.249:5060 —>
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: sip:****1757009@vncluster.******.it
CSeq: 949938626 INVITE
Expires: 180
Content-Length: 195
Call-Info: sip:18.27.187.249:5060;method=“NOTIFY;Event=telephone-event;Duration=2000”
Supported: resource-priority,siprec, 100rel
Contact: sip:[email protected]
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBA[email protected]
Organization: MSW
Max-Forwards: 44
Accept: application/sdp, application/dtmf-relay

v=0
o=- 68359645363350 68359645363350 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50182 RTP/AVP 18 8 96
a=rtpmap:96 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<— Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
Call-ID: 0gQAAC8WAAACBA[email protected]
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
CSeq: 949938626 INVITE
WWW-Authenticate: Digest realm=“asterisk”,nonce=“1680884007/ac52791123c80db90b778b4179712446”,opaque=“4e823ad849dac98d”,algorithm=MD5,qop=“auth”
Server: FPBX-16.0.40(19.8.0)
Content-Length: 0

<— Received SIP request (476 bytes) from UDP:18.27.187.249:5060 —>
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
CSeq: 949938626 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBA[email protected]
Max-Forwards: 44

<— Received SIP request (1047 bytes) from UDP:18.27.187.249:5060 —>
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+18c165f3+8ce413f8
To: sip:****1757009@vncluster.******.it
CSeq: 155897261 INVITE
Expires: 180
Content-Length: 199
Call-Info: sip:18.27.187.249:5060;method=“NOTIFY;Event=telephone-event;Duration=2000”
Supported: resource-priority,siprec, 100rel
Contact: sip:[email protected]
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
Organization: MSW
Max-Forwards: 54
Accept: application/sdp, application/dtmf-relay

v=0
o=- 118022352207549 118022352207549 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50184 RTP/AVP 18 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<— Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+18c165f3+8ce413f8
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
CSeq: 155897261 INVITE
WWW-Authenticate: Digest realm=“asterisk”,nonce=“1680884007/ac52791123c80db90b778b4179712446”,opaque=“135b3e6734db18da”,algorithm=MD5,qop=“auth”
Server: FPBX-16.0.40(19.8.0)
Content-Length: 0

<— Received SIP request (476 bytes) from UDP:18.27.187.249:5060 —>
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
From: sip:****1915169@vncluster.******.it;tag=18.27.187.249+1+18c165f3+8ce413f8
To: sip:****1757009@vncluster.******.it;tag=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
CSeq: 155897261 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
Max-Forwards: 54

<— Transmitting SIP request (548 bytes) to UDP:18.27.187.249:5060 —>
OPTIONS sip:vnpublic.******.it SIP/2.0
Via: SIP/2.0/UDP 158.5.114.56:5060;rport;branch=z9hG4bKPj075d10a1-f71f-43bb-97b7-3ee3f03cf4f6
From: sip:39****1757009@vncluster.******.it;tag=63e69b54-7edc-411e-bf5c-10bd926ec51e
To: sip:39****1757009@vncluster.******.it
Contact: sip:39****[email protected]:5060
Call-ID: d695cbe4-9be4-4903-b0fe-397c166ea1a9
CSeq: 3947 OPTIONS
Route: sip:vnpublic.******.it
Route: sip:39****1757009@vncluster.:5060******.it
Max-Forwards: 70
User-Agent: FPBX-16.0.40(19.8.0)
Content-Length: 0

<— Received SIP response (1024 bytes) from UDP:18.27.187.249:5060 —>
SIP/2.0 200 OK
Call-ID: d695cbe4-9be4-4903-b0fe-397c166ea1a9
CSeq: 3947 OPTIONS
From: sip:39****1757009@vncluster.******.it;tag=63e69b54-7edc-411e-bf5c-10bd926ec51e
To: sip:39****1757009@vncluster.******.it;tag=sip+1+73dd01e6+8c4c14c9
Via: SIP/2.0/UDP 158.5.114.56:5060;received=158.5.114.56;rport=5060;branch=z9hG4bKPj075d10a1-f71f-43bb-97b7-3ee3f03cf4f6
Content-Length: 0
Supported: resource-priority,siprec, 100rel
Server: DC-SIP/2.0
Organization: MSW
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,OPTIONS,PRACK,UPDATE,SUBSCRIBE,NOTIFY,REFER,INFO,PUBLISH
Accept-Encoding: identity
Accept: application/sdp,application/simple-message-summary,message/sipfrag,application/isup,multipart/mixed,application/hook-flash,application/vq-rtcpxr,application/media_control+xml,text/plain,application/x-as-feature-event+xml,application/calling-name-info,application/vnd.etsi.sci+xml, application/dtmf-relay

2

Because you have set authorisation to inbound or both, in which case it is not an error, or because the INVITE cannot be matched up with any known endpoint. In the second case, your endpoint either isn’t called ****1915169 or its SIP Server or Match/Permit settings don’t cover 18.27.187.249.

In the first case, additonally, the provider doesn’t know how to authenticate to you (generally true), which is why it loops on 401, rather than proceeding to a successful authentication.

PJSIP Logging enabled
<--- Received SIP request (1043 bytes) from UDP:18.27.187.249:5060 --->
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+d14c6622+33008bb5
To: <sip:****1757009@vncluster.******.it>
CSeq: 535253210 INVITE
Expires: 180
Content-Length: 195
Call-Info: <sip:18.27.187.249:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: resource-priority,siprec, 100rel
Contact: <sip:[email protected]>
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
Organization: MSW
Max-Forwards: 44
Accept: application/sdp, application/dtmf-relay

v=0
o=- 39471695329630 39471695329630 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50180 RTP/AVP 18 8 96
a=rtpmap:96 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<--- Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+d14c6622+33008bb5
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
CSeq: 535253210 INVITE
WWW-Authenticate: Digest realm="asterisk",nonce="1680884006/9396c7f61b34ffab233f0a2fb6b73aeb",opaque="1eb9b772568cc05f",algorithm=MD5,qop="auth"
Server: FPBX-16.0.40(19.8.0)
Content-Length:  0


<--- Received SIP request (476 bytes) from UDP:18.27.187.249:5060 --->
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+d14c6622+33008bb5
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+779f59a678cb42aeb71639316e9941aa1+sip+1+c53d3bd3
CSeq: 535253210 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBAAALxYAAKN04ivRrjLHCzvV/[email protected]
Max-Forwards: 44


<--- Received SIP request (1043 bytes) from UDP:18.27.187.249:5060 --->
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: <sip:****1757009@vncluster.******.it>
CSeq: 949938626 INVITE
Expires: 180
Content-Length: 195
Call-Info: <sip:18.27.187.249:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: resource-priority,siprec, 100rel
Contact: <sip:[email protected]>
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBAAALxYAAOnpBknVZtkxMp4bfWc8VQM15G1f3fhnLukkmeWnHHAD@18.27.187.249
Organization: MSW
Max-Forwards: 44
Accept: application/sdp, application/dtmf-relay

v=0
o=- 68359645363350 68359645363350 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50182 RTP/AVP 18 8 96
a=rtpmap:96 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<--- Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
Call-ID: 0gQAAC8WAAACBAAALxYAAOnpBknVZtkxMp4bfWc8VQM15G1f3fhnLukkmeWnHHAD@18.27.187.249
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
CSeq: 949938626 INVITE
WWW-Authenticate: Digest realm="asterisk",nonce="1680884007/ac52791123c80db90b778b4179712446",opaque="4e823ad849dac98d",algorithm=MD5,qop="auth"
Server: FPBX-16.0.40(19.8.0)
Content-Length:  0


<--- Received SIP request (476 bytes) from UDP:18.27.187.249:5060 --->
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+1d120e3a+34b4e7ec
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+cfe6ab35feefe12a7ff927b6352905d11+sip+1+c53d3c7f
CSeq: 949938626 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBAAALxYAAOnpBknVZtkxMp4bfWc8VQM15G1f3fhnLukkmeWnHHAD@18.27.187.249
Max-Forwards: 44


<--- Received SIP request (1047 bytes) from UDP:18.27.187.249:5060 --->
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+18c165f3+8ce413f8
To: <sip:****1757009@vncluster.******.it>
CSeq: 155897261 INVITE
Expires: 180
Content-Length: 199
Call-Info: <sip:18.27.187.249:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: resource-priority,siprec, 100rel
Contact: <sip:[email protected]>
Content-Type: application/sdp
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
Organization: MSW
Max-Forwards: 54
Accept: application/sdp, application/dtmf-relay

v=0
o=- 118022352207549 118022352207549 IN IP4 18.27.187.249
s=-
c=IN IP4 18.27.187.249
t=0 0
m=audio 50184 RTP/AVP 18 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=ptime:20

<--- Transmitting SIP response (661 bytes) to UDP:18.27.187.249:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 18.27.187.249:5060;rport=5060;received=18.27.187.249;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+18c165f3+8ce413f8
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
CSeq: 155897261 INVITE
WWW-Authenticate: Digest realm="asterisk",nonce="1680884007/ac52791123c80db90b778b4179712446",opaque="135b3e6734db18da",algorithm=MD5,qop="auth"
Server: FPBX-16.0.40(19.8.0)
Content-Length:  0


<--- Received SIP request (476 bytes) from UDP:18.27.187.249:5060 --->
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.27.187.249:5060;branch=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
From: <sip:****1915169@vncluster.******.it>;tag=18.27.187.249+1+18c165f3+8ce413f8
To: <sip:****1757009@vncluster.******.it>;tag=z9hG4bK+9d1d97507f300c9a51a26353eae69b641+sip+1+c53d3ce2
CSeq: 155897261 ACK
Content-Length: 0
Call-ID: 0gQAAC8WAAACBAAALxYAAEjW1q37GnJQ4Ryr7KfLeSE6Hl4PtbcP/[email protected]
Max-Forwards: 54

<--- Transmitting SIP request (548 bytes) to UDP:18.27.187.249:5060 --->
OPTIONS sip:vnpublic.******.it SIP/2.0
Via: SIP/2.0/UDP 158.5.114.56:5060;rport;branch=z9hG4bKPj075d10a1-f71f-43bb-97b7-3ee3f03cf4f6
From: <sip:39****1757009@vncluster.******.it>;tag=63e69b54-7edc-411e-bf5c-10bd926ec51e
To: <sip:39****1757009@vncluster.******.it>
Contact: <sip:39****[email protected]:5060>
Call-ID: d695cbe4-9be4-4903-b0fe-397c166ea1a9
CSeq: 3947 OPTIONS
Route: <sip:vnpublic.******.it>
Route: <sip:39****1757009@vncluster.******.it:5060>
Max-Forwards: 70
User-Agent: FPBX-16.0.40(19.8.0)
Content-Length:  0


<--- Received SIP response (1024 bytes) from UDP:18.27.187.249:5060 --->
SIP/2.0 200 OK
Call-ID: d695cbe4-9be4-4903-b0fe-397c166ea1a9
CSeq: 3947 OPTIONS
From: <sip:39****1757009@vncluster.******.it>;tag=63e69b54-7edc-411e-bf5c-10bd926ec51e
To: <sip:39****1757009@vncluster.******.it>;tag=sip+1+73dd01e6+8c4c14c9
Via: SIP/2.0/UDP 158.5.114.56:5060;received=158.5.114.56;rport=5060;branch=z9hG4bKPj075d10a1-f71f-43bb-97b7-3ee3f03cf4f6
Content-Length: 0
Supported: resource-priority,siprec, 100rel
Server: DC-SIP/2.0
Organization: MSW
Allow-Events: message-summary,refer,dialog,line-seize,presence,call-info,as-feature-event,calling-name,ua-profile
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,OPTIONS,PRACK,UPDATE,SUBSCRIBE,NOTIFY,REFER,INFO,PUBLISH
Accept-Encoding: identity
Accept: application/sdp,application/simple-message-summary,message/sipfrag,application/isup,multipart/mixed,application/hook-flash,application/vq-rtcpxr,application/media_control+xml,text/plain,application/x-as-feature-event+xml,application/calling-name-info,application/vnd.etsi.sci+xml, application/dtmf-relay

-------------------------
3

outbound authentication, but I have a server that resolves to nothing and a proxy, should I set both server and proxy in Match?

4

You need a match /permit for 18.27.187.249. I don’t know if that is your proxy or not. If it is, you will only be able to access one endpoint through it, and it isn’t just an outbound proxy. If it is not, this might be part of a range of addresses, and you should find the complete range, from your provider.

18.0.0.0/11 comes back to MIT, and the Via lines indicate there is no proxy involved.

The address does not reverse resolve. That’s not a good sign. Are you sure this call is legitimate? Obviously you should not set match/permit lines for toll fraudsters. On the other hand, a fraudster would likely try a full, probably international, phone number.

1 Like
5

It was it, thank you.
IPs are scrambled for security.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.