If you create a URI that know not to be valid, or don't know to be
valid, you are asking for trouble. This is certainly the case with b.com
constructs an a.com uri. And its also true when b.com creates a uri with
the b.com domain for a phone number not belonging to b.com, and gives
it to somebody who has no service relationship with b.com. This might
work in some cases, but it is no basis for normative behavior.
We need to specify something that can be expected to work.
Paul
Francois Audet wrote:
> I understand what you are saying.
>
> But I have difficulty imagining a case where the owner of the domain of the
> service provider or enterprise (example.com) would not be able to reach a
> PSTN gateway.
>
> I guess you are worried about [EMAIL PROTECTED] phoning [EMAIL PROTECTED] and
> b.com doesn't have
> a gateway but wants to forward to PSTN (and wants the originating to fork
> the bill). So it sends tel URI instead. Sure, but again, I doubt it will
> work very well.
>
> I guess you could cheat and put a.com in the SIP contact. I think there are
> lots of cases where the domain will be ignored anyways.
>
> Again, don't shoot the messenger: it makes sense to me to use Tel URI for
> this. I am just saying it may cause interop problems. Maybe that's ok, and
> maybe implementations will start implementing tel URI.
>
>
> On Apr12 2008 21:48 , "Juha Heinanen" <[EMAIL PROTECTED]> wrote:
>
>> Francois Audet writes:
>>
>>> Every single implementation that I've see does the following:
>>>
>>> Contact: sip:[EMAIL PROTECTED];user=phone
>>>
>>> Where example.com is the domain of the forwarding user. The SIP proxy will
>>> then route it to a PSTN if appropriate.
>> i think you have not followed this thread. it has been pointed out that
>> the above does no work if caller does not have the right to use pstn
>> gateway of example.com.
>>
>> -- juha
>
>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
