Hi, Other please correct me if I’m wrong. NOTIFY should use record-route header. Make sure your kamailio servers set the record-route header for SUBSCRIBE requests.
Regards, Allen From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Veerabhara Gundu Sent: Wednesday, 9 July 2014 3:25 p.m. To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] Fwd: Need help with Routing presence NOTIFY messages Hello Experts, I have two Kamailio servers with built in presence servers with load balanced with DNS, both sharing same data base. Registration, authentication and messaging are working without any problem. When it comes to Presence, NOTIFY messages generated by Kamailio is getting rejected by firewall if the client didn't register to that particular Kamailio. In MESSAGES case, I read the socket info from Location table, if the client is not registered to that Kamailio forwarded to the server which serving that user. But in NOTIFY case, these messages are not coming to routing logic at all, Kamailio is directly sending messages by looking at the contact information from active-watchers table. One possible solution I am thinking is, separating presence logic and starting that as separate server. That way I can play with contact header. Any other thoughts, I appreciate any help with this. I have spent enough time on this. Thanks, Veera Thanks, Veera
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
