[miroesq]

i just got a UTstarcomm F3000 and for the life of me, can't figure out how to set it up. i know how my settings should be, but their instructions are super confusing, especially the part about sip terminal use outbound proxy and use DNS or IP for proxy.

i have axvoice with the following softphone settings:

SIP Username = SIP Username
Authorization user = SIP Username
Password = SIP Password
Domain realm: sip.axvoice.com
SIP proxy = sip.axvoice.com
use outbound proxy: Never
Sent internal IP: Default
Register: Always
Voicemail Sip URL: none (leave it blank)
STUN Server = sip.axvoice.com
DNS Primary = 216.143.132.20
DNS Secondary = 216.143.132.21

i have all my settings set correctly, but the phone is just not registering. i set the sip terminal use outbound proxy to no, which is correct, but in the couple of set-up instructions i saw Pipeline Telecom..VOiP, PC-to-Phone, SMS, Callback UT Starcom F3000 Web Configuration and the like, they always have it set to yes, so i tried it and it is still not working.



any help is highly appreciated thanks

[hfrisch]

Put sip.axvoice.com into the Outbound Proxy field and then set the phone to use the outbound proxy. Also, leave the phone with both registrar and proxy using DNS (rather than IP).

[hfrisch]

I just noticed another likely problem: Your post shows your STUN server as sip.axvoice.com. My guess is that you should change that to stun.axvoice.com. If the STUN request goes to the SIP server, it is likely that the server will not respond and then the phone will not be able to send registration messages since it won't know it's own public IP - from STUN.

If you look in the phone's local log and don't see any "Register out" messages, that is the likely cause.

[miroesq]

Originally Posted by hfrisch

Put sip.axvoice.com into the Outbound Proxy field and then set the phone to use the outbound proxy. Also, leave the phone with both registrar and proxy using DNS (rather than IP).

i already tried that and it didn't work. the phone would make one call and that would be that. one way audio issues thereafter.

[miroesq]

Originally Posted by hfrisch

My guess is that you should change that to stun.axvoice.com.

will try this and let you know

Originally Posted by hfrisch

If you look in the phone's local log and don't see any "Register out" messages, that is the likely cause.

the phone registers, but only for a minute or so. or is this message referring to something else?


thanks a lot for the help

[hfrisch]

What software release is this phone running? Current phones are shipping with 5.6 and there is a 5.9 beta available.

If it registers at all - with the sip server set in the outbound proxy field - then I would suggest leaving it that way.

If you are getting one way audio, that could be due to NAT (the packets are not finding their way back to you) or it could be due to the phone/server negotiating an RTP port that the firewall is blocking. For the RTP traffic outbound from the phone, you can try changing the RTP port (default is 10100 - you can change to 8000 or something in that range). If the server is picking a blocked port, then there is not much to be done - though if other devices work, that is not likely the problem.

[miroesq]

Originally Posted by hfrisch

What software release is this phone running? Current phones are shipping with 5.6 and there is a 5.9 beta available.

I'm using 5.6. Does the 5.9 address the issue we are having below?

Originally Posted by hfrisch

If it registers at all - with the sip server set in the outbound proxy field - then I would suggest leaving it that way.

It does register, but the problem is that it does not keep it's registration. After one call, in or out, the registration is dropped or something as we are no longer able to make or receive calls, we have to restart the phone.

thanks buddy

[hfrisch]

I have not seen the problem so I can't say if 5.9 would do any better than 5.6. I would say that if you have in a phone that had been upgraded at some point (label under the battery says something older for software releases) and not reset, then a reset of SIP and WiFi may cure your problem.

5.9 may help as well - other things seem to be better, mostly roaming and the trouble where the phone uses up the battery in a big hurry when not registered.

[miroesq]

Originally Posted by hfrisch

I would say that if you have in a phone that had been upgraded at some point (label under the battery says something older for software releases) and not reset, then a reset of SIP and WiFi may cure your problem.

it is literally one of the first phone. it had firmware 1.62 or something like that. i will try a reset and let you know.

where can i get a copy of the new firmware?

thanks

[hfrisch]

If the phone was one of the first and had never been reset, then a reset may fix a lot. There were several WPA and WEP related variable as well as hand over thresholds that were added and that did not have values initially. A reset will initialize those things (even if they are not visible).

As for 5.9st,m you should be able to get it from the same dealers who sold the phones - where did you get yours?