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.





Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old August 8th, 2007, 07:52 PM
gpant gpant is offline
Junior Member
 
Join Date: Feb 2007
Posts: 11
gpant is on a distinguished road
Default WIP330 & SPA9000 setup problems

Hi, I am trying to setup my WIP330 with my SPA9000 and have some problems. The 9k has 16 extensions and I have 7 SPA942 and 3 SPA941 fully working on it using 2 voip providers and 1 spa3102 only used for incoming calls.

My problem is this, when I make a call through the WIP<>ITSP although the others can hear me I dont instead I listen to weird noises(depending on witch encoding I use). I cant call any other extensions through the phone instead it diverts the call to the ITSP. If I call the WIP through another phone using its extension I can have a proper conversation(really good quality).

My WIP Setup is:

SIP : 104 @ <9k IP> : 6060
SIP Proxy: <9k IP>
Port: 6060
Registrar :<9k IP>
Port :6060
Expiry:3600
Timer:0
Display:WIP
SIP Format:Normal
Outbound Proxy: *(I tried both with setting this to <9k IP> and blank)
Port:
Name: 104
Password:

Payload: *(Tried All)
Packet: Small
DTMF Relay: Disabled (I cant set it to enabled it always reverts to disabled)
UDP: 5060
RTP: 16384

QoS
SIP : 68
RTP: b8

Edit:
I am using an WRT54GL with OpenWRT Firmware
WPA-PSK (WIP330 cant handle a full key so I am using a short one)
Static IP
The phone registers with the 9k and it shows under the PBX Status with its extension

Last edited by gpant : August 8th, 2007 at 07:57 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old August 10th, 2007, 11:59 AM
gpant gpant is offline
Junior Member
 
Join Date: Feb 2007
Posts: 11
gpant is on a distinguished road
Default Re: WIP330 & SPA9000 setup problems

Anyone here managed to register his WIP330 on a SPA9000 and have it fully working? if so care to share your settings?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old August 14th, 2007, 11:55 AM
Walford58 Walford58 is offline
Senior Member
 
Join Date: Jul 2007
Location: West Midlands, UK
Posts: 222
Walford58 is on a distinguished road
Default Re: WIP330 & SPA9000 setup problems

Hi
I'm putting together a small system myself based on WIP330 SPA9k and SPA400 with some softphones.

I use the test facility with the ITSP to check the delay, echo and general quality of call. Find out what the contact number is for your ITSP as they also vary according to whether you can record, echo or just listen.

The settings do depend on the configuration of the 9k, but my WIP Setup is:

SIP : 202@ <9k IP> : 5070
SIP Proxy: <9k IP>
Port: 5070
Registrar :<9k IP>
Port :5070
Expiry:3600
Timer:0
Display:NONE
SIP Format:Normal
Outbound Proxy: <9k IP>
Port: 6060 (this is set as the proxy listen port on the SIP tab in the 9k)
Name: 202
Password: <password as defined in the 9k SIP tab for PBX ext password)

Payload: G729, G711a, G711u
Packet: Small
DTMF Relay: Disabled
UDP: 5060
RTP: 8000

QoS
SIP :
RTP:

This is still a work in progress, but seems to function OK

9k firmware is 5.1.8 and WIP firmware 1.02.12S
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old August 14th, 2007, 01:44 PM
humba3 humba3 is offline
Senior Member
 
Join Date: Jun 2006
Posts: 1,075
humba3 is an unknown quantity at this point
Default Re: WIP330 & SPA9000 setup problems

Is there any particular reason you have the proxy and registrar port set to 5070 but the outbound proxy to 6060? Didn't you mistype anywhere as this configuration isn't supposed to work.. you'd either get outgoing calls (the INVITE being sent to port 6060 on the SPA9k), or can't even register (the proxy port on the SPA9k being either 5070 or 6060 both not both.. according to your message it's 6060 - so that leaves us with two choices: either the phone still sends REGISTER packets to port 6060 regardless of the 5070 setting, or you mistyped... the SPA9000 won't accept registrations on the wrong port).

Unless you activated passwords, you won't need a password on any phone you connect to the SPA9k - you also won't need an outbound proxy (in fact many IPTSPs indicate OBs even though it's the same box as the proxy/registrar which shows that they don't quite get what the OB is for either).
__________________
There are two essential pieces to tracking down a problem with your VoIP equipment:
  • The configuration of every device involved
  • SIP protocol traces
And don't forget: there's no such thing as giving too much information when describing a problem.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old August 14th, 2007, 03:33 PM
Walford58 Walford58 is offline
Senior Member
 
Join Date: Jul 2007
Location: West Midlands, UK
Posts: 222
Walford58 is on a distinguished road
Default Re: WIP330 & SPA9000 setup problems

Quote:
Originally Posted by humba3 View Post
Is there any particular reason you have the proxy and registrar port set to 5070 but the outbound proxy to 6060? Didn't you mistype anywhere as this configuration isn't supposed to work.. you'd either get outgoing calls (the INVITE being sent to port 6060 on the SPA9k), or can't even register (the proxy port on the SPA9k being either 5070 or 6060 both not both.. according to your message it's 6060 - so that leaves us with two choices: either the phone still sends REGISTER packets to port 6060 regardless of the 5070 setting, or you mistyped... the SPA9000 won't accept registrations on the wrong port).
I double checked and it was not mistyped. However the SPA9k proxy listen port was set to 6060. I've tried a few alternative configurations and it appears the WIP330 requires a unique port to connect to as it would not register to 5060, 5061, 5062 or 5080. I had set the SIP ports range to between 5060 and 5080, so I have now set the listen port to 5079 and this seems to connect fine again. The proxy is set to WAN so I sort of see some logic there.
I'm also experiencing loss of sound from me to the called party using the Plusnet SIP account to PSTN, although I have no problem hearing them clearly. The test call to Plusnet is clear as well in both directions. Is it possible this selection of ports might affect the audio, even though it's fine with the Plusnet network?

Quote:
Originally Posted by humba3 View Post
Unless you activated passwords, you won't need a password on any phone you connect to the SPA9k
It apears that most of the softphones require a password field, and I want to be able to restrict which devices connect, so this works for me at the moment. By taking out the password on the SPA9k, the WIP330 still connects with a password field entered and none in the SPA9k, but not the other way round.

Quote:
Originally Posted by humba3 View Post
you also won't need an outbound proxy (in fact many IPTSPs indicate OBs even though it's the same box as the proxy/registrar which shows that they don't quite get what the OB is for either).
I would agree with you for direct connection - I use Plusnet for one SIP account and Sipgate for the other. Plusnet seems to be very difficult to set up, particularly with NAT and firewalls, but I have now been able to make connection by tweaking a few settings by trial and error. They "require" an OB. Sipgate do not.
However the WIP330 will not register with the SPA9k unless the OB proxy is defined in the settings.

Thanks very much for your input.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Old August 14th, 2007, 03:33 PM
  #6 (permalink)  
Old August 14th, 2007, 08:09 PM
humba3 humba3 is offline
Senior Member
 
Join Date: Jun 2006
Posts: 1,075
humba3 is an unknown quantity at this point
Default Re: WIP330 & SPA9000 setup problems

Can you trace whether the WIP300 sends RTP on port 5070? It has to send SIP messages to port 6060 as this is the port the SPA9000 listens for SIP messages.

Quote:
By taking out the password on the SPA9k, the WIP330 still connects with a password field entered and none in the SPA9k, but not the other way round.
That seems to be a limit of the phone though.. there's no mandatory authentication in SIP.. it's purely optional. And your experiment seems to indicate that the SPA9k ignores any auth header unless it's configured to require a password for registration.

Quote:
However the WIP330 will not register with the SPA9k unless the OB proxy is defined in the settings.
I have a theory on that.. while you have the proper address in the register and proxy server fields, you have the wrong port (trust me.. there ain't no registering unless you send it to port 6060 or whatever proxy port is defined.. I once switched my SPA9k to port 5060 for a change and not a single phone in my network could connect) - but you have the proper port on the OB. If you can, do an Ethereal trace.. I'm convinced it'll show all SIP messages being sent to port 6060 on the SPA9000. And if you change the OB port to something else, you'll see the SIP traffic going there and there won't be a response.
__________________
There are two essential pieces to tracking down a problem with your VoIP equipment:
  • The configuration of every device involved
  • SIP protocol traces
And don't forget: there's no such thing as giving too much information when describing a problem.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old August 14th, 2007, 09:59 PM
Walford58 Walford58 is offline
Senior Member
 
Join Date: Jul 2007
Location: West Midlands, UK
Posts: 222
Walford58 is on a distinguished road
Default Re: WIP330 & SPA9000 setup problems

Quote:
Originally Posted by humba3 View Post
Can you trace whether the WIP300 sends RTP on port 5070? It has to send SIP messages to port 6060 as this is the port the SPA9000 listens for SIP messages.
I've run a trace. SIP messages are only sent to the listening port (was 6060, now 5079) when a call is initiated. To be honest though, I don't understand many of the syslog messages.

Quote:
Originally Posted by humba3 View Post
..while you have the proper address in the register and proxy server fields, you have the wrong port (trust me.. there ain't no registering unless you send it to port 6060 or whatever proxy port is defined.
I agree registration has to be by the proxy port. I haven't worked out whether the other ports are assigned by the SPA9k to the handset, or if its a limitation of the handset, or possibly the proxy port is purely for registration and the other ports are for SIP messages. The trace seems to show messages from the defined port 5066 handed to 5060 of the same IP address.

Quote:
Originally Posted by humba3 View Post
If you can, do an Ethereal trace.. I'm convinced it'll show all SIP messages being sent to port 6060 on the SPA9000. And if you change the OB port to something else, you'll see the SIP traffic going there and there won't be a response.
There you're losing me. I have downloaded Wireshark, but setting up the filters and analysing the information requires a bit more technical know-how than I have at the moment. It did flag up a couple of anomalies which I tracked down.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old August 15th, 2007, 02:42 AM
gpant gpant is offline
Junior Member
 
Join Date: Feb 2007
Posts: 11
gpant is on a distinguished road
Default Re: WIP330 & SPA9000 setup problems

My original settings were correct for use with many ITSP's other than my main one (i-call.gr), I can also make calls through SPA9k SPA3102, but when I make calls through i-call I get garbage. I will need to sniff my wifi router traffic and see if I can pinpoint the problem.

As a side note although initially I could make calls to any extension in spa9k as well as make calls ( I dont use a prefix to call through my main ITSP) now all internal extensions fail immediately, but normal calls pass through (inaudible of course).

The phone also looses connectivity randomly but often, it most of the times reconnects and registers but this reduces battery life to max 4/4.5 hours.

Last edited by gpant : August 15th, 2007 at 02:53 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:



Similar Threads for: WIP330 & SPA9000 setup problems
Thread Thread Starter Forum Replies Last Post
WIP330 working with SPA9000 JoWeaver Linksys SPA9000/SPA400 Support Forum 7 February 5th, 2007 07:17 PM
How to setup spa9000 to get public ip? hp91 Linksys SPA9000/SPA400 Support Forum 1 December 22nd, 2006 12:25 AM
spa9000 with remote spa841 setup problem likuid Linksys SPA9000/SPA400 Support Forum 0 September 27th, 2006 10:29 PM
SP841 setup and configuration problems vergel Linksys (Sipura) VoIP Support Forum 1 June 23rd, 2006 12:54 PM
Linksys WIP330 Setup Help bsdaiwa Linksys (Sipura) VoIP Support Forum 1 June 10th, 2006 03:43 PM



All times are GMT. The time now is 12:28 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.