Re: [Sipping] User Preferred Contact Address

[Paul Kyzivat <[e-mail]>]

Aisling,

Similar things have been discussed recently. (See 
draft-jennings-sipping-instance-id-01.txt) To identify particular 
endpoints uniquely, the +sip.instance feature tag has been proposed. It 
isn't especially user-friendly but it is unique.

You could define, somewhere, a mapping between sip.instance values and 
user-friendly names.

You could also define a different feature tag for the express purpose of 
providing a friendly name for a contact, but then you run the risk of it 
not being unique, and of requiring a way to provision the device with 
the value.

	Paul

Aisling O'Driscoll wrote:
> Hello all,
> 
> I am hoping to get opinions on the below:
> 
> I am considering research options in either extending CPL to support a
> REGISTER messages (some research has been done with CPL & SUBSCRIBE
> messages for presence) or perhaps adding a field to a SIP REGISTER
> message?...any other suggestions also welcome.
> 
> The reason I am considering the above is because I would like a user
> to be able to choose their preferred SIP end device to have a call
> delivered to e.g. office hard phone or pda softphone, laptop
> softphone etc. This user would have registered many times
> from the various end user devices with the same url and would
> therefore have multiple contact addresses. I cannot think how I can
> associate a particular contact address with "office phone" or
> "laptop" etc. 
> 
> However if I could extend CPL script syntax for this or perhaps add
> an extra field in a sip register message indicating the place the
> contact address is associated with, could this could work?
> 
> I cannot think of other methods of implementing this scenario. The
> problem with extending a SIP REGISTER message is that it would
> require every user to have a dedicated client. Anything I could do
> purely on the service provider side?
> 
> Many thanks for your ideas and guidance,
> BR,
> Aisling O' Driscoll.
> 
> 
> 
> -------------------Legal  Disclaimer---------------------------------------
> 
> The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP