I found out the same. It is automatically handled by the
RegisterAgent, but there seems to be another problem at reading out
some data. So the "realm" and "username" values can not be read out
although they were defined.
I just assigned them my standard values and will take care of that
problem later.

After doing that the demo application also sends a second request
containing the authorization data. But this request is also still
answered with a 401 error.
There's at least one more error....

Andrea, did you change anything in the code or did you just run it and
the app works perfectly?
Did you just try the call functionality or also the register function
by using a sip server?

Making calls isn't also a problem. That now (after rebuilding the
project) works. But the register functionality not....




On 9 Jul., 13:00, "Andrea Bernardi" <[EMAIL PROTECTED]> wrote:
> Yes, is a standard procedure for digest-authentication.
> The MjSip MjSip should manage this situation, in the code present in
> RegisterAgent.java in the function onTransFailureResponse.
> Maybe you can debug this section to see if there is an error.
>
> Best Regards,
> Andrea Bernardi
>
> 2008/7/9 andyn <[EMAIL PROTECTED]>:
>
>
>
> > Hi,
>
> > yes, I've tried both the name and the id after the "@". But what I
> > just found out:
> > if I try the same (registering on the sip server) with x-lite, the
> > same error comes up. So after the first request of x-lite, the
> > response contains also a 401 error saying the same like on Android /
> > the demo application (unauthorized). The difference between the demo
> > application and x-Lite:
> > x-Lite sends a request AGAIN, and the second request also contains the
> > authorization data that looks like this:
>
> > Authorization:
> > Digest username="xxx",
> > realm="xx.somewhere.com",
> > nonce="4874614acf6992cbc7cd3681a342ec2f0392180a",
> > uri="sip:xx.somewhere.com",
> > response="e5fa2fe1b25087b2632c64f8ae006503",
> > algorithm=MD5
>
> > So what I'm now trying to do is to get the application sending these
> > authorization data too after the first response.
>
> > I don't know if it is a normal procedure that first a request is sent
> > without the authorization data and when it fails the second request
> > contains this data or if it is a server specific problem...any
> > ideas???
>
> > On 8 Jul., 10:30, "Zhihong GUO" <[EMAIL PROTECTED]> wrote:
> > > Have you try a user id followed by @xx.xx.xx.xx where xx.xx.xx.xx is the
> > > server ip.
>
> > > 2008/7/8 andyn <[EMAIL PROTECTED]>:
>
> > > > Hi there,
>
> > > > have anyone tried to get the demo application running included in the
> > > > MjSip zip package from HSC?
> > > > The whole zip package can be downloaded under:
>
> > > >http://www.hsc.com/resourceCenter/resource.aspx
>
> > > > I used Wireshark for checking the data transmitted to my sip server.
> > > > But there's only one request been sent which is answered by the server
> > > > with an "401 Unauthorized". To register again (to start a new try) the
> > > > emulator must be restarted.
>
> > > > I checked the authentication data by running x-lite on my notebook and
> > > > it works. So it doesn't seem to be a server problem does it? And data
> > > > is transmitted to server (hence it isn't a forwarding / firewall
> > > > problem)...
>
> > > > Any suggestions?
> > > > I hope to get some help...
>
> > > > Thanks
>
> > > > Andy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to