default  Req.-URI  To  From  Contact   R-R/Route  external

Hi, Thanks a lot, seems that I should carefully re-read the protocol. 2008/11/18 Hoi-Ho Chan <hoiho.chan@gmail.com> > 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 >> > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > -- 而如何让自己的内心产生力量，在于自己而不在于别人。等到一跃而过，回头去看的时候，一个人因此获得了宝贵的经验和自信，下一次就可以面对更宽更深的壕沟。关键在于有多少意愿去面对这种犹豫时刻，因为大部分情况下，我们可以选择绕路的方法而回避这种艰难的选择。

I want to enable TCP in symbian. How to do that? Where is the settings

Does port restricted NAT works with PJSIP. After some investigation I figured that my mobile operator is using Port restricted NAT and I am getting registration time out. I also tried using X-Lite to investigate. Same result. Request time out.

The symbian application is not working with my mobile operator internet. I saw its a port restricted NAT they are using. The STUN resolve the IP address 119.35.38.8 and put the on SIP header. I tried to ping or trace route the IP with No luck. It cant be found. I tried using STUN separate client with different STUN server. The result is same IP. But why the hell it cant be found with tracert? The I connected my PC with the internet from mobile with PC suite and tried X-Lite. X-Lite does not work either. Request time out. The last thing I tried is Fring. Fortunately or Unfortunately it works just fine. But seemed like Fring does use their own proxy server to route the SIP packet??? Anything special going on behind????

The port restricted NAT should work in normal conditions (only symetric NAT has problems with STUN). The problem maybe is not only the NAT of your provider and there are more restrictions on it. Did you try with another sipserver?. About the problem with the ping/tracert, is posible that the ICMP protocol won`t be permited on the sipserver (only 5060UDP). Fring works because uses a proxy server and could have another tecnique to manage the NAT (media proxy, ...) or is less restricted that your actual sipprovider. On Mon, Dec 1, 2008 at 4:39 PM, Rawshan Iajdani <iajdani@provati.com> wrote: > The symbian application is not working with my mobile operator internet. > I saw its a port restricted NAT they are using. The STUN resolve the IP > address 119.35.38.8 and put the on SIP header. I tried to ping or trace > route the IP with No luck. It cant be found. I tried using STUN separate > client with different STUN server. The result is same IP. But why the hell > it cant be found with tracert? > > The I connected my PC with the internet from mobile with PC suite and tried > X-Lite. X-Lite does not work either. Request time out. > > The last thing I tried is Fring. Fortunately or Unfortunately it works just > fine. But seemed like Fring does use their own proxy server to route the SIP > packet??? Anything special going on behind???? > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > -- William Brito

Basically I own my sip server. The only thing I don't won is the internet connectivity from my sip phone to the server. Server IP is fine but I was talking about the client IP resolved by the stun.. From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of William Brito Sent: Tuesday, December 02, 2008 4:50 AM To: pjsip list Subject: Re: [pjsip] How fring works??? The port restricted NAT should work in normal conditions (only symetric NAT has problems with STUN). The problem maybe is not only the NAT of your provider and there are more restrictions on it. Did you try with another sipserver?. About the problem with the ping/tracert, is posible that the ICMP protocol won`t be permited on the sipserver (only 5060UDP). Fring works because uses a proxy server and could have another tecnique to manage the NAT (media proxy, ...) or is less restricted that your actual sipprovider. On Mon, Dec 1, 2008 at 4:39 PM, Rawshan Iajdani <iajdani@provati.com> wrote: The symbian application is not working with my mobile operator internet. I saw its a port restricted NAT they are using. The STUN resolve the IP address 119.35.38.8 and put the on SIP header. I tried to ping or trace route the IP with No luck. It cant be found. I tried using STUN separate client with different STUN server. The result is same IP. But why the hell it cant be found with tracert? The I connected my PC with the internet from mobile with PC suite and tried X-Lite. X-Lite does not work either. Request time out. The last thing I tried is Fring. Fortunately or Unfortunately it works just fine. But seemed like Fring does use their own proxy server to route the SIP packet??? Anything special going on behind???? _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -- William Brito

You sipserver has a publicIP address?. On Mon, Dec 1, 2008 at 5:59 PM, Rawshan Iajdani <iajdani@provati.com> wrote: > Basically I own my sip server. The only thing I don't won is the internet > connectivity from my sip phone to the server. Server IP is fine but I was > talking about the client IP resolved by the stun.. > > > > > > *From:* pjsip-bounces@lists.pjsip.org [mailto: > pjsip-bounces@lists.pjsip.org] *On Behalf Of *William Brito > *Sent:* Tuesday, December 02, 2008 4:50 AM > *To:* pjsip list > *Subject:* Re: [pjsip] How fring works??? > > > > The port restricted NAT should work in normal conditions (only symetric NAT > has problems with STUN). The problem maybe is not only the NAT of your > provider and there are more restrictions on it. Did you try with another > sipserver?. About the problem with the ping/tracert, is posible that the > ICMP protocol won`t be permited on the sipserver (only 5060UDP). > > Fring works because uses a proxy server and could have another tecnique to > manage the NAT (media proxy, ...) or is less restricted that your actual > sipprovider. > > On Mon, Dec 1, 2008 at 4:39 PM, Rawshan Iajdani <iajdani@provati.com> > wrote: > > The symbian application is not working with my mobile operator internet. I > saw its a port restricted NAT they are using. The STUN resolve the IP > address 119.35.38.8 and put the on SIP header. I tried to ping or trace > route the IP with No luck. It cant be found. I tried using STUN separate > client with different STUN server. The result is same IP. But why the hell > it cant be found with tracert? > > The I connected my PC with the internet from mobile with PC suite and tried > X-Lite. X-Lite does not work either. Request time out. > > The last thing I tried is Fring. Fortunately or Unfortunately it works just > fine. But seemed like Fring does use their own proxy server to route the SIP > packet??? Anything special going on behind???? > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > -- > > William Brito > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > -- William Brito