Dear Guillaume,
Many thanks for your response, actually I asked the provider to make the authorization name the same as the Tel. number which solved my problem and the client registered successfully and smoothly made calls.
So I will follow the steps u advised in case I have to deal with the old configuration, and sure will keep you updated.
My Q now, why making the Auth. number the same as the Tel. number solved my problem:)?, Does the client provide the tel. number implicitly in the authorization process as an authorization username?
Many thanks in advance,On Mon, Jan 16, 2012 at 9:51 AM, Guillaume BERAUDO
<address@hidden> wrote:
Hi Ahmed,
I am sorry for not answering you earlier.
Your email get burried and I only found it this morning.
> While investigating the Android code base, I found that the class
> called "LinphoneAuthInfoImpl" I found this method:
> > private native long newLinphoneAuthInfo(String username, String
> > userid, String passwd, String ha1,String realm);
Nice
> which the "LinphoneAuthInfoImpl" calls it passing the "userid" with
> "null". What is this "userid"? Is it the Authorization username I'm
> seeking for? How can I properly pass the Authorization username to
> the Linphone core?
I think it is the one you are looking for.
You should:
- add a constructor on the model of the current one, with the userId;
- add a factor method "createAuthInfo" in LinphoneCoreFactoryImpl;
- fix the newLinphoneAuthInfo function in linphonecore_jni.cc;
- update relevant java interfaces;
- update UI.
If you do all this and it works for you, feel free to contribute a
patch to the mailinglist.
Guillaume