Re: [1'b68'1 astrad V8] Tester Notify sur astrad (200 clients) : Statistique

Salut,

Ci-dessous les expires des 32 clients en question :
L’expires est supérieur 3 minutes ce qui suffisant pour ne pas avoir des appels entrants mais c’est difficile à remarquer (c-a-d pas des email dans support).

Expire Time

mysql> select username,contact,expires,last_modified,TIMEDIFF(expires,last_modified) as diff from location where username in ('41215500068','41215500119','41215500443','41215501630','41215501668','41215501782','41215502447','41215505983','41215506213','41215507553','41215509534','41215509627','41215509647','41225501060','41225502374','41225503273','41225503613','41225503672','41225503674','41225503885','41225503984','41225503997','41225503997','41245042354','41245042539','41265042169','41265042432','41315042556','41315042932','41325042441','41325042745') order by diff;
+-------------+--------------------------------------+---------------------+---------------------+----------+
| username    | contact                              | expires             | last_modified       | diff     |
+-------------+--------------------------------------+---------------------+---------------------+----------+
| 41265042XXX | sip:41265042XXX@82.146.207.238:5060  | 2011-06-10 15:50:31 | 2011-06-10 15:45:33 | 00:04:58 |
| 41215507XXX | sip:41215507XXX@77.56.107.162:5060   | 2011-06-10 15:52:34 | 2011-06-10 15:47:35 | 00:04:59 |
| 41245042XXX | sip:41245042XXX@85.3.212.253:54927   | 2011-06-10 15:53:08 | 2011-06-10 15:48:09 | 00:04:59 |
| 41215501XXX | sip:41215501XXX@92.104.164.33:54348  | 2011-06-10 15:49:20 | 2011-06-10 15:42:40 | 00:06:40 |
| 41225501XXX | sip:41225501XXX@80.11.130.233:5060   | 2011-06-10 15:58:30 | 2011-06-10 15:48:32 | 00:09:58 |
| 41225503XXX | sip:41225503XXX@178.198.239.83:54827 | 2011-06-10 15:55:50 | 2011-06-10 15:45:52 | 00:09:58 |
| 41225503XXX | sip:41225503XXX@188.60.119.63:59610  | 2011-06-10 16:17:01 | 2011-06-10 15:17:03 | 00:59:58 |
| 41215505XXX | sip:41215505XXX@85.5.245.109:63754   | 2011-06-10 16:21:42 | 2011-06-10 15:21:44 | 00:59:58 |
| 41225503XXX | sip:41225503XXX@89.217.13.166:5060   | 2011-06-10 16:35:00 | 2011-06-10 15:35:01 | 00:59:59 |
| 41225502XXX | sip:41225502XXX@178.199.98.50:49666  | 2011-06-10 16:41:44 | 2011-06-10 15:41:44 | 01:00:00 |
+-------------+--------------------------------------+---------------------+---------------------+----------+
32 rows in set (0.01 sec)

Linksys Nat Keep Alive Enable
Que des Linksys dont l’option Keep-Alive est désactivée par défaut contrairement à Siemens

Ngrep du Notify envoyé depuis mon Linksys (Nat Keep Alive Enable=yes)

U 85.1.224.90:50462 -> 94.23.225.212:5060
NOTIFY sip:astrad.switzernet.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.121:5060;branch=z9hG4bK-14950136.
From: "41215500327" <sip:41215500327@astrad.switzernet.com>;tag=15b54ee8d21f37bo0.
To: <sip:astrad.switzernet.com>.
Call-ID: 2edde58c-6b0fad27@192.168.1.121.
CSeq: 3 NOTIFY.
Max-Forwards: 70.
Event: keep-alive.
User-Agent: Linksys/SPA921-5.1.8.
Content-Length: 0.
.

Ngrep sur astrad6 afin de chercher les User-Agents

astrad6:~# ngrep -pql -W byline "41215500XXX|41215500YYY|..." dst host 91.121.142.9 and port 5060 | egrep '^(User-Agent|Contact)'

Contact: 41225503XXX <sip:41225503XXX@192.168.1.37:5060>;expires=600.
User-Agent: Linksys/SPA1001-3.1.19(SE).
Contact: 41225503XXX <sip:41225503XXX@192.168.1.37:5060>;expires=600.
User-Agent: Linksys/SPA1001-3.1.19(SE).
Contact: 41225503XXX <sip:41225503XXX@192.168.1.37:5060>;expires=600.
User-Agent: Linksys/PAP2T-5.1.6(LS).
Contact: 41225503XXX <sip:41225503XXX@192.168.1.37:5060>;expires=600.
User-Agent: Linksys/PAP2T-5.1.6(LS).
User-Agent: TRACER 4.13.
Contact: 41225503XXX <sip:41225503XXX@192.168.1.37:5060>;expires=600.
User-Agent: TRACER 4.13.
...

On 2011-06-10 13:04, Emin Gabrielyan wrote:

Hello,

See my replies below, inline with your text.

Envoyé de mon iPad

Le Jun 10, 2011 à 11:49, Oussama Hammami <oussama.hammami@switzernet.com> a écrit :

Bonjour

J'ai voulu tester le pire scénario possible. Ce qui prouve que la consommation CPU augmentera de 5% au pire des cas.

Ok, but here you are using the "asterisk -r" too frequently. We are interested to measure the CPU cost of the "notify" procedure. I prefer to send the notifies every 5 seconds with a minimum number of asterisk commands. This will measure the real cost of notify, instead of the bash et al.

Statistique :
Sur 202 clients enregistré (dans location3), on a :

51

200 OK

81

489 Bad Event

1

501 Not Implemented

30

405 Method Not Allowed

2

603 Decline

37

No Response

Total

165/202

Finalement on voit très bien que on a 37 clients sur 202 qui ont des problèmes NAT.

If you are right, meaning that the 32 clients did not send you replies because of NAT and not because their phones do not understand, then an hour after activating the frequent notifies, you will see this number drop to near zero. What is interesting is also to see the expire time of registrations of these 32 clients.
Emin
J’ai testé envoi de Notify à mon telephone (41215500327):

Action

Date

Result

Register

10:16:03

200 OK

Call to my phone

10:19:29

no incoming call

Register

10:22:04

200 OK

Notify

every 30 seconds

200 OK

Call to my phone

10:25:32

180 Ringing

* * *

On 2011-06-10 04:26, Emin Gabrielyan wrote:
You send the notifies one by one. The CPU consumption will be less if you group numbers ten by ten and in order to use a single notify command per such a group.

Emin.

Envoyé de mon iPad

Le Jun 9, 2011 à 20:03, Done-by Oussama Hammami <oussama.hammami@switzernet.com> a écrit :

  
Done
http://switzernet.com/3/public/110609-astradv8-notify/

On 2011-06-09 20:03, Task-by Oussama Hammami wrote:
    
      
    