Barry Desborough wrote:
> Any opinions on this matter?
>
> Another manufacturer's UA is registering, using user=phone in its To:,
> From:
> and Contact: headers. My UA is a simple POTS access device. All the user
> can
> do is enter telephone digits. When I try to call from my UA to the other
> device, omitting the user=phone parameter, the registrar can't resolve
> the
> URL.
>
> Now it seems to me that the user=phone parameter is only useful in the
> Contact: header - the registration should be done without this parameter
> in
> the To: and From: headers. After all, the registered address is a pretty
> abstract value - all that really matters is that the registrar can
> resolve
> the Contact: URL from it. Is this reasoning correct, or am I missing
> something?
This has been a continuing source of confusion, and is currently logged
as issue #281, in fact.
Generally, the mapping of an incoming request URI to obtain a key into
the DB of registered contact is a matter of local policy, but it needs
to be done in a consistent and coherent manner, in order to avoid
interop problems. This particular item, use of user=phone, has been a
source of trouble for some time.
I believe that the correct thing to do in this particular case is that
the registrar should not user the user=phone when using the
address-of-record from the REGISTER. Furthermore, it ought to be
stripped from the incoming r-uri, although it probably should not have
been there in the first place if the caller has no idea about the
meaning of the numbers being entered. Generally, the user=phone is in
there if the number is known to represent a PSTN number, rather than
just a string of digits that are of local significance.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PH: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
