[mbulles]

Hi,

Using V10 I always receive this message in my log:

[CM102001]: Authentication failed for SipReq: REGISTER sip.xxxxxxx.com tid=6B14A3D996EBFECF cseq=REGISTER / 504 from(wire); Reason: License limit, processing or network error

The REGISTER sip.xxxxxxx.com is not an ip phone but the 3CX host itself?

What could be the cause?

Kind regards.

[nickybrg]

HI

Can you post the whole extract of the logs?

You have something installed on the same machine that is trying to register with the 3CX Phone system? This is how it looks from here - but I might be wrong.

Ignore the licence limit issue - that is an event raised by mistake. What is interesting is network error part.

Something on the same machine is causing problems.

[systola]

Hi Nicky!

I've got absolutely the same issue.

Almost every hour and sometime even more often.

Running 3CX SP4 on a W2K8R2 fairly fresh install with no additional software.

Any (new) guesses?

[nickybrg]

Make a wireshark capture and send us the logs for checking. Upload it somewhere and send me a pm.

[systola]

shall I restrict the sniff to port 5060 only?

[nickybrg]

sip server runs on 5060. So authentication requests must come on 5060.

So yes restrict 5060.

But what is the failed authentication message you get in the logs? Can you post the extract?

A - is it coming from inside? Outside?
B) do you get the license error as it is described in this post?

[systola]

capture is running, waiting for the log occurence.

yes, my message looks exactly the same as the one from the topic-originator, obviously, there are other numbers/IDs.

[feestbeestzaandam]

I Have the same problem but i cant see the solution here.
Wat was the magic tric to do?

I have the folowing error message who will and can help me??
I also use v10 free edition and i love it.

14:18:52.515 [CM102001]: Authentication failed for SipReq: REGISTER "external ip adres" tid=9C3E45B92EC24938 cseq=REGISTER / 6222 from(wire); Reason: License limit, processing or network error

[systola]

i was told by nickybrg after he analyzed my capture to ignore this message if all clients register successfully.

[nickybrg]

Whoever has this message, make a wireshark capture and make sure the registers are captured.

If everything is running smooth, you can ignore this message.

If you have problems however you will need to investigate. When I last digged into this problem, I found that that message you see was not even being generated by us.

What phones are being used? Is this a fritzbox at a by any chance?