PC
Peter Cai
Mon, Nov 10, 2008 2:21 AM
Hi all,
PJSIP automatically escape "#" to "%23".
But in my case, I have to have "#" un-escaped in the message.
I've skimmed the documents of PJSIP but didn't found any clues how to
change this behavior.
Has anyone ever met the same problem?
Hi all,
PJSIP automatically escape "#" to "%23".
But in my case, I have to have "#" un-escaped in the message.
I've skimmed the documents of PJSIP but didn't found any clues how to
change this behavior.
Has anyone ever met the same problem?
GL
Gang Liu
Mon, Nov 10, 2008 6:15 AM
It is ok if remote side handle URL correctlly.
What's your problem?
regards,
Gang
On Mon, Nov 10, 2008 at 10:21 AM, Peter Cai newptcai@gmail.com wrote:
It is ok if remote side handle URL correctlly.
What's your problem?
regards,
Gang
On Mon, Nov 10, 2008 at 10:21 AM, Peter Cai <newptcai@gmail.com> wrote:
> Hi all,
>
> PJSIP automatically escape "#" to "%23".
>
> But in my case, I have to have "#" un-escaped in the message.
>
> I've skimmed the documents of PJSIP but didn't found any clues how to
> change this behavior.
>
> Has anyone ever met the same problem?
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
HC
Hoi-Ho Chan
Mon, Nov 10, 2008 7:41 AM
must be escaped to %23 per the SIP syntax. If the remote party requires
to appear in the user portion of the URI then it's not conforming to the
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai newptcai@gmail.com wrote:
# must be escaped to %23 per the SIP syntax. If the remote party requires #
to appear in the user portion of the URI then it's not conforming to the
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com> wrote:
> Hi all,
>
> PJSIP automatically escape "#" to "%23".
>
> But in my case, I have to have "#" un-escaped in the message.
>
> I've skimmed the documents of PJSIP but didn't found any clues how to
> change this behavior.
>
> Has anyone ever met the same problem?
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
GL
Gang Liu
Mon, Nov 10, 2008 9:57 AM
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com wrote:
must be escaped to %23 per the SIP syntax. If the remote party requires
to appear in the user portion of the URI then it's not conforming to the
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai newptcai@gmail.com wrote:
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com> wrote:
> # must be escaped to %23 per the SIP syntax. If the remote party requires #
> to appear in the user portion of the URI then it's not conforming to the
> standard.
>
> Thanks
> Donald
>
> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com> wrote:
>
>> Hi all,
>>
>> PJSIP automatically escape "#" to "%23".
>>
>> But in my case, I have to have "#" un-escaped in the message.
>>
>> I've skimmed the documents of PJSIP but didn't found any clues how to
>> change this behavior.
>>
>> Has anyone ever met the same problem?
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip@lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
PC
Peter Cai
Mon, Nov 10, 2008 2:27 PM
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com wrote:
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com wrote:
must be escaped to %23 per the SIP syntax. If the remote party requires
to appear in the user portion of the URI then it's not conforming to the
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai newptcai@gmail.com wrote:
--
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com> wrote:
> I guess remote party didn't convert %23 into #.
>
> regards,
> Gang
>
> On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com> wrote:
>>
>> # must be escaped to %23 per the SIP syntax. If the remote party requires
>> # to appear in the user portion of the URI then it's not conforming to the
>> standard.
>>
>> Thanks
>> Donald
>>
>> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> PJSIP automatically escape "#" to "%23".
>>>
>>> But in my case, I have to have "#" un-escaped in the message.
>>>
>>> I've skimmed the documents of PJSIP but didn't found any clues how to
>>> change this behavior.
>>>
>>> Has anyone ever met the same problem?
>>>
>>> _______________________________________________
>>> Visit our blog: http://blog.pjsip.org
>>>
>>> pjsip mailing list
>>> pjsip@lists.pjsip.org
>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip@lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
--
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
GL
Gang Liu
Tue, Nov 11, 2008 10:58 AM
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai newptcai@gmail.com
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com wrote:
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com
must be escaped to %23 per the SIP syntax. If the remote party
to appear in the user portion of the URI then it's not conforming to
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai newptcai@gmail.com wrote:
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai <newptcai@gmail.com>
> :) Right, that's the problem.
>
> As "esacpe" in URI is optional in RFC3261, I have no strong reason to
> ask the other team to convert %23 to #.
>
> Actually I was laughed because I asserted that the escape is a "MUST"
> before I read the RFC carefully.
>
> On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com> wrote:
> > I guess remote party didn't convert %23 into #.
> >
> > regards,
> > Gang
> >
> > On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com>
> wrote:
> >>
> >> # must be escaped to %23 per the SIP syntax. If the remote party
> requires
> >> # to appear in the user portion of the URI then it's not conforming to
> the
> >> standard.
> >>
> >> Thanks
> >> Donald
> >>
> >> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> PJSIP automatically escape "#" to "%23".
> >>>
> >>> But in my case, I have to have "#" un-escaped in the message.
> >>>
> >>> I've skimmed the documents of PJSIP but didn't found any clues how to
> >>> change this behavior.
> >>>
> >>> Has anyone ever met the same problem?
> >>>
> >>> _______________________________________________
> >>> Visit our blog: http://blog.pjsip.org
> >>>
> >>> pjsip mailing list
> >>> pjsip@lists.pjsip.org
> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >>
> >>
> >> _______________________________________________
> >> Visit our blog: http://blog.pjsip.org
> >>
> >> pjsip mailing list
> >> pjsip@lists.pjsip.org
> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >>
> >
> >
> > _______________________________________________
> > Visit our blog: http://blog.pjsip.org
> >
> > pjsip mailing list
> > pjsip@lists.pjsip.org
> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
>
>
>
> --
>
> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
PC
Peter Cai
Wed, Nov 12, 2008 9:39 AM
It's not a MUST in RFC3216, it's only OPTIONAL.
See PAGE 152. "o" means optional.
default Req.-URI To From Contact R-R/Route external
user -- o o o o o o
2008/11/11 Gang Liu gangban.lau@gmail.com:
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai newptcai@gmail.com
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com wrote:
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com
wrote:
must be escaped to %23 per the SIP syntax. If the remote party
requires
to appear in the user portion of the URI then it's not conforming to
the
standard.
Thanks
Donald
On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai newptcai@gmail.com wrote:
--
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
It's not a MUST in RFC3216, it's only OPTIONAL.
See PAGE 152. "o" means optional.
default Req.-URI To From Contact R-R/Route external
user -- o o o o o o
2008/11/11 Gang Liu <gangban.lau@gmail.com>:
> I think "#" must be encoded if we need put it into URI.
>
> As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
> disallowed within the URI syntax.
>
> regards,
> Gang
>
> 2008/11/10 Peter Cai <newptcai@gmail.com>
>>
>> :) Right, that's the problem.
>>
>> As "esacpe" in URI is optional in RFC3261, I have no strong reason to
>> ask the other team to convert %23 to #.
>>
>> Actually I was laughed because I asserted that the escape is a "MUST"
>> before I read the RFC carefully.
>>
>> On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com> wrote:
>> > I guess remote party didn't convert %23 into #.
>> >
>> > regards,
>> > Gang
>> >
>> > On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com>
>> > wrote:
>> >>
>> >> # must be escaped to %23 per the SIP syntax. If the remote party
>> >> requires
>> >> # to appear in the user portion of the URI then it's not conforming to
>> >> the
>> >> standard.
>> >>
>> >> Thanks
>> >> Donald
>> >>
>> >> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com> wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> PJSIP automatically escape "#" to "%23".
>> >>>
>> >>> But in my case, I have to have "#" un-escaped in the message.
>> >>>
>> >>> I've skimmed the documents of PJSIP but didn't found any clues how to
>> >>> change this behavior.
>> >>>
>> >>> Has anyone ever met the same problem?
>> >>>
>> >>> _______________________________________________
>> >>> Visit our blog: http://blog.pjsip.org
>> >>>
>> >>> pjsip mailing list
>> >>> pjsip@lists.pjsip.org
>> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >>
>> >>
>> >> _______________________________________________
>> >> Visit our blog: http://blog.pjsip.org
>> >>
>> >> pjsip mailing list
>> >> pjsip@lists.pjsip.org
>> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >>
>> >
>> >
>> > _______________________________________________
>> > Visit our blog: http://blog.pjsip.org
>> >
>> > pjsip mailing list
>> > pjsip@lists.pjsip.org
>> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >
>> >
>>
>>
>>
>> --
>>
>> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip@lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
--
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
GL
Gang Liu
Wed, Nov 12, 2008 11:04 AM
Yes, user part could be normal format if we put user into URI.
But URI spec don't allow '#' within URI syntax.
So I think if it is bad if we put '#' into user part without escaping
because it isn't a corrent URI.
regards,
Gang
2008/11/12 Peter Cai newptcai@gmail.com
It's not a MUST in RFC3216, it's only OPTIONAL.
See PAGE 152. "o" means optional.
default Req.-URI To From Contact R-R/Route external
user -- o o o o o o
2008/11/11 Gang Liu gangban.lau@gmail.com:
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai newptcai@gmail.com
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com
wrote:
must be escaped to %23 per the SIP syntax. If the remote party
requires
to appear in the user portion of the URI then it's not conforming
Hi all,
PJSIP automatically escape "#" to "%23".
But in my case, I have to have "#" un-escaped in the message.
I've skimmed the documents of PJSIP but didn't found any clues how
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
Yes, user part could be normal format if we put user into URI.
But URI spec don't allow '#' within URI syntax.
So I think if it is bad if we put '#' into user part without escaping
because it isn't a corrent URI.
regards,
Gang
2008/11/12 Peter Cai <newptcai@gmail.com>
> It's not a MUST in RFC3216, it's only OPTIONAL.
>
> See PAGE 152. "o" means optional.
>
> default Req.-URI To From Contact R-R/Route external
> user -- o o o o o o
>
>
> 2008/11/11 Gang Liu <gangban.lau@gmail.com>:
> > I think "#" must be encoded if we need put it into URI.
> >
> > As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
> > disallowed within the URI syntax.
> >
> > regards,
> > Gang
> >
> > 2008/11/10 Peter Cai <newptcai@gmail.com>
> >>
> >> :) Right, that's the problem.
> >>
> >> As "esacpe" in URI is optional in RFC3261, I have no strong reason to
> >> ask the other team to convert %23 to #.
> >>
> >> Actually I was laughed because I asserted that the escape is a "MUST"
> >> before I read the RFC carefully.
> >>
> >> On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com>
> wrote:
> >> > I guess remote party didn't convert %23 into #.
> >> >
> >> > regards,
> >> > Gang
> >> >
> >> > On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com>
> >> > wrote:
> >> >>
> >> >> # must be escaped to %23 per the SIP syntax. If the remote party
> >> >> requires
> >> >> # to appear in the user portion of the URI then it's not conforming
> to
> >> >> the
> >> >> standard.
> >> >>
> >> >> Thanks
> >> >> Donald
> >> >>
> >> >> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com>
> wrote:
> >> >>>
> >> >>> Hi all,
> >> >>>
> >> >>> PJSIP automatically escape "#" to "%23".
> >> >>>
> >> >>> But in my case, I have to have "#" un-escaped in the message.
> >> >>>
> >> >>> I've skimmed the documents of PJSIP but didn't found any clues how
> to
> >> >>> change this behavior.
> >> >>>
> >> >>> Has anyone ever met the same problem?
> >> >>>
> >> >>> _______________________________________________
> >> >>> Visit our blog: http://blog.pjsip.org
> >> >>>
> >> >>> pjsip mailing list
> >> >>> pjsip@lists.pjsip.org
> >> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Visit our blog: http://blog.pjsip.org
> >> >>
> >> >> pjsip mailing list
> >> >> pjsip@lists.pjsip.org
> >> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Visit our blog: http://blog.pjsip.org
> >> >
> >> > pjsip mailing list
> >> > pjsip@lists.pjsip.org
> >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >>
> >>
> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
> >> _______________________________________________
> >> Visit our blog: http://blog.pjsip.org
> >>
> >> pjsip mailing list
> >> pjsip@lists.pjsip.org
> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
> > _______________________________________________
> > Visit our blog: http://blog.pjsip.org
> >
> > pjsip mailing list
> > pjsip@lists.pjsip.org
> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
>
>
>
> --
>
> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
GL
Gang Liu
Wed, Nov 12, 2008 11:10 AM
There are two questions:
1, whether we need escape user chars when building Req-URI. the answer is
OPTIONAL;
2, whether '#' allowed within URI. I think answer is NO.
So
sip:11111#22222@example.com isn't a correct SIP URI
regards,
Gang
2008/11/12 Gang Liu gangban.lau@gmail.com
Yes, user part could be normal format if we put user into URI.
But URI spec don't allow '#' within URI syntax.
So I think if it is bad if we put '#' into user part without escaping
because it isn't a corrent URI.
regards,
Gang
2008/11/12 Peter Cai newptcai@gmail.com
It's not a MUST in RFC3216, it's only OPTIONAL.
See PAGE 152. "o" means optional.
default Req.-URI To From Contact R-R/Route external
user -- o o o o o o
2008/11/11 Gang Liu gangban.lau@gmail.com:
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai newptcai@gmail.com
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com
wrote:
must be escaped to %23 per the SIP syntax. If the remote party
requires
to appear in the user portion of the URI then it's not conforming
Hi all,
PJSIP automatically escape "#" to "%23".
But in my case, I have to have "#" un-escaped in the message.
I've skimmed the documents of PJSIP but didn't found any clues how
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
There are two questions:
1, whether we need escape user chars when building Req-URI. the answer is
OPTIONAL;
2, whether '#' allowed within URI. I think answer is NO.
So
sip:11111#22222@example.com isn't a correct SIP URI
regards,
Gang
2008/11/12 Gang Liu <gangban.lau@gmail.com>
> Yes, user part could be normal format if we put user into URI.
> But URI spec don't allow '#' within URI syntax.
> So I think if it is bad if we put '#' into user part without escaping
> because it isn't a corrent URI.
>
> regards,
> Gang
>
> 2008/11/12 Peter Cai <newptcai@gmail.com>
>
> It's not a MUST in RFC3216, it's only OPTIONAL.
>>
>> See PAGE 152. "o" means optional.
>>
>> default Req.-URI To From Contact R-R/Route external
>> user -- o o o o o o
>>
>>
>> 2008/11/11 Gang Liu <gangban.lau@gmail.com>:
>> > I think "#" must be encoded if we need put it into URI.
>> >
>> > As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
>> > disallowed within the URI syntax.
>> >
>> > regards,
>> > Gang
>> >
>> > 2008/11/10 Peter Cai <newptcai@gmail.com>
>> >>
>> >> :) Right, that's the problem.
>> >>
>> >> As "esacpe" in URI is optional in RFC3261, I have no strong reason to
>> >> ask the other team to convert %23 to #.
>> >>
>> >> Actually I was laughed because I asserted that the escape is a "MUST"
>> >> before I read the RFC carefully.
>> >>
>> >> On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com>
>> wrote:
>> >> > I guess remote party didn't convert %23 into #.
>> >> >
>> >> > regards,
>> >> > Gang
>> >> >
>> >> > On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> # must be escaped to %23 per the SIP syntax. If the remote party
>> >> >> requires
>> >> >> # to appear in the user portion of the URI then it's not conforming
>> to
>> >> >> the
>> >> >> standard.
>> >> >>
>> >> >> Thanks
>> >> >> Donald
>> >> >>
>> >> >> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com>
>> wrote:
>> >> >>>
>> >> >>> Hi all,
>> >> >>>
>> >> >>> PJSIP automatically escape "#" to "%23".
>> >> >>>
>> >> >>> But in my case, I have to have "#" un-escaped in the message.
>> >> >>>
>> >> >>> I've skimmed the documents of PJSIP but didn't found any clues how
>> to
>> >> >>> change this behavior.
>> >> >>>
>> >> >>> Has anyone ever met the same problem?
>> >> >>>
>> >> >>> _______________________________________________
>> >> >>> Visit our blog: http://blog.pjsip.org
>> >> >>>
>> >> >>> pjsip mailing list
>> >> >>> pjsip@lists.pjsip.org
>> >> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Visit our blog: http://blog.pjsip.org
>> >> >>
>> >> >> pjsip mailing list
>> >> >> pjsip@lists.pjsip.org
>> >> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >> >>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Visit our blog: http://blog.pjsip.org
>> >> >
>> >> > pjsip mailing list
>> >> > pjsip@lists.pjsip.org
>> >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >>
>> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
>> >> _______________________________________________
>> >> Visit our blog: http://blog.pjsip.org
>> >>
>> >> pjsip mailing list
>> >> pjsip@lists.pjsip.org
>> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >
>> >
>> > _______________________________________________
>> > Visit our blog: http://blog.pjsip.org
>> >
>> > pjsip mailing list
>> > pjsip@lists.pjsip.org
>> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >
>> >
>>
>>
>>
>> --
>>
>> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip@lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>
>
HC
Hoi-Ho Chan
Mon, Nov 17, 2008 5:48 PM
I think we have misunderstanding here, this is Table 1 of RFC3261, and it
describes whether certain URI components can be included in a SIP URI.
"user" is clearly optional because in a SIP REGISTER it's not included in
the request URI but the host portion is mandatory.
If you look a little bit down section 19.1.2, here is the paragraph:
For each component, the set of valid BNF expansions defines exactly which
characters may appear unescaped. All other characters MUST be escaped.
is not in the list of characters which may appear unescaped in the user
component. Hence it MUST be escaped.
Thanks
Donald
2008/11/12 Peter Cai newptcai@gmail.com
It's not a MUST in RFC3216, it's only OPTIONAL.
See PAGE 152. "o" means optional.
default Req.-URI To From Contact R-R/Route external
user -- o o o o o o
2008/11/11 Gang Liu gangban.lau@gmail.com:
I think "#" must be encoded if we need put it into URI.
As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
disallowed within the URI syntax.
regards,
Gang
2008/11/10 Peter Cai newptcai@gmail.com
:) Right, that's the problem.
As "esacpe" in URI is optional in RFC3261, I have no strong reason to
ask the other team to convert %23 to #.
Actually I was laughed because I asserted that the escape is a "MUST"
before I read the RFC carefully.
On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu gangban.lau@gmail.com
I guess remote party didn't convert %23 into #.
regards,
Gang
On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan hoiho.chan@gmail.com
wrote:
must be escaped to %23 per the SIP syntax. If the remote party
requires
to appear in the user portion of the URI then it's not conforming
Hi all,
PJSIP automatically escape "#" to "%23".
But in my case, I have to have "#" un-escaped in the message.
I've skimmed the documents of PJSIP but didn't found any clues how
有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
I think we have misunderstanding here, this is Table 1 of RFC3261, and it
describes whether certain URI components can be included in a SIP URI.
"user" is clearly optional because in a SIP REGISTER it's not included in
the request URI but the host portion is mandatory.
If you look a little bit down section 19.1.2, here is the paragraph:
For each component, the set of valid BNF expansions defines exactly which
characters may appear unescaped. All other characters MUST be escaped.
# is not in the list of characters which may appear unescaped in the user
component. Hence it MUST be escaped.
Thanks
Donald
2008/11/12 Peter Cai <newptcai@gmail.com>
> It's not a MUST in RFC3216, it's only OPTIONAL.
>
> See PAGE 152. "o" means optional.
>
> default Req.-URI To From Contact R-R/Route external
> user -- o o o o o o
>
>
> 2008/11/11 Gang Liu <gangban.lau@gmail.com>:
> > I think "#" must be encoded if we need put it into URI.
> >
> > As I know, RFC 2396 says '#' is excluded US-ASCII character, '#' is
> > disallowed within the URI syntax.
> >
> > regards,
> > Gang
> >
> > 2008/11/10 Peter Cai <newptcai@gmail.com>
> >>
> >> :) Right, that's the problem.
> >>
> >> As "esacpe" in URI is optional in RFC3261, I have no strong reason to
> >> ask the other team to convert %23 to #.
> >>
> >> Actually I was laughed because I asserted that the escape is a "MUST"
> >> before I read the RFC carefully.
> >>
> >> On Mon, Nov 10, 2008 at 5:57 PM, Gang Liu <gangban.lau@gmail.com>
> wrote:
> >> > I guess remote party didn't convert %23 into #.
> >> >
> >> > regards,
> >> > Gang
> >> >
> >> > On Mon, Nov 10, 2008 at 3:41 PM, Hoi-Ho Chan <hoiho.chan@gmail.com>
> >> > wrote:
> >> >>
> >> >> # must be escaped to %23 per the SIP syntax. If the remote party
> >> >> requires
> >> >> # to appear in the user portion of the URI then it's not conforming
> to
> >> >> the
> >> >> standard.
> >> >>
> >> >> Thanks
> >> >> Donald
> >> >>
> >> >> On Sun, Nov 9, 2008 at 8:21 PM, Peter Cai <newptcai@gmail.com>
> wrote:
> >> >>>
> >> >>> Hi all,
> >> >>>
> >> >>> PJSIP automatically escape "#" to "%23".
> >> >>>
> >> >>> But in my case, I have to have "#" un-escaped in the message.
> >> >>>
> >> >>> I've skimmed the documents of PJSIP but didn't found any clues how
> to
> >> >>> change this behavior.
> >> >>>
> >> >>> Has anyone ever met the same problem?
> >> >>>
> >> >>> _______________________________________________
> >> >>> Visit our blog: http://blog.pjsip.org
> >> >>>
> >> >>> pjsip mailing list
> >> >>> pjsip@lists.pjsip.org
> >> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Visit our blog: http://blog.pjsip.org
> >> >>
> >> >> pjsip mailing list
> >> >> pjsip@lists.pjsip.org
> >> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Visit our blog: http://blog.pjsip.org
> >> >
> >> > pjsip mailing list
> >> > pjsip@lists.pjsip.org
> >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >>
> >>
> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
> >> _______________________________________________
> >> Visit our blog: http://blog.pjsip.org
> >>
> >> pjsip mailing list
> >> pjsip@lists.pjsip.org
> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
> > _______________________________________________
> > Visit our blog: http://blog.pjsip.org
> >
> > pjsip mailing list
> > pjsip@lists.pjsip.org
> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
>
>
>
> --
>
> 有一种人,不知道是因为DNA的变异还是前世的夙缘,总是无法安稳下来。他们的生命之流如同咆哮奔涌的大河,没有一刻能够停顿下来。在寂静无人的深夜里,无梦相扰的安睡中,心中也有猛兽会随时醒来,躁动不安,永无宁日。
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip@lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>