9 Jun
2017
9 Jun
'17
10:39 a.m.
On Fri, 9 Jun 2017, Daniel-Constantin Mierla wrote:
On 09.06.17 08:58, Thufir Hawat wrote:
thufir@doge:~$
thufir@doge:~$ sudo ngrep -d any -qt -W byline port 5060
interface: any
filter: (ip or ip6) and ( port 5060 )
U 2017/06/09 00:33:13.016586 192.168.1.7:5060 -> 78.47.51.102:5060
REGISTER sip:openrcs.com SIP/2.0.
Call-ID: a73d7a44c5ca9d9ed23d347e38a560cd@0:0:0:0:0:0:0:0.
CSeq: 1 REGISTER.
From: "thufir" <sip:thufir@openrcs.com>;tag=e6261e66.
To: "thufir" <sip:thufir@openrcs.com>.
Via: SIP/2.0/UDP
192.168.1.7:5060;branch=z9hG4bK-393333-d483503bcdbe2ba54859c2878d3cddfd.
Max-Forwards: 70.
User-Agent: Jitsi2.8.5426Linux.
Expires: 600.
Contact: "thufir"
<sip:thufir@192.168.1.7:5060;transport=udp;registering_acc=openrcs_com>;expires=600.
Content-Length: 0.
.
U 2017/06/09 00:33:13.207083 78.47.51.102:5060 -> 192.168.1.7:5060
SIP/2.0 401 Unauthorized.
Call-ID: a73d7a44c5ca9d9ed23d347e38a560cd@0:0:0:0:0:0:0:0.
CSeq: 1 REGISTER.
From: "thufir" <sip:thufir@openrcs.com>;tag=e6261e66.
To: "thufir"
<sip:thufir@openrcs.com>;tag=897398a4e4993a34f7061d7cde36a9dd.747f.
Via: SIP/2.0/UDP
192.168.1.7:5060;branch=z9hG4bK-393333-d483503bcdbe2ba54859c2878d3cddfd;rport=49204;received=192.157.119.2.
WWW-Authenticate: Digest realm="openrcs.com",
nonce="WTpQZVk6TzlB3R+ar4G+iNBsiVv/CCYb".
Server: kamailio (5.1.0-dev3 (x86_64/linux)).
Content-Length: 0.
.
U 2017/06/09 00:33:13.214224 192.168.1.7:5060 -> 78.47.51.102:5060
REGISTER sip:openrcs.com SIP/2.0.
Call-ID: a73d7a44c5ca9d9ed23d347e38a560cd@0:0:0:0:0:0:0:0.
CSeq: 2 REGISTER.
From: "thufir" <sip:thufir@openrcs.com>;tag=e6261e66.
To: "thufir" <sip:thufir@openrcs.com>.
Max-Forwards: 70.
User-Agent: Jitsi2.8.5426Linux.
Expires: 600.
Contact: "thufir"
<sip:thufir@192.168.1.7:5060;transport=udp;registering_acc=openrcs_com>;expires=600.
Via: SIP/2.0/UDP
192.168.1.7:5060;branch=z9hG4bK-393333-895d23a7b018122554dfc31aa33b18e8.
Authorization: Digest
username="thufir",realm="openrcs.com",nonce="WTpQZVk6TzlB3R+ar4G+iNBsiVv/CCYb",uri="sip:openrcs.com",response="04179dd6d394ab270525e8b349a3b33d".
Content-Length: 0.
.
U 2017/06/09 00:33:13.410068 78.47.51.102:5060 -> 192.168.1.7:5060
SIP/2.0 401 Unauthorized.
Call-ID: a73d7a44c5ca9d9ed23d347e38a560cd@0:0:0:0:0:0:0:0.
CSeq: 2 REGISTER.
From: "thufir" <sip:thufir@openrcs.com>;tag=e6261e66.
To: "thufir"
<sip:thufir@openrcs.com>;tag=897398a4e4993a34f7061d7cde36a9dd.3d80.
Via: SIP/2.0/UDP
192.168.1.7:5060;branch=z9hG4bK-393333-895d23a7b018122554dfc31aa33b18e8;rport=49204;received=192.157.119.2.
WWW-Authenticate: Digest realm="openrcs.com",
nonce="WTpQZVk6TzlB3R+ar4G+iNBsiVv/CCYb".
Server: kamailio (5.1.0-dev3 (x86_64/linux)).
Content-Length: 0.
.
^Cthufir@doge:~$
thufir@doge:~$
The config is like so:
https://pasteboard.co/gnodqc0dg.png
I'm able to use ekiga from Android, but that's using STUN or something
behind the scenes with CSipSimple. Also, not only does anveo work on the
hardphone, but so does sip2sip.info insofar as I'm able to call and get
sound from Ekiga (on Android) to the IP phone.
The inference I draw, if not conclusion, is that the network is ok.
but, the 401 unauthorized looks like password problem. All I can say is
that copy/pasted from the generated password...
thanks,
Thufir
On Fri, 9 Jun 2017, Daniel-Constantin Mierla
wrote:
perfect. Please check this reasoning: *because* anveo works fine
from an IP phone *therefore* the SIP ALG on my home router isn't
mangling traffic on 5060. (Anveo uses SIP.)
Yes, I saw that openrcs has commendable security on the password.
I'll take a look with ngrep from Ubuntu.
I just downloaded latest Jitsi,
started it, and set the SIP account to
username(a)openrcs.com and put in there the password. It registered from
the first attempt, with the default settings (udp on port 5060). So vary
likely something is misconfigured in your jitsi or in the network, if it
doesn't work for you.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
On 09.06.17 07:18, Thufir Hawat wrote:
> On Thu, 8 Jun 2017, Daniel-Constantin Mierla wrote:
>> On 08.06.17 10:26, Thufir Hawat wrote:
..
Each SIP
account needs its own port number? Starting at 5060 and
going up. Why does kamailio listen on 5062? This means that the
*outbound* settings need to specify 5062, but inbound might be most
anything?
No, it is no need for own port for each sip account. Kamailio on
openrcs.com listens on 5062 as well as on the default 5060. The reason
for 5062 is that some corporate/isp companies block port 5060, or there
are some broken SIP ALGs on home routers mangling traffic for port 5060,
messing it.
So you can use default port 5060.
What operating system are you using for Jitsi? Can you sniff network
traffic on port 5060? If you are on linux, try:
ngrep -d any -qt -W byline port 5060
On windows you can use wireshark.
The output from the sniffer is good to see what happens on the network.
Also, be aware that openrcs.com has a different password for SIP account
than the one used for web interface. You have to go to the SIP account
page and see/generate it there. 