VoIP Mailing List Archives

[ohjelmistoarkkitehti a...]

Hello,


After a small break from working on this, I got the idea of tcpdumping the correct ports. What I see is REGISTER messages from Kamailio port to Asterisk, which are replied with 401 Unauthorized. Why is this happening? In my sippeers table the secret field has no value (tried both NULL and empty string) and the added field sippasswd has the correct password for the user. 


The above might be the cause of my problem, would anyone be able to advice me to get to correct behaviour? Now Kamailio sees the clients as registered, which would be wrong if Asterisk doesn't. 


cheers,
Olli





2014-04-24 11:27 GMT+03:00 Olli Heiskanen <ohjelmistoarkkitehti@gmail.com (ohjelmistoarkkitehti@gmail.com)>:

[ldardini at gmail.com]

It is the way it works. First the phone sends a REGISTER without any password. Asterisk answers with a "Unauthorized" and provide a nonce to be used for the next registration attempt, using it to encrypt the password.

Leandro



2014-05-14 13:12 GMT+02:00 Olli Heiskanen <ohjelmistoarkkitehti@gmail.com (ohjelmistoarkkitehti@gmail.com)>:

[ohjelmistoarkkitehti a...]

Hello,

Thank you for your response.


Actually, I managed to solve a part of the problem; as I use Kamailio to handle authentication, problem was that even though authentication went ok through Kamailio, Asterisk refused to accept messages from Kamailio. That's why Asterisk sent the 401. I think I had incorrect values in the realtime sippeers table rows, and also I had to add values to deny and permit fields, which in fact were in the wrong order. So no wonder I was having problems with authentication! (and yes, I do know how digest authentication works )


I fixed the deny values to 0.0.0.0/0.0.0.0 and permit value to Kamailio ip. 


Even after this I had problems having Asterisk accept the authentications. Asterisk cli was saying: 
ERROR[20605]: chan_sip.c:30790 build_peer: Bad ACL entry in configuration line 0 : kamailioip:5060



... that was because I had tried to define kamailio ip with port, as Kamailio and Asterisk are on the same machine, but removing the port solved that (not sure but I guess it is good I use 5060 for Kamailio and 5070 for Asterisk instead of vice versa, perhaps this solution wouldn't work then). Then I found that I had to add values to fields: nat (to force_rport) and defaultip (to 0.0.0.0), and only after that I got Asterisk to see the registered peers. So now everything looks ok from both Asterisk and Kamailio when it comes to authentication. 


I still can't get calls going though, in the asterisk cli I get 'Everyone is busy/congested at this time', so I'm going to continue investigating that. If you guys have good advice for me at this time I'll be most happy to take them.


cheers,
Olli





2014-05-15 17:17 GMT+03:00 Leandro Dardini <ldardini@gmail.com (ldardini@gmail.com)>: