|
Posted by Vox Humana on December 28, 2005, 3:17 pm
If you were Registered and logged in, you could reply and use other advanced thread options
"Wolfgang S. Rupprecht"
>
> > I assume this is a Sipphone issue? I never have problems with my other
VOIP
> > provider.
>
> It might be, or it could be something at your end. Might you have two
> phones or ata's behind one NAT box? If so, things might be a bit
> crunchy. Incoming packets for port 5060 (sip) and/or 5004 (rtp) could
> be going to the wrong phone/ATA when an externally initiated
> connection was starting up.
>
> The only way to really tell what is going on is slap a tcpdump on the
> external line between the modem and nat-box and watch the
> transactions. From the SIP headers, it should be very obvious if your
> side is blowing off the incoming connections, or if the problem is
> further upstream.
>
> Having just gone through this with two of my voip/pstn gatewaying
> providers, I can say that problems like this do exist. In my case,
> the a lack of any SIP packet coming in around the time the remote end
> got a fast busy is pretty strong proof that something upstream is
> either overloaded or misconfigured.
Thanks for the reply. I have a single ATA behind my D-Link router. The ATA
has been assigned a static IP address and is in the DMZ. Line one is
configured for one provider and is assigned to port 5060. The second line
is configured for Sipphone and assigned to port 5061. I will take this up
with the people at Sipphone. If I can't resolve the problem, I will just
drop Sipphone. I would like to find a reliable provider with a pay-go plan
that doesn't charge for incoming calls. I use Teliax as my primary VOIP
provider and while their service is good, I hate the idea of paying for
incoming calls. I rarely make outgoing calls. They charge 2 cents for the
first 1- 60 seconds and 2 cents a minute thereafter for both incoming and
outgoing calls.
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map