Igor Slepchin wrote:
>
> Here is a quote from 2543bis:
>
> user: The name of the user addressed. Note that this field MAY be empty
> where the destination host does not have a notion of users, e.g., for
> embedded devices.
>
> So I guess what you are seeing is OK.
Hmmm...so what is a proxy for a domain to do when it gets an INVITE request
where the host part matches its domain? I guess one option is, as Jo
pointed out, to send a 405 Method Not Allowed final response.
But even in case of embedded devices where the username is skipped, there
has to be a way to address unambiguously which embedded device is being
invited? Is it the refrigirator? the toaster? or the microwave? If I
have a proxy fronting my home devices (let's say my home domain is vkg.com),
it will get terribly upset if it only got an
INVITE sip:vkg.com SIP/2.0
Which embedded device should it proxy the INVITE to? I guess maddr
parameter could be used here to unambiguously pick a resource:
INVITE sip:vkg.com;maddr=toaster.vkg.com SIP/2.0
But the issue I am talking about is a proxy receiving an INVITE without a
username AND without a maddr parameter. Unless UACs specifically know that
they are addressing embedded devices, the username should be present in the
R-URI.
Thanks,
- vijay
--
Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org}
Internet Software and eServices Group
Lucent Technologies/Bell Labs Innovations 263 Shuman Blvd., Rm 1A-413
Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
