[shownow]

I just bought a new spa1000,I found it is quite slow to get connected.
when I dail a number,say fwd or sipphone,by using xten or other hard ip phone,the other end will ring immediately.but when I use spa1000,it takes up to 10 sec.to ring.Is there any configuration I can adjust to solve the problem?

[mberlant]

What do your Dial Plans look like? You probably have very generic Dial Plans that must wait until they believe that you have finished dialing before they connect the call.

[shownow]

hello mberlant,thanks for your reply
I bought this spa 1000 from voxilla store and did not change anything except user info. to it. here is my dail plan
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)
anything wrong with it?

btw,what does dail plan mean?can you give a brief explanation.

[shownow]

It seems this problem does not relate on dail plan because it happens on incoming call too.The spa1000 waits 10 sec. to ring after I dail from anthor ip phone.

[mberlant]

What STUN server are you pointing to? I recommend stun.fwdnet.net:3478 (including the :3478). you can find this entry at the bottom of the SIP configuration page. What DNS server are you using? If you don't have any DNS servers listed near the top of the Info page, or if the only entry is your router, you should manually put real DNS server IP addresses into the spots on the System page.

What may be happening is that the STUN server you are using now is very slow to respond to your queries. STUN's function is to tell your client what port your router has assigned if for certain functions, so that it can relay this information on to your VoIP provider's SIP server and calls can be placed and received. STUN is used "twice" in SIP. It is used first when registering with the SIP server. This occurs every 30 minutes on FWD, so an extra 10 seconds won't be noticed by you.

The other time that STUN is used is when placing or receiving a call. Part of the process is to assign the RTP port, which carries the actual voice payload. An incoming call request comes in to your SIP client, which assigns an RTP port and sends that information in the form of a STUN query to any STUN server. Your router sees if the requested RTP port is available and allows the query to go on as requested or changes the query if the requested port is already occupied by another user. Whatever the situation, the STUN server echoes what it hears back to the SIP client, which gives that "public" information to the SIP server. The SIP server then patches the voice path onto the assigned RTP port, rings your phone and you answer the phone and speak.

All of this generally takes about 100 milliseconds. If, however, you have problems communicating with your STUN server this 10 seconds (that you didn't notice once every 30 minutes) becomes very noticeable when the entire process should be taking well under one second.

So, I recommend that you check out both your DNS and STUN settings and see if one of them (I hope) is improperly configured.

Michael

[shownow]

thanks for your informative reply.still want more help :P
I use sipphone service,so STUN I use is stun01.sipphone.com:3478,I have 3 sip clients in my LAN,xten lite,handytone486,spa1000.Only spa1000 has this problem,the other two work very well,i.e.rings immediately after dailing.so I suppose sipphone's STUN has no problem,neverthless I changed STUN to FWD's.surprisingly spa1000 rings almost immediatley(still 1-2 sec.late than the others)
what cause this delay puzzles me very much.I don't have a DNS server except my router's.If this is the problem,why doesn't xten lite have it?xten doesn't have a DNS either.
can you please recommend some souce for STUN

[mberlant]

Based upon your last comment, it seems that your sluggish STUN is caused by slow DNS resolution. You are seeing quicker connections using FWD's STUN server because your DNS can find it faster than it could find SIPphone's. There are two ways to deal with this problem.

The better way is to log into your router and go to either the Status or WAN screen. Find the list of two or three DNS servers shown there and write them down. Then, go to the System page of your Sipura configuration service and put the first two addresses in the Sipura. Now, when your Sipura needs an address it will go directly to your ISP's DNS server instead of going to your router, which will search its tables in vain and then relay the request on to the ISP's server.

If this doesn't work for some reason, you can replace the FQDN, stun.fwdnet.net:3478 with its IP address, 69.90.168.14:3478. Doing this will bypass DNS lookup entirely for this STUN server. The downside is that if FWD ever moves this server you won't find it because you're still looking for it at its old address.

Good luck.

Michael