ageet Forums

Well, I test and I test and I test.... I tested a lot of things without good results... I conected from different places, I used different sip ports, I reinstalled agephone mobile ... and in all the cases I have the same problem...""Not registered to sip server". Now I have the problem that the comunication start, sound the phone in the other party side but no one can hear our voices, same problem if the other party call me... Im sending the logs Michel.
Another bugs that I found is with the power saving option, I have the option "Keep Device On: disable" but when I start Agephone mobile the wireless start on also..
A suggestion: Colud you addded a litle notice over the phone number buttons saying if we are connected using wifi or phone? also in options is a good idea to have the conection parameters options like " 1) first wifi, 2)only wifi, 3) first phone. 4) only phone 5)always ask" like Fring soft have..

I'm looking forward to receiving your log files and from what I can see now it seems perfectly normal that you have audio problems if the SIP server is not registered correctly due to network problems. I like your suggestion regarding the network management: Users should know which connection is in use and the connection management should be more fine grained indeed. I will pass this on to our programmers and discuss it with them and I am sure that we will find a good solution to implement these things.

As for your bug report, I am not too sure if I understand you correctly. "Keep Device On: disable" has nothing to do with the wireless connection starting up and "Activate Wireless" is the only option that has any influence on this. Unless you set it to "WiFi" or "3G", AGEphone Mobile should never cause a connection to be started.

On further note: "Keep Device On" was originally intended for some smartphones that lacked a more fine grained power management. This was never the case on touchscreen phones and hence these options shouldn't even be there. I will also discuss this with our programmers and hope that there is a good way to show different menus on both WM editions.

Michael wrote:I'm looking forward to receiving your log files and from what I can see now it seems perfectly normal that you have audio problems if the SIP server is not registered correctly due to network problems.

More data:
While trying to figure out whats going on i made a few test.
In the same network I can make calls from the HTC Touch HD using another two SIP client software, but I cant with Agephonemobile.
My guess is that comunication between AgePhone Mobile and the SIP servers is not working for some reason. Also I tested this in differents places using differents internet providers with equal results.

I hope you can help me.

Thanks

Thank you very much for the log files and if possible, please send your simple and detailed log files (description) to michael // ageet // com for our reference and we will see what we can do for you

Michael wrote:Thank you very much for the log files and if possible, please send your simple and detailed log files (description) to michael // ageet // com for our reference and we will see what we can do for you

Well I were collecting a lot of calls (intention of calls) that I couldnt made with Agephone mobile but I can made with SJPhone. Agephone mobile have a lot of bugs (NAT registration problems, audio,etc..). Im sending the datailed logs to your e-mail.

Thank you very much for the files! We will take a look at the logs and fix any errors we encounter.

I could get my hands on the HTC Touch Diamond and Pro recently and tested them with two different VoIP providers over WiFi and 3G. The voice quality was satisfactory in all the tests and I couldn't reproduce any of the audio quality problems described in this thread. Any problems you experience are not device specific and have other reasons. To mention one in particular since you use voxalot: Please make sure to disable the server side NAT traversal option as I have found it to decrease the call quality significantly. Also, raising the audio buffers by a notch or two definitely helps mending the problems. I am using 120 - 180 for the playback and 120 ms for the recording buffer.

Other than that I can confirm the following problems:

1. AGEphone Mobile does not wake up correctly when a call is received in standby mode. Neither the screen nor the speaker gets activated and thus it is impossible to notice the call. We are working on this and I am looking forward to see this error fixed soon.

2. AGEphone Mobile looses its registration to the SIP server when in standby mode. This always happens after the period set under "Register Expires" runs out. While the softphone re-registers correctly when the phone is active it fails to do so when in standby mode. We are currently looking into this and I hope that our programmers can find a fix.

Michael wrote:1. AGEphone Mobile does not wake up correctly when a call is received in standby mode. Neither the screen nor the speaker gets activated and thus it is impossible to notice the call. We are working on this and I am looking forward to see this error fixed soon.

2. AGEphone Mobile looses its registration to the SIP server when in standby mode. This always happens after the period set under "Register Expires" runs out. While the softphone re-registers correctly when the phone is active it fails to do so when in standby mode. We are currently looking into this and I hope that our programmers can find a fix.

Hi Michael,

I've recently bought my first license of AGEphone Mobile and I'm using it on an HTC Diamond with Windows Mobile 6.1.

Are these standby issues solved in the current AGEphone mobile version (2.80 - 2009.11.10) ?

Thanks!
Alejandro

As far as I know the first issue should be resolved as we faced this behavior also with the Toshiba TG-01 that we have been focusing on in the past months. Please let me know if you experience this error and I will pass your report on to our programmers for another revision.

The second error persists to this day as we were busy with some large contracts and our guys simply didn't have the time. I won't forget reminding them about it if only for the reason that I finally want to see this work correctly on my own Touch Pro 2. Please bear with us a while longer.