Hi Takeshi, Routing the presence traffic does not require USRLOC/REGISTRATION at all. The clients do send PUBLISH to the presence agent and they also send the SUBSCRIBE request to it. The PA (presence agent) is sending back the NOTIFY requests within the dialog created by the SUBSCRIBE request. So, the NOTIFY will be route back based on the Record-Route you did for SUBSCRIBE.
Regards, Bogdan mayamatakeshi wrote: > Hello, > I am testing opensips as registrar in the following scenario: > > UA ---REGISTER---> opensips (load-balancer) ----REGISTER with header > Path----> opensips (registrar). > > This works fine, and I have the INVITEs that reach the registrar going > thru both proxies as expected: > > UA <-----INVITE----- opensips(load-balancer) > <-------INVITE-------opensips(registrar) <------ GW > > But now I want to make the registrar to work as a presence server and > I want the NOTIFY requests to go thru the load-balancer too (to permit > reach UAs behind NAT). > Is this possible? I mean, when presence is processed by opensips, it > seems to me we cannot route NOTIFY requests using the usrloc data from > the registrar, because the NOTIFYs generated by this are not processed > by the cfg file. > So, is there any way to do this? > > br, > takeshi > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
