Summary:	ASTERISK-02426: Authentication _sometimes_ fail with clients
Reporter:	Roy Sigurd Karlsbakk (rkarlsba)	Labels:
Date Opened:	2004-09-17 05:45:40	Date Closed:	2004-09-25 02:01:40
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/NewFeature
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Using vanilla SIP friends from a mysql from latest CVS, SIP authentication sometimes fail, usually after some time. When this happens, it's usually enough to reboot the SIP client to get it online again. Username/password is not changed in the time between working/not working. This may seem to be a problem behind NAT although I have not verified it yet. ****** ADDITIONAL INFORMATION ****** I have not yet managed to get a SIP debug from both when authentication succeeds and when it fails, and then to compare these two. I'll attach it as fast as I can get it. Have anyone else seen this happen?
Comments:	By: Roy Sigurd Karlsbakk (rkarlsba) 2004-09-17 06:09:49 It may look like the SIP registration is timed out before the limit (currently set to default/max 3600/7200): The client, after some time, sends another channel name than right after registration: SIP/xxxx-hhhhhhhh instead of the defined SIP-1xxxxxx-hhhhhhhh where 1xxxxxx is the defined SIP login thanks roy By: Brian West (bkw918) 2004-09-17 16:14:23 Try this: #ifdef SIP_MYSQL_FRIENDS #define MYSQL_FRIENDS #include <mysql/mysql.h> #endif to this: #ifdef SIP_MYSQL_FRIENDS #define MYSQL_FRIENDS #define MYSQL_USERS #include <mysql/mysql.h> #endif /* Ehud Gavron 08-Jun-2004:                                            */                                                                                     /*    The Mysql stuff works great for peers but not for users.         */                                                                                     /* Unfortunately multi-line phones (e.g. cisco 7960) and many          */ /* SIP users behind the same NAT gateway need users.  So....           */ By: Mark Spencer (markster) 2004-09-17 17:51:41 You're going to have to have more information than this to keep this bug open.  You'll have to supply some debugging showing what's going on.