Andreas Mueller Posted April 1, 2016 Report Posted April 1, 2016 Hello,Registering a device fails in my test kazoo cluster (3 hosts, first is rabbit).The rabbit.log says that everything is fine (AMQP connections accepted)But kamailio.log says:|log|failed to query registrar for authentication credentials for user_test@xxx.xxx.xxx.xxx (xxx is the ip address)Any suggestions, where I could start to look for? I used this guide for the installation (CentOS-6.7-x86_64 as operating system) https://2600hz.atlassian.net/wiki/display/Dedicated/via+RPM Greets,Andreas
denverUser Posted January 15, 2018 Report Posted January 15, 2018 I've got the exact same problem. Anyone find a solution?
extremerotary Posted January 15, 2018 Report Posted January 15, 2018 @denverUser Hey, can you provide the log lines above and below the error from kamailio, and answer a few questions? What version of kazoo, ecallmgr, freeswitch, and kamailio are you running? I understand that it's a registration question with Kamailio, but all the versions together will help to isolate if it's a versioning issue between anything. You can use 'rpm -qa | grep {{ something }}' to find out the installed versions (where {{ something }} == "kazoo" for example). Then, if running version 4.0+, from the command line, you can run 'kazoo-applications status' to see what version(s) are actually running (as opposed to installed). This output will also help in general to see what apps you have running, etc. Is this a single-server install? I'm sure you've triple-checked the SIP creds, but I have to ask! Feel free to remove any personal info from the logs, like IPs or realm names and I'll take a look!
Administrators mc_ Posted January 16, 2018 Administrators Report Posted January 16, 2018 @Andreas Mueller you might want to use CentOS 7 and the install instructions here: https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/ In any case, walking through those steps might help you figure out what is wrong in your existing system as well.
denverUser Posted January 16, 2018 Report Posted January 16, 2018 Thanks for the quick response. It's a multi server deploy. We fixed it by triple-checking the SIP creds. Had to make the domain's match the sub accounts under which the devices were registered.
Recommended Posts