12:23 < Gugge> as far as i can tell realtime in 1.6.1 doesnt load sipusers anymore, and loads entries from sippeers as both users and peers, ignoring the type column in the table. Anyone wanna help me debug why? :)12:27 <@kpfleming> did you read UPGRADE.txt?12:27 <@kpfleming> in 1.6.1, 'type=user' is gone12:30 -!- nandersson [n=nanderss@72.Red-88-28-236.staticIP.rima-tde.net] has quit ["Leaving"]12:32 < Gugge> i read about that somewhere .. but using type=peer in a static sip.conf avoids the peer lookup in chan_sip.conf12:32 < Gugge> /* First find devices based on username (avoid all type=peer's) */12:32 < Gugge> using realtime nomatter what i type in the type column it matches there12:45 < Gugge> kpfleming, would you say its by design that a realtime peer is matched based on username only, or should i fill a bugreport?12:45 <@kpfleming> i do not know enough to say for sure12:45 < Gugge> if its by design ill just remove the username matching from my source12:45 <@kpfleming> i'd suggest raising this question on the asterisk-dev list12:45 < Gugge> ill try, thankyou12:49 <@jsmith> kpfleming: I thought that was just in memory... not in the config files12:49 <@kpfleming> maybe i'm misunderstanding then12:49 <@kpfleming> i think you may be right, actually12:50 <@kpfleming> both type=peer and type=user are stored in the same structures12:50 <@kpfleming> so then this sounds like a bug12:50 < Gugge> i guess i could try another backend than mysql too12:50 <@jsmith> "kill the user" was for killing the user structure in memory, not killing the "user" device type in sip.conf12:51 <@kpfleming> the backend type should not matter12:52 < Gugge> it just seems like all entries in the sippeers table is loaded as frineds12:52 < Gugge> friends12:52 < Gugge> no matter if type is set or not on them12:53 <@kpfleming> yes, i'd say that is a bug, and you should look through the issue tracker to see if it's been reported already12:54 < Gugge> will do