sipXecs 4.6 - unable to get credentials

[Matthew Hodgins]

I'm unable to register any endpoints to my sipXecs server. The credentials are present in the postgres DB, but there is no credentials.xml file in /var/sipxdata/sipdb. The sipregistrar.log is full of:

2012-08-22T15:14:10.068243Z":285:AUTH:ERR:sipxecs.sqa.lifesize.com:SipRegistrarServer:b6df7b70:SipRegistrar:"Unable to get credentials for '***@sipxecs.sqa.lifesize.com', realm='sipxecs.sqa.lifesize.com',user='200'"

I've seen this problem in another archived post, but no real solution was found.

Environment:
sipXecs 4.6.0
LifeSize/Tandberg/Polycom video endpoints (treated as users when registering)

Steps taken:

1. Install sipXecs 4.6.0 from CD
2. Run through the guided command line configuration
3. Through the web interface, enable SIP Registrar and SIP proxy
4. Reboot via command line
5. Through the web interface, create a new user (verify sip_password in postgres DB)
6. Try registering an endpoint with this user

I have another 4.2.1 installation of sipXecs that does not exhibit this issue. I've attached the registrar-config file to this e-mail.

Thanks in advance!

[Michael Picher]

i think you missed the yum update step that must be done after install from
ISO...

iso is not kept up to date... hmmm... how many times have i said this?

Post by Matthew Hodgins
I'm unable to register any endpoints to my sipXecs server. The credentials
are present in the postgres DB, but there is no credentials.xml file in
2012-08-22T15:14:10.068243Z":285:AUTH:ERR:sipxecs.sqa.lifesize.com:SipRegistrarServer:b6df7b70:SipRegistrar:"Unable
sipxecs.sqa.lifesize.com',user='200'"
I've seen this problem in another archived post, but no real solution was found.
sipXecs 4.6.0
LifeSize/Tandberg/Polycom video endpoints (treated as users when registering)
1. Install sipXecs 4.6.0 from CD
2. Run through the guided command line configuration
3. Through the web interface, enable SIP Registrar and SIP proxy
4. Reboot via command line
5. Through the web interface, create a new user (verify sip_password
in postgres DB)
6. Try registering an endpoint with this user
I have another 4.2.1 installation of sipXecs that does not exhibit this
issue. I've attached the registrar-config file to this e-mail.
Thanks in advance!
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.

[Tony Graziano]

This post might be inappropriate. Click to display it.

[Matthew Hodgins]

This post might be inappropriate. Click to display it.

[Douglas Hubler]

Post by Matthew Hodgins
I've run 'yum update' and rebooted, but that didn't resolve my issue. My
SIP domain is sipxecs.sqa.lifesize.com (same as my SIP realm)

in mongo, does
db.entity.find();
return anything?

Looks like you've done the needful, Can you take a snapshot and send me the
file off list?
As possible workaround after taking snapshot, try selecting the server in
System/Servers and sending profiles.

[Matthew Hodgins]

Sending profiles worked! I'm now able to register endpoints to the sipXecs and dial calls using their extension.

I'll send you the snapshot anyway in case there is an actual bug that might need to be fixed instead of a configuration error.

Thanks for your help guys!


From: Douglas Hubler <***@ezuce.com<mailto:***@ezuce.com>>
Reply-To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>>
Subject: Re: [sipx-users] sipXecs 4.6 - unable to get credentials

On Wed, Aug 22, 2012 at 1:14 PM, Matthew Hodgins <***@lifesize.com<mailto:***@lifesize.com>> wrote:
I've run 'yum update' and rebooted, but that didn't resolve my issue. My SIP domain is sipxecs.sqa.lifesize.com<http://sipxecs.sqa.lifesize.com> (same as my SIP realm)

in mongo, does
db.entity.find();
return anything?

Looks like you've done the needful, Can you take a snapshot and send me the file off list?
As possible workaround after taking snapshot, try selecting the server in System/Servers and sending profiles.

[Douglas Hubler]

Post by Matthew Hodgins
Sending profiles worked! I'm now able to register endpoints to the sipXecs
and dial calls using their extension.

Your snapshot was very helpful. Turns out you're one of the few that
*didn't* enable "SIP Capture" and there was a bug if that feature is
NOT on caused this issue.

I'm building fix ready for tomorrow, but I suspect you'll have to Send
Profiles for many changes you make to your system until you either
update tomorrow or enable SIP Capture until then.

Thanks for testing!

[Douglas Hubler]

Post by Matthew Hodgins
I'm unable to register any endpoints to my sipXecs server. The credentials
are present in the postgres DB, but there is no credentials.xml file in

yum update and describe system more as Tony and Michael said. Also
note that, that file is no longer used, info is in database. To read

mongo imdb
db.entity.find({'ident' : { $regex : '***@.*'}})

For more query options see
http://docs.mongodb.org/manual/reference/operators/