Can someone help explain what this means [manager.c:2461 authenticate: Seems to have passed...]

knotbeerdan · July 24, 2012, 6:59am

I have set up a FreePBX system version 1.1005.210.62-1 and when I enter the asterisk CLI I see this error every few seconds. It doesnt seem to have to had any effect on the system but I would like to find the problem and resolve these errors.


[2012-07-23 23:50:23] NOTICE[18820]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:26] NOTICE[18823]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:28] NOTICE[18831]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:32] NOTICE[18839]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:33] NOTICE[18842]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:35] NOTICE[18850]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:40] NOTICE[18858]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:43] NOTICE[18866]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:48] NOTICE[18874]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:51] NOTICE[18882]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:54] NOTICE[18890]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:55] NOTICE[18893]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:50:58] NOTICE[18901]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:03] NOTICE[18909]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:04] NOTICE[18917]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:05] NOTICE[18920]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:10] NOTICE[18928]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:13] NOTICE[18936]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:17] NOTICE[18944]: manager.c:2461 authenticate: Seems to have passed...
[2012-07-23 23:51:20] NOTICE[18952]: manager.c:2461 authenticate: Seems to have passed...

alan · July 24, 2012, 11:37am

I think it is just a notice that tells you something connected to the AMI. I think it is harmless.

dicko · July 24, 2012, 12:26pm

hehe you seem to have missed posting the good bit . . .

Seems to have passed . . .

what? wind? maybe the missing bit would be helpful?

knotbeerdan · July 24, 2012, 10:20pm

That is all that it shows in the asterisk CLI
[2012-07-23 23:51:04] NOTICE[18917]: manager.c:2461 authenticate: Seems to have passed…

obelisk · July 24, 2012, 11:16pm

What is the asterisk version ? I do not see that message in anything since 1.6.2

Make sure the manager port is not exposed to the outside world. You should be able to put

bindaddr = 127.0.0.1

in the general section of manager.conf plus block tcp port 5038 at the firewall.

alan · July 25, 2012, 12:52am

I think based on the FreePBX distro he said he installed it is Asterisk 10. It is possible that in Asterisk 10 some of the log messages are different then previous versions.

knotbeerdan · July 25, 2012, 2:21am

Alan,

Yes it is version 10

Obelisk,

I changed the bind address from 0.0.0.0 to 127.0.0.1 and I still see the messages.

Unfortunately the client did not want a pfsense router (my preferred router for home / small business) and there is a netgear router in place at the office. My client finally put money in the account for the trunk provider so I have now been able to test outbound calls, and they work flawlessly, as does inbound. I do not think this message is anything severe but wanted to make ure that the system wasnt being compromised, and also wanted to see if anyone else has come across these messages.

knotbeerdan · July 25, 2012, 3:14am

When I turned on SIP debug for a few minutes this was the result. I have my softphone connected externally (temporary for testing), and one CISCO 7940 / 7960 registered internally.


<--- SIP read from UDP:myexternalIP::52192 ---
SUBSCRIBE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-b12c653c871c8a3b-1---d8754z-;rport
Max-Forwards: 70
Contact: 
To: ;tag=as7efd9a4b
From: ;tag=0f524c4b
Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.
CSeq: 25 SUBSCRIBE
Expires: 0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Supported: timer
User-Agent: X-Lite 4 release 4.1 stamp 63215
Authorization: Digest username="6666",realm="asterisk",nonce="1a8c25d5",uri="sip:[email protected]:5060",response="af50cb8e82b4121cd59a41a196c880c0",algorithm=MD5
Event: message-summary
Content-Length: 0
<------------->

— (15 headers 0 lines) —

Found peer ‘6666’ for ‘6666’ from myexternalIP:52192

[2012-07-24 19:41:37] NOTICE[9183]: chan_sip.c:14952 check_auth: Correct auth, but based on stale nonce received from ‘sip:[email protected];tag=0f524c4b’
— Transmitting (no NAT) to myexternalIP:52192 —

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-b12c653c871c8a3b-1—d8754z-;received=MyExternalIP;rport=52192

From: sip:[email protected];tag=0f524c4b

To: sip:[email protected];tag=as7efd9a4b

Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.

CSeq: 25 SUBSCRIBE

Server: FPBX-2.10.1(10.5.0)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“684074fa”, stale=true

Content-Length: 0

Scheduling destruction of SIP dialog ‘YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.’ in 6400 ms (Method: SUBSCRIBE)
— SIP read from UDP:myexternalIP:52192 —

SUBSCRIBE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-72dcf4095c5cb14f-1—d8754z-;rport

Max-Forwards: 70

Contact: sip:[email protected]:52192

To: sip:[email protected];tag=as7efd9a4b

From: sip:[email protected];tag=0f524c4b

Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.

CSeq: 26 SUBSCRIBE

Expires: 0

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Supported: timer

User-Agent: X-Lite 4 release 4.1 stamp 63215

Authorization: Digest username=“6666”,realm=“asterisk”,nonce=“684074fa”,uri=“sip:[email protected]:5060”,response=“ebd857b433a798cd3253b34ddd2c429b”,algorithm=MD5

Event: message-summary

Content-Length: 0
<------------->

— (15 headers 0 lines) —

Found peer ‘6666’ for ‘6666’ from myexternalIP:52192
— Transmitting (no NAT) to myexternalIP:52192 —

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-72dcf4095c5cb14f-1—d8754z-;received=MyExternalIP;rport=52192

From: sip:[email protected];tag=0f524c4b

To: sip:[email protected];tag=as7efd9a4b

Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.

CSeq: 26 SUBSCRIBE

Server: FPBX-2.10.1(10.5.0)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Expires: 0

Content-Length: 0

Reliably Transmitting (no NAT) to myexternalIP:11730:

NOTIFY sip:[email protected]:52192 SIP/2.0

Via: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK0da2aae9;rport

Max-Forwards: 70

Route: sip:[email protected]:52192

From: “Unknown” sip:[email protected];tag=as7efd9a4b

To: sip:[email protected]:52192;tag=0f524c4b

Contact: sip:[email protected]:5060

Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.

CSeq: 116 NOTIFY

User-Agent: FPBX-2.10.1(10.5.0)

Event: message-summary

Content-Type: application/simple-message-summary

Subscription-State: terminated;reason=timeout

Content-Length: 88
Messages-Waiting: no

Message-Account: sip:*[email protected]

Voice-Message: 0/0 (0/0)

[2012-07-24 19:41:37] NOTICE[10306]: manager.c:2461 authenticate: Seems to have passed…
— SIP read from UDP:myexternalIP:52192 —

SIP/2.0 200 OK

Via: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK0da2aae9;rport=5060

Contact: sip:[email protected]:52192

To: sip:[email protected]:52192;tag=0f524c4b

From: "Unknown"sip:[email protected];tag=as7efd9a4b

Call-ID: YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.

CSeq: 116 NOTIFY

User-Agent: X-Lite 4 release 4.1 stamp 63215

Content-Length: 0
<------------->

— (9 headers 0 lines) —

Really destroying SIP dialog ‘YzAxMTFhY2MyNN57AMWZjM2FlM2I0N2Y2MDMxZDEyY2M.’ Method: SUBSCRIBE
— SIP read from UDP:myexternalIP:52192 —

REGISTER sip:clientdomain.com SIP/2.0

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-9f409e1a1089975a-1—d8754z-;rport

Max-Forwards: 70

Contact: sip:[email protected]:52192;rinstance=f79730722b7dd419;expires=0

To: sip:[email protected]

From: sip:[email protected];tag=5fa85a66

Call-ID: OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.

CSeq: 7 REGISTER

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Supported: timer

User-Agent: X-Lite 4 release 4.1 stamp 63215

Authorization: Digest username=“6666”,realm=“asterisk”,nonce=“3b4038c5”,uri=“sip:clientdomain.com”,response=“057ee1ba229d1ffcbe0a813ec3c30cc0”,algorithm=MD5

Content-Length: 0
<------------->

— (13 headers 0 lines) —

Sending to myexternalIP:52192 (NAT)
— Transmitting (no NAT) to myexternalIP:52192 —

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-9f409e1a1089975a-1—d8754z-;received=MyExternalIP;rport=52192

From: sip:[email protected];tag=5fa85a66

To: sip:[email protected];tag=as37a3da30

Call-ID: OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.

CSeq: 7 REGISTER

Server: FPBX-2.10.1(10.5.0)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="04c2bbb5"

Content-Length: 0

Scheduling destruction of SIP dialog ‘OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.’ in 32000 ms (Method: REGISTER)
— SIP read from UDP:myexternalIP:52192 —

REGISTER sip:clientdomain.com SIP/2.0

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-284ba65483720724-1—d8754z-;rport

Max-Forwards: 70

Contact: sip:[email protected]:52192;rinstance=f79730722b7dd419;expires=0

To: sip:[email protected]

From: sip:[email protected];tag=5fa85a66

Call-ID: OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.

CSeq: 8 REGISTER

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Supported: timer

User-Agent: X-Lite 4 release 4.1 stamp 63215

Authorization: Digest username=“6666”,realm=“asterisk”,nonce=“04c2bbb5”,uri=“sip:clientdomain.com”,response=“99f2f13a65db9ce748b48ec038d05435”,algorithm=MD5

Content-Length: 0
<------------->

— (13 headers 0 lines) —

Sending to myexternalIP:52192 (no NAT)

– Unregistered SIP ‘6666’
— Transmitting (no NAT) to myexternalIP:52192 —

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.139:11730;branch=z9hG4bK-d8754z-284ba65483720724-1—d8754z-;received=MyExternalIP;rport=52192

From: sip:[email protected];tag=5fa85a66

To: sip:[email protected];tag=as37a3da30

Call-ID: OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.

CSeq: 8 REGISTER

Server: FPBX-2.10.1(10.5.0)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Expires: 0

Date: Wed, 25 Jul 2012 02:41:37 GMT

Content-Length: 0

Scheduling destruction of SIP dialog ‘OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.’ in 32000 ms (Method: REGISTER)

[2012-07-24 19:41:44] NOTICE[10314]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:41:46] NOTICE[10322]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:41:49] NOTICE[9183]: chan_sip.c:13544 sip_reregister:    – Re-registration for  [email protected]

REGISTER 11 headers, 0 lines

Reliably Transmitting (NAT) to CallcentricIP:5060:

REGISTER sip:callcentric.com SIP/2.0

Via: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK0a1d8dbd;rport

Max-Forwards: 70

From: sip:[email protected];tag=as59ebfd4e

To: sip:[email protected]

Call-ID: [email protected]

CSeq: 159 REGISTER

User-Agent: FPBX-2.10.1(10.5.0)

Authorization: Digest username=“17772XXXXXX”, realm=“callcentric.com”, algorithm=MD5, uri=“sip:sip:callcentric.com”, nonce=“dadabb98b90cc5189320b709e7c26fe4”, response="d9a8a75c99e6693a09527942b33f7bd3"

Expires: 120

Contact: sip:[email protected]:5060

Content-Length: 0

— SIP read from UDP:CallcentricIP:5060 —

SIP/2.0 200 Ok

v: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK0a1d8dbd;rport=5060

f: sip:[email protected];tag=as59ebfd4e

t: sip:[email protected]

i: [email protected]

CSeq: 159 REGISTER

m: sip:[email protected]:5060;expires=60

l: 0
<------------->

— (8 headers 0 lines) —

Scheduling destruction of SIP dialog ‘[email protected]’ in 32000 ms (Method: REGISTER)

[2012-07-24 19:41:49] NOTICE[9183]: chan_sip.c:21492 handle_response_register: Outbound Registration: Expiry for callcentric.com is 60 sec (Scheduling reregistration in 45 s)

[2012-07-24 19:41:51] NOTICE[10325]: manager.c:2461 authenticate: Seems to have passed…

Really destroying SIP dialog ‘[email protected]’ Method: REGISTER

[2012-07-24 19:41:59] NOTICE[10333]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:42:00] NOTICE[10341]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:42:06] NOTICE[10344]: manager.c:2461 authenticate: Seems to have passed…

Really destroying SIP dialog ‘OTgzYWJlMzA0YjBhNWIwMDAyMDRiNGE0N2IzZjRkOWI.’ Method: REGISTER

[2012-07-24 19:42:13] NOTICE[10352]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:42:15] NOTICE[9183]: chan_sip.c:13544 sip_reregister:    – Re-registration for  [email protected]

REGISTER 10 headers, 0 lines

Reliably Transmitting (NAT) to 67.216.35.205:5060:

REGISTER sip:67.216.35.205 SIP/2.0

Via: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK59c0c145;rport

Max-Forwards: 70

From: sip:a97341syB0XXXXX[email protected];tag=as1ea40246

To: sip:[email protected]

Call-ID: [email protected]

CSeq: 116 REGISTER

User-Agent: FPBX-2.10.1(10.5.0)

Expires: 120

Contact: sip:[email protected]:5060

Content-Length: 0

— SIP read from UDP:67.216.35.205:5060 —

SIP/2.0 200 OK

Via: SIP/2.0/UDP ClientexternalIP:5060;branch=z9hG4bK59c0c145;received=ClientexternalIP;rport=5060

From: sip:[email protected];tag=as1ea40246

To: sip:[email protected];tag=gssb160561fcaae4af40524610885a29c28

Call-ID: [email protected]

CSeq: 116 REGISTER

Server: Gafachi UAS v110.09

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE

Contact: sip:[email protected]:5060

Date: Wed, 25 Jul 2012 02:42:15 GMT

Content-Length: 0
<------------->

— (11 headers 0 lines) —

Scheduling destruction of SIP dialog ‘[email protected]’ in 32000 ms (Method: REGISTER)

[2012-07-24 19:42:15] NOTICE[9183]: chan_sip.c:21492 handle_response_register: Outbound Registration: Expiry for 67.216.35.205 is 120 sec (Scheduling reregistration in 105 s)

[2012-07-24 19:42:16] NOTICE[10360]: manager.c:2461 authenticate: Seems to have passed…

[2012-07-24 19:42:21] NOTICE[10363]: manager.c:2461 authenticate: Seems to have passed…

Really destroying SIP dialog ‘[email protected]’ Method: REGISTER

[2012-07-24 19:42:28] NOTICE[10371]: manager.c:2461 authenticate: Seems to have passed…

knotbeerdan · July 25, 2012, 6:41am

I looked at the freepbx system I have running at home and I am running Aterisk V 10.4.0 and I do not see the errors in the CLI.

The Asterisk version on the clients machine is 10.5.0…

Maybe there is something different.
When I was building the box I had to use the latest release to install on the RAID. (although I did not try every release available)

knotbeerdan · July 27, 2012, 8:26pm

So I was logged into the server and noticed that whenever the system status page refreshed another line shows up, so it would seem that the wen interface is definitely to blame here.

knotbeerdan · July 27, 2012, 8:26pm

So I was logged into the server and noticed that whenever the system status page refreshed another line shows up, so it would seem that the wen interface is definitely to blame here.

cardy_c · December 10, 2012, 5:33pm

Does anyone know a way to stop this apprearing in the CLI it’s a bit annoying when you are troubleshooting in terminal.If i remember there was something used to happen like this in an older versions and you could modify something to stop it but I can’t remember the details.

bksales · December 12, 2012, 2:55am

i have not had a chance to dig into this at all yet, other than to confirm that when in the asterisk cli the message displays every 7 seconds

bksales · December 12, 2012, 3:07am

when doing something on the admin panel. every click of the admin panel results in a line. looks to me like someone left a debug line turned on.

tm1000 · December 12, 2012, 10:00pm

Hi

It’s left over debug that was never removed in the asterisk source. The only way you cant stop it is to remove the line in main/manager.c and recompile asterisk. There is no other way to correct this. You can also update to Asterisk 11 or downgrade to 1.8.

http://svn.asterisk.org/svn/asterisk/branches/10-digiumphones/main/manager.c

http://bit.ly/QVKCCy

system · June 4, 2014, 7:38pm