It is certainly permissible for the contact header to contain the address of a proxy. For instance, it may contain an Address of Record that is mapped by the proxy back to the physical address of the UAS. This is one way to solve the problem of providing a globally routable contact address when the actual address of the UAS is not globally routable. But you had better take care doing this - there had better be no ambiguity about which UAS is identified.

Paul

Alex Agranov wrote:
Hi,

I'm trying to understand wether it is possible that Contact: header in INVITE
sent by some UAC contains URI with the hostname of the Proxy and not of
the UAC itself?

All endpoints that I've tested send URI with their own hostname.
But I don't manage to find this explicit requirement if RFC3261.
Can somebody clarify this issue, please?

Best regards,
Alex Agranov
---
Senior Software Engineer
COMGATES Ltd.
15 Hagalim Avenue
Herzliya, 46725
Israel
Tel. +972.9.950.0404, Ext: 228
Fax. +972.9.950.0385
Mobile. +972.54.928435


_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


Reply via email to