News & Reviews
More How-To's & Tips More News
More Reviews Device Configuration Tools
No account yet? Create one
Forgot your Username or Password?

Welcome to the Voxilla VoIP Forum.

Voxilla has been a trusted source for accurate, up-to-date information on the IP Communications industry since 2002. A dedicated staff of reporters and engineers produce feature articles and product reviews to keep industry watchers abreast of the people, companies, and trends driving a fast moving market.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact us.





Closed Thread
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old November 22nd, 2006, 09:04 PM
hfrisch hfrisch is offline
Member
 
Join Date: Feb 2006
Location: NJ USA
Posts: 31
hfrisch
Default Configuring the UTStarcom F3000 for BroadVoice

To configure the UTStarcom F3000 for BroadVoice BYOD, the following SIP settings should work fine:

The settings for the F3000 for BroadVoice, under their “Bring Your Own Device” plans should be:

Press Menu - WiFi Settings - Signal Protocol - SIP - Select one of the 3 profiles - Set
Go through the items on that menu one at a time (from the top):
SIP Register Server Mode = DNS (not IP)
SIP Register Server Domain = sip.broadvoice.com
SIP Register Server IP Address = 0.0.0.0 (not used if DNS)
SIP Register Server Port = 5060
SIP Outbound Proxy = DNS (not IP)
SIP Outbound Server Domain = proxy.broadvoice.com (proxy.dca.broadvoice.com, proxy.lax.boradvoice.com, proxy.nyc.broadvoice.com, or proxy.chi.broadvoice.com are also valid choices here, though proxy.broadvoice.com will let the DNS server pick)
SIP Outbound Server IP Address = 0.0.0.0 (not used if DNS)
SIP Outbound Server Port = 5060
SIP User Name = your phone number
SIP Authentication String = your phone number (note: This could be different if Sim-Ring is used)
SIP Password = your password from Account Settings (note: This is NOT the web login password for managing your account – it is a random set of 10 numbers and letters)
To administer the SIP Password, you need to enter the security code for the phone (default is 888888)
SIP Profile = what ever string you would like to display when the phone is registered and on standby. I use BV followed by my phone number.
Attached Images
File Type: jpg BV F3000 Screen.jpg (11.9 KB, 14 views)

Last edited by hfrisch : November 22nd, 2006 at 09:11 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
  #2 (permalink)  
Old November 23rd, 2006, 12:04 PM
acorbeil acorbeil is offline
Junior Member
 
Join Date: Oct 2006
Posts: 28
acorbeil is on a distinguished road
Default Re: Configuring the UTStarcom F3000 for BroadVoice

Here are some more info for BV setup:

In Local Network Config set the following:
- Primary DNS Server IP Address: 147.135.0.6
- Secondary DNS Server IP Address: 147.135.8.6
- DNS Server IP Address Source: Get DNS Server IP Address From Local Address

In RTP and STUN
DNS Query Type to SRV (Service Record)

This enables you to have an Outbound proxy like:
proxy-lax.broadvoice.com

As I understand it, it would allow Broadvoice to redirect the proxy if they are having problems/maintenance issues without affecting you.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
  #3 (permalink)  
Old November 23rd, 2006, 04:01 PM
hfrisch hfrisch is offline
Member
 
Join Date: Feb 2006
Location: NJ USA
Posts: 31
hfrisch
Default Re: Configuring the UTStarcom F3000 for BroadVoice

The DNS servers specified are the BV DNS servers. This would let them redirect queries to proxy.broadvoice.com (rather than to a specific location).

With respect to the DNS type - you can use DNS-SRV if you use the proxy-lax.broadvoice.com format. If you use proxy-lax, then DNS-SRV will work and no SRV will not work. Similarly, if you use proxy.lax.broadvoice.com, the phone will work OK with DNS-SRV off, but will NOT work with DNS-SRV on (the phone has 4 DNS servers - 2 local, 2 from DHCP - it will check all 4 for the SRV response and give up rather than fall back to A-Record).
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
  #4 (permalink)  
Old November 28th, 2006, 08:39 PM
acorbeil acorbeil is offline
Junior Member
 
Join Date: Oct 2006
Posts: 28
acorbeil is on a distinguished road
Default Re: Configuring the UTStarcom F3000 for BroadVoice

The DNS-SRV option should be set on each SIP and not be global. With DNS-SRV on it works for BV but not for FWD. Also with more memory in these phones it would be nice to have all the SIPs working at the same time.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:



Similar Threads for: Configuring the UTStarcom F3000 for BroadVoice
Thread Thread Starter Forum Replies Last Post
How to Configure UTstarcom F3000 miroesq Other Hardware/Software 18 January 5th, 2007 07:35 PM
Configuring Polycom 501 For Broadvoice knapp910 Polycom VoIP Support Forum 0 October 12th, 2006 12:50 AM
UTstarcom F3000 Wifi VoIP Phone 802.11 b/g and Asterisk ferdies Asterisk Support Forum 1 August 9th, 2006 08:45 PM
Configuring Cisco IP Communicator with BroadVoice..Need Help jayshen BroadVoice Support Forum 0 June 23rd, 2005 08:13 AM
Help configuring SPA-841 with BroadVoice slicemaster101 BroadVoice Support Forum 19 April 23rd, 2005 10:29 PM



All times are GMT. The time now is 06:35 PM.


vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd. SEO by vBSEO 3.0.0 ©2007, Crawlability, Inc. Logos and trademarks are the property of Voxilla or their respective owner. All other content © 2003-2007 by Voxilla, Inc.