Hi, according to RFC 3261 - requests within dialog (like this NOTIFY) are sent with AOR set to "remote target URI" (12.2.1.1). This URI is taken from Contact header field received in dialog initial request (12.1.1; it is SUBSCRIBE here) or in target refresh requests/responses sent within this dialog.
By other words it means that what you send in Contact header in SUBSCRIBE it will be sent in first line of NOTIFY (and the NOTIFY is routed to this place).
Vaclav
On Sat, Nov 11, 2006 at 11:22:34PM -0500, SER LIST wrote:
Hi, I have SER Proxy and PRESENCE running on different machines. REGISTERS are being forwarded by SER Proxy to PRESENCE and PRESENCE is storing the location information in "location" db.
What I am seeing is that when the PRESENCE Server sends NOTIFYs to watchers, it sends them to the SER PROXY (destination IP Is that of SER PROXY) but the URI in NOTIFY is that of the watchers LOCATION INFO. Is this correct? I would like the NOTIFY URI to contain the SIP DOMAIN and not the contact info.
e.g. user 444 registers with SER PROXY (sip.xx.com). It is registering from 10.1.1.1:12321 (location info). SER PROXY sends the REGISTER TO Presence server which stores this info in location database (location is 444@10.1.1.1:12321). Now when Presence Server sends NOTIFY, it sends it to the SER PROXY IP BUT the NOTIFY URI IS:
NOTIFY sip:444@10.1.1.1:12321 SIP/2.0
How can I have the NOTIFY URI to be :
NOTIFY sip:444@sip.xx.com SIP/2.0
Any suggestions would be higlhy appreciated.
Ready for the world's first international mobile film festival celebrating the creative potential of today's youth? Check out Mobile Jam Fest for your a chance to WIN $10,000! www.mobilejamfest.com
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers