Windows Mobile 5 & "MakeCall" Request Timeout

AF
Ayman Farouk
Mon, May 19, 2008 7:08 PM

Dear All,

I have a small configuration, two Windows Mobile devices "WM5.0" and a SIP
Proxy within the same WLAN. I managed to register the devices into the SIP
proxy, but I cannot make calls. Whenever I try to do, I get a request
timeout error. Attached are the two LOG files from the two mobile devices.

Thanks,

--
a.

Dear All, I have a small configuration, two Windows Mobile devices "WM5.0" and a SIP Proxy within the same WLAN. I managed to register the devices into the SIP proxy, but I cannot make calls. Whenever I try to do, I get a request timeout error. Attached are the two LOG files from the two mobile devices. Thanks, -- a.
BP
Benny Prijono
Tue, May 20, 2008 8:43 AM

On Mon, May 19, 2008 at 8:08 PM, Ayman Farouk aymanfm@gmail.com wrote:

Dear All,

I have a small configuration, two Windows Mobile devices "WM5.0" and a SIP
Proxy within the same WLAN. I managed to register the devices into the SIP
proxy, but I cannot make calls. Whenever I try to do, I get a request
timeout error. Attached are the two LOG files from the two mobile devices.

I'm not sure what's causing this, but it looks like the network is
fine and the client sends the correct request. I tend to think that
it's the proxy (192.168.1.113) that for some reason is unable to
respond to the request. Have you configured the client with the
correct route set/proxy? Is the destination URI correct (maybe you
should replace sip:dack@192.168.1.80 with sip:dack@192.168.1.79)?

Cheers
Benny

On Mon, May 19, 2008 at 8:08 PM, Ayman Farouk <aymanfm@gmail.com> wrote: > Dear All, > > I have a small configuration, two Windows Mobile devices "WM5.0" and a SIP > Proxy within the same WLAN. I managed to register the devices into the SIP > proxy, but I cannot make calls. Whenever I try to do, I get a request > timeout error. Attached are the two LOG files from the two mobile devices. > I'm not sure what's causing this, but it looks like the network is fine and the client sends the correct request. I tend to think that it's the proxy (192.168.1.113) that for some reason is unable to respond to the request. Have you configured the client with the correct route set/proxy? Is the destination URI correct (maybe you should replace sip:dack@192.168.1.80 with sip:dack@192.168.1.79)? Cheers Benny > Thanks, > > -- > a. > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >