Empathy List Archives

KT

Knight Tiger

Fri, Oct 12, 2007 1:43 AM

Hi,

I am using a public STUN server (stun.xten.com) to obtain my public IP
address during pjsua initialization. I look at the Ethereal/Wireshark
captures and I find that the pjsip client sends the DNS resolution query
first. (I do not have this entry cached in my network). But it sends more
DNS queries and then starts to send NetBIOS queries and finally timesout and
declares no resolution possible.

I am interested in cutting the timeout for the DNS (and NETBIOS) resolution.
I would like the application to inform the user more speedily than it does
right now. I am running the pjsip client on a windows mobile device. Is the
DNS resolution handled by Windows CE or the PJSIP application handles it ?

What could I do to reduce the query time ?

I thank you all in advance,
Warm regards,
Knight

Hi, I am using a public STUN server (stun.xten.com) to obtain my public IP address during pjsua initialization. I look at the Ethereal/Wireshark captures and I find that the pjsip client sends the DNS resolution query first. (I do not have this entry cached in my network). But it sends more DNS queries and then starts to send NetBIOS queries and finally timesout and declares no resolution possible. I am interested in cutting the timeout for the DNS (and NETBIOS) resolution. I would like the application to inform the user more speedily than it does right now. I am running the pjsip client on a windows mobile device. Is the DNS resolution handled by Windows CE or the PJSIP application handles it ? What could I do to reduce the query time ? I thank you all in advance, Warm regards, Knight

PL

Paul Levin

Fri, Oct 12, 2007 11:24 AM

Knight,
Are you using WireShark on a Windows Mobile device? Can you explain how you're doing that please?
Thanks,
Paul

Knight Tiger wrote: > Hi,

I am using a public STUN server (stun.xten.com) to obtain my public IP address during pjsua initialization. I look at the Ethereal/Wireshark captures and I find that the pjsip client sends the DNS resolution query first. (I do not have this entry cached in my network). But it sends more DNS queries and then starts to send NetBIOS queries and finally timesout and declares no resolution possible.

I am interested in cutting the timeout for the DNS (and NETBIOS) resolution. I would like the application to inform the user more speedily than it does right now. I am running the pjsip client on a windows mobile device. Is the DNS resolution handled by Windows CE or the PJSIP application handles it ?

What could I do to reduce the query time ?

I thank you all in advance,
Warm regards,
Knight
<pre wrap="">
<hr size="4" width="90%"></hr>
_______________________________________________
Visit our blog: <a class="moz-txt-link-freetext" href="http://blog.pjsip.org">http://blog.pjsip.org</a>

pjsip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pjsip@lists.pjsip.org">pjsip@lists.pjsip.org</a>
<a class="moz-txt-link-freetext" href="http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org">http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org</a>
 

KT

Knight Tiger

Fri, Oct 12, 2007 4:59 PM

Paul,
I am not running Wireshark on the WM device. I am sorry about not
being accurate. I had a Computer connected on the same hub as the AP to
which to the WM device connects wirelessly. This computer was running
Wireshark and not the WM device. Although I would love to have Wireshark
running on the WM device :)

Thanks
Knight

On 10/12/07, Paul Levin paul@apcl.us wrote:

Knight,
Are you using WireShark on a Windows Mobile device? Can you explain
how you're doing that please?
Thanks,
Paul

Knight Tiger wrote:

Hi,

I am using a public STUN server (stun.xten.com) to obtain my public IP
address during pjsua initialization. I look at the Ethereal/Wireshark
captures and I find that the pjsip client sends the DNS resolution query
first. (I do not have this entry cached in my network). But it sends more
DNS queries and then starts to send NetBIOS queries and finally timesout and
declares no resolution possible.

I am interested in cutting the timeout for the DNS (and NETBIOS)
resolution. I would like the application to inform the user more speedily
than it does right now. I am running the pjsip client on a windows mobile
device. Is the DNS resolution handled by Windows CE or the PJSIP application
handles it ?

What could I do to reduce the query time ?

I thank you all in advance,
Warm regards,
Knight

Visit our blog: http://blog.pjsip.org

pjsip mailing listpjsip@lists.pjsip.orghttp://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

Paul, I am not running Wireshark on the WM device. I am sorry about not being accurate. I had a Computer connected on the same hub as the AP to which to the WM device connects wirelessly. This computer was running Wireshark and not the WM device. Although I would love to have Wireshark running on the WM device :) Thanks Knight On 10/12/07, Paul Levin <paul@apcl.us> wrote: > > Knight, > Are you using WireShark on a Windows Mobile device? Can you explain > how you're doing that please? > Thanks, > Paul > > > Knight Tiger wrote: > > Hi, > > I am using a public STUN server (stun.xten.com) to obtain my public IP > address during pjsua initialization. I look at the Ethereal/Wireshark > captures and I find that the pjsip client sends the DNS resolution query > first. (I do not have this entry cached in my network). But it sends more > DNS queries and then starts to send NetBIOS queries and finally timesout and > declares no resolution possible. > > I am interested in cutting the timeout for the DNS (and NETBIOS) > resolution. I would like the application to inform the user more speedily > than it does right now. I am running the pjsip client on a windows mobile > device. Is the DNS resolution handled by Windows CE or the PJSIP application > handles it ? > > What could I do to reduce the query time ? > > I thank you all in advance, > Warm regards, > Knight > > ------------------------------ > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing listpjsip@lists.pjsip.orghttp://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 > >

BP

Benny Prijono

Tue, Oct 16, 2007 3:01 PM

Knight Tiger wrote:

 Knight Tiger wrote:

 Hi,

 I am using a public STUN server (stun.xten.com
 <http://stun.xten.com>) to obtain my public IP address during
 pjsua initialization. I look at the Ethereal/Wireshark captures
 and I find that the pjsip client sends the DNS resolution query
 first. (I do not have this entry cached in my network). But it
 sends more DNS queries and then starts to send NetBIOS queries and
 finally timesout and declares no resolution possible.

 I am interested in cutting the timeout for the DNS (and NETBIOS)
 resolution. I would like the application to inform the user more
 speedily than it does right now. I am running the pjsip client on
 a windows mobile device. Is the DNS resolution handled by Windows
 CE or the PJSIP application handles it ?

If you don't configure nameserver in pjsua_config (it looks like you
didn't), then the host resolution will be done by Windows (via
gethostbyname() API). Not sure how we could reduce the query time
for this, maybe you'll find something in MSDN.

cheers,
-benny

 What could I do to reduce the query time ?

Knight Tiger wrote: > Knight Tiger wrote: >> Hi, >> >> I am using a public STUN server (stun.xten.com >> <http://stun.xten.com>) to obtain my public IP address during >> pjsua initialization. I look at the Ethereal/Wireshark captures >> and I find that the pjsip client sends the DNS resolution query >> first. (I do not have this entry cached in my network). But it >> sends more DNS queries and then starts to send NetBIOS queries and >> finally timesout and declares no resolution possible. >> >> I am interested in cutting the timeout for the DNS (and NETBIOS) >> resolution. I would like the application to inform the user more >> speedily than it does right now. I am running the pjsip client on >> a windows mobile device. Is the DNS resolution handled by Windows >> CE or the PJSIP application handles it ? If you don't configure nameserver in pjsua_config (it looks like you didn't), then the host resolution will be done by Windows (via gethostbyname() API). Not sure how we could reduce the query time for this, maybe you'll find something in MSDN. cheers, -benny >> What could I do to reduce the query time ?

pjsip@lists.pjsip.org

STUN DNS resolution timeout -regarding