[2018-07-09 10:53:35] NOTICE[2820] chan_sip.c: Registration from ‘“125” sip:’ failed for ‘’ - Wrong password
When making an new extension on the asterisk system the extension wont register, tried this on multiple phones.
However an existing extension will register to a new phone.
Using a Cisco IP phone .
Have you checked the log to make sure the correct sip.conf entry is being used for the device? Have you used the CLI commands to inspect configuration? Did you change things and forget to reload?
I hope it is correct to post a message with the same problem.
I have an ISDN gateway, Innovaphone IP800, already used with Asterisk 11 (in Elastix 2), so I am sure it is compatible.
I used the same configuration I had previously used, adapted to the new system, and I get the message :
chan_sip.c: Registration from '<sip:IP800-06-0f-ae@192.168.0.1>' failed for '192.168.0.182:2073' - Wrong password
I checked the password 100 times, and changed it 10 times. I have two other gateways (Linksys and OpenVox) which work. I cannot imagine where is the problem. The log shows what I can see in the cli with -vvv
Configuration is :
host=dynamic
username=Numeris
secret=azert
type=peer
===================
username=Numeris
secret=azert
type=user
context=from-trunk
I have tried with long and short passwords, simple or complicated, with different ports (5060 or others, or automatic), nothing works and I have no idea of the reason.
The gateway and the computer running asterisk is connected to the same switch, we don’t have sub-networks.
Ip addresses :
asterisk : 192.168.0.1
ip800 : 192.168.0.182
Just in case the full transmission is :
<------------->
[2018-08-09 19:30:48] VERBOSE[2437] chan_sip.c: --- (10 headers 0 lines) ---
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c:
<--- SIP read from UDP:192.168.0.182:2073 --->
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.182:2073;branch=z9hG4bK-F71238E0;rport
From: <sip:IP800-06-0f-ae@192.168.0.1>;tag=2613775490
To: <sip:IP800-06-0f-ae@192.168.0.1>
Call-ID: 89437538e909d311ac90009033060fae@192.168.0.182
CSeq: 2877 REGISTER
Contact: <sip:IP800-06-0f-ae@192.168.0.182:2073>;expires=120
Content-Length: 0
Expires: 120
Max-Forwards: 70
User-Agent: (innovaphone IP800/6.00 sr2-hotfix12 [08-60901.12/424/110])
Allow-Events: reg,dialog,message-summary
<------------->
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: --- (12 headers 0 lines) ---
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: Sending to 192.168.0.182:2073 (no NAT)
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: Sending to 192.168.0.182:2073 (no NAT)
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.0.182:2073 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.182:2073;branch=z9hG4bK-F71238E0;received=192.168.0.182;rport=2073
From: <sip:IP800-06-0f-ae@192.168.0.1>;tag=2613775490
To: <sip:IP800-06-0f-ae@192.168.0.1>;tag=as200ec981
Call-ID: 89437538e909d311ac90009033060fae@192.168.0.182
CSeq: 2877 REGISTER
Server: FPBX-2.11.0(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0da15dd7"
Content-Length: 0
<------------>
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: Scheduling destruction of SIP dialog '89437538e909d311ac90009033060fae@192.168.0.182' in 32000 ms (Method: REGISTER)
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c:
<--- SIP read from UDP:192.168.0.182:2073 --->
REGISTER sip:192.168.0.1 SIP/2.0
Authorization: Digest username="Numeris",realm="asterisk",nonce="0da15dd7",response="76b8060a9526ce2bd8ca1c6ef3a763be",uri="sip:192.168.0.1",algorithm=MD5
Via: SIP/2.0/UDP 192.168.0.182:2073;branch=z9hG4bK-F71238E1;rport
From: <sip:IP800-06-0f-ae@192.168.0.1>;tag=2613775491
To: <sip:IP800-06-0f-ae@192.168.0.1>
Call-ID: 89437538e909d311ac90009033060fae@192.168.0.182
CSeq: 2878 REGISTER
Contact: <sip:IP800-06-0f-ae@192.168.0.182:2073>;expires=120
Content-Length: 0
Expires: 120
Max-Forwards: 70
User-Agent: (innovaphone IP800/6.00 sr2-hotfix12 [08-60901.12/424/110])
Allow-Events: reg,dialog,message-summary
<------------->
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: --- (13 headers 0 lines) ---
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c: Sending to 192.168.0.182:2073 (no NAT)
[2018-08-09 19:30:49] VERBOSE[2437] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.0.182:2073 --->
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.0.182:2073;branch=z9hG4bK-F71238E1;received=192.168.0.182;rport=2073
From: <sip:IP800-06-0f-ae@192.168.0.1>;tag=2613775491
To: <sip:IP800-06-0f-ae@192.168.0.1>;tag=as200ec981
Call-ID: 89437538e909d311ac90009033060fae@192.168.0.182
CSeq: 2878 REGISTER
Server: FPBX-2.11.0(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
<------------>
[2018-08-09 19:30:49] NOTICE[2437] chan_sip.c: Registration from '<sip:IP800-06-0f-ae@192.168.0.1>' failed for '192.168.0.182:2073' - Wrong password
Hello, I have exactly the same issue.
I compute by my self the Authorization response to check, and it 's correct.
I tried to change password, port, username, and network configuration (with/without nat)
but I have always the same error; Wrong password …
Have you solved this issue ?
regards
Yes I have (it took a lot of time and tries !). As far as I understand, the problem comes from a bug in the version of Asterisk used in Elastix 4. When the gateway tries to register, asterisk uses the trunk name instead of the username, and the registration fails.
You have two options : either use the same name for the trunk name and the username, or register in the other direction (Asterisk registers to the gateway). Here is my configuration in Elastix :
Trunk name : Numeris 3
Peer details
host=192.168.0.182
username=Numeris3 (should be the same as trunk name)
secret=abc123456
type=peer
nat=yes
User context : ip800-trunk (put what you want here)
User details
secret=abc123456
type=user
context=from-trunk
Thanks a lot.
I put the same number my sip.config
[number]
username=number
and it 's ok.
in fact, I understand taht username it 's only a description but not used for the register
thanks again