Vikram Chhibber wrote:
> the url format that you have provided is not a sip therefore there is
> no user and host part. The url format is tel therefore you need to
> discard the host portion of that url. The user portion you need to
> treat it as local tel number with phone-context, tgrp and
> trunk-context as parameters.
The above is not correct!
This is a sip uri. Any server that is not authoritative for the domain
isp.example.net is expected to route the request using sip routing rules
based on that domain name.
Once it reaches a server authoritative for isp.example.net, that server
will route based on the user part of the request. At that time the
user=phone is considered, the user part treated as a tel uri, and
routing done appropriately.
This is a key difference between using a sip uri with user=phone vs
using a tel uri. If a tel uri had been used, then *any* server could
route based on the phone number.
Paul
> ~Vikram
> On 5/4/07, Gayathri Madda <[EMAIL PROTECTED]> wrote:
>> Hi all
>>
>> can u please suggest how to parse this as per ABNF Rule
>> sip:5550100;phone-context=+1-630;tgrp=TG-1;trunk-context=
>> [EMAIL PROTECTED];user=phone
>>
>> As per RFC we use "@" for parsing host and user part
>> Here in this case :
>> "5550100;phone-context=+1-630;tgrp=TG-1;trunk-context=example.com" is
>> consider as user part and called party number is corrupted while mapping to
>> H323 set up message.
>>
>> Thanks in Advance
>>
>> Regards
>> Gayathri
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
