Re: [dispatch] draft-lavers-sipcore-immersive-capability-00.txt

["Kevin P. Fleming" <[e-mail]>]

On 03/13/2012 07:24 PM, Paul Kyzivat wrote:
> On 3/13/12 6:33 PM, Kevin P. Fleming wrote:
>> On 03/09/2012 02:47 PM, Paul Kyzivat wrote:
>>
>>> But I would be more than pleased if people who know of actual uses piped
>>> up here and told us about them.
>>
>> This discussion prompted those of us in the SIP Forum's FoIP Task Group
>> to change our plans and start working on proposing a "+sip.fax" feature
>> tag, intended for use by carriers who need to route calls differently if
>> the calling endpoint is FAX-capable (which will more than likely mean
>> the purpose of the call is to complete a FAX transaction).
>
> I've already said it a couple of times in this thread, but I'll say it
> again:
>
> Routing to a target based on the *capabilities* of the caller is ill
> conceived. Those capabilities don't equate to what the caller intends to
> do.
>
> Routing based on caller *preferences* however makes perfect sense. But
> then you should actually implement 3841 to do it.

In this case, the purpose isn't target selection, it's mid-path network 
element selection (carriers who need to send calls through different 
paths if the call is likely to use T.38), although I doubt that 
distinction matters much for your argument :-)

The target does not change, but the network path in between the source 
and target uses this information to ensure that the network can support 
what the call could (is likely) to need in order to be successful.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: [e-mail] | SIP: [e-mail] | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org