[Serusers] handle_publish crashes in PA

Okay... I'll admit, this isn't the most recent PA module, but I thought someone might have a hint nonetheless. I'm running SER 0.9.6. I do NOT wish to upgrade to the somewhat haphazard presence snapshot as it's not entirely in stable/usable condition yet. I was, however, under the impression that simple PUBLISH/SUBSCRIBE methods would work okay on this version of the module. Am I mistaken? Usual stuff in the ser.cfg if(method=="SUBSCRIBE") { if(!t_newtran()) { log(1, "SUBSCRIBE newtran error\n"); sl_reply_error(); }; handle_subscription("registrar"); break; }; if(method=="PUBLISH") { if(!t_newtran()) { log(1, "PUBLISH newtran error\n"); sl_reply_error(); }; handle_publish("registrar"); break; }; When my Snom phone sends a publish, it looks like this: U 66.112.115.10:2057 -> 66.112.115.34:5060 PUBLISH sip:11019552444@my.domain.com:5060 SIP/2.0. Via: SIP/2.0/UDP 66.112.115.10:2057;branch=z9hG4bK-nc00a965o8y5;rport. From: "Death" <sip:11019552444@my.domain.com:5060>;tag=o6bezw24ge. To: "Death" <sip:11019552444@my.domain.com:5060>. Call-ID: 3c267063afc8-19wbm3ssr4y3@snom190. CSeq: 1 PUBLISH. Max-Forwards: 70. Event: proxy-config. Content-Type: application/text. Content-Length: 0. . It sends this (with slightly different From: tags) 9 times and then ser coredumps without a word to the log. Any ideas? Give up presence for now and just tell my users to get over it? :) N.