Hello,
See my replies below, inline with your text.
Envoyé de mon iPad
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:
|