Cant make inbound calls and getting 401 errors

Status
Not open for further replies.

ringtexas

New Member
Aug 25, 2021
8
0
1
53
I am using FusionPBX on Debian. I am able to make outbound calls, but no inbound Also I am getting 401 errors. I am using MicroSIP as my softphone and it says it is online, but when I use sngrep I get these errors.

2021/08/29 19:04:59.322613 97.99.81.32:64482 -> 68.183.26.144:5060
REGISTER sip:pbx.ringtexas.com SIP/2.0
Via: SIP/2.0/UDP 10.1.1.28:64482;rport;branch=z9hG4bKPj1a6afc3f42db4cd0995e254030a39561
Max-Forwards: 70
From: "Operator" <sip:1001@pbx.ringtexas.com>;tag=29e1a5690d7443acb992919dbef7944d
To: "Operator" <sip:1001@pbx.ringtexas.com>
Call-ID: cae982f31cd74c6ea6794ad91a9b7b9c
CSeq: 35393 REGISTER
User-Agent: MicroSIP/3.20.6
Contact: "Operator" <sip:1001@10.1.1.28:64482;ob>
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0

2021/08/29 19:04:59.323529 68.183.26.144:5060 -> 97.99.81.32:64482
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.1.1.28:64482;rport=64482;branch=z9hG4bKPj1a6afc3f42db4cd0995e254030a39561;received=97.99.81.32
From: "Operator" <sip:1001@pbx.ringtexas.com>;tag=29e1a5690d7443acb992919dbef7944d
To: "Operator" <sip:1001@pbx.ringtexas.com>;tag=S7BrHt8mDgcej
Call-ID: cae982f31cd74c6ea6794ad91a9b7b9c
CSeq: 35393 REGISTER
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
WWW-Authenticate: Digest realm="pbx.ringtexas.com", nonce="7b217901-890f-473b-8c68-a555ac3fd631", algorithm=MD5, qop="auth"
Content-Length: 0

Any suggestions.....no fail2ban issues either. I did update the ACLs to add my SIP provider with CIDR /32.

One more note when I do make inbound calls I get the following 407 error. I definitely don't know what I am doing. :-(

2021/08/29 19:10:32.300229 63.247.69.226:5060 -> 68.183.26.144:5080
INVITE sip:14693108844@68.183.26.144:5080;transport=udp;gw=10d597e4-ad0c-48f1-b364-9df5dd66200a SIP/2.0
Record-Route: <sip:63.247.69.226;lr=on;ftag=gK0e5a698b;vsf=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADtpc3VwLW9saT02Mjtwc3RuLXBhcmFtcz04MDg
DE4MDg4ODI7Y3BjPW9yZGluYXJ5;dlgcor=3b11.4ee2>
Via: SIP/2.0/UDP 63.247.69.226;branch=z9hG4bK906d.dcfadc88011cf4aa6392a88cd03b2bba.0
Via: SIP/2.0/UDP 206.147.72.21:5060;branch=z9hG4bK0eB56033232f9ad9825
From: "JOHN DOE " <sip:9724153500@206.147.72.21>;tag=gK0e5a698b
To: <sip:4693108844@63.247.69.226>
Call-ID: 487478538_48049013@206.147.72.21
CSeq: 978771 INVITE
Max-Forwards: 24
Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE,NOTIFY,PRACK,UPDATE,OPTIONS,MESSAGE,PUBLISH
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: <sip:9724153500@206.147.72.21:5060>
Supported: timer,100rel,precondition
Session-Expires: 1800
Min-SE: 90
Content-Length: 284
Content-Disposition: session; handling=required
Content-Type: application/sdp
Privacy: off

v=0
o=Sonus_UAC 260176 381508 IN IP4 206.147.72.21
s=SIP Media Capabilities
c=IN IP4 206.147.72.24
t=0 0
m=audio 63178 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20

Thoughts?
 
401 response is an auth challenge, your client will need to respond to it, 407 is also proxy auth reated. try using zoiper as a client and see whether you can progress.
 
  • Like
Reactions: ringtexas
401 response is an auth challenge, your client will need to respond to it, 407 is also proxy auth reated. try using zoiper as a client and see whether you can progress.
Thanks...will try zoiper....i was just in the middle of searching better softphone options. -Thanks.
 
For inbound calls. You will need to add your carriers IP to the ACL. Search on here , there are loads of examples
 
DigitalDaz......let me first say I am very impressed with your responses on this board. I know it is not easy given some of the ask for help. That said, I appreciate the feedback and suggestion to my issue. It turned out I missed a prefix on my inbound call. Last thing to fix is my caller ID as it is using my Trunk ID. Thank you.
 
Yeah....i tried that....but for whatever reason it breaks or kills my outbound calls......probably something else but I will figure it out.
 
Yeah....i tried that....but for whatever reason it breaks or kills my outbound calls......probably something else but I will figure it out.
tried both pid and rpid....did not break the outbound on either, but did not fix the caller id. Weird.
 
Status
Not open for further replies.