Credentials error in logs

[thames]

Hi Folks

This is threatening to lose me even more hair than I have already!

Looking at the logs I continually see this error and I have absolutely no idea how to find the problem, let alone fix it. I've checked all my usernames and passwords for each extension and they all appear to be correct. The auth and password for the gateways are working and both SKYPE and OrbTalk are registered and idle.

Can anyone throw light on where to look for this error?

10:49:53.352 [CM102001]: Authentication failed for SipReq: REGISTER 127.0.0.1:5060 tid=a173a83e25310f2f cseq=REGISTER [email protected]:6062 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
10:49:31.935 [CM102001]: Authentication failed for SipReq: REGISTER 127.0.0.1:5060 tid=47101533282bf018 cseq=REGISTER [email protected]:6062 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
10:49:28.594 Currently active calls [none]
10:49:10.411 [CM102001]: Authentication failed for SipReq: REGISTER 127.0.0.1:5060 tid=b25e5311c40de640 cseq=REGISTER [email protected]:6062 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
10:48:56.592 Currently active calls [none]
10:48:48.893 [CM102001]: Authentication failed for SipReq: REGISTER 127.0.0.1:5060 tid=c654cc15f01ec66b cseq=REGISTER [email protected]:6062 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
10:48:27.354 [CM102001]: Authentication failed for SipReq: REGISTER 127.0.0.1:5060 tid=51257c65015ff803 cseq=REGISTER [email protected]:6062 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

Cheers
Chris

 

[SY]

First check:
netstat -ano
It shows list of all TCP/UDP ports which are used by processes running on local host.
Then locate process which uses 6062 and then decide whether to stop it or reconfigure.

 

[thames]

Hi SY

Here it is:
Proto Local Address Foreign Address State PID
UDP 0.0.0.0:6062 *:* 3292

I have absolutely no idea why that port is in use on the Windows 7 machine... any ideas?

Cheers
Chris

 

[SY]

UDP 0.0.0.0:6062 *:* 3292
Selected part of the line specifies PID (process identifier)
You can find it in the list of processes (see Task Manager)