"Pour les quatre premières séries, le téléphone s’enregistre sur un serveur Astrad, puis sur un serveur PortaSIP pour les appels enregistrements suivants."
This phrase is not clear, read it.
In the table of packets, do not center the text in the last column of comments.
The last sections of results and conclusions are well done, but the beginning misses the introduction, abstract, or continuity. You must say, "we showed that ..." and tell shortly the most important conclusion in two words. Before bringing the tables you mus say "the table below shows ...".
Emin Gabrielyan
La documentation est ici :
http://switzernet.com/3/public/110623-portasip-vs-astradV7-incoming/
On 2011-06-23 14:14, Oussama Hammami wrote:
La fréquence de l’envoi des paquets vides est de 15s.
2011-06-23 14:08:47 U 91.121.101.126:5060 -> 62.202.88.127:51368
2011-06-23 14:08:47 ....
2011-06-23 14:09:02 U 91.121.101.126:5060 -> 62.202.88.127:51368
2011-06-23 14:09:02 ....
2011-06-23 14:09:17 U 91.121.101.126:5060 -> 62.202.88.127:51368
2011-06-23 14:09:17 ....
2011-06-23 14:09:32 U 91.121.101.126:5060 -> 62.202.88.127:51368
2011-06-23 14:09:32 ....
2011-06-23 14:09:47 U 91.121.101.126:5060 -> 62.202.88.127:51368
2011-06-23 14:09:47 ....
|
On 2011-06-23 13:21, Nicolas Bondier wrote:
Bonjour,
The email was addressed to me, I made the test with Oussama. And
it was
to late for redaction.
1) First tests, discovering of the empty packet
So, first the test with Astrad, as you know, router close the
port and
no incomming call are possible.
mysql> select name,ipaddr,port,FROM_UNIXTIME(regseconds) from sippeers2 where name=41215500327;
+-------------+---------------+-------+---------------------------+
| name | ipaddr | port | FROM_UNIXTIME(regseconds) |
+-------------+---------------+-------+---------------------------+
| 41215500327 | 62.202.88.127 | 49699 | 2011-06-22 19:59:39 |
+-------------+---------------+-------+---------------------------+
1 row in set (0.00 sec)
mysql> select name,ipaddr,port,FROM_UNIXTIME(regseconds) from sippeers2 where name=41215500327;
+-------------+---------------+-------+---------------------------+
| name | ipaddr | port | FROM_UNIXTIME(regseconds) |
+-------------+---------------+-------+---------------------------+
| 41215500327 | 62.202.88.127 | 51364 | 2011-06-22 20:50:11 |
+-------------+---------------+-------+---------------------------+
1 row in set (0.00 sec)
|
After that, we registered our phone on fr3.youroute.net
(91.121.101.126). Here are the results, PortaSip keep the NAT
port open
by sending empty packet. (Here we see the Hexadecimal data).
The phone was continiously reachable after 3 minutes even more.
# ngrep -x host 62.202.88.127 and port 51368
interface: sis0 (91.121.101.0/255.255.255.0)
filter: (ip or ip6) and ( host 62.202.88.127 and port 51368 )
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
U 91.121.101.126:5060 -> 62.202.88.127:51368
00 00 00 00 ....
#
|
2) First tests, discovering of the empty packet
Concerning the frequency :
I did the test again this morning and used the ngrep -T option
to see
the delta time between the precedent and the current packet.
They are sent every 15 seconds. (First delta time doesn't
matter, this
is the time between I launch the ngrep and first packet).
First I have to know on wich port I have to ngrep :
+-------------+----------------+---------------------+-------------------------------------+---------------------+
| username | domain | last_modified |
contact | expires |
+-------------+----------------+---------------------+-------------------------------------+---------------------+
| 41215500336 | 91.121.101.126 | 2011-06-23 10:40:49 | sip:41215500336@62.202.88.127:59954 | 2011-06-23 11:40:49 |
+-------------+----------------+---------------------+-------------------------------------+---------------------+
So the frequency is 4 packets/minutes.
# ngrep -xT host 62.202.88.127 and
port
59954
interface: sis0 (91.121.101.0/255.255.255.0)
filter: (ip or ip6) and ( host 62.202.88.127 and port
59954 )
#
U +8.828961 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U +15.010139
91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U +15.010191
91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U +15.010419
91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U +15.010895
91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U +15.010522
91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
|
3) Results of the empty packet
Now, I wait more than 3 minutes on portaSip for these tests,
register
expires is 1 hour. So no REGISTER during the tests.
They are two ngrep :
- "-t" for a timestamp in the form of YYYY/MM/DD HH:MM:SS.UUUUUU
everytime a packet is matched
- "less 64" to keep only the empty packet (they have a 8 bytes
lenght.)
FIGURE1
fr3# ngrep -xt host 62.202.88.127 and
port
59954 and less 64
interface: sis0 (91.121.101.0/255.255.255.0)
filter: (ip or ip6) and ( host 62.202.88.127 and port
59954 and less 64
)
#
U 2011/06/23 11:31:25.672320
91.121.101.126:5060
-> 62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:31:40.682476 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:31:55.692646 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:32:10.702807 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:32:25.712976 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:32:40.723157 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:32:55.781549 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:33:10.791462 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:33:25.801646 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:33:40.874484 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:33:55.884952 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:34:10.895114 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:34:25.905274 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:34:40.915442 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:34:55.925596 91.121.101.126:5060 ->
62.202.88.127:59954
00 00 00
00 ....
#
U 2011/06/23 11:35:10.935767
91.121.101.126:5060
-> 62.202.88.127:59954
00 00 00
00 ....
|
Here the second ngrep took in the same time. I just diplay
important
informations.
Explanations are below.
FIGURE2
fr3# ngrep -pqlt -W byline host
91.121.101.126 and port 59954 | grep -B1 -i 'SIP/2.0[
\.]'
POINT 1
U 2011/06/23 11:31:37.625159
91.121.101.126:5060 ->
62.202.88.127:59954
INVITE |
|