› VitalPBX Community Support › General Discussion › extension 401 Unauthorized
- This topic has 1 reply, 1 voice, and was last updated 2 months, 2 weeks ago by
linkat.
- Post
-
- November 7, 2020 at 9:56 am
Hi,i have installed VitalPBX 3.0.3-4 on CentoOS in a VPS cloud.
We tray to config 2 extension with 2 phone:
- Yealink T40P
- Yealink W52P
The PBX is the same, config is the same on the phone and on the extensions.
Yealink W25P register OK
Yealink T40P not register and have 401 Unauthorized
can you help me ?
thanks
0
- Replies
-
- November 7, 2020 at 7:57 pm
this is the log of unregistered phone:[2020-11-07 03:19:31] VERBOSE[1481] chan_sip.c:
<— SIP read from UDP:PUBLICIPPHONE:5060 —>
REGISTER sip:NAMESERVERPBX:5363 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.89:5060;branch=z9hG4bK3363910184
From: “101” <sip:101consaba@NAMESERVERPBX:5363>;tag=400487022
To: “101” <sip:101consaba@NAMESERVERPBX:5363>
Call-ID: 0_533907209@192.168.1.89
CSeq: 1 REGISTER
Contact: <sip:101consaba@192.168.1.89:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T40P 54.84.0.90
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0<————->
[2020-11-07 03:19:31] VERBOSE[1481] chan_sip.c: — (13 headers 0 lines) —
[2020-11-07 03:19:31] VERBOSE[1481] chan_sip.c: Sending to PUBLICIPPHONE:5060 (NAT)
[2020-11-07 03:19:31] VERBOSE[1481] chan_sip.c:
<— Transmitting (NAT) to PUBLICIPPHONE:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.89:5060;branch=z9hG4bK3363910184;received=PUBLICIPPHONE;rport=5060
From: “101” <sip:101consaba@NAMESERVERPBX:5363>;tag=400487022
To: “101” <sip:101consaba@NAMESERVERPBX:5363>;tag=as70c7c964
Call-ID: 0_533907209@192.168.1.89
CSeq: 1 REGISTER
Server: VitalPBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=”asterisk”, nonce=”5c4a8a8a”
Content-Length: 0And then repeat the same REGISTER-UNAUTHORIZED
This is the log of registered phone:
<— SIP read from UDP:PUBLICIPPHONE:1024 —>
REGISTER sip:NAMESERVERPBX:5363 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.90:5060;branch=z9hG4bK3105595912
From: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=1349807409
To: “102” <sip:102cordless@NAMESERVERPBX:5363>
Call-ID: 0_3128709771@192.168.1.90
CSeq: 1 REGISTER
Contact: <sip:102cordless@192.168.1.90:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink W52P 25.81.0.65
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0<————->
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: — (13 headers 0 lines) —
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Sending to PUBLICIPPHONE:1024 (NAT)
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Sending to PUBLICIPPHONE:1024 (NAT)
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c:
<— Transmitting (NAT) to PUBLICIPPHONE:1024 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.90:5060;branch=z9hG4bK3105595912;received=PUBLICIPPHONE;rport=1024
From: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=1349807409
To: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=as4311f1ce
Call-ID: 0_3128709771@192.168.1.90
CSeq: 1 REGISTER
Server: VitalPBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=”asterisk”, nonce=”1a047ac2″
Content-Length: 0<————>
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Scheduling destruction of SIP dialog ‘0_3128709771@192.168.1.90’ in 32000 ms (Method: REGISTER)
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c:
<— SIP read from UDP:PUBLICIPPHONE:1024 —>
REGISTER sip:NAMESERVERPBX:5363 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.90:5060;branch=z9hG4bK4023484519
From: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=1349807409
To: “102” <sip:102cordless@NAMESERVERPBX:5363>
Call-ID: 0_3128709771@192.168.1.90
CSeq: 2 REGISTER
Contact: <sip:102cordless@192.168.1.90:5060>
Authorization: Digest username=”102cordless”, realm=”asterisk”, nonce=”1a047ac2″, uri=”sip:NAMESERVERPBX:5363″, response=”2cdbbd1059bca8bcd1915b0a932493fd”, algorithm$
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink W52P 25.81.0.65
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0<————->
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: — (14 headers 0 lines) —
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Sending to PUBLICIPPHONE:1024 (NAT)
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Registered SIP ‘102cordless’ at PUBLICIPPHONE:1024
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c: Reliably Transmitting (NAT) to PUBLICIPPHONE:1024:
OPTIONS sip:102cordless@192.168.1.90:5060 SIP/2.0
Via: SIP/2.0/UDP 51.210.188.81:5474;branch=z9hG4bK6026ef71;rport
Max-Forwards: 70
From: “asterisk” <sip:asterisk@51.210.188.81:5474>;tag=as79ff9ab9
To: <sip:102cordless@192.168.1.90:5060>
Contact: <sip:asterisk@51.210.188.81:5474>
Call-ID: 228652b97c77cb0b4b0c3cc61f04f61a@51.210.188.81:5474
CSeq: 102 OPTIONS
User-Agent: VitalPBX
Date: Sat, 07 Nov 2020 19:46:53 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0—
[2020-11-07 19:46:53] VERBOSE[1481] chan_sip.c:
<— Transmitting (NAT) to PUBLICIPPHONE:1024 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.90:5060;branch=z9hG4bK4023484519;received=PUBLICIPPHONE;rport=1024
From: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=1349807409
To: “102” <sip:102cordless@NAMESERVERPBX:5363>;tag=as4311f1ce
Call-ID: 0_3128709771@192.168.1.90
CSeq: 2 REGISTER
Server: VitalPBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 3600
Contact: <sip:102cordless@192.168.1.90:5060>;expires=3600
Date: Sat, 07 Nov 2020 19:46:53 GMT
Content-Length: 0Help! 🙂
thanks
0
- You must be logged in to reply to this topic.