[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ring] SIP registration problem
From: |
Guillaume Roguez |
Subject: |
Re: [Ring] SIP registration problem |
Date: |
Sat, 26 Nov 2016 14:00:46 -0500 (EST) |
----- Le 26 Nov 16, à 10:36, vwf address@hidden a écrit :
> Hello,
>
> I have a SIP registration problem. iptel.org works fine, ostel.co does
> not register using similar information. ostel.co gives either a status
> "Host unreachable" or "Invalid". My ostel.co account is valid: Jitsi
> works just fine with ostel.co
>
> Ring version: 20161123.1.3120ba5~dfsg1-1 (on Debian Stable)
>
> Information used for ostel.co:
> hostname: ostel.co
> username: myname (without @ostel.co)
> password: ********** (tested)
> proxy: <empty>
> DTMF: RTP
> (advanced)
> local port: 7060 (5060 is already in use)
> published address: same as local parameters
> use stun: stun.ekiga.net
> SDP session negotiation: <default values>
> (security)
> <nothing, all default>
>
> What is going wrong? What can I do to test?
>
> Thank you
Hi,
It's a problem of used server:port configuration.
"ostel.co" (resolved here by 66.151.32.200) returns an ICMP packet "Destination
unreachable (port unreachable)"
if you try to send any UDP packets to the port 5060.
So I doubt that any programs can work with "ostel.co:5060" server.
You may have indicated another port to use in your Jitsi's configuration, but
it's not 5060.
Or maybe it's not "ostel.co" (or both).
Contact your SIP provider to obtain the correct server:port configuration to
use.
--
Guillaume Roguez | Senior Free Software Consultant
Ring Project Development Director - https://ring.cx
RingID: 007871859FFA8E8FFDE776A6BA8E8FA35ABD9A7B
PGP : 2A3A3627C9DCA7E733EE1034820371F4E07DE571