Hi all!!!<br><br>I&#39;m experiencing quite difficulties setting up a dedicated (and separated) presence server with NATted end-points and the dstblacklist feature.<br><br>I&#39;d like to get some info about the construction of the most important headers (Req-URI,Contact,To,From,Via,Routr) for the different NOTIFY modalities depending on the state of the subscription.
<br><br>Setting up async_auth_queries I&#39;ve seen the pending and the active NOTIFY have different Req-URI and the second one is blocked by the NAT router. Further mid-dialog NOTIFYs providing changes in the presence status has also different headers...
<br>My main concern is whether the info for constructing the routing headers is taken from location table, from watcherinfo.dialog table, or from the incoming message...I know I could follow the code but an explanation would provide a really helpfull overview and later checking the code will be much simpler.
<br><br><br>Thanks in advance,<br>Samuel.<br>