27 Jun
2007
27 Jun
'07
8:10 p.m.
Hi,
I have a working basic openser + asterisk setup. Twinkle works OK and
wengophone doesn't. It tries to connect and then after a while times out.
While debugging I noticed a lot of OPTIONS ping requests are going
unanswered by openser because it contains an user in the uri.
Registration seems to be working OK.
I've attached the ngrep output that shows this.
Has anyone got wengophone to work with openser?
--
Radu Spineanu
interface: eth0 (217.73.174.0/255.255.255.224)
filter: (ip or ip6) and ( port 5060 )
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
REGISTER sip:217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=123456789..Route: <sip:217.73.174.13;lr>..From: nobo
dy <sip:nobody@217.73.174.13>;tag=123456789..To:
<sip:nobody@217.73.174.13>..Call-ID: 000001@ping..Contact:
<sip:nobody@82.79.243.82>..C
Seq: 2 REGISTER..Content-Length: 0....
#
U 217.73.174.13:5060 -> 82.79.243.82:5060
SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP
82.79.243.82:5060;rport=5060;branch=123456789..From: nobody
<sip:nobody@217.73.174.13>;tag=12
3456789..To:
<sip:nobody@217.73.174.13>;tag=5e02e7658def22f683939a852e493344.3f4e..Call-ID:
000001@ping..CSeq: 2 REGISTER..WWW-Authentic
ate: Digest realm="217.73.174.13",
nonce="46823bd8e5f68588801e0655bbc907e2425ee03f"..Server: OpenSER (1.2.1-notls
(x86_64/linux))..Conte
nt-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
REGISTER sip:217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1094221745..Route: <sip:217.73.174.13:5060;lr
..From:
<sip:1001@217.73.174.13>;tag=1065314925..To:
<sip:1001@217.73.174.13>..Call-ID: 807187534@82.79.243.82..CSeq: 1 REGISTER..Conta
ct: <sip:1001@82.79.243.82:5060>..Max-Forwards: 70..User-Agent:
wengo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 2940..Content-Length:
0....
#
U 217.73.174.13:5060 -> 82.79.243.82:5060
SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP
82.79.243.82:5060;rport=5060;branch=z9hG4bK1094221745..From:
<sip:1001@217.73.174.13>;tag=106
5314925..To:
<sip:1001@217.73.174.13>;tag=5e02e7658def22f683939a852e493344.4bcc..Call-ID:
807187534@82.79.243.82..CSeq: 1 REGISTER..WWW-
Authenticate: Digest realm="217.73.174.13",
nonce="46823bd9c467d1377ec65d343c7dfc7bd40513c3"..Server: OpenSER (1.2.1-notls
(x86_64/linux
))..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
REGISTER sip:217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK2031845783;xxx-nat-type=sym..Route: <sip:217.
73.174.13:5060;lr>..From: <sip:1001@217.73.174.13>;tag=1065314925..To:
<sip:1001@217.73.174.13>..Call-ID: 807187534@82.79.243.82..CSeq:
2 REGISTER..Contact: <sip:1001@82.79.243.82:5060>..Authorization: Digest
username="1001", realm="217.73.174.13", nonce="46823bd9c467d137
7ec65d343c7dfc7bd40513c3", uri="sip:217.73.174.13",
response="2e3d2c8bb188495863d4306f5cd5ba5c", algorithm=MD5..Max-Forwards:
70..User-A
gent: wengo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 2940..Content-Length: 0....
#
U 217.73.174.13:5060 -> 82.79.243.82:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP
82.79.243.82:5060;rport=5060;branch=z9hG4bK2031845783;xxx-nat-type=sym..From:
<sip:1001@217.73.174.13>;
tag=1065314925..To:
<sip:1001@217.73.174.13>;tag=5e02e7658def22f683939a852e493344.142c..Call-ID:
807187534@82.79.243.82..CSeq: 2 REGISTE
R..Contact: <sip:1001@82.79.243.82:5060>;expires=2940..Server: OpenSER
(1.2.1-notls (x86_64/linux))..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
#
U 82.79.243.82:5060 -> 217.73.174.13:5060
OPTIONS sip:ping@217.73.174.13 SIP/2.0..Via: SIP/2.0/UDP
82.79.243.82:5060;rport;branch=z9hG4bK1028071012..From: Radu <sip:1001@217.73.1
74.13>;tag=675779892..To: <sip:ping@217.73.174.13>..Call-ID:
1333741103@82.79.243.82..CSeq: 20 OPTIONS..Max-Forwards: 70..User-Agent: we
ngo/v1/wengophoneng/wengo/rev0/trunk/..Expires: 120..Accept:
application/sdp..Content-Length: 0....
exit
14 received, 0 dropped
28 Jun
28 Jun
11 a.m.
Hi!
1. please use "ngrep -W byline ......"
2. wengophone registers successfully to openser
3. it sends OPTIONS sip:ping@......
Although the user "ping" is unknown to openser it should at least reply
with some error message - e.g. 404. Thus I guess you have a bug in your
config.
regards
klaus
Radu Spineanu wrote:
Hi,
I have a working basic openser + asterisk setup. Twinkle works OK and
wengophone doesn't. It tries to connect and then after a while times out.
While debugging I noticed a lot of OPTIONS ping requests are going
unanswered by openser because it contains an user in the uri.
Registration seems to be working OK.
I've attached the ngrep output that shows this.
Has anyone got wengophone to work with openser?
--
Radu Spineanu
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
12:01 p.m.
We have a few users using Wengophone on our OpenSER 1.2.1 server. Works just
fine - or as expected I believe. However those pings are annoying... It
keeps sending OPTIONS to sip:ping@ourdomain.tld every 20 seconds or so...
// sip:gojensen@uninett.no | h323: 004710012
pstn: +47 73 55 79 23 | fax: +47 73 55 79 01
-----Original Message-----
From: users-bounces(a)openser.org
[mailto:users-bounces@openser.org] On Behalf Of Klaus Darilion
Sent: Thursday, June 28, 2007 10:00 AM
To: Radu Spineanu
Cc: users(a)openser.org
Subject: Re: [OpenSER-Users] wengophone and openser
Hi!
1. please use "ngrep -W byline ......"
2. wengophone registers successfully to openser 3. it sends
OPTIONS sip:ping@......
Although the user "ping" is unknown to openser it should at
least reply with some error message - e.g. 404. Thus I guess
you have a bug in your config.
regards
klaus
Radu Spineanu wrote:
Hi,
I have a working basic openser + asterisk setup. Twinkle
works OK and
wengophone doesn't. It tries to connect and
then after a
while times out.
While debugging I noticed a lot of OPTIONS ping requests are going
unanswered by openser because it contains an user in the uri.
Registration seems to be working OK.
I've attached the ngrep output that shows this.
Has anyone got wengophone to work with openser?
--
Radu Spineanu
----------------------------------------------------------------------
--
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6357
days inactive
6358
days old
2 comments
3 participants
participants (3)
-
Geir O. Jensen -
Klaus Darilion -
Radu Spineanu