Hello,

the NOTIFY requests generated by Kamailio should come from presence modules, not from pua. The pua group of modules should help with generating PUBLISH or SUBSCRIBE requests for various purposes.

If you just need to handle SUBSCRIBE/PUBLISH coming from end points, then you do not need pua modules, presence/presence_xml are needed for user status presence.

For BLF you may need both presence and pua groups of modules, in combination with dialog module, so kamailio publishes call-related states

Cheers,
Daniel

Hello, I have some trouble to figure out how routing works when the request coming from the kamailio itself (used as a user agent per example) .I try to use presence PUA... modules. The issue I have is the NOTIFY requests aren't sent to the good destination; it doesn't seems to obey to the contact or other informations when the device did a SUBSCRIBE. I don't want to ask to troubleshoot the presence module directly I just want to know how Kamailio deals with request coming from Kamailio itself (in the case of a NOTIFY generated by PUA_... modules My mains questions are: Does the pua modules when generating request  like NOTIFY will pass through request_route ? Does the pua modules when generating  request  like NOTIFY will be sent only when t_relay() is used or UA kamailio based request bypass all the logic of the Kamailio proxy behavior ?  I'm trying to understand if I can modify the NOTIFY request to change destination before the "routing decision" is made by Kamailio Kamailio 5.6.0 used as : -proxy to remote pbx for call dialog -registrar/location server -media relaying and nat management -...and I try to use it as a presence server instead to use the pbx behind kamailio

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda