Hi Al,
Hope you don't mind the nickname.
Please don't delete the mail, it has useful info (like configuration).
Anyway from a previous mail i see that your ppg is listening on port 8080.
Therefore to capture your PAP document use (if I remember correctly):
tcpdump -nxX host <applicationIP> port 8080
If you are not seeing anything it means you are not sending anything. To see
anything your application must reside on a different machine. You probably
cannot capture traffic between wapbox and bearerbox, because they are on the
same server. Therefore nothing on ports 13002, 13001, etc.
BR,
Nikos
----- Original Message -----
From: "Alvaro Cornejo" <cornejo.alv...@gmail.com>
To: "Nikos Balkanas" <nbalka...@gmail.com>; "users" <users@kannel.org>
Sent: Friday, April 03, 2009 6:40 PM
Subject: Re: Wapbox dies when receiving wappush
Hi Nikos
I tried again with the bearer info below but still not working.
I updated to latest cvs and still nothing
Something I see is that wap info -compared to smsbox info) seems
incomplete. There is no info about queue. Is that correct?:
Box connections:
wapbox, IP 10.10.5.2 (on-line 0d 0h 0m 48s)
smsbox:(none), IP 10.10.5.2 (0 queued), (on-line 0d 0h 0m 48s)
Also, I'm trying to capture info from network with tcpdump but get nothing:
[r...@srvcom1 feat]# netstat -an |grep 8080
tcp 0 0 0.0.0.0:8080 0.0.0.0:*
LISTEN
[r...@srvcom1 feat]# netstat -an |grep 13002
tcp 0 0 0.0.0.0:13002 0.0.0.0:*
LISTEN
tcp 0 0 10.10.5.2:13002 10.10.5.2:48950
ESTABLISHED
tcp 0 0 10.10.5.2:48950 10.10.5.2:13002
ESTABLISHED
[r...@srvcom1 sbin]# tcpdump -vv port \( 13002 or 49102 \)
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
[r...@srvcom1 sbin]# tcpdump -vv port 13002
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
however I can capture packets to 13000 but not ports 13001
[r...@srvcom1 sbin]# tcpdump -vv port 13000
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
09:20:05.883484 IP (tos 0x0, ttl 56, id 28127, offset 0, flags [DF],
proto: TCP (6), length: 40)
dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 >
srvcom1.smsglobal.com.mx.13000: ., cksum 0x2e73 (correct),
3676648555:3676648555(0) ack 2820572204 win 15008
09:20:05.889837 IP (tos 0x0, ttl 56, id 28128, offset 0, flags [DF],
proto: TCP (6), length: 40)
dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 >
srvcom1.smsglobal.com.mx.13000: ., cksum 0x23fb (correct), 0:0(0) ack
537 win 17152
09:20:05.896755 IP (tos 0x0, ttl 56, id 28129, offset 0, flags [DF],
proto: TCP (6), length: 40)
dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 >
srvcom1.smsglobal.com.mx.13000: F, cksum 0x19e3 (correct), 0:0(0) ack
976 win 19296
[r...@srvcom1 sbin]# tcpdump -vv port 13001
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
neither 8080
[r...@srvcom1 sbin]# tcpdump -vvvv port 8080
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
[r...@srvcom1 sbin]# tcpdump port 13002
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
What is even more extrange is that after wap dies, port 13002 still in
listenong mode..
[r...@srvcom1 feat]# netstat -an |grep 13002
tcp 0 0 0.0.0.0:13002 0.0.0.0:*
LISTEN
[r...@srvcom1 feat]#
Any ideas?
Thanks for your help & time
Alvaro
|-----------------------------------------------------------------------------------------------------------------|
Envνe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perϊ, Mιxico y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com
2009/4/3 Nikos Balkanas <nbalka...@gmail.com>:
The only curious thing that I observed is "bearer missing". Try to supply
that as well:
<quality-of-service priority="high"
delivery-method="unconfirmed"
network-required="true"
network="gsm"
bearer-required="true"
bearer="SMS"/>
If that fails, then you need a tcpdump, or snoop, to capture the packet
sent
by your application.
BR,
Nikos
